Safety Recognition Programs That Do Not Hide Injuries

Chris Fredette
3 hours ago
4 min read

In 2024, employers logged 2.5 million recordable injuries and illnesses in private industry, and BLS counted 5,070 workers killed on the job. Those are the ones that got written down.

Safe + Sound Week 2026 is built around safety and health recognition programs, and that instinct is correct. Recognition works. The problem is that the most common version of it in construction rewards the absence of a number, and the fastest way to make a number go away is to stop writing it down.

The program that looks like safety and works like a gag order

A steel erection crew is 71 days into a 90-day streak. Everybody knows the number. At 90 days with no recordables the company buys lunch and every man on the crew gets a jacket with the project name on it. The foreman has mentioned it three times this week.

On day 71 a guy tweaks his shoulder pulling a choker. Sore, but he can still work. He knows exactly what reporting it does to the count, and he knows what his foreman said about the jacket. So he works it out. Three weeks of favoring the arm turns into a compensation pattern, and fourteen months later it surfaces as a workers comp claim on a rotator cuff that started as a first aid case and two weeks of light duty.

Nobody in that story is a villain. The foreman wanted his crew to have something. The company wanted to celebrate work that was genuinely going well. The incentive just quietly told a worker that his shoulder was going to cost forty people a lunch.

What OSHA actually says about incentive programs

This is worth getting precise, because the internet version of it is wrong in both directions.

29 CFR 1904.35(b)(1)(iv) prohibits an employer from discharging or discriminating against an employee for reporting a work-related injury or illness. In October 2018 OSHA issued a memorandum clarifying how that applies to incentive programs, and it did not ban anything. Programs that reward workers for reporting near misses or hazards are always permissible. Rate-based programs, the kind that reward an injury-free month or evaluate a manager on their unit's lack of injuries, are also permissible, as long as they are not implemented in a way that discourages reporting.

The line worth reading twice is this one: OSHA notes that a statement telling employees they are encouraged to report and will not face retaliation may not by itself be adequate to ensure that employees actually feel free to report, particularly when the consequence of reporting is losing a substantial reward. The agency then lists precautions that help, including an incentive program that rewards identifying unsafe conditions, training that reinforces reporting rights and the non-retaliation policy, and a real mechanism for evaluating whether workers are willing to report.

OSHA puts the same warning in its own campaign material. The Champion Safety Challenge handout carries a note that recognition programs should encourage safe work practices and should never penalize workers for reporting. When the agency running the recognition campaign builds a caution into the handout, that is worth noticing.

So the legal question is narrow and the practical question is wide. Your rate-based program is probably lawful. The question that matters on Monday morning is whether the guy with the sore shoulder believes he can say so.

Recognize the input, not the absence of the output

The fix is not to cancel the lunch. It is to change what the lunch is attached to. Tie recognition to things your crew controls directly and can do more of.

A worker who reports a near miss with enough detail that somebody can actually fix the condition, not just log it.
A foreman whose pre-task plan names the specific hazard on that specific elevation instead of reproducing yesterday's.
Anyone who calls a stop-work and turns out to be wrong, because honoring a wrong stop-work costs you an hour and teaching people not to call one costs considerably more.
A crew that closes out corrective actions from the last walk before the next walk happens.
The person who flags that a fix from last month has quietly drifted back to the way it was.

Every one of those is a leading indicator. They go up when your program is working. Injury counts, by contrast, go down when your program is working and also when people stop reporting, which makes them a poor thing to buy lunch for. A metric with two very different causes and one direction is not a metric you want driving behavior.

Questions worth asking about your own program

Are safety incentive programs against OSHA rules? No. OSHA permits both reporting-based and rate-based programs. The prohibition is on retaliating against someone for reporting, and the 2018 memo says a rate-based program only crosses the line when it is run in a way that discourages reporting.

We already have a no-retaliation policy in the handbook. Is that enough? OSHA addressed this directly and the answer is that it may not be. A written statement that reporting is encouraged can be inadequate on its own, especially when reporting costs somebody a real reward. What matters is whether workers behave as though reporting is safe, not whether the policy says it is.

How would I know if my program is suppressing reports? Watch the ratio, not the count. If recordables are flat or falling while near-miss and hazard reports are also flat or falling, that is not a safe site, that is a quiet one. Healthy programs usually see reporting go up before injuries come down.

Can we keep the milestone lunch? Sure. Attach it to something the crew drives directly, like completed corrective actions or reporting participation, instead of to whether anyone got hurt.

Key Takeaways

OSHA permits safety incentive programs, including rate-based ones. The prohibition in 1904.35(b)(1)(iv) is on retaliation for reporting.
OSHA has stated that a written non-retaliation policy alone may not be adequate when reporting costs a worker a substantial reward.
Rate-based recognition asks the crew to protect a number, and the cheapest way to protect a number is silence.
Recognize behaviors the crew controls: near-miss reports, specific pre-task planning, stop-work calls, and closed corrective actions.
If injuries and near-miss reports are falling at the same time, look harder before you celebrate.

Recognition programs are easy to write and easy to get wrong. TriCore reviews incentive and recognition structures as part of a full safety program assessment, including the harder question of whether your reporting culture can survive the program you built. Start that conversation at tricoresafety.com.