Use-of-Force Report Form (Law Enforcement)

Use this form for any incident where an officer applies force beyond routine contact, including physical restraint, weapon display, or other escalated control measures. It is meant to capture the facts of the event, not to replace an incident report or arrest report when those are also required. If your agency has a separate threshold for reporting, use that policy to decide when this form is mandatory.

The reporting officer should complete the initial submission as soon as practical after the incident while details are fresh. A supervisor then reviews the report, adds comments, and records the review outcome. Agencies can also route the form to internal affairs, training, or records staff if their workflow requires additional review.

It is used each time a reportable use-of-force event occurs, so the cadence is event-driven rather than scheduled. Some agencies require submission before the end of shift, while others allow completion after immediate scene duties are finished. The template supports both same-day reporting and later supervisory review.

The summary should explain what happened, what led to the force, what force was used, and what happened immediately after. Keep it factual and chronological, and avoid speculation or conclusions that are not supported by observed facts. Include enough detail for a supervisor or reviewer to understand the sequence without reading between the lines.

The form creates a consistent audit trail by capturing the officer, date, time, location, force level, injuries, witness information, and supervisor review outcome. That structure helps agencies compare incidents, identify patterns, and support internal review processes. It also reduces missing fields that can weaken documentation quality.

Yes. Agencies can add conditional logic for weapon type, subject injury, or medical response, and they can tailor force categories to match local policy. You can also add required fields for body-worn camera reference numbers, case numbers, or chain-of-command routing if those are part of your workflow.

Common mistakes include vague force descriptions, missing timestamps, inconsistent witness details, and failing to state why the force was justified. Another frequent issue is collecting too much personal data when only minimal identifying information is needed. The template is designed to keep the report focused on necessary facts and reviewable evidence.

It works well alongside incident reporting, body-worn camera logs, evidence tracking, and supervisor approval workflows. Agencies often connect it to records management or case management systems so the report can be stored with the incident file. If your process includes training follow-up or policy review, the supervisor outcome field can trigger those next steps.

An ad hoc memo can miss key facts, vary by officer, and make review harder because every report is structured differently. This template standardizes the fields that matter most, including force justification, injuries, witnesses, and supervisor review. That consistency makes it easier to compare incidents and maintain a clear record.