Loading...
safety

Use-of-Force Report Form (Law Enforcement)

Use this Use-of-Force Report Form to document what happened, what force was used, who was involved, and what medical or supervisor follow-up occurred. It gives you a consistent record for review, audit trail, and incident analysis.

See it in MangoApps Get Started

Trusted by frontline teams 15 years of frontline software

Built for: Law Enforcement · Public Safety · Municipal Government

Overview

This Use-of-Force Report Form captures the facts of a law enforcement incident in a structured way: who reported it, when and where it happened, what the subject did, what force was used, whether anyone was injured, what medical response occurred, and what witnesses or evidence support the record.

Use it when an encounter involves force that needs formal documentation, supervisor review, or later audit. The template is designed to keep the report factual and complete without forcing every field to be filled in when it does not apply. That makes it a good fit for agencies that want consistent incident records, clear review notes, and a reliable audit trail.

Do not use this form as a general arrest report, a complaint form, or a narrative-only memo. It is also not the right fit for incidents where no force was used and no review is required. If your agency needs policy-specific force categories, chain-of-command routing, or internal affairs escalation, those can be added through customization and conditional logic. The form works best when officers can complete it soon after the event, with witness, evidence, and medical fields available only when relevant. That keeps the record focused, reduces unnecessary PII collection, and makes supervisor review faster and more consistent.

Standards & compliance context

  • Collect only the incident details needed for the report to support data minimization and reduce unnecessary PII exposure.
  • If the form is used in a public-facing context, make labels, validation, and navigation accessible in line with WCAG 2.1 AA.
  • Use clear consent or disclosure language if the form collects witness contact details, subject medical information, or other sensitive PII.
  • Keep medical-response fields limited to what is necessary for the incident record and follow the minimum-necessary principle where health information is involved.
  • Preserve a supervisor review trail so the report supports internal audit and policy review without altering the original officer submission.

General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.

What's inside this template

Submission Notice

This section tells the officer what submitting the form means and what review or routing will happen next.

  • I confirm this report is accurate to the best of my knowledge and submitted in accordance with department policy. (required)
  • What happens after I submit?

    The report is routed to a supervisor for review and audit trail retention. If the incident requires follow-up, you may be asked to provide clarification, evidence references, or additional documentation.

Officer and Assignment Details

These fields identify who is reporting the incident and anchor the report to a specific time, place, and assignment.

  • Reporting Officer Name (required)
  • Badge Number (required)
  • Agency / Unit (required)
  • Date of Incident (required)
  • Time of Incident (required)
  • Incident Location (required)

Incident Overview

This section captures the core facts of the encounter, including the incident type, subject behavior, and a concise narrative summary.

  • Incident Type (required)
  • Subject Behavior Before Force Was Used (required)
  • Narrative Summary of Events (required)

    Describe the sequence of events factually and in chronological order. Include only observable facts, not conclusions.

Force Used

These fields document exactly what force was applied so reviewers can compare the selection with the written account.

  • Force Levels Applied (required)
  • Force Details

    Add one entry for each force tactic used.

Injuries and Medical Response

This section records whether anyone was injured and what medical attention or response was provided after the incident.

  • Did any injury occur? (required)
  • Subject Injury Type
  • Was medical attention provided or requested?
  • Medical Response Notes

    Document only the minimum necessary facts, such as first aid, EMS request, transport, or refusal of care.

Witnesses, Evidence, and Review

These fields connect the report to witnesses, recordings, and supervisor review so the record can be verified and followed up.

  • Were witnesses present? (required)
  • Witness Details
  • Body-Worn Camera Used? (required)
  • Evidence / Report Reference Numbers

    List related case numbers, evidence tags, or body-worn camera reference IDs if applicable.

  • Supervisor Review Notes

    For supervisory use during review, policy assessment, and audit trail documentation.

How to use this template

  1. 1. Configure the submission notice so the officer sees what happens after submit, including supervisor review, audit trail retention, and any follow-up routing.
  2. 2. Assign the officer fields and incident fields first, then use conditional logic to reveal injury, witness, and evidence sections only when those details apply.
  3. 3. Have the reporting officer enter the incident facts, select the force levels applied, and write a factual narrative that matches the selected fields.
  4. 4. Complete the injury and medical response section when anyone was hurt or evaluated, using clear validation so dates, times, and required notes are captured accurately.
  5. 5. Route the completed report to a supervisor for review, correction if needed, and final action tracking, then store the record with the related evidence references.

Best practices

  • Mark required versus optional fields clearly so officers know exactly what must be completed before submission.
  • Use conditional logic to hide witness, evidence, and medical follow-up fields until the incident facts make them relevant.
  • Keep the narrative factual and chronological, and avoid conclusions that are not supported by the observed event.
  • Use field types that match the data, such as date pickers for dates and numeric inputs for counts or badge numbers.
  • Record the force level and the force details separately so reviewers can compare the selection with the written explanation.
  • Include a clear submission acknowledgment that explains who reviews the report and what happens after it is submitted.
  • Limit PII to what the agency actually needs for the incident record and avoid collecting unnecessary identifiers.

What this template typically catches

Issues teams running this template most often surface in practice:

The force level is selected, but the narrative does not explain why that level was used.
The injury section is skipped even though the incident notes mention pain, bleeding, or medical evaluation.
Witnesses are listed without enough detail to contact or identify them later.
The body-worn camera field is left blank, making it hard to cross-reference video with the report.
The report uses vague language like "subject was noncompliant" without describing the specific behavior observed.
Supervisor review notes are missing, so the record does not show whether the report was checked for completeness.
The form collects more personal data than needed for the incident, creating avoidable privacy risk.

Common use cases

Patrol Supervisor Review
A patrol officer submits a report after a restraint or takedown, and the supervisor uses the review section to confirm the force level, check the narrative, and note any follow-up action.
Body-Worn Camera Cross-Reference
An agency uses the evidence reference field to link the report to body-worn camera footage, making it easier to verify the timeline and compare the written account with the recording.
Injury-Related Incident Documentation
When a subject reports pain or visible injury, the officer completes the medical response fields so the agency has a clear record of what care was offered and what happened next.
Internal Policy Audit
A command staff reviewer uses completed forms to check whether incidents are being documented consistently and whether force details match the agency's reporting expectations.

Frequently asked questions

What incidents should be documented with this form?

Use this form for any law enforcement encounter where force was applied, threatened, or escalated beyond routine contact. It is also useful when there is an injury, medical response, witness involvement, or body-worn camera footage tied to the event. If your agency has a separate minor-contact log, this template should still be used when the incident requires a formal use-of-force record.

Who should complete the report?

The reporting officer should complete the initial narrative and factual fields as soon as practical after the incident. A supervisor can then review the submission, verify completeness, and add follow-up notes. If your agency requires chain-of-command review, this template supports that workflow without changing the original incident record.

How often is this form used?

It is used on an as-needed basis, each time a qualifying use-of-force incident occurs. It is not a periodic checklist or shift report. Agencies often standardize it so every event is captured in the same format, which makes review and trend analysis easier.

What information should be included in the narrative?

The narrative should describe the sequence of events, the subject behavior, the force used, and the immediate outcome in plain factual language. Include only details that are necessary to explain the incident and support review. Avoid speculation, editorial language, or conclusions that are not backed by observed facts.

How does this template support compliance and review?

The fields create a structured record that supports internal audit trail, supervisor review, and consistent incident documentation. It also helps agencies limit unnecessary PII by collecting only the details needed to explain the event. If your agency has policy, accreditation, or reporting requirements, the form can be customized to match them.

Can this form be customized for different agencies or units?

Yes. You can add agency-specific force categories, policy references, review sign-off fields, or routing steps for internal affairs or training. You can also use conditional logic so injury, witness, and evidence fields appear only when relevant, which keeps the form shorter and easier to complete.

What are the most common mistakes when filling it out?

Common mistakes include leaving the force level too vague, skipping the medical response section, and writing a narrative that does not match the selected force fields. Another frequent issue is collecting unnecessary personal data when a minimal incident record would do. Clear required vs. optional fields and a complete submission notice help prevent those gaps.

How does this compare with an ad-hoc incident memo?

An ad-hoc memo usually varies by officer and often misses key details, which makes review and comparison difficult. This template standardizes the fields, prompts for witness and evidence references, and gives supervisors a consistent review point. That makes the record easier to audit and easier to use for policy, training, or case follow-up.

Related templates

Forms

Employee Bloodborne Pathogen Exposure Incident Report

Use this Employee Bloodborne Pathogen Exposure Incident Report to document a workplace exposure, ...
Forms

Employee Safety Reporting Program Form

Use this Employee Safety Reporting Program Form to capture hazards, near misses, unsafe condition...
Forms

Firearms Range Qualification Scoring Sheet

Record firearms qualification results, pass/fail status, and instructor certification in one stru...
Forms

Dealership Technician PPE Issuance and Training Record

Track PPE issued to dealership technicians and document safety training in one record. Use it to ...
Forms

SDS Safety Data Sheet Request Form

Use this SDS Safety Data Sheet Request Form to collect the exact chemical, supplier, and site det...
Inspections

Body-Worn Camera Activation Compliance Audit Worksheet

Audit body-worn camera activation, categorization, access, and retention handling against policy ...
Sop

Downed Power Line Make-Safe Response SOP

Downed Power Line Make-Safe Response SOP for first responders and utility crews to isolate the sc...
Hr Policy

Anti-Harassment & Anti-Discrimination Policy

Anti-Harassment & Anti-Discrimination Policy template for defining prohibited conduct, reporting ...

Go deeper on the topic

Related concepts
  • Standard Operating Procedure
    A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
  • Workforce Management
    Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
  • Daily Huddle
    A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
  • Deskless Worker
    A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
Related guides

Ready to use this template?

Get started with MangoApps and use Use-of-Force Report Form (Law Enforcement) with your team — pricing built for small business.

Get Started