Internal audits that find problems worth fixing
There’s a belief about internal audits that I run into on nearly every site, and it’s doing a lot of damage. It goes: a good audit is one that comes back clean.
It’s exactly backwards. An audit that finds nothing hasn’t proved your system works. It’s proved your audit doesn’t.
“We passed, so we’re fine”
A clean report feels like a result. The folders are there, the training’s been done, nobody’s been hurt lately, so the audit says what everyone expected it to say and the meeting’s over in twenty minutes. The trouble is you’ve tested the filing, not the work.
Passing an internal audit that only ever asks “have you got a procedure for this?” tells you a procedure exists. It tells you nothing about whether anybody follows it. Those are wildly different things, and only one of them will save you when something goes wrong.
It’s the same gap that catches firms out at certification. When I’m getting an ISO system ready for its audits, the internal ones are where the real work happens. They’re the only chance you get to find the problem before somebody else finds it for you.
“Auditing is about catching people out”
This one’s why your team goes quiet the second you walk on with a clipboard.
If people think an audit is a hunt for someone to blame, they’ll show you the tidy version. You’ll get the machine that was cleaned this morning and the operator who’s been told what to say. You’ll come away with a clean report and no idea what actually happens on a Tuesday afternoon in week three.
I’ve never found the fear approach gets you anywhere useful. Ask people what gets in the way of doing the job properly and you’ll hear things that never make it into a report. A guard that’s awkward so it comes off. A form that gets filled in at the end of the week from memory. That’s the good stuff. That’s what you came for.
“Follow the checklist”
A checklist is a floor, not a ceiling. If your audit never leaves the list, it’ll never find anything the list didn’t already anticipate, and the list was written by someone who didn’t know what was going to go wrong either.
Pick something real and follow it all the way through instead. Take one actual job, one actual delivery, one actual near miss, and trace it from start to finish. Does the paperwork match what happened? Where did it drift? That’ll teach you more in an hour than a day of ticking.
What a good one leaves behind
A good audit leaves you with a short list of things that are genuinely wrong, in enough detail that somebody can act on them. Not “housekeeping requires attention.” What, where, why it matters, who’s sorting it, by when.
And if you keep finding the same thing, stop writing it up as a finding. It isn’t a finding any more, it’s a design problem, and you need to fix the process rather than keep recording that people aren’t following it.
So here’s what I’d do this week. Take your last internal audit report, find the cleanest section in it, and go and look at that job yourself. If the two don’t match, you’ve learned something about your auditing, not just about the job. Our checklists are free to work through if you’d rather start with something in front of you than a blank page.