Luck Is Not a Safety Record
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.
No recordables in three years. Low EMR. Clean prequal submissions. The owner believes it’s because the company is careful, the crews are experienced, and everyone takes safety seriously.
All of that may be true.
It’s also possible that the operation hasn’t had an incident because it hasn’t had a bad day yet — not because it’s structurally protected against one.
Those two explanations look identical from the outside. They don’t look identical on the day the bad day arrives.
What Luck Looks Like in a Safety Program
Luck in a safety program looks like safety.
The near-misses that go unreported create the impression that conditions are better than they are. The hazards that haven’t yet produced incidents don’t show up on the OSHA 300 log. The training gaps that haven’t been tested yet don’t appear in the records.
The program looks clean because the record is clean — and the record is clean partly because nothing bad has happened yet.
That’s a reasonable outcome to have. It’s not a reasonable thing to rely on.
The Company With One Incident and a Strong Program
This company looks worse on paper — for now.
One recordable. EMR ticking up. A prequal submission that requires explanation.
But behind that incident record is a program that captured near-misses, investigated to root cause, closed corrective actions, and produced a documented improvement. The incident revealed a gap. The gap got fixed. The program is stronger because of it.
Over three to five years, this company’s record and program converge. The incident rate comes down because the program was designed to learn from failures. The EMR improves because the program reduced frequency and managed workers’ comp claims well. The prequal conversations become easier because there’s evidence of a systematic response rather than a blank claim of safety culture.
Luck Corrects
A safety record built on luck doesn’t hold. The conditions that create near-misses eventually produce incidents. The hazards that go unaddressed eventually find a day when the outcome is different.
When that happens, the company without a program scrambles — because nothing about its past success prepared it for a real response. The OSHA visit, the insurance conversation, the client inquiry — all of them arrive at once, and the answer to every question is a version of “we’ve always been careful.”
That answer doesn’t hold up. Careful isn’t a program. It’s a posture.
What the Difference Looks Like in Practice
The owner who runs a program knows:
- What the highest-risk hazards in the operation are, right now
- Which corrective actions are open and how long they’ve been open
- Whether training is current for the work that’s being done
- What the near-miss data is telling them about conditions
The owner who’s been lucky doesn’t have those answers — and hasn’t needed them yet.
The question isn’t whether you’ve been lucky. Most companies have, at some point.
The question is whether you’re building a record or building a program. One of them holds up when things stop going right.
Record vs. Program
Being lucky isn’t a failure. Most companies have gone years without a bad day and never had to find out what they were actually standing on. But luck isn’t something you can point to when someone asks what you’d do differently, and it isn’t something that holds up the day it runs out. A program is something you can point to. It’s the difference between explaining your safety after the fact and proving it before anyone has to ask.
Access the 10 questions every owner should be able to answer about their safety program.
Safety Plus can help you see where your program stands today, where the gaps are, and what it would take to build a safety system you can rely on, before a bad day puts it to the test.
Recommended Reading
How Safety Failures Cascade
Safety failures rarely arrive alone. That’s the part most owners miss — not because they haven’t thought about safety, but because the sequence isn’t visible until after something goes wrong. A near-miss doesn’t get reported. The hazard stays open. The hazard eventually produces an incident. The incident produces an OSHA visit with citations and fines.…
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…
When the Market Will Not Push, You Have To
Some companies get pushed into good safety. The rest have to push themselves. The discipline is the same; the only question is who supplies it. If you are a contractor working for a major general contractor, you do not have to be disciplined about safety. The GC is disciplined for you. They audit, they require…
Persistent vs. Perishable Safety Programs
If your program only exists because of one OSHA visit, you do not have a program. You have a hangover. There are two kinds of safety programs, and most owners cannot tell which one they have until it is gone. Persistent programs are held up by something outside the building A persistent program has a…
SAFETY MANAGEMENT SIMPLIFIED
Prevent Tragedy and Scale Effectively by Making Safe Work Efficient