Skip to content
Tailboard
POL-105Police OperationsSOP

Response to Resistance Reporting

Documentation, supervisor review, and accountability for force events.

Draft — awaiting subject-matter-expert sign-off.

This template has been authored from the standards listed below but has not yet been reviewed by a named SME. Do not adopt without review through your authority having jurisdiction.

Read before using

This is a template. It is not your department's policy.

Tailboard templates are drafted as generic starting points aligned to national standards. They are nota substitute for your department's own review or for adoption through your Authority Having Jurisdiction (AHJ). For topics carrying significant exposure (use of force, medical scope, civil rights), route through qualified counsel before adoption.

Every placeholder marked [BRACKETED] must be completed before adoption. Every section must be reviewed against your department's staffing, apparatus, water supply, EMS scope, geography, and the specific laws of your state. What applies to a career department in a city may not apply to a volunteer department in a rural jurisdiction, and vice versa.

Standards, regulations, and best practices are updated regularly. Verify the current edition of every standard cited before adopting this document. Once adopted, this document becomes your department's responsibility — not Tailboard's.

Want this tailored to your department?

Open it in the Policy Builder. Answer a few questions about your staffing, apparatus, and conditions — we'll adapt every section to match.

Number

POL-105

Version

1.0

Last reviewed

2026-05-01

Next review

2027-05-01

Summary

This policy defines when and how [AGENCY NAME] members report uses of force, how those reports are reviewed up the chain of command, and how aggregate data is used to identify training needs and policy gaps.

Definitions

Reportable Force
Any application of force beyond officer presence and verbal control. Includes hands-on control resulting in pain compliance or take-down, OC, CEW, baton, impact projectile, canine bite, firearms discharge (including at animals), pointing a firearm at a person, and any force resulting in complaint of injury or visible injury.
Critical Incident
Any officer-involved shooting, in-custody death, deadly-force application, or use of force resulting in serious bodily injury.

Purpose

To ensure every reportable force event is timely documented, reviewed independently of the involved officer, and used to improve agency performance.

Scope

Applies to all sworn members and to any [AGENCY NAME] personnel who employ force in the course of their duties.

When a Force Report Is Required

  • Any hands-on force beyond escort holds and routine handcuffing.
  • Any deployment or discharge of OC, CEW, baton, or impact projectile.
  • Any canine bite or apprehension.
  • Any firearm discharge by an officer (intentional or accidental, including at animals).
  • Any pointing of a firearm at a person.
  • Any force resulting in injury, complaint of injury, or medical evaluation.
  • Any allegation by a subject, witness, or attorney that force was used.

Timing

  • Verbal notification to supervisor at the scene or immediately after.
  • Initial written report before the officer goes off duty.
  • Critical incident reports may be deferred per the Critical Incident Response policy, but at minimum a placeholder report is opened the same shift.

Required Content

Incident Identification

  • Date, time, location.
  • Case number, CAD incident number.
  • Officer(s) involved, witnessing officers.
  • Subject identification (when known).

Pre-Force Context

  • Nature of the call and information known to the officer.
  • Subject's behavior leading to the force decision.
  • De-escalation attempted and results.
  • Lawful basis for the contact / detention / arrest.

Force Used

  • Specific force option(s) employed.
  • Number of applications.
  • Subject's response to each application.
  • Transitions between force options and rationale.
  • Each officer's role.

Subject Information

  • Apparent age, size, condition.
  • Indicators of intoxication, mental health crisis, medical condition.
  • Statements and behaviors during and after the contact.
  • Demographic data as captured per state and federal reporting requirements.

Outcome

  • Injuries to subject(s) and officer(s).
  • Medical aid summoned, treatment provided.
  • Photographs taken (subject, officer, scene).
  • Charges filed.
  • Body-worn camera and other video identifiers.

Supervisor Response

  1. Supervisor responds to the scene for any force resulting in injury, any CEW or impact deployment, any firearm discharge, or any allegation of misconduct.
  2. Supervisor conducts preliminary on-scene review.
  3. Supervisor identifies and documents witnesses.
  4. Supervisor reviews available video.
  5. Supervisor takes possession of any deployed less-lethal device for evidentiary handling per policy.
  6. Supervisor completes the supervisor's force-review report within 7 days.

Chain of Command Review

  • First-line supervisor reviews for completeness, policy compliance, and training implications.
  • Watch commander reviews and either concurs or flags for further investigation.
  • Division commander reviews monthly trend data and individual cases referred up.
  • Chief of police reviews critical-incident cases and an annual summary.

Investigations

  • Routine force reports are administratively reviewed.
  • Cases with allegations of misconduct, significant injury, or policy concerns are referred to Internal Affairs / Professional Standards.
  • Critical incidents trigger the Critical Incident Response protocol — separate criminal and administrative tracks, external review where applicable, peer support, and counsel access.

Body-Worn Camera

All reportable force events shall be captured by BWC where the involved officer is BWC-equipped. Failure to activate BWC for a reportable force event requires explanation in the report. See the Body-Worn Camera policy for activation, retention, and review requirements.

Data Collection & Reporting

  • Aggregate force data is reviewed quarterly by command staff.
  • Annual public report includes total events by type, demographics, outcomes, and trends.
  • FBI National Use-of-Force Data Collection submissions per federal requirements.
  • State reporting per state law.

Confidentiality

  • Force reports may be subject to public records law and discovery; assume any field documentation will be made public.
  • Personal information of subjects, juveniles, victims of crime is handled per agency records policy.
  • Officer personal information is protected per state law.

Training

  • Initial training in report-writing and force reporting at academy and onboarding.
  • Annual scenario-based reporting training tied to use-of-force refresher.
  • Supervisor training in force review at promotion.

Responsibilities

Involved Officer

  • Notify supervisor at the time of the event.
  • Complete reports timely.
  • Cooperate with administrative review.
  • Per the Critical Incident Response policy and applicable law, statements in criminal investigations and administrative investigations are handled separately.

Supervisor

  • Respond to qualifying events.
  • Conduct preliminary review.
  • Complete the supervisor's force-review report.
  • Identify training and policy implications.

Command Staff

  • Monthly review of aggregate data.
  • Quarterly trend analysis.
  • Annual public reporting.

References

  • IACP Model Policy on Use of Force Reportingiacp.org
  • CALEA Standards 1.3calea.org
  • FBI National Use-of-Force Data Collectionfbi.gov/services/cjis/ucr/use-of-force
  • DOJ COPS Force Tracking Toolkitcops.usdoj.gov
  • State Statute on Use of Force Reporting[INSERT STATE]

Adapt this template

Before this template becomes your department's policy, review the following items and adjust accordingly. Anything else that does not match your operation should be updated as well.

  • DRAFT — Requires legal review and SME sign-off before publication or adoption.
  • Identify the platform used for force reports (RMS module, separate form).
  • Align supervisor review timelines with state public-records law.
  • Coordinate with Body-Worn Camera, Use of Force, and Internal Affairs policies.

Adoption signature

Adopted by (Name, Rank)
Signature
Effective date
Next scheduled review

Before adoption checklist

  • ☐Replace [DEPARTMENT NAME] throughout the document.
  • ☐Complete every [BRACKETED] placeholder.
  • ☐Confirm the current edition of every cited standard.
  • ☐Check against your state statutes and state fire marshal rules.
  • ☐Route for chief review. Topics with significant exposure (use of force, medical scope) also go through qualified counsel.
  • ☐Confirm alignment with any mutual-aid agreements.
  • ☐Schedule a training plan for the new policy before effective date.
  • ☐Announce adoption in writing to all members. Archive the prior version.
  • ☐Set the next review date — annually at minimum.