Law Enforcement in Work Zones: When It Helps and How It Gets Paid For

Uniformed officers in work zones are one of the few line items where the contractor is usually not the decision maker, is often not the employer, and still ends up carrying the scheduling risk. It is worth understanding exactly what an officer changes, what the officer does not change, and how the hours move through procurement so you are not eating them.

What an officer actually changes

The behavioral effect is real and federal regulation says so directly. Under 23 CFR 630.1108, the presence of a uniformed law enforcement officer and a marked law enforcement vehicle in view of motorized traffic can affect driver behavior and help maintain appropriate speeds. That same section lists the conditions that point toward using enforcement: frequent worker presence near high-speed traffic, complex changes in traffic patterns, night operations, an existing crash history, and situations where unexpected queuing is anticipated.

That maps to a specific place on the job. The effect is on the approach and through the transition, where drivers are still deciding what speed to carry. It shows up in the crash types that dominate work zone fatalities. FHWA reports that speeding was a factor in 34 percent of fatal work zone crashes in 2022, and that rear-end collisions accounted for 174 of them, or 21 percent, per the FHWA work zone facts and statistics page. Those are approach-speed and queue-arrival problems, which is exactly the window an officer influences.

What an officer does not do is stop a vehicle. A patrol car is not positive protection. The same federal section that endorses enforcement treats positive protection devices as a separate category, indicated where workers have no means of escape from intruding traffic. If your exposure problem is physical, enforcement is not the answer to it — see positive protection in work zones explained. Officers and barrier solve different problems and one does not substitute for the other.

Two other honest limits. The effect is generally strongest while the unit is visible and tends to fade downstream of it, which is why placement matters more than headcount. And an officer is not a traffic control device — signs, channelizing devices, and flagging still have to be right on their own terms.

Stationary versus circulating

Two deployment patterns show up in practice.

Stationary means the unit parks in a fixed, visible position on the approach, typically upstream of the advance warning area or near the beginning of the transition, with lights running. This is the pattern that produces the speed effect people are paying for. It is also the pattern most likely to be specified when the agency has a queue or a speed history it is worried about.

Circulating or roving means the officer patrols the corridor, enforcing rather than sitting. This is the pattern used when the concern is corridor-wide behavior, or when a single fixed point cannot cover a long or phased setup. It produces enforcement activity but a weaker steady-state visual deterrent at any one point.

There is a third, distinct use that gets conflated with the first two: an officer directing traffic or providing incident management during a closure or a crossover cutover. That is an active traffic operations role, not a deterrent role, and it needs explicit coordination with your crew about who is in control of traffic at any given moment.

Required versus elected

The requirement usually comes from the owner. Federal-aid agencies operate under 23 CFR 630 Subpart K, and 23 CFR 630.1106 requires an agency policy that addresses positive protection devices, exposure control measures, and other traffic control measures including uniformed law enforcement officers, and that policy has to address reimbursement agreements for law enforcement service. FHWA's own work zone regulation and policy page describes Subpart K as covering, among other things, uniformed law enforcement deployment during construction operations and contract pay items.

Practically, that means officer presence lands on your job one of three ways:

• Specified in the contract or the traffic control plan. The requirement is written, there is usually a pay item, and you are administering it rather than deciding it.
• A permit condition. Common on municipal and utility work. The permit says an officer is required for certain closure types or certain hours.
• Elected. You or the general contractor decide the exposure justifies it — a bad intersection, a night shift on a high-speed arterial, a phase where queues are predictable.

Elected use is where contractors get burned, because the hours are real money and nobody agreed in advance who pays. Decide that before the officer is dispatched, not after the invoice.

Requirements vary substantially by state, by agency, and by local jurisdiction. Confirm what applies with the authority having jurisdiction for your specific project before you price it or promise it.

How it gets procured and billed

The general shape, and you should verify the specifics locally every time: the officer is engaged through their own law enforcement agency under an extra-duty or off-duty program rather than being hired by you directly. The agency sets the hourly rate, the minimum call-out, the vehicle or administrative fee, and the cancellation window. On federal-aid work there is typically a reimbursement agreement between the owner agency and the law enforcement agency, and a corresponding contract pay item. 23 CFR 630.1012 requires that project plans and specifications include appropriate pay item provisions for implementing the transportation management plan, either through method-based or performance-based specifications.

What that means for your estimate:

• Never bury officer hours in your flagging rate. Quote them as a separate line, ideally as a pass-through with a stated administrative markup. If you fold them in, you lose visibility the first time an officer minimum triggers on a two-hour job. The same discipline applies across your rate sheet — see quoting traffic control jobs faster.
• Price the minimum, not the expected hours. Extra-duty programs commonly bill a minimum block regardless of actual time worked. If you quoted actual hours you are short from the start.
• Get the cancellation window in writing. Officer cancellations frequently have to be made further out than your own crew cancellations. A job that cancels at 5 a.m. may still owe the officer.

Scheduling and cancellation friction

This is the part that costs real money and rarely appears in anyone's cost model.

Officer scheduling generally runs on a different calendar than yours. Requests often need to go in days ahead, they are filled by volunteers, and they are subject to being pulled for actual police business. Meanwhile your job may move by a day on a phone call. Every one of those moves has to be pushed back through the officer request, and the ones that do not get pushed produce either a no-show or a billable cancellation.

A few habits that reduce the bleed:

• Treat the officer as a resource on the job record, not a note in someone's phone. If the job date moves, the officer request has to move with it, and somebody has to confirm it moved. This is exactly the kind of dependency a dispatch board should surface — see daily dispatch routine for traffic control companies.
• Log the officer's arrival and departure on the daily ticket the same way you log crew time. If the invoice from the agency disagrees with your ticket, the ticket is your only evidence.
• Record the no-show explicitly, with a timestamp and the name of whoever you notified. That single field decides who eats the standby.

Traffic OS treats the officer as a schedulable line on the job with its own hours and its own billing treatment, and the signed daily ticket carries the timestamps, so the reconciliation against the agency invoice is a document comparison rather than a memory contest.

Coordinating with the crew

The most common wasted officer hour is a correctly billed, correctly scheduled officer parked in the wrong place.

Give the arriving officer a thirty-second brief: where the advance warning starts, where the taper begins, where the work space is, and where you want the unit staged so approaching drivers see it before they commit. If the concern is queue arrival, the useful position is upstream of where the queue tail is expected to sit, not at the work space. If the officer parks past the activity area, they are visible only to drivers who have already passed the decision point.

Also settle who is in control of traffic. FHWA training material for uniformed officer use in work zones flags recurring problems including officers moving traffic control devices and conflicts between officers and flaggers, and identifies understanding who is in control of the traffic as a critical concern. On your site, that conversation happens at arrival or it happens badly in the middle of a lane closure.

Night work amplifies all of this — visibility, fatigue, and the fact that speeds are usually higher with lower volumes. If you are running officers on night shifts, read night work traffic control: what changes alongside this. And if your reason for wanting an officer is intrusion risk rather than speed, the response side matters as much as the deterrent — see work zone intrusion prevention and response and work zone speed management and enforcement.

The short version

An officer buys you approach-speed compliance and driver attention on a specific stretch of road, for a specific window, at a rate you do not set. It is a legitimate countermeasure with federal backing and real limits. Price it as its own line, schedule it as its own resource with its own cancellation window, position it upstream where it does work, and document arrival and departure on the ticket. Do that and the officer is a manageable cost. Skip any one of those and it becomes an unrecoverable one.