Every site I've worked at had a near miss program on paper. There was a form, a box by the time clock, and a line in the safety policy saying every near miss must be reported.
And almost nobody used it.
It wasn't because near misses weren't happening. Walk the floor for an hour and you'll see a forklift cut a corner too close, a load swing a little too far, or someone reaching past a guard to clear a jam. They happen every shift. They just don't get written down.
That's a problem, because near misses are the cheapest lessons you'll ever get. Nobody got hurt, nothing has to go on the OSHA log, and you get a free look at exactly where the next injury is going to come from. Lose those reports and you're waiting for the injury to teach you instead.
Here's what I've learned about why people stay quiet, and what actually changes it.
The Five Real Reasons Near Misses Go Unreported
1. Reporting takes too long
If reporting means finding a supervisor, finding the right form, and filling out a full page in the middle of a shift, it isn't going to happen. The operator has a production number to hit. A two-page form loses to that every time.
The fix: make it take under a minute. A QR code posted at each work area that opens a short form on their phone, with no login, will get more reports in a week than a paper box gets in a year.
2. They're afraid of getting someone in trouble, including themselves
A lot of near misses involve someone taking a shortcut. If the last person who reported one watched a coworker get written up, the lesson everyone learned was "keep your mouth shut."
The fix: separate near miss reporting from discipline, and say so out loud. Focus the follow-up on the condition or the process, not the person. Allowing anonymous reports helps too. You'll lose a little detail, but you'll get a lot more reports.
3. Nothing ever happens after they report
This is the big one. An operator reports that the guard on Line 3 is loose. Three weeks later it's still loose, and nobody ever told them anything. Why would they report the next one?
The fix: close the loop every time. Turn the report into a corrective action with an owner and a due date, and tell the person who reported it what was done. Even "we ordered the part, it's in next Tuesday" counts.
4. Incentives that punish honesty
If the plant gets a pizza party for 100 days without an incident, think about what that does to the person who has to report one on day 99. Programs built around low numbers tend to reward silence.
The fix: reward the behavior you want. Recognize people for reporting hazards and near misses, and celebrate the fixes that came out of them. Under 29 CFR 1904.35, employers also have to make sure their programs don't discourage employees from reporting injuries and illnesses, so this matters beyond culture.
5. People don't know what counts
Ask five operators to define a near miss and you'll get five answers. Some think it only counts if it was almost a serious injury. Some think it has to involve a machine.
The fix: keep the definition simple, something like "anything that could have hurt someone but didn't," and give real examples from your own site in toolbox talks. People report what they recognize.
Don't Fix It With a Quota
When near miss reports are low, the first idea in a lot of plants is to require them: every employee submits two a month, or every supervisor turns in five a week. I understand why. It's measurable, and the numbers go up right away.
But I've watched what happens next. People start reporting the same wet floor sign over and over. Reports get filled out in the parking lot on the last day of the month. Supervisors make them up to hit the number. Within a couple of months you have a stack of reports that don't mean anything, and the real hazards are buried in it.
Worse, it teaches people that reporting is paperwork you do to keep the safety department off your back, which is the opposite of what you want.
A good near miss program isn't measured by how many reports come in. It's measured by how many hazards get found and fixed. If reporting is fast, safe, and leads to real fixes, people will report because it's worth their time, and you won't need to require it.
What a Working Near Miss Program Looks Like
When it's working, you'll notice a few things:
- Reports go up on their own. A rising near miss count is usually a good sign, as long as nobody is being forced to hit a number. It means people trust the process.
- Every report turns into an action. Even small ones get an owner and a close-out date.
- Reporters hear back. Within a few days, not a few months.
- You see patterns. Three reports about the same dock door in a month tells you where to spend money before someone gets hurt.
- Leadership talks about it. When the plant manager mentions a near miss fix in a shift meeting, everyone notices.
Start This Week
You don't need a new program to get started. Pick one area, post a simple way to report, and commit to closing out every report from that area within a week. Tell people what got fixed. Once the first few reports turn into real fixes, the rest of the floor will start reporting too.
Make Reporting Take 30 Seconds
With TruVex, workers scan a QR code at their work area and report a near miss or hazard from their phone. No login and no paper. Every report can become a corrective action with an owner and a due date, so nothing sits in a box, and you can see patterns across every site.
Book a DemoThe Bottom Line
Workers don't stay quiet because they don't care. They stay quiet because reporting is slow, it feels risky, and it never seems to change anything. Fix those three things and the reports will come.
That's a big part of why we built QR reporting into TruVex. I wanted reporting a hazard to be faster than walking away from it.
If you want to talk through your own near miss program, book a 15-minute call. It's one safety professional talking to another.
This article is general safety guidance and is not legal advice. For recordkeeping and anti-retaliation requirements, see 29 CFR 1904.35 and OSHA guidance.