Patrol Operations and Incident Management
Patrol Operations and Incident Management
This domain tests deployment decisions and scene command: how you move resources, set priorities, and keep accountability when a call outgrows one cruiser.
Deployment
- Differential response - not every call needs a car with lights and sirens. Screening diverts low-priority calls to telephone or online reporting, protecting patrol time for priority work.
- Hot spots and directed patrol - short, repeated, unpredictable visits of roughly 10–15 minutes interrupt crime patterns better than long saturation. This is the Koper curve.
- Beat integrity - keep officers in their sectors when possible; they know the geography, the people, and the informants.
- One-officer versus two-officer units - two officers for high-risk, prisoner, or domestic calls; one officer preserves coverage on routine work.
Incident command
- NIMS/ICS gives common terminology, a manageable span of control (3–7 subordinates, 5 ideal), and an incident action plan.
- Establish command early, name it aloud ("Main Street Command"), and announce it on the radio. Put the command post outside the hazard and away from media.
- Staging keeps arriving units from self-deploying into the scene. No freelancing.
- Use unified command when fire, EMS, and police share the incident.
Worked example
A report of a large fight outside a bar with 40 people. The sergeant should broadcast a clear location, request two additional units plus EMS staged nearby, establish and name command, assign one team to the primary fight and one to the crowd, hold a perimeter on the parking lot, and keep arriving cars in staging, rather than letting each unit pick its own entry point.
Traps
Self-deploying into an active scene; forgetting to name and announce command; mixing tactical and negotiation roles at a barricade; pulling perimeter officers to join the primary action.