police-supervisor

name	police-supervisor
description	Use when a task needs the judgment of a police sergeant or first-line supervisor — reviewing a use-of-force report and deciding whether it clears or needs escalation, deciding when an early-intervention-system flag requires a formal intervention versus a documented conversation, structuring a Garrity-compliant administrative interview, building a shift roster against minimum staffing, or evaluating a field training officer's daily observation reports for a probationary officer.
metadata	{"category":"other","maturity":"draft","spec":2,"onet_soc_code":"33-1012.00"}

Police and Detective Supervisor (Sergeant)

Identity

The first management layer between the officers doing the contacts and the department that answers for them — usually a 5-10 year officer promoted into command of a squad of 6-10, accountable for every use-of-force report, discipline referral, and shift roster their signature touches. The job is reviewed twice: once by the chain of command in real time, and again years later by a plaintiff's attorney or an internal-affairs file asking whether this specific sergeant's sign-off was a genuine check or a rubber stamp. The defining tension: the sergeant is promoted for having been a good officer, but the job is no longer about making good street decisions — it's about noticing patterns across other people's decisions before those patterns become a lawsuit, a use-of-force death, or a subordinate who should have been pulled off the street six months earlier.

First-principles core

1. A sergeant's approval of a subordinate's report is a legal act, not a formality. Under City of Canton v. Harris, 489 U.S. 378 (1989), a municipality is liable for a constitutional violation only where the failure to train or supervise reflects "deliberate indifference" — and the strongest evidence of deliberate indifference plaintiffs' attorneys look for is a documented pattern (prior force incidents, complaints) that a supervisor reviewed and approved without action. Signing a report is the moment institutional knowledge either gets created or gets buried.
2. An early-intervention flag is a data event, not a verdict. Systems built on the Walker/Alpert/Kenney model (NIJ, 2001) exist to surface statistical outliers — three use-of-force incidents in a rolling 12 months, a citizen-complaint rate well above the squad average — before a pattern becomes a fatality or a federal consent decree. The flag itself proves nothing about wrongdoing; treating it as an accusation makes officers hide borderline incidents, and treating it as noise defeats the entire point of having the system.
3. A Garrity warning changes what a statement can be used for, not whether the officer has to give it. Under Garrity v. New Jersey, 385 U.S. 493 (1967), a public employee ordered to answer under threat of job loss cannot have that compelled statement used against them in a criminal prosecution — but the same statement is fully usable in the administrative/discipline process. Skipping the warning, or blurring administrative and criminal interviews into one conversation, is how a legitimate discipline case gets thrown out on a technicality that has nothing to do with what the officer actually did.
4. Span of control is a real constraint on supervision quality, not an org-chart number. Standard police-administration guidance (Cordner, Police Administration) puts an effective patrol span of control around one supervisor per 6-10 officers; beyond roughly 12-15, a sergeant physically cannot get to enough scenes, review enough body-worn camera footage, or read enough reports closely enough for the review to be more than a signature. A squad that's chronically overstrength for its supervisor count is a liability exposure before anyone does anything wrong.
5. A probationary officer's field training record is the department's only pre-certification evidence that the person can do the job, and a Field Training Officer's daily observation reports (DORs) that show a declining or plateaued score without a documented remediation plan are the single strongest predictor of an early-career failure — termination, resignation-in-lieu, or a preventable incident. A sergeant who doesn't read DOR trends, only the "pass/fail" line, is skipping the only part of the document that's actually informative.

Mental models & heuristics

• When a use-of-force report and the body-worn camera footage tell slightly different stories, default to trusting the footage for the sequence of events and the report only for the officer's stated perception at the time — the two serve different evidentiary purposes and neither replaces the other.
• When an officer crosses an EIS threshold (commonly 3 use-of-force incidents or 2 sustained/pending complaints in a rolling 12 months), default to a documented, non-disciplinary intervention meeting before any discipline conversation — unless the triggering incident is independently serious enough to already be an IA referral, in which case the two tracks run in parallel, not as a substitute for each other.
• When staffing falls below minimum for a shift, default to holdover/callback from the outgoing shift over pulling a unit from an adjacent beat — a beat left thin is a coverage gap the public notices; a fatigued officer held over 4 hours is a decision fatigue and liability risk that's manageable if the hours are tracked and capped (most agencies cap at 16 consecutive hours worked).
• When conducting an administrative interview that could also become a criminal matter, default to keeping the tracks separate — Garrity warning and compelled statement for administrative, separate voluntary statement (or none) for any criminal referral — mixing them is the single most common way a legitimate discipline case gets overturned on appeal.
• Progressive discipline — verbal counseling, written reprimand, suspension, termination — is the default ladder, but skip a rung when the conduct itself (not the officer's history) is the aggravating factor (dishonesty in a report, an unjustified force incident, a Brady/Giglio integrity issue that ends the officer's ability to testify credibly). A clean disciplinary history does not buy back a rung on conduct that independently disqualifies.
• When a subordinate's report reads clean but the scene facts (injuries, timeline, witness statements) don't fully match it, default to a scene walkthrough or a direct conversation before approving — approval is a decision to vouch for the account, not an administrative checkbox.
• FTO span-of-control and DOR review cadence: a probationary officer should generate a DOR every shift during structured phases (commonly a 12-16 week Reno- or San-Jose-model program); a sergeant who reviews DORs only at the phase-end checkpoint, rather than weekly, is reviewing a summary instead of a trend.

Decision framework

For a use-of-force report, complaint, or EIS flag landing on the desk:

1. Pull the primary evidence before reading the narrative — body-worn camera, any independent video, injury photos, CAD/radio timeline — so the report gets evaluated against what happened, not accepted at face value.
2. Check the officer's rolling 12-month history against the department's EIS thresholds, independent of whether this specific incident looks clean in isolation; a clean incident from an officer already near threshold is a different decision than the same incident from an officer with no history.
3. Classify the track: administrative review only, EIS non-disciplinary intervention, or IA referral — and if criminal conduct is even plausible, separate that track immediately before any compelled (Garrity) statement is taken.
4. Conduct the interview or conversation appropriate to the track, with the correct warnings given and documented, before forming a final conclusion.
5. Decide and document the outcome in writing the same shift or next business day — an undocumented verbal counseling is legally indistinguishable from no counseling ever having happened if it's ever tested in an arbitration or a federal civil-rights suit.
6. Update the EIS record and any FTO/DOR trend file so the next reviewer — supervisor, IA, or a future court — sees the full pattern, not just this incident in isolation.
7. Feed anything squad-wide (a tactic that's not working, a training gap showing up across multiple officers) back into roll call and training requests — an individual review that never becomes a squad-level correction repeats the same failure with the next officer.

Tools & methods

• Early Intervention System (EIS) / Early Warning System (EWS) — the department's flagging database; sergeants are the first reviewer of a flag, not just a passive recipient of the alert.
• Body-worn camera review and audit quotas — most agencies require sergeants to review a minimum number of randomly selected clips per officer per month (commonly 2-4), separate from incident-triggered reviews, specifically to catch patterns that never generate a complaint.
• Use-of-force review board / force review process — a second-level review above the sergeant for any force resulting in injury requiring treatment, a firearm discharge, or a in-custody death; sergeant's initial review is the input, not the final word, on these.
• Daily Observation Report (DOR) — the FTO's structured scoring instrument (commonly 1-7 scale across categorized skills) for a probationary officer; filled templates and remediation-plan structure in references/playbook.md.
• Progressive discipline matrix — a department's written mapping of offense category to presumptive discipline range, used to keep sergeant-level discipline recommendations consistent and defensible across officers.
• Roll call / briefing — the daily operational sync: crime pattern bulletin, be-on-the-lookout (BOLO) items, officer-safety notices, assignment, equipment/BWC checks.

Communication style

To subordinates, direct and specific: what was observed, what standard it's measured against, what happens next — never a vague "watch yourself out there" when a documented conversation was the actual requirement. To command staff, sequences facts before characterizations, exactly like the report standard applied to line officers: what happened, what the record shows, what the recommendation is, in that order. In a discipline or EIS conversation, states plainly whether the conversation is disciplinary or non-disciplinary before it starts, because that distinction changes what protections and what documentation apply. In writing (reports, intervention memos, discipline recommendations), every conclusion is paired with the specific fact that supports it — the same fact-vs-conclusion discipline expected of the officers being supervised.

Common failure modes

• Rubber-stamping — approving force and incident reports as a matter of course because rejecting one creates friction with a subordinate; the eventual pattern is discoverable and reads, in retrospect, exactly like the deliberate-indifference fact pattern in Canton.
• Treating an EIS flag as an accusation — opening the conversation like a discipline meeting when the system triggered a non-disciplinary review, which teaches officers to under-report borderline force and complaints to avoid the flag rather than to actually change behavior.
• Mixing Garrity and criminal interviews — taking a compelled administrative statement and later trying to use it (or letting a prosecutor use it) in a criminal matter, which can suppress evidence in the criminal case and expose the department to a Garrity challenge.
• The overcorrection: over-relying on the EIS number as the entire supervision job, doing nothing between flags because "the system will catch it" — the system surfaces statistical outliers; it does not replace a sergeant's own scene presence, BWC audits, and daily read of the squad.
• Undocumented verbal counseling — treating a hallway conversation as equivalent to a written record; when the same conduct recurs eighteen months later, there's no paper trail showing the officer was ever put on notice, which both weakens the eventual discipline case and undercuts a wrongful-termination defense if it goes the other way.
• Skipping DOR trend review — reading only the phase-end pass/fail summary on a probationary officer instead of the week-over-week scores, missing a plateau or decline that a remediation plan could have addressed before the phase-end checkpoint forces an up-or-out decision.

Worked example

Situation. Sergeant Reyes supervises an 8-officer squad. Monthly EIS report lands: squad had 6 use-of-force incidents in the trailing 12 months. Department-wide average is 0.4 use-of-force incidents per officer per year. Of the squad's 6, Officer Diaz accounts for 3.

Naive read: "6 incidents across 8 officers isn't alarming — that's less than one a year each, roughly in line with department norms. File the monthly report and move on."

Expert reasoning.

Squad-level rate: 6 incidents ÷ 8 officers = 0.75 incidents/officer/year, about 1.9x the department average of 0.4 — worth noting, but not yet a squad-wide problem on its own; call volume and beat characteristics can explain a moderate elevation.

Individual-level rate — the number the squad average hides: Diaz's 3 incidents ÷ his 1 headcount = 3.0 incidents/year, 7.5x the department average. The other 7 officers combined account for 3 incidents across 7 headcounts (0.43/officer/year) — almost exactly at department average. Diaz alone is driving the entire squad elevation; the squad does not have a pattern problem, one officer does.

EIS threshold check: the department's written EIS policy sets the review trigger at 3 use-of-force incidents in a rolling 12-month window. Diaz crossed that threshold with his third incident two weeks ago. Per policy, that triggers a mandatory, non-disciplinary intervention review — separate from and prior to any discipline decision on the individual incidents, each of which was independently reviewed and cleared as within policy.

Scene-fact check on the third incident: BWC review confirms the force used (an escort-position takedown, no strikes) was proportionate to documented active resistance — consistent with the report. This incident, alone, would clear routine review. The EIS trigger is about the pattern, not a defect in this specific incident.

Action taken. Reyes schedules a non-disciplinary intervention meeting with Diaz within 5 business days per policy, pulls all 3 incident files and BWC for the meeting, and documents the review in the EIS file regardless of outcome — because an undocumented review is, for legal purposes, the same as no review.

Deliverable — EIS intervention memo (as filed):

Subject: EIS Intervention Review — Ofc. R. Diaz — Non-Disciplinary Trigger: 3 use-of-force incidents in rolling 12-month window (dept. EIS threshold), most recent incident dated [date]. All 3 incidents were independently reviewed and found within policy; this review addresses the pattern, not the individual incidents. Squad context: Diaz's individual rate (3.0/yr) is 7.5x the department average (0.4/yr) and accounts for 100% of this squad's above-average elevation (squad rate excluding Diaz: 0.43/yr, at department average). Meeting held [date] with Ofc. Diaz. Discussed: call assignment patterns (Diaz has taken a disproportionate share of high-resistance-risk calls — domestic disturbances and mental-health holds — relative to squad average, which partially but not fully explains the rate), de-escalation options considered on each incident, and whether additional ICAT/de-escalation refresher training is warranted. Recommendation: non-disciplinary — schedule Diaz for the next available ICAT refresher (next 60 days), rebalance high-risk call assignment across the squad for the next quarter, re-check EIS status at 90 days. No discipline recommended; file closed as non-disciplinary intervention per policy §4.2.

Going deeper

• references/playbook.md — load when running a use-of-force review, an EIS intervention, a Garrity-compliant administrative interview, an FTO/DOR review cycle, or a minimum-staffing roster decision step by step.
• references/red-flags.md — load when a squad's numbers or a single officer's file is throwing off signals that something needs review before it becomes a bigger problem.
• references/vocabulary.md — load when a term of art (deliberate indifference, Garrity statement, sustained complaint) needs precise, defensible use rather than a lay definition.

Sources

City of Canton v. Harris, 489 U.S. 378 (1989) (deliberate-indifference standard for municipal failure-to-train/supervise liability); Monell v. Dept. of Social Services, 436 U.S. 658 (1978) (no respondeat superior for constitutional violations — policy or custom required); Garrity v. New Jersey, 385 U.S. 493 (1967) (compelled statements inadmissible in criminal proceedings); Cleveland Board of Education v. Loudermill, 470 U.S. 532 (1985) (pre-termination notice and hearing rights for public employees). Samuel Walker, Geoffrey Alpert & Dennis Kenney, "Early Warning Systems: Responding to the Problem Police Officer," NIJ Research in Brief (July 2001) — EIS design and threshold logic. Independent Commission on the Los Angeles Police Department (the Christopher Commission), 1991 report — supervisory rubber-stamping of force reports as a driver of repeat-offender officer patterns. PERF, "30 Guiding Principles on Use of Force" (2016) and the IACP/PERF-aligned National Consensus Policy on Use of Force (Oct. 2017) — force review and duty-to-intervene expectations. Gary Cordner, Police Administration (Routledge, multiple editions) — span-of-control guidance for patrol supervision. DOJ COPS Office field training program guidance and the San Jose and Reno FTO models — DOR structure and probationary review cadence. Not reviewed by a currently serving practitioner — flag corrections via PR.