Patrol Operations and Deployment
Patrol Operations and Deployment tests whether you can put people where the work is, and prove it. Items cover calls-for-service analysis, shift design, directed patrol, differential response, and workload measures.
Core rules
- Deployment follows demand. Map calls by hour of day, day of week, and geography before changing shifts. Habitual equal staffing per shift is a common cause of both slow response and idle time.
- Uncommitted time is a deployment resource, not waste. It funds directed patrol, problem solving, and training.
- Differential response: low-priority calls can be handled by telephone or online reporting, freeing patrol for in-progress and high-harm calls.
- Directed patrol concentrates effort on identified hot spots and times; saturation without analysis simply moves crime.
Worked example
A department runs three eight-hour shifts with six officers on the overnight shift. Analysis shows 34 percent of calls fall between 2000 and 0200 Friday and Saturday, while the current shift change occurs at 2300. Two changes follow from the data. First, add overlapping 10-hour shifts covering 1900 to 0300 on peak nights. Second, hold two officers from routine call response during peak hours and assign them to the corridor generating the most violent calls. Shift length is a secondary decision; the primary decision is matching coverage to the demand curve.
Traps that cost marks
- Believing faster average response time alone proves effective deployment.
- Cutting minimum staffing without checking officer-safety and backup-time data.
- Deploying saturation patrol with no analysis and no defined duration.
- Comparing clearance rates across agencies without normalizing for call mix.
- Staffing by tradition rather than by documented demand.