No category of security incident carries more legal risk than use-of-force events. A single poorly documented use-of-force incident can generate lawsuits that threaten the existence of a security company.
Why UOF Documentation Is Different
Standard incident reports are important. Use-of-force documentation is critical. The legal standard for reviewing force incidents requires detailed accounting of:
- The threat assessment — what did the guard perceive and why?
- De-escalation attempts — what steps were taken before force was used?
- Force proportionality — was the level of force reasonable given the threat?
- Post-force actions — what medical attention was provided? Who was notified?
- Witness information — who saw the incident and what were their accounts?
The Documentation Standard
Every use-of-force report should capture:
Pre-Incident Context
- Guard's post assignment and relevant post orders
- Events leading up to the confrontation
- Environmental conditions (lighting, crowd, weather)
- Subject behavior and verbal exchanges
Force Application
- Specific techniques or tools used
- Duration of force application
- Subject's response at each stage
- Any injuries to either party
Post-Incident Actions
- Medical assessment and treatment
- Supervisor notification timeline
- Law enforcement contact (if applicable)
- Witness identification and statements
- Evidence preservation (photos, video, physical evidence)
Common Documentation Failures
The three documentation failures that most often lead to adverse outcomes:
Technology Requirements
A proper UOF documentation system must:
- Guide the guard through structured, required fields
- Capture GPS location and timestamp automatically
- Support voice-to-text for faster, more detailed narratives
- Require supervisor review within a defined timeframe
- Generate a complete evidence pack including all related documentation
- Flag the incident for compliance review against use-of-force policies
Training Connection
Documentation and training must be linked. Every UOF incident should trigger a review cycle: was the force justified? Was the documentation complete? What training gaps does the incident reveal? This feedback loop is both operationally valuable and legally protective — it demonstrates organizational commitment to continuous improvement.