Avoid bias in use of force reports by sticking to observable facts and actions

This explains why substituting conclusions for facts is a common slip when documenting use of force, the risks of bias, and how to stick to observable actions. Learn how precise, factual reporting supports transparency, accountability, and reliable reviews in security operations.

Understanding Use-of-Force Documentation: What to Record, What to Avoid

When a use-of-force incident occurs, the written record isn’t just a formality. It’s a foundational document that shapes perceptions, informs review processes, and can influence legal outcomes. In the world of protective security, the goal of any incident report is simple: tell an accurate, objective story of what happened, based on observable facts, not on personal conclusions or assumptions. A surprisingly common misstep is substituting conclusions for factual information. Let’s unpack why this happens, why it’s a big deal, and how to keep the writing honest, precise, and useful.

The core problem: conclusions masquerading as facts

Think about how most of us communicate in everyday life. We naturally interpret actions through our own lenses. In a tense incident, that reflex can slip into a report and quietly corrupt the narrative. When writers include conclusions—interpretations like “the subject was obviously aggressive” or “the officer overreacted”—they’re injecting value judgments that aren’t directly observable. The document then becomes a blend of what happened and what the writer thinks about why it happened. That’s risky.

In a clean report, observations are separated from interpretations. Observations are what you saw and heard: the exact words spoken, the physical actions taken, the timing of those actions, the positions of people involved, the presence of any weapons, the use of protective equipment, the environment at the scene, and the sequence of events as they unfolded. Interpretations—things like “intent,” “threat level,” or “unnecessary force”—belong in separate sections or in a professional reflection, not in the factual body of the record. When conclusions leak into the facts, two problems creep in: bias and ambiguity.

Bias can sneak in quickly. If a writer has a personal opinion about a person or a situation, it may color the language or emphasize certain details over others. Ambiguity follows. When a report says, “the subject appeared hostile,” that’s a subjective read. It leaves readers wondering, “Hostile how? In what moment? Based on what observable cue?” A factual account would describe observable cues: raised hands, shouts, steps backward, a lunge, the exact words used, the time stamps, the distances involved. The difference isn’t trivial; it determines how the incident is understood during reviews, investigations, or court proceedings.

What a good report looks like: facts first, context second

A robust use-of-force report follows a clear, logical structure that prioritizes verifiable information. Here’s a practical blueprint you can adapt to most agency formats:

• Opening details: Date, time, location, the parties involved (without names if policy requires anonymization), and the role of the observer (officer, supervisor, civilian witness).

• Incident chronology: A precise timeline of events, from initial contact to resolution, with time stamps or intervals. Note any pauses, delays, or decoupled moments—things that matter for understanding causation or escalation.

• Observable actions: What each person did and said that is directly perceptible. Use precise verbs: “took a step backward,” “raised the object,” “shouted,” “made a verbal command,” “deployed a restraint,” “held the door open,” etc.

• Use-of-force specifics: The type of force used, the order in which it was deployed, duration if relevant, and any intermediate steps (warnings given, de-escalation attempts, attempts to disengage).

• Equipment and environment: Body-worn camera status, taser or other devices involved, number of officers present, lighting, weather, terrain, boundaries, and any obstacles.

• Observations by others: Notes from witnesses, supervisors, or partners that corroborate or challenge the account, with a focus on firsthand observations rather than conclusions.

• Post-incident actions: Medical attention, transport, safeguarding evidence, chain-of-custody details, and the next steps in the investigation or administrative process.

• Documentation integrity: A clear statement that the report reflects what was observed or heard, with disclaimers about any speculation and a note on limitations (e.g., “does not include recovered video due to preservation constraints”).

Language that serves clarity, not persuasion

Choosing words carefully matters. Favor concrete, objective language over evaluative terms. For example, instead of writing “the subject attempted to grab the officer,” you could log “the subject reached toward the officer’s torso.” Instead of “the officer forcefully restrained,” say “the officer applied a leg lock and handcuffs, maintaining control until compliance was achieved.” If you’re unsure whether a detail is material, ask: Does this detail influence understanding of what happened or the sequence of actions? If not, it may be extraneous and can be omitted to keep the report focused.

The role of time and sequence

Time stamps are your best friends here. If your system records events in seconds, use them. A precise clock provides a shared frame of reference for readers who may be reconstructing the scene later. It helps to annotate moments that led to escalation or de-escalation—like the shift from verbal commands to physical contact, or the moment warnings were given, if applicable. When in doubt, write “approximately” or “around” only when you’re certain the approximation doesn’t distort the sequence and you can annotate the source of the estimate.

Balancing detail with readability

A good report is readable without sacrificing accuracy. Short sentences, active voice, and straightforward structure help. But don’t oversimplify. Complex incidents benefit from concise paragraphs that trace the sequence logically. Use bullet points for lists of actions or equipment when it enhances clarity, but avoid turning the document into a shopping list of adjectives. The aim is truth, not drama.

What to avoid, and why it matters

• Substituting conclusions for facts (the big one): You already know why this is problematic, but the ripple effects are real. It undermines credibility and can complicate later reviews or audits.

• Extraneous details: It’s tempting to add color or speculate about motives, background, or emotions. Resist. If a detail doesn’t illuminate what happened, it’s probably noise that clutters the record.

• Negative framing of participants: Focus on observable actions rather than labeling people. Phrases like “the noncompliant suspect” can carry pejorative weight and bias. Opt for objective descriptions: “the individual did not comply with verbal commands.”

• Ambiguity in timing: Vague phrases like “shortly after” leave room for misinterpretation. If you can’t pin down timing, use precise descriptors such as “within 15 seconds” or “after a 12-second interval.”

• Assumptions about intent: Statements about why someone did something belong in analytical conclusions, not in the description of what was observed. Save the interpretive commentary for separate sections that discuss policy, training implications, or risk assessment.

A culture of documentation: practices that support honesty

Good documentation isn’t a one-off task; it’s a practice embedded in daily routines. Here are some habits that help keep reports trustworthy:

• Immediate notes, later polish: Jot down observations as soon as possible, then review for clarity, accuracy, and consistency. The human brain loves to fill gaps; captured details at the moment reduce memory distortions.

• Use checklists: A simple incident-report checklist can remind you to cover essential elements—time, location, participants, actions, scope of force, de-escalation attempts, and evidence chain-of-custody.

• Separate facts from interpretation: When you find yourself leaning toward a conclusion, pause and reframe the sentence to reflect observable facts. If interpretation is necessary, label it clearly and place it in an interpretive section.

• Corroboration: Where possible, corroborate statements with other evidence—video footage, audio, and third-party accounts. If discrepancies exist, document them and note possible reasons.

• Chain of custody: For physical evidence or devices (weapons, restraints, PPE, cameras), maintain an unbroken log that records where items were stored, who accessed them, and when they were transferred.

• Standards and templates: Align with organizational style guides or national protective security guidelines. Consistency makes cross-agency reviews smoother and reduces confusion.

• Training and practice: Regular training on writing practices helps staff internalize the difference between observable facts and personal analysis. Use real-world scenarios to illustrate pitfalls and best practices.

Technology as an ally, not a crutch

Many agencies rely on body-worn cameras, dashboard cameras, and digital reporting tools. These technologies can be incredibly helpful in constructing an accurate narrative, but they’re not a substitute for careful writing. Video and audio records provide raw material—the observations—but the writer still must translate those observations into a precise, narrative, fact-based report. Think of tech as an ally that supplies corroborating detail; the human touch is still essential for organizing, interpreting, and presenting that detail responsibly.

From observation to accountability: the ethical thread

Documentation carries a heavy ethical weight. It’s not just about fulfilling a policy requirement; it’s about accountability, transparency, and trust. Clear, factual reporting supports fair review, protects rights, and helps prevent misinterpretation. When people read a report, they’re forming perceptions about the actions taken, the proportionality of force used, and the overall handling of the incident. Those judgments hinge on how well the story is told. And that story should be grounded in fact, not inference.

Real-world examples: learning through practice

Consider two brief vignettes to illustrate the difference between a factual account and a conclusion-laden one.

• Fact-based log: “At 14:23:05, I approached the individual, who was standing in the doorway with hands at their sides. The individual stated, ‘I don’t want trouble,’ and took a step back. I gave three verbal commands—‘Back up, hands up, show me your hands.’ The individual did not comply, moving toward the doorway and placing a hand on the doorframe. At 14:24:11, I deployed a wrist-lock restraint while maintaining four-point contact. The individual ceased movement at 14:24:27, and I escorted them to a secure position for handcuffing. Body cam remained active throughout.”

• Conclusion-laden log: “The subject was clearly aggressive and attempted to overwhelm the officer, so force was necessary to prevent harm.”

The first version reads like a chain of observable facts, with dates, times, actions, and outcomes. The second one injects interpretation and emotion, which muddies the record and invites challenge during reviews. The difference matters, especially when the record might be scrutinized years later, or when it’s used to inform policy decisions, training needs, or legal considerations.

A closing thought: what you’re aiming for

Documenting use-of-force incidents well is less about catching someone in the wrong and more about preserving an objective, usable history of events. The best reports stand up under scrutiny because they’re built on observable facts, clearly separated from interpretation, and crafted with an eye toward future reviews, accountability, and learning. It’s not about drama or rhetoric; it’s about precision, honesty, and a responsibility to those involved.

So next time you sit down to put pen to page—or more likely, finger to keyboard—remember the backbone: facts first, interpretations second, and a steady commitment to clarity. When you foreground observable actions, precise timings, and verifiable details, you create a record that helps protect rights, supports fairness, and—most importantly—serves the truth. And that truth? It’s the anchor that keeps protective security work credible, professional, and human.