The Sane Perspective - October 2026
Updated: Oct 26

⚠️ Near misses: the warnings we can't afford to ignore
“Nobody was hurt.”
It’s often one of the first things we say after a near miss.
And of course, that’s a good outcome.
But I don’t think it should be the end of the conversation.
During my time working in construction, I’ve reviewed situations where the difference between a near miss and a serious incident has been uncomfortably small.
A person was somewhere slightly different.
Something fell in a different direction.
Someone noticed at the right moment.
Or circumstances simply worked in our favour.
When that happens, I think we need to ask a different question:
What actually stopped someone from getting hurt?
Was it one of the controls we had put in place?
Did somebody recognise the danger and intervene?
Or, if we're being realistic, were we simply lucky?
That distinction matters.
🔍 Reporting is only the beginning
We rightly encourage people to report near misses.
But recording one on a system and raising a corrective action doesn't necessarily mean we've learnt from it.
For me, the value comes from understanding why it happened in the first place.
What was planned?
What actually happened?
What was different?
Had something changed during the work?
Were the controls practical?
Was the work being adequately supervised?
And perhaps most importantly, what do the people involved think happened?
Those conversations often tell us far more than the form itself.
🗣️ How we respond matters
If we want people to report near misses, we also need to think about what happens when they do.
Imagine an operative raises something that nearly went wrong.
What's our first reaction?
Do we listen and try to understand?
Or do we immediately start looking for who made the mistake?
Accountability matters, but so does creating an environment where people feel comfortable telling us when something hasn't gone to plan.
Because if reporting a near miss becomes an unpleasant experience, there's a risk the next one simply doesn't get reported.
And then we've lost an opportunity to learn.
👷 Talk to the people doing the work
This is something I keep coming back to in my work.
The people closest to the task often understand the practical problems better than anyone.
They know if access is difficult.
They know if the sequence isn't working.
They know if two trades are getting in each other's way.
They know when the method described in the RAMS doesn't quite reflect what they're actually having to do.
So after a near miss, I'd always want their involvement.
Not simply:
“Here's what we've decided needs to change.”
But:
“What happened?”
“What made the job difficult?”
“What could we do differently?”
Sometimes the answer will be obvious.
Sometimes it won't.
But we're far more likely to understand what really happened if we involve the people who were there.
📋 The answer isn't always more paperwork
There can be a tendency after something goes wrong to add another control, another form or another procedure.
Sometimes that's absolutely necessary.
But not always.
The answer might be better planning.
It might be changing the sequence of work.
Providing different equipment.
Improving access.
Strengthening supervision.
Separating trades.
Or simply having a better conversation before the task starts.
I've become increasingly conscious that more paperwork doesn't automatically mean we've reduced the risk.
What matters is whether something genuinely changes on site.
🔄 Close the learning, not just the action
This is probably the part I think we can sometimes do better.
An action gets raised.
Someone completes it.
The action is marked closed.
Job done.
But has the learning travelled any further?
Could another Trade Contractor face the same issue?
Could the same situation exist elsewhere on the project?
Is there something worth sharing with another project entirely?
A near miss gives us information without somebody having to pay the price of an injury.
We should make the most of it.
And if the same type of near miss keeps happening, despite actions being closed, then perhaps we're dealing with the symptoms rather than the cause.
💭 Learning before someone gets hurt
For me, this is what near-miss reporting should ultimately be about.
Not statistics.
Not increasing the number of reports because it looks good on a dashboard.
And not completing another form simply because the procedure says we should.
It's about recognising that something nearly happened and using that opportunity to prevent it happening again.
I'd much rather have a difficult conversation after a near miss than have the same conversation after somebody has been injured.
So perhaps the most useful question isn't:
“Who was responsible?”
Maybe we should start with:
“What can this teach us?”
Because a near miss is only valuable if we do something with what it tells us.
The opportunity is there to learn before someone gets hurt. The question is whether we're prepared to use it.
💭 Do you think we get enough value from near-miss reporting in construction, or are we sometimes too focused on recording and closing the action?
🦺 At Sane Health & Safety Ltd, I work alongside project teams and contractors to provide practical, proportionate health and safety support, helping organisations learn from what happens on site and turn those lessons into meaningful improvements.
If you need support with incident and near-miss reviews, safety tours, audits, RAMS or general construction health and safety, feel free to get in touch.
📱 07816 897342
Advise | Assure | Add Value



Comments