Use-of-Force and Special-Circumstance Documentation — Law Enforcement / Security

Objective. Students will complete a use-of-force report that documents officer actions, subject behavior, and perceived threat level in objective, chronological, legally sufficient language.

Why Use-of-Force Reports Matter

Every time a security officer or law enforcement officer applies force — from a firm grip to a takedown — a written record must follow. Courts, supervisors, prosecutors, defense attorneys, and civil litigants will read that report. The report does not just describe what happened; it becomes the official account of what happened. An incomplete or poorly worded report can expose the officer, the agency, and the employer to civil liability, disciplinary action, or criminal review, regardless of whether the force itself was justified.

The legal standard most often applied to officer use of force is objective reasonableness: would a reasonable officer facing the same facts, at that moment, have responded the same way? Your report must allow a reader — who was not present — to reconstruct that moment accurately and reach the same conclusion. Every word choice either supports or undermines that goal.

Required Elements of a Use-of-Force Report

A legally sufficient use-of-force report must contain all of the following elements:

Date, time, and location of the incident
Identities of all involved parties (officers, subjects, witnesses)
Subject behavior described in observable, specific terms before officer response is described
Threat cues the officer perceived — verbal statements, physical movements, weapons present or implied
Each force technique or tool used, in chronological order, with the level of force identified
Subject response to each application of force
When force stopped and why
Injuries observed or reported, and medical attention provided or offered
Supervisor notification and time

Omitting any element creates a gap that opposing counsel will exploit. Courts have found reports legally insufficient when officers described what they did without first establishing why the threat level justified that response.

Subject Behavior Before Officer Response

Always document what the subject did before you document what you did. This sequencing mirrors the legal analysis: force is a response to a threat, not a starting point. Write the threat first, then the response.

Weak (reversed order): "I applied a wrist-lock because the subject was combative."

Strong (correct order): "The subject pulled his right arm back, clenched his fist, and moved toward Officer Davis. I applied a standard wrist-lock to the subject's right wrist."

The second version shows the reader the threat cue before the technique. This structure protects the report legally.

Objective Language vs. Conclusions

A report must record observable facts, not the officer's interpretations stated as facts. Conclusions belong to supervisors, investigators, and courts — not to the narrative section of your report.

| Avoid (conclusion) | Use instead (observation) |

|---|---|

| "The subject was on drugs." | "The subject's pupils were dilated, speech was slurred, and he did not respond to verbal commands." |

| "He intended to attack me." | "The subject raised his right hand above his shoulder and moved toward me at a rapid pace." |

| "She was out of control." | "The subject struck the wall repeatedly with an open hand and screamed." |

Describe what you saw, heard, and felt. Let those facts speak for themselves.

Chronological Order

Begin at the moment you were dispatched or first encountered the situation, and move forward in time without jumping around. Use specific clock times where possible. Readers should be able to follow the incident as it unfolded, step by step. Avoid phrases like "at some point" or "eventually." If you do not know an exact time, write "approximately" followed by your best estimate.

Active Voice and Complete Sentences

Active voice keeps accountability clear. "I directed the subject to show his hands" is clearer and more legally defensible than "The subject was directed to show his hands." Passive voice obscures who took the action — a serious problem when personal liability is at stake.

Write complete sentences. Fragments, abbreviations, and bullet points in the narrative section look informal and suggest the report was rushed. Courts expect professional, complete prose.

Language Pitfalls That Weaken Reports

Vague descriptors: "tall," "large," "aggressive" without supporting detail
Emotional language: "enraged," "terrifying" — these are conclusions about internal states
Jargon without explanation: spell out any technique or term a layperson might not know
Speculation: "I believe he was going for a weapon" — write instead what you observed that led to that perception
Inconsistency: if your verbal statement to your supervisor differs from the report, credibility is damaged

Safety Considerations in Documentation

Reporting is not only a legal obligation — it is a safety tool. Accurate use-of-force records help agencies identify patterns, retrain officers when needed, and detect equipment failures. If a subject was injured during a use-of-force encounter, document that medical attention was offered and provided. Failure to document injury assessment can constitute a safety and liability failure independent of the force itself. Always follow agency protocol on supervisor notification immediately after any use of force; do not delay report writing until the next shift if policy requires immediate documentation.

Key terms9

Objective reasonablenessThe legal standard used to evaluate officer use of force: whether a reasonable officer facing the same circumstances at that moment would have responded in the same way.

Use-of-force reportA written, formal account that documents the events, subject behavior, threat level, force techniques used, subject response, and outcome of any incident in which an officer applied force.

Chronological orderPresenting events in the sequence in which they occurred, from first contact forward in time, so readers can follow the incident as it unfolded.

Threat cueA specific, observable behavior or condition — a movement, verbal statement, or weapon — that caused the officer to perceive a threat justifying a response.

Active voiceA sentence construction in which the subject performs the action (e.g., "I applied the restraint") rather than receiving it, keeping individual accountability clear in the narrative.

Force levelThe category or type of force applied in a given moment, such as verbal commands, physical control, or intermediate weapons, documented in proportion to the threat presented.

Objective languageWords that describe observable, verifiable facts — what was seen, heard, or physically felt — as opposed to conclusions, interpretations, or emotional characterizations.

LiabilityLegal responsibility for harm or damages; poor or incomplete use-of-force documentation can expose officers and their employers to civil or criminal liability.

OmissionA required element that is missing from a report; omissions create evidentiary gaps that can undermine an officer's account in court or administrative review.

In class: Lecture on the legal and agency requirements for use-of-force reporting: why every application of force must be documented, what elements courts and supervisors look for, and how omissions or subjective language can expose the officer and employer to liability; students outline key requirements. · Case-study analysis: students read two sanitized, real-world use-of-force reports (one that held up legally, one that was challenged) and complete a comparison worksheet identifying specific language choices that strengthened or weakened each report. · Scenario writing exercise: students watch a 3-minute instructor-narrated use-of-force simulation video, then independently write a full use-of-force report narrative from the officer's perspective using only what was depicted; reports are peer-reviewed against a provided checklist before instructor review.
Materials: Use-of-force report forms (training versions), sanitized case-study reports, comparison worksheet, simulation video, use-of-force report checklist, POST Basic Course use-of-force documentation reference.
Check: Scored narrative report: instructor evaluates against an 8-criterion rubric (chronological order, subject behavior described before officer response, force level documented, no conclusions stated as facts, active voice, complete sentences, no missing elements, objective language); pass mark 6/8 criteria met.

Practice check8

Answer each question, then check it. Nothing is recorded; this is your own practice.