Don’t Be Scared of Your Incident Register

I’ve sat across the table from a lot of providers clutching their incident register like it’s a speeding ticket. “It’s a bit… full,” they whisper, as if I’m about to call the Commission on speed dial.

Let me put your mind at rest with the single most reassuring sentence in this whole field:

a full incident register is a good sign.

Yep. Read it again.

Auditors and quality folk do not get nervous when they see incidents. We get nervous when we open a register that’s emptier than a Bunnings snag stand at 4:55 on a Sunday. Because an empty register almost never means nothing happened. It means nothing got written down. And a culture that doesn’t write things down is a culture that isn’t looking — and the things you’re not looking at are exactly the things that bite you.

Incidents are not evidence you’re failing. They’re evidence you’re awake. Every entry is a little flare going up saying “we noticed, we recorded, we did something.” That’s the whole point of the Incident Management Rules — not to make incidents disappear, but to make sure that when they happen, your organisation actually responds, learns, and doesn’t quietly repeat them next Tuesday.

The fear, I think, comes from a maths error. People assume fewer incidents recorded equals fewer incidents occurring. Nope. It usually just equals fewer incidents recorded. The participant who slipped still slipped. The medication error still happened. You’ve just chosen not to know about it, which is the worst of both worlds — you carry the risk AND you carry the surprise.

Here’s the reframe I want tattooed on your team’s brains: a recorded incident is a problem you can manage. An unrecorded one is a problem that’s managing you.

So go on. Open the register. Look at it. If it’s busy, good — that’s a team that’s paying attention. Your job isn’t to make the numbers small. It’s to make the learning big. Find the patterns, fix the causes, close the loop. A register that breathes is a register that protects you.

Now, one fair caveat before you go full send — because this cuts both ways. There’s a world of difference between recording incidents internally and reporting them up to the Commission. A busy internal register is healthy. But lodging reportable incidents “just in case,” every time someone’s a bit unsure, is not the flex people think it is. Over-reporting when in doubt usually means one thing: your team isn’t clear on what actually meets the threshold. Clarity, not volume, is the goal.

And if you’re genuinely lodging a stack of reports that do meet the threshold? That’s not a gold star either. That’s a flashing sign on the dash saying “time for some trend and causal analysis.” A high volume of legitimate reportables means something upstream is generating them — a setting, a roster, a cohort, a practice — and your job is to go find it, not just keep filing the paperwork.

Stop treating it like a confession booth. Start treating it like a smoke alarm. You want it going off before the kitchen’s on fire.

If your register’s giving you the jitters — or your reportables are climbing and nobody’s asking why — I can help you read it like a pro and build the trend analysis behind it. Grab a time on my Calendly.

Book a FREE Consult and Let's Look at Your Reports