Close Call Reporting: Building a Culture Where People Actually Tell You What Nearly Happened

The Information You Are Not Getting

The load that swung wide and missed. The board that gave way over a void with nobody on it. The reversing wagon and the operative who stepped back just in time. Long before a site has its serious accident, it has these — the same failures, rehearsing, with better luck. Close calls are the cheapest safety information in existence: complete accident causation, minus the injury, delivered free by witnesses. Every one reported is a chance to fix a cause while it costs nothing. Which makes the real question uncomfortable: on most sites, that information exists in the workforce's heads and never reaches anyone who can act on it. The gap is not awareness. It is culture — and culture, in this case, is built from surprisingly mechanical parts.

Why People Do Not Report

Ask operatives why they did not report a near miss and the answers repeat across every site in the country. Nothing happens — the last three cards went into the box and were never heard of again, so why write a fourth. It will come back on someone — on me for admitting I was in the wrong place, or on my mate whose strop it was, or on my company at the next supplier review. It is hassle — the form lives in the office, takes ten minutes, and asks questions written for an insurance file. It was nothing — the near miss normalised into "just one of those things" because it happens weekly. Each of these is a design flaw in the system, not a flaw in the workforce, and each has a specific fix.

Design the System People Will Use

Make reporting take a minute. Wherever the workforce is, with whatever is in their pocket — a phone photo and two sentences beats a beautifully structured form nobody fills in. Accept verbal reports through supervisors and have the supervisor log it; the information matters, not the authorship. Make it blame-safe and mean it. The first time a close call report turns into a disciplinary, the system dies for a year, and everyone will know within a day. Anonymous routes help, but visible fairness helps more: reports about behaviour get treated as reports about conditions that produced the behaviour. Chase the fix, not the number. Targets for report counts produce reports about gloves and puddles — impressive volume, zero information. What you want rewarded is quality: the report that surfaces a genuine trap gets praised publicly, whoever raised it.

The Feedback Loop Is the Whole Game

One mechanism decides whether reporting lives or dies: does the person who reported — and everyone watching — see something happen? Close the loop in three moves, every week. Acknowledge: every report gets a response to the reporter, fast. Act: each report gets an owner and an action with a date, tracked to closure like any other site action — including the honest "we looked, and here is why we are not changing it", which is still feedback. Broadcast: a weekly slot — the Friday briefing works — that says: here is what you raised this week, here is what we fixed, here is what is in progress. Ten minutes, names optional, fixes specific. Sites that run that loop see reporting climb month on month; sites that skip it watch the box empty out, and conclude wrongly that there is nothing to report.

Then use the data as data. One report is an anecdote; a register is a pattern. The same gate throwing up vehicle-pedestrian conflicts, reversing incidents clustering in one compound, strops and slings recurring across different gangs — trends tell you where the next accident is queuing, and they only appear if reports are logged somewhere that can count, filter and trend them rather than in a carbon-copy book.

What Good Looks Like

A healthy close call system has a texture you can feel. Reports arrive steadily, including from subcontractors, including about things that embarrass the site's own arrangements. The ratio of condition-fixes to "be more careful" outcomes is high. The workforce can name a change that came from a report — the relocated gate, the new one-way, the banned fitting — because those stories circulate. And the numbers hold up: reporting rate stable or rising, actions closed inside their dates, trends reviewed monthly with the same seriousness as programme and cost. None of it needs a slogan. It needs a one-minute reporting route, a genuinely safe reception, and a feedback loop that runs every single week — because the workforce already knows what nearly happened today. The only question is whether your site is set up to hear it.