Why Your Incident Reports Say Nothing Happened
Rustom Sutaria 
A blank incident log doesn't mean nothing happened. It means nobody wrote it down. Here's why that silence should worry you.
Why Your Incident Reports Say Nothing Happened
It's the Tuesday safety review. The dashboard is up on screen, showing zero incidents this month and zero near misses. Someone in the room looks relieved.
Two floors down, on the hangar floor, your Engineer or your Technician has just re-torqued a fastener they weren't fully sure about, signed it off and moved on. They didn't write anything up. In their minds it wasn't a violation, and it wasn't worth mentioning. It was just Tuesday.
That gap, between what your dashboard shows and what your Engineers & Technicians actually know, is the real story. Not the one on the page. The one underneath it.
A blank report is not the same as a clean one.
When did you last read an incident report that genuinely unsettled you?
Not a late submission or a minor procedural slip, but something that told you how work really gets done on a difficult shift under critical time pressure.
If it's been a while, that's worth serious contemplation. It might mean your operation has quietly become safer. It might also mean your people have learned that reporting doesn't change much, or that it's easier not to be the one who speaks up.
A blank log doesn't tell you nothing happened. It tells you nobody wrote anything down. Those aren't the same thing, and it's easy to let one stand in for the other without noticing.
How the silence builds up
None of this starts with anyone deciding to stop reporting. It builds from small choices that each seem reasonable at the time.
Your Engineers & Technicians skip a report because nothing came of the last one.
Your supervisor lets a shortcut go because raising it feels like more trouble than it's worth.
You read a clean risk register, and understandably, take it as good news!!
On their own, none of these choices look like a problem. Together, over months, they produce a system that looks calm on the surface while the actual conditions underneath go unrecorded.
This industry talks a lot about the Swiss Cheese model and the holes in your defences. What gets said less often is that those holes are usually invisible to you specifically, because the people who could point them out have decided it isn't worth the conversation.
Why it costs more than it looks like
If a regulator or investigator ever sits across from you after something has gone wrong, they won't be interested in how tidy your system looked beforehand. They'll want to know what you knew, when you knew it and why you didn't know sooner.
"We had no reports" doesn't land as reassurance in that room. It can sound like evidence that your organisation wasn't set up to hear what it needed to hear.
That's the fear worth naming honestly: not that something will go wrong, but that when it does, the truthful answer to "did you know?" turns out to be "we should have."
A compliant system and a genuinely safe one aren't automatically the same thing. The gap between them tends to stay hidden right up until the point it costs the most.
The question worth asking yourself
You can't act on what your people aren't telling you, and a green dashboard on its own won't tell you whether that's because things are genuinely fine, or because everyone has quietly agreed it's easier not to say.
So before the next safety review, it's worth asking honestly: if something were wrong in your organisation right now, would you actually hear about it from your Engineers & Technicians, or would you find out afterwards, in a room where the questions are no longer friendly?
Categories: : Safety Culture, Just Culture