The Near Miss That Never Made the Report
For all its improvements over the years, incident reporting culture is still built around outcomes. Something breaks, someone gets hurt, a vehicle is damaged, and then there's a form, an investigation, a root cause identified, and changes made.
A system solely designed to respond after the fact, rather than to gather information that can lead to prevention.
This is the reporting gap: the information from events most useful for prevention fail to get reviewed and acted on.
The numbers behind the near miss
The safety literature has been consistent on this for decades, regardless of which version of the accident triangle you were taught. For every serious injury, there are minor incidents, and sometimes dozens of near misses sitting beneath them.
The exact ratios vary by study and industry, but the shape never changes. Near misses vastly outnumber the incidents that make it onto a form, and they share the same root causes.
Here’s an example of what we’re illustrating:
|
Outcome |
Number |
|
Fatal injury |
1 |
|
Serious/major injury |
207 |
|
Over-3-day injury |
1,402 |
|
Minor injury (≤3 days) |
2,754 |
These figures illustrate the same principle as Heinrich’s safety triangle; that severe injuries are accompanied by many less-serious events, but they're based on UK data (HSE).
Reversing vehicle incidents remain one of the most consistent causes of fatality and serious injury across a wide range of industries, and the same conditions that produce a fatal strike also produce a hundred near misses that thankfully never get near a fatality.
The near miss isn't a lesser version of the accident. It's the same event, minus the moment the driver happened to check the mirror at the right second, or the worker happened to step the right way.
Treat it as luck, and luck runs out, but treat it as the valuable data it is, and it becomes the earliest possible warning system you have.
What actually goes wrong, most of the time
Talk to enough site managers and a pattern emerges. It's rarely a single dramatic failure. It's usually a small, repeatable communication breakdown:
· A hand signal given in low light, half-seen through a dirty windscreen or mirror
· A worker assuming the driver has clocked them, when the driver hasn't
· A banksman signalling with a dark coloured glove that blends into a dark uniform or the background
· A driver routinely reversing out of habit, a familiar route, on the assumption that nothing's changed since yesterday
None of these are equipment failures or procedural violations in the way an incident report likes to categorise things. They're gaps in the moment-to-moment communication between the person on the ground and the person behind the wheel.
And because nothing went wrong, they rarely get flagged as a problem worth fixing, even though they're the exact conditions a serious incident grows out of.
Building a culture where the close call gets said out loud
Getting near misses reported isn't really a paperwork problem. It's a culture problem, and it comes down to three things.
Make it quick
If reporting a near miss takes as long as reporting an actual incident, it won't get done. A quick chat at a toolbox talk, a quick note on a phone, a tally on a whiteboard: Any quick low friction action outside a full form will help bring more incidents to the forefront.
Make it blame-free
The fastest way to kill near-miss reporting is to treat it as a confession. If a worker believes that saying "the wagon nearly didn't see me" will lead to a conversation about what they did wrong, they won’t ever say anything. The point of the report isn't to find fault. It's to find the pattern before the pattern finds a person.
Make it visible
When a near miss does get reported, close the loop. Show the team what changed because of it. A different reversing route, a toolbox talk, a piece of kit swapped out. Nothing kills future reporting faster than a report that visibly goes nowhere.
The fix is often smaller than the risk
It's worth saying plainly: most near misses involving reversing vehicles trace back to the same root cause: A signal that wasn't seen clearly enough, quickly enough, by the person who needed to see it. That's not a training problem or a procedural failure so much as a visibility problem, in the literal sense.
A hand signal is only useful if it's unmistakable against the background it's given in, in the light it's given in, at the distance it's given from.
That's a fixable problem, and often a cheap one. High-contrast, high-visibility glove design exists specifically to make sure a signal is read as a signal, not just another shape in a driver's peripheral vision on a wet Tuesday morning.
It won't rewrite a site's whole safety culture on its own, but it removes one of the most common single points of failure in the chain that turns a near miss into an actual one.
The report that's worth writing
The near miss that never made the report is trying to tell you something for free. It's the version of the incident that cost nothing: No injury, no downtime, no investigation, and still contains everything you'd need to know to stop the next one.
The sites that treat those two seconds as data, not luck, are the ones where the near miss stays a near miss.
Author: Len Bridgeman
Sources:
https://www.hse.gov.uk/pubns/near-miss-book.htm
https://www.hse.gov.uk/pubns/priced/hsg101.pdf