Use of Force Reporting Guide for Security Teams

A use-of-force incident does not end when the subject is under control, separated from others, or transferred to law enforcement. What you write afterward can determine whether your actions are understood as reasonable, necessary, and within policy. This use of force reporting guide is built for security professionals who need to document decisions with the same discipline they bring to the incident itself.

A clear report protects the public, your employer, your credentials, and your career. A vague, emotional, or incomplete report can create doubts even when your actions were appropriate. The goal is not to write the longest report. The goal is to create an accurate record that explains what happened, why you acted, what force was used, and what happened next.

Why Force Reporting Is a Professional Skill

Security personnel are often judged after an incident by people who were not there: supervisors, clients, investigators, attorneys, regulators, and sometimes a jury. They will rely heavily on reports, video, witness accounts, and medical records. Your report provides the operational context that footage alone may not show, including verbal warnings, changing behavior, distance, access to weapons, the presence of bystanders, and the time available to make decisions.

A professional report also shows that force was not your first option. It documents the steps taken to gain voluntary compliance, such as observation, communication, direction, distance, calling for assistance, and de-escalation. This matters because reasonable force is generally evaluated in context, not by looking only at the final physical contact.

Your agency policy, state law, licensing requirements, contract rules, and site procedures all affect what must be reported. Do not assume that a report format used at one employer will meet another employer’s requirements. Know the reporting chain before an incident occurs.

Use of Force Reporting Guide: Write Facts, Not Conclusions

The most reliable reports are factual, chronological, and specific. They distinguish what you personally saw and heard from what someone else told you. They do not try to diagnose a person’s motives, mental state, or medical condition unless you are qualified and required to do so.

Instead of writing, “The subject was aggressive,” describe the conduct: “The subject clenched both fists, stepped toward me from approximately three feet away, and stated, ‘I will hurt you.’” The second version allows the reader to understand why you perceived a threat without asking them to accept a broad label.

Avoid loaded language, insults, exaggeration, and unsupported conclusions. Terms such as “combative,” “resisting,” or “noncompliant” may be appropriate when they are defined by policy, but they should be supported by details. Explain precisely what the person did or did not do after being given a clear, lawful direction.

The same standard applies to your own actions. Do not write that you “had to” use force without explaining why. Identify the threat or resistance, the commands given, the options considered if there was time, and the specific action taken. If you used a control hold, handcuffs, OC spray, or baton, name the technique or tool accurately and report the duration, number of applications or strikes if applicable, and the result.

Build the Report in a Clear Sequence

Start with the basic circumstances: date, time, exact location, assignment, post, client site, and the names or identifiers of involved personnel. State why you were present and how the incident came to your attention. If a call, alarm, observation, or witness statement prompted your response, record that source.

Then document the subject’s behavior in order. Include relevant movements, statements, refusal to follow directions, attempts to leave, assaultive actions, visible weapons, or efforts to access potential weapons. Distance and positioning are often significant. A person across a room presents a different immediate concern than a person within striking range.

Next, record your communication. State the commands or warnings you gave as closely as you can remember them. Include whether the subject appeared to hear and understand you, whether language barriers were present, and whether you attempted de-escalation. If time allowed, describe requests for backup or law enforcement assistance.

After that, describe the force used. Identify who applied it, who it was applied to, where it was applied, and how long it lasted. Report each separate action in order. If multiple security officers were involved, write only your own observations and actions unless your reporting system specifically requires a team narrative. Never guess what another officer perceived or intended.

Close the sequence with control, care, and transfer. Explain how the incident stopped, whether restraints were checked and monitored, whether injury was claimed or observed, and what first aid or emergency medical response was offered. Record the arrival time and actions of police, EMS, supervisors, or site management. If the subject was released, removed, arrested, or transported, state by whom and when.

Details That Should Never Be Left Out

For any report involving force, capture these details before memory fades:

• The behavior that created the safety concern or resistance.
• The verbal directions, warnings, and de-escalation efforts used.
• The specific force option, technique, or equipment deployed.
• The duration, repetitions, body area involved, and effectiveness of the action.
• Visible injuries, complaints of pain, medical aid offered, and monitoring provided.
• Witness names or contact information, camera locations, photos, radio traffic, and other evidence.
• Notifications made to supervisors, law enforcement, EMS, and the client.

This is not a script. Some details will not apply to every event. A brief escort of a cooperative trespasser should not be documented like an active assault. However, a report should always give a reader enough information to understand the decision-making process and verify what occurred.

Describe Medical Care and Restraint Monitoring Carefully

Medical documentation is a major part of force reporting. If a person says they are injured, report the statement in quotation marks when possible. If you observe redness, bleeding, swelling, impaired breathing, altered consciousness, or another condition, document exactly what you observed and when. Do not minimize complaints because no obvious injury is visible.

If restraints were used, document the type of restraint, fit, placement, safety check, and ongoing monitoring. Positioning matters. Follow your employer’s policy and training on safe restraint practices, medical distress, and emergency response. Once a person is under control, the duty to monitor does not stop.

If OC spray or another chemical agent was deployed, record the product used, the number and approximate duration of applications, the direction of spray, contamination concerns, decontamination steps, and medical evaluation or assistance offered. If a baton was used, identify the target area, number of strikes, threat that justified each action, and post-incident medical care. Your report should match your training and policy language without copying phrases you cannot support from memory.

Common Reporting Errors That Create Problems

The first error is waiting too long. Complete the report as soon as practical after required medical care, scene security, notifications, and evidence preservation are handled. Memory becomes less reliable with every interruption. If you must make notes first, preserve them according to policy rather than discarding or altering them.

The second error is coordinating language with other staff. Officers can discuss immediate safety facts and required operational information, but each person should prepare an independent, truthful account. Reports that use identical wording or omit obvious differences in perspective can appear coached.

The third error is treating the report as a defense statement instead of an incident record. Do not argue with imagined critics or add unnecessary opinions about the subject’s character. Accurate details are more persuasive than self-justification.

Finally, never alter a completed report without following agency procedure. If you discover an error, use an approved supplemental report or correction process that preserves the original record and explains the change.

Training Makes Better Reports Possible

Good reporting begins before the incident. Personnel need practical training in verbal de-escalation, force decision-making, defensive tactics, restraint safety, OC spray or baton deployment where authorized, and post-incident responsibilities. A credential shows that you have completed instruction, but your continued value comes from applying that instruction under pressure.

Scenario-based practice is especially useful because it connects communication, observation, force options, medical awareness, and reporting into one professional response. GC Tactical Training emphasizes qualifications that help frontline personnel respond responsibly, document clearly, and strengthen their professional credibility.

Before your next shift, review your employer’s use-of-force policy, reporting form, camera procedures, supervisor notification rules, and medical-response expectations. When an incident happens, clear decisions matter. When it is over, clear documentation helps ensure those decisions can be understood.