A supervisor’s use-of-force review,
and what its absence shows.

Most agencies require a supervisor to respond whenever force above a defined threshold is used, and that response is a sequence of tasks rather than a signature. The supervisor goes to the scene, confirms that medical aid was requested and rendered, and takes control of the immediate aftermath while the scene is intact and the people who saw it are still present.

The tasks a supervisory response is built from.

• Respond to the scene and confirm that aid was requested and rendered
• Identify the involved officers and the officers who witnessed the force, and separate them where the policy requires it
• Locate civilian witnesses while they are still on scene, and record how to reach them
• Take or arrange the statements the policy requires, including from the subject where possible
• Document injuries, and document their absence, in the manner the policy sets
• Review the available video, and note what it shows and what it does not cover
• Complete the supervisory review and route it up the chain within the stated time

Order matters as much as the list. A supervisor who reviews video before taking statements is doing something different from one who reviews it afterward, and agencies differ on which they require. The analysis reads the agency’s own policy on that point rather than assuming a practice, and then reads what the record shows was actually done on the day.

A completed supervisory review shows a supervisor engaging with the event: the force described in specific terms rather than in policy vocabulary, the resistance the officer reported set against what the video shows, the witnesses named, and a stated conclusion with the reasoning behind it. A review like that is affirmative evidence of supervision, and the analysis reports it as such when the record supports it.

The other outcomes are equally legible. A review completed late, after a complaint arrived, is a different fact than one completed on the shift. A review consisting of a single line adopting the officer’s narrative shows a supervisor who signed rather than reviewed. And where policy required a review and nothing was produced, the empty space in the file is what the analysis reports, with the date the review was due.

A supervisory review that restates the officer’s report in the officer’s words has documented nothing. The question is what the supervisor did that the officer could not have done alone.

The records that carry this are requested by name: the completed supervisory review or proof of its absence, the use-of-force report and each supplement filed to it, the policy setting the threshold for a supervisory response and the deadline for the review, and the involved supervisor’s own training on it. Those items are the working file for supervision and discipline analysis, and they are among the first records to go missing.

A single review describes one incident. The same supervisor’s reviews across a year describe how the shift is supervised. Where those reviews adopt the officer’s narrative incident after incident, or where a shift’s reviews are the same paragraph with the dates changed, the question stops being about one supervisor. That run belongs alongside complaint histories and flag data in early warning systems and supervision. What it establishes under Monell v. Department of Social Services, 436 U.S. 658 (1978) is counsel’s question; the analysis measures supervisory practice against agency policy and national standards and stops there. The supervisory review is worth asking for early for a plainer reason: it is often the only assessment in the file that was written before anyone had a case to defend.