Safety Incentive Programs for Traffic Control Crews: Rewarding the Right Things

A traffic control company announces a crew bonus for every quarter without a recordable injury. Two months in, a flagger twists an ankle stepping off a truck. Her crew is three weeks from the bonus. She says nothing, works on it for two weeks, and the injury that would have been a day of rest becomes six weeks off.

Nobody intended that. The program rewarded a number, and the cheapest way to produce the number was silence.

This guide covers how to reward safety without paying people to hide problems: what OSHA has said about incentive programs, why reporting matters so much in this trade, and what a workable program looks like for a company with a few dozen people in the field. It is general information, not legal advice. State-plan OSHA programs can differ, so check with your safety adviser.

What OSHA has said

The rule in the background is OSHA's recordkeeping regulation. 29 CFR 1904.35 requires employers to establish a reasonable procedure for employees to report work-related injuries and illnesses promptly and accurately, and says a procedure is not reasonable if it would deter or discourage a reasonable employee from accurately reporting. It also prohibits discharging or in any manner discriminating against an employee for reporting a work-related injury or illness.

In 2018 OSHA issued a memorandum clarifying how that applies to incentive programs. The October 11, 2018 memorandum states that incentive programs can be an important tool to promote workplace safety and health. It describes two kinds:

• Programs that reward workers for reporting near-misses or hazards, and encourage involvement in the safety and health management system.
• Rate-based programs that focus on reducing the number of reported injuries and illnesses, typically a prize or bonus at the end of an injury-free period.

On the second kind, the memorandum says rate-based incentive programs are also permissible as long as they are not implemented in a manner that discourages reporting. It suggests that an employer can counterbalance the risk by adding elements such as an incentive that rewards employees for identifying unsafe conditions, a training program that reinforces reporting rights and responsibilities, and a mechanism for accurately evaluating employees' willingness to report injuries and illnesses.

So the question OSHA asks is not whether you have a bonus. It is whether the way you run it discourages people from reporting. OSHA's broader guidance on safety and health programs puts worker participation and hazard identification at the center of an effective program.

Why reporting matters more in this trade

Most of what can hurt a traffic control crew gives a warning first.

A driver enters the taper and swerves out. A truck backs toward a flagger and stops. A sign stand blows over into the lane. A pickup runs the flagger's stop. Each of those is a near miss. Each tells you something about the setup, the site or the procedure, and each costs nothing if someone writes it down.

The alternative is to learn the same lesson from a crash. In the 2026 AGC and HCSS highway work zone survey, 60 percent of contractors reported at least one crash involving a moving vehicle in their work zones during the past year. Behind crashes like those are close calls that someone on a crew saw and, in many companies, nobody asked about.

A company that hears about its near misses can move a flagger station, lengthen a taper, change how devices are picked up, or tell a customer that a site is not safe as drawn. A company that hears nothing changes nothing. See work zone intrusion prevention and response and preventing backover incidents in work zones for two areas where near-miss reports are especially useful.

That is why an incentive that suppresses reporting is worse than no incentive. It removes the cheapest safety information you have.

What to reward

Reward what people do, not what happens to them. The useful test is whether a crew member can earn it through their own actions today.

Near-miss and hazard reports. The core of the program. Reward the report, not the absence of reports. Some companies give a small fixed amount for each report; others enter each report into a monthly draw. Either works if every report gets a response.

Pre-shift checks completed. Vehicle walk-around, device condition, radios, apparel. A check that is recorded every shift for a month is a fair thing to recognize.

Setups that pass inspection. When a supervisor or an agency inspector checks a closure and finds it correct, the crew that built it should hear about it. See work zone inspections and agency audits.

Briefings held and attended. A crew lead who runs a real briefing every morning is doing the most important safety job in the company. See tailgate safety meetings for traffic control crews.

Training and credentials. Completing a course, renewing a certification early, or cross-training as a spotter or crew lead.

Suggestions that are adopted. If a flagger's idea changes a procedure, say so publicly and reward it.

Stopping work. The hardest one, and the most valuable. A crew lead who refuses to open a closure because the setup is wrong, or pulls a flagger from a station with no escape route, should be backed and recognized, even when the customer is unhappy.

What not to reward, or how to do it carefully

Injury-free periods as the only measure. This is the design that teaches silence. If you keep a rate-based element because customers and insurers look at your rates, pair it with reporting rewards that are at least as attractive, and never withhold a reward from a crew because one of them reported an injury.

Team penalties. Cancelling a whole crew's bonus because of one report turns crewmates into enforcers of silence.

Speed. Rewarding the fastest setup or pickup rewards the shortcuts that hurt people.

Zero device losses. A bonus for returning every cone encourages a worker to step into a live lane to retrieve one. Track device losses as a cost, not as a crew target. See charging for damaged and lost traffic control devices.

Discipline deserves a separate word. A company can and should have rules, and enforce them. The line to watch is disciplining someone because they reported an injury or a hazard. If discipline regularly follows reports, people stop reporting, and you may have a legal problem as well. Ask counsel before you build a discipline policy around incidents.

A simple program that works

For a company with two to six crews, this is enough.

1. One way to report, taking under a minute. A text to a fixed number, a form on a phone, or a line on the daily ticket. Offer it in the languages your crews speak. See training Spanish-speaking traffic control crews.
2. A response within a day. Somebody acknowledges each report and says what will happen.
3. A monthly review. Ten minutes with the crew leads: what was reported, what changed.
4. Visible recognition. Name the report and the change it led to at the next briefing.
5. A modest reward tied to participation. Gift cards, a paid lunch, an extra hour of pay, a draw. The amount matters less than the consistency.
6. A quarterly look at the numbers. Reports per crew, checks completed, inspection results. A crew with no reports for a quarter is not a safe crew. It is a crew that is not reporting.

Keep it small enough to run every month without fail. A grand program that lapses in the busy season teaches people that it was never serious.

Measuring whether it is working

Count the things you are rewarding, alongside the outcomes.

• Near-miss and hazard reports per month. Early on, a rising number is good news.
• Share of shifts with a recorded pre-shift check.
• Share of reports with a documented response.
• Inspection pass rate.
• Recordable injuries and lost time, as the lagging measure.

Our guide to measuring safety performance in a traffic control company explains how leading and lagging measures fit together, and OSHA recordkeeping for traffic control companies covers the logs.

There is a commercial side. Customers and insurers ask for your record, and a claim follows you for years through your experience modification rate. See safety records and EMR in traffic control prequalification. A reporting program lowers that rate honestly, by catching problems while they are still cheap. It is also a retention tool: people stay where they are listened to. See hiring and retaining flaggers.

Where the records live

The program runs on small records made every day: who was on which crew, whether the briefing was held, whether the check was done, what was reported. If those live on paper in trucks, nobody can count them and the monthly review does not happen.

Traffic OS keeps crew assignments, daily tickets and job files together with an audit log, so the participation side of a program can be counted from records crews are already making. The features page shows what is included and pricing is by flat monthly tier with driver seats included, so field staff can report from their own logins.

To see daily crew records in one place, book a walkthrough.

The short version

Reward reporting, checks, training and good setups. Be careful with any reward that depends on an injury count, and never take a reward away because someone reported. OSHA's position is that incentive programs are useful and that rate-based ones are acceptable only when they do not discourage reporting. In a trade where almost every serious incident is preceded by close calls, the reports are worth more than the bonus costs.