Chapter 03
Near-miss loops
How to take near-miss reporting from a logging exercise to a closed loop that visibly changes the way the site behaves.
01
Why near-miss data is mostly wasted
Most projects collect near-miss data and then waste most of it. The reports are filed, classified into categories, counted on a dashboard, and forgotten. The pattern goes nowhere because nobody returns to it. The workforce sees that reporting a near-miss produces no visible change, and reporting volume drops over the months. By the time a real incident occurs, the leading indicators were in the data for weeks, but no one was reading them. The captured base offers a way to bind a near-miss to a captured view, which makes the report much harder to forget. A near-miss with a thirty-second clip attached to it is a finding the next safety meeting can return to without ambiguity. The clip is also what changes the conversation with the workforce: when a banksman sees that their report led to a visible review and a change, the next report is more likely to come in. Reporting culture is built by the closeout, not by the campaign.
02
Mechanics of a near-miss that closes
A near-miss closes when a corrective action has been taken and recorded. The corrective action does not need to be large. It might be a refresher toolbox talk for the affected crew, a change in the lay-down arrangement, a permit rewrite that adds a control, a stand-down on the activity until the controls are visibly back in place, or a scope change for a piece of plant. What matters is that the action exists, that someone is named, that it is evidenced when it is done, and that the near-miss is then explicitly closed in the system. Without that closure step, the near-miss becomes a number on a dashboard and nothing more. With it, it becomes a learning the team can repeat. The captured base supports the loop by holding the original clip alongside the corrective action evidence, so the before and after are stored together. A near-miss that lives without its closure is a debt that the project carries into its next quarter.
03
The recurrence pattern
Across a project, the same near-miss often happens in the same area or on the same package, often with the same control failing. A pattern of helmets-off during deck pours on level four, three weeks running, is not a finding — it is a programme of work. A pattern of vehicle-pedestrian close calls at the same gate, four times in a month, is a layout problem rather than a behavioural one. The captured base makes the pattern visible because the records are tagged by location and activity. The site leader who reads the near-miss summary weekly, with location and package overlays, will see the pattern emerge before it becomes an incident. The portfolio leader who reads it monthly across projects will see organisational patterns — the same subcontractor, the same activity type, the same time of day — that no individual site can see. Pattern detection is one of the few places where reporting volume actually pays back.
04
Workforce trust and the failure modes
The credibility of the near-miss loop depends on what the workforce sees. If reports lead to visible action and visible change, reporting volume sustains. If reports lead to disciplinary action against the reporter, reporting collapses within weeks and the project flies blind. The standard failure modes are: classification without action, action without evidence, action that punishes the reporter, and a meeting cycle that never returns to the previous week's items. The discipline is the reverse of all four — explicit action, evidenced closure, a clear no-blame stance for honest reports, and a meeting cycle that always opens with last week's open items. Done consistently, the near-miss loop becomes the most useful leading indicator the safety system has.
Practice
01. Pull the near-miss reports from the past quarter and overlay them on a site plan by location and activity. Identify the top three patterns of recurrence.
Look for: A simple plan with dots or counts, and three written patterns. Typical patterns include a delivery yard with vehicle-pedestrian incidents, a working-at-height activity with edge protection issues, and a lifting area with exclusion zone breaches.
02. Draft a short note to the workforce explaining what happens to a near-miss after it is reported. Keep it under one page and write it in plain language a foreman will accept.
Look for: A page covering: how to report, what review looks like, the no-blame stance for honest reports, and an example of a recent near-miss that produced a visible change. The example matters more than the policy.
Checkpoint
For the last three near-misses on your project, can you show the closeout evidence and any pattern of recurrence you noticed?
Recommended reading