Ask a safety manager to explain why a serious incident happened, and the honest answer is rarely simple. It's rarely one broken procedure, one missed check, or one person who got it wrong. It's usually a sequence of smaller failures that, on their own, wouldn't have caused any harm at all.
That's the idea behind the Swiss cheese model of safety failure, a concept safety professionals have used for decades to explain how incidents actually happen. It's also one of the clearest ways to understand where a spreadsheet fits into your organisation's real exposure to risk.
Slices, Not a Single Wall
Picture your organisation's defences against a safety incident as a stack of slices of Swiss cheese. Each slice represents a layer of protection:
- Your training programme
- Your certification checks
- Your site inductions
- Your supervision
- Your equipment maintenance schedule
- Your compliance records
No single slice is solid. Every layer has holes in it somewhere, because no system run by people is ever perfect. A training programme might have a gap in its coverage of a particular risk. A certification check might rely on paperwork that's slightly out of date. That's not a flaw unique to any one organisation. It's the nature of running complex operations at scale.
Under normal circumstances, those holes don't matter, because the slices are stacked. A gap in one layer gets caught by the layer behind it. The system holds.
An incident occurs when the holes in several slices line up at the same moment, allowing something to pass straight through every layer of protection at once.
Where the Spreadsheet Sits in the Stack
A compliance spreadsheet is one of those slices. Specifically, it's meant to be the layer that confirms a worker is trained, certified, and fit to be on site before anything else happens.
The trouble is that a spreadsheet's holes are larger and more persistent than most people realise. A version that's six weeks out of date. A subcontractor's certificate that was never verified against the file it should have landed in. A renewal that lapsed quietly in a row nobody was watching. Because a spreadsheet is a static snapshot rather than a live system, its holes don't shrink over time. They tend to grow, one uncaught update at a time.
When that layer is already weak, it takes far less for the other layers to line up around it. A supervisor who's stretched thin. A site induction that got rushed because of scheduling pressure. A near miss that almost happened last month and was never properly logged as a lesson learned. None of those individually causes an incident. Together, with a compliance record that can't reliably catch a gap, they can.
Why "Nobody Did Anything Wrong" Is the Uncomfortable Part
One of the more difficult truths about the Swiss cheese model is that it rarely points to a single culprit. Investigations into serious incidents in high-hazard industries frequently conclude that everyone involved was, individually, doing a reasonable job with the information and tools available to them. The failure was in how the layers combined, not in any one person's judgement.
That's a hard thing for an organisation to sit with, because it means the fix isn't disciplinary. It's structural. If your training records are one of the layers with a large, persistent hole in it, tightening supervision or running an extra briefing won't close that hole. Only a system built to actually catch the gap will.
Turning Near Misses Into a Closed Loop
The organisations that get the most value from this model don't treat it as a one-off diagnosis. They use it as a loop. When a near miss happens, and near misses happen far more often than serious incidents, the right response is to work out which slice let it through and how far the hole extends.
That requires records worth interrogating. A spreadsheet, reconstructed after the fact from whichever version happens to be nearest to hand, makes that kind of lessons-learned review slow and unreliable at exactly the moment speed and reliability matter most. A live compliance system, one that shows what was true at the time rather than what someone eventually typed in, makes the review meaningful.
Closing the Hole That's Yours to Close
Chorus doesn't claim to close every hole in your safety defences. Supervision, equipment, site conditions and a hundred other factors sit well outside what a training and compliance platform can influence.
What it can do is make sure the training and competence layer isn't the weak slice waiting to line up with everything else. Real-time visibility of who's certified, who isn't, and where a subcontractor's paperwork doesn't match reality removes one of the more common and most avoidable holes in the stack.
The slices will never be perfect. That's not the goal. The goal is making sure the one you're responsible for holds when everything else is under pressure.
Chorus helps hazardous industry operators turn training and competence into a slice that holds. If you want to understand where your current system's holes actually are, get in touch
Article tags:
