Lessons from safety incidents that did not make headlines

Construction is very good at learning from the big failures. When something catastrophic happens, when there is loss of life, when there is a major structural collapse, the industry responds. Investigations are launched, reports are written, guidance is updated and behaviours change. These events shape regulation and redefine standards, but those are not the incidents that define day-to-day risk, writes John Ridgeway.

The vast majority of problems in construction never make the news. They don’t lead to public inquiries or industry-wide reform. They are smaller, contained, often resolved quickly and quietly. A connection installed incorrectly. A temporary works decision made under pressure. A detail that doesn’t quite work as intended. A sequence that causes a near miss rather than a failure. Individually, they seem minor, but collectively, they tell a much more important story.

On most projects, there are moments where things could have gone differently. A load is misjudged, but corrected in time. A clash between trades is discovered before it becomes critical. A safety issue is spotted just before it leads to an accident. A material performs slightly differently than expected, but not enough to trigger formal reporting.

These are not failures in the traditional sense. They are often absorbed into the programme, resolved through experience and moved on from quickly and that is precisely the problem, because what gets absorbed rarely gets analysed.

Near Misses Are Not Minor Events

In many industries, near misses are treated as seriously as actual incidents. They are recorded, investigated and used as a primary source of learning. In construction, they are often handled informally, with a conversation on site, a quick adjustment, or a note to “keep an eye on it next time.”

The job moves on, but a near miss is not a sign that everything is fine. It is evidence that something nearly went wrong. It reveals a weakness in design, coordination, sequencing, or decision-making. If that weakness is not properly understood, it remains in the system, waiting to reappear under slightly different conditions.

When you look closely at incidents that don’t make headlines, patterns begin to emerge. They are rarely caused by a single failure. More often, they are the result of small compromises that build over time.

Information that arrives late. Details that are not fully resolved. Assumptions made between disciplines. Decisions taken to maintain programme. Changes introduced without full coordination. None of these are unusual. In fact, they are part of everyday construction, but when they combine, they create the conditions for failure.

The difference between a near miss and a serious incident is often not the nature of the problem, it is timing, context and a degree of luck.

There are understandable reasons why these incidents are not formally captured. Projects are under pressure. Time is limited. Teams move quickly from one issue to the next. There is also a natural reluctance to document problems that didn’t result in failure, particularly when they have been resolved, but in not capturing them, we lose something valuable.

We lose the opportunity to understand how risk actually manifests on site, not in theory, but in practice. We lose the chance to identify recurring issues before they escalate and perhaps most importantly, we lose insight into how decisions are really made under pressure.

Experience vs Systematic Learning

Construction relies heavily on experience. Good people spot problems early, make adjustments and keep projects moving. That experience is invaluable, but it is also inconsistent.

What one experienced site manager identifies immediately, another may not. What one team resolves effectively, another may struggle with. Without a structured way to capture and share learning, knowledge remains with individuals rather than becoming part of the wider system. This is why the same types of issues continue to appear across different projects, different teams and different organisations.

If the industry wants to improve, it cannot rely solely on learning from major failures. Those events are too rare and too extreme to reflect everyday reality. The real opportunity lies in the incidents that almost happened. This does not require complex systems or additional bureaucracy. It starts with a change in mindset:

• Treat near misses as valuable data, not minor interruptions
• Create space to reflect on what nearly went wrong
• Look for patterns, not isolated events
• Share insights across teams, not just within projects

These are small shifts, but they change how risk is understood.

The most important lessons in construction are often the ones that never needed to be learned the hard way. The connection that held, but only just. The sequence that worked, but created tension on site. The decision that solved the problem, but introduced a new risk elsewhere.

These moments rarely appear in reports. They don’t attract attention, but they are where the real understanding of construction risk lives. If we start paying closer attention to them, we move from reacting to failure to anticipating it and that is where meaningful improvement begins.