The Near-Misses You’re Not Hearing About

Most companies track incidents. Very few have a consistent near-miss reporting process. And most of the ones that say they do are really just tracking the near-misses that get reported — which is a fraction of the ones that actually happened.

What a Near-Miss Actually Is

A near-miss is a situation where something could have gone wrong, and didn’t. The load shifted but held. The worker stepped back in time. The spill happened away from the equipment. The outcome was fine.

Because the outcome was fine, most companies treat it as a non-event.

That’s the mistake.

The outcome was luck. The condition that created the situation wasn’t. And if the condition isn’t addressed, it sits there — waiting for the next time the outcome isn’t fine.

Why They Don’t Get Reported

Near-misses don’t get reported for predictable reasons.

Workers don’t want to slow production. Supervisors don’t want to create paperwork. Nobody got hurt, so it doesn’t feel worth raising. And in some companies — even ones where leadership says they want to hear about problems — reporting a near-miss has historically led to blame rather than correction.

That last one is the most important. If the culture around incidents is to find fault with the person rather than fix the condition, reporting stops. People learn quickly that the safest thing to do after a near-miss is say nothing.

So nothing gets said. The condition stays. And leadership is left believing the operation is safer than it is, because the silence looks like the absence of problems.

What the Silence Actually Tells You

When a company has few or no reported near-misses, there are two possible explanations.

One is that hazardous conditions almost never arise — which is unlikely in any real operation involving equipment, height, chemicals, or moving vehicles.

The other is that hazardous conditions do arise, but people aren’t reporting them.

The second explanation is almost always right. And if it is, the near-miss data isn’t missing because there’s nothing to report. It’s missing because the program isn’t capturing it.

That’s not a minor gap. Near-miss data is the earliest warning your safety program has. It’s cheaper than incident data, more plentiful, and more actionable — because the condition still exists and can still be corrected. Once it produces an incident, the window for prevention is closed.

The Question Worth Asking

If a foreman on your busiest crew had a close call last Tuesday, would you know about it today?

Not eventually. Not after someone mentioned it in passing. Today.

If the honest answer is “maybe not,” the program isn’t getting the signal it needs.

That’s not because your people don’t care. It’s because the program hasn’t made reporting easy, safe, and clearly connected to corrective action rather than blame.

What Changes When Near-Misses Get Captured

Companies that track near-misses consistently see patterns their incident logs never showed them. The same hazard appearing across multiple crews. The same piece of equipment involved in multiple close calls. The same shift, the same task, the same conditions — repeated until something finally goes wrong.

That pattern is visible long before the incident. But only if the near-misses are getting reported, recorded, and reviewed.

The incident is the expensive lesson. The near-miss is the cheap one. Most companies are paying for expensive lessons they could have avoided.

Don’t Wait for an Incident to Find the Gaps

Most safety programs aren’t missing incidents. They’re missing the data that comes before incidents; the near-misses that get shrugged off because nothing happened this time. That silence isn’t safety. It’s a signal your program isn’t set up to hear yet. The condition that almost caused a problem last Tuesday is still sitting there today, waiting for a different outcome.

See the 10 questions every owner should be able to answer about their safety program. 

Get clarity on what your safety program might be missing. See how Safety Plus can help you capture the signals that matter, identify risk earlier, and turn safety data into action before a near-miss becomes an incident.

Book a Demo.

Recommended Reading

The Anatomy of Defensible Proof

Oct 6, 2026

A project superintendent at a 90-person industrial contractor got a call the day after a serious incident. The company’s attorney needed documentation: training records for the three workers involved, the last inspection report covering that work area, and the corrective action log for any related hazards identified in the prior six months. The training records…

Insurance Reviews Are Not Inspections

Sep 28, 2026

Most owners think about audit-readiness as one thing. Pass the OSHA inspection, stay current on prequal requirements, keep the insurance renewal from getting complicated. One program, built to satisfy whoever happens to be asking. That framing is really the problem. An OSHA inspection, an insurance review, and a GC prequal evaluation are three separate assessments…

Why Binders Fail Under Pressure

Sep 22, 2026

Picture the owner of a 60-person specialty contractor the morning an OSHA inspector shows up unannounced. He knows the safety program is in decent shape. The policies are written. Inspections have been happening. Training got done before the last big project kicked off. He walks to the filing cabinet, pulls out the binder, and hands…

Luck Is Not a Safety Record

Sep 8, 2026

Most owners know whether their safety record is good. Fewer of them know whether their safety program is good. Those are different things — and confusing one for the other is one of the more expensive mistakes in safety management. The Company With No Incidents and No Program This company exists. You may know one.…

SAFETY MANAGEMENT SIMPLIFIED

Prevent Tragedy and Scale Effectively by Making Safe Work Efficient