Everyone knows the reportable incidents. The harder job is the one before that — recognising, recording and triaging every incident that happens, including the ones that turn out to be nothing. Here's what good triage looks like, and why it's where your incident system quietly succeeds or fails.
The Accorda Team · 14 September 2026
Something happens on a Saturday night shift. A support worker isn't sure it "counts" — nobody was hurt, it sorted itself out, and the person who'd know the rules doesn't start until Monday. So it doesn't get written down. Three weeks later, in a slightly different form, it happens again.
If that scenario makes you wince a little, you're not alone. Most providers have a clear picture of what a reportable incident is and how fast it has to be reported. The harder, quieter part of incident management is everything that happens before that: recognising that something is an incident at all, capturing it properly in the moment, and working out what to do with it. That's triage — and it's where good incident systems either hold together or quietly come apart.
The reassuring news is that none of this requires more heroics from your team. It requires the incident to have somewhere sensible to land, and a consistent way of sorting it once it's there.
It's easy to think incident management is reportable-incident management, because that's the part with the deadlines attached. But your obligation is broader than the reportable subset — across every framework, you're expected to capture and manage the whole picture.
For registered NDIS providers, having an incident management system is a condition of registration. It has to capture all incidents — not only the ones that must be notified to the NDIS Commission. Reportable incidents are a specific, serious subset that must additionally be reported within set timeframes; the rest still need to be recorded, managed and resolved.
Aged care is just as explicit. Under the strengthened Quality Standards, the outcome statement requires that a provider "must use an incident management system to safeguard individuals and acknowledge, respond to, effectively manage and learn from incidents." The Commission's guidance spells out that providers must "record, investigate, respond to and manage incidents and near misses," that "incidents can be clinical or non-clinical" and "can also relate to worker safety," and that you need clear processes to "acknowledge incidents, record incidents, assess and investigate incidents." Note the near misses — the things that could have caused harm but didn't. Those count too.
Early childhood services under the National Quality Framework record incidents, injuries, trauma and illness, notify parents as soon as practicable, and notify the regulator of serious incidents — a child's death, a serious injury or illness requiring urgent attention, any emergency that brings emergency services — generally within 24 hours.
Different sectors, same underlying expectation: everything gets recorded, the serious things get escalated, and you can show what you did with all of it.
The dangerous incident usually isn't the one you reported a bit late. It's the one nobody recognised as an incident at all — so it was never written down, never assessed, and never fixed.
Triage is a word borrowed from emergency medicine, and it fits. It's the sorting step: an incident comes in, and someone works out how serious it is, what category it falls into, whether it has to be reported, and what needs to happen next.
In a care setting that means running each incident through a few quick questions. What actually happened, in plain terms? Who was involved, and was anyone harmed — or could they have been? What kind of incident is it? How serious is it? Does this cross the line into a reportable incident? And who owns the follow-up?
Do that consistently and a pile of "somethings" becomes an ordered list you can act on. Skip it, and you're left with a drawer of half-remembered events that all look equally urgent and equally ignorable.
Here's the catch that trips up good providers: the person who witnesses an incident is almost never the person who knows the reporting rules. It's a support worker at the end of a long shift, a new casual, someone on their phone in a client's lounge room right after something went wrong. Expecting them to also be a compliance expert in that moment is where the system asks too much.
When incident systems fail, it's rarely a dramatic failure. It's usually one of four quiet ones.
It never gets recorded. The person on shift didn't recognise the event as an incident, or wasn't sure, so it stayed a hallway conversation. You can't triage what you never captured.
It's captured inconsistently. Everyone writes free-text in their own style, with no categories and no severity, so two similar incidents look nothing alike and patterns are invisible.
The reportable one isn't spotted in time. It sits in an inbox or a notebook until someone senior happens to read it — and by then the clock has been running for two days.
Nothing happens next. It's logged, but no one owns the follow-up, the cause is never addressed, and the same thing happens again.
Notice that only one of those is about reporting deadlines. The other three all live in the triage step — the part with no external clock forcing your hand, which is exactly why it's the part that slips.
A triage process that holds up has a few plain features, and none of them are complicated.
It's easy to capture in the moment — quick enough that a stressed worker actually uses it, rather than promising to "write it up later" (which becomes never). It's categorised consistently, so every incident carries a type and a severity and can be compared with the others. It surfaces the reportable ones fast, so nothing serious sits unseen while a deadline ticks. Every incident has a clear owner and a next action, tracked until it's genuinely closed. And the whole set gets reviewed for patterns, because three minor incidents of the same kind are trying to tell you something.
That last point is what regulators mean by continuous improvement. As the aged care guidance puts it, you investigate to "find and manage the underlying cause of an incident and prevent it from happening again," and you "look for trends to find organisation-wide issues." Triage done well is what makes that possible — you can only spot a trend across incidents you actually recorded and sorted.
This is the part of incident management Accorda was built for, so let's be precise about the boundary.
Accorda gives your team a deliberately simple quick-report form — the kind of thing someone can complete on a phone, one-handed, right after a difficult shift. The AI then structures that hurried free-text into a proper, categorised record, so a rushed note doesn't become an unusable one. When a manager triages the incident, the system flags whether it looks reportable and why — assistive, never silently authoritative. Corrective actions, each with an owner and a due date, hang off the incident and are tracked to close-out. The record sits behind tamper-evident integrity, so the timeline of what you knew and when you acted holds up later. And when an audit comes, the incident register pulls into a one-click evidence pack.
What Accorda does not do is make the reporting call for you or submit the notification to the regulator on your behalf. Deciding that something is a reportable incident is a judgement your team owns, and the report goes in through the regulator's own channels. No compliance software should pretend otherwise. What Accorda does is make sure nothing gets lost on the way there: that incidents actually get captured, that they're recorded consistently, that the serious ones surface quickly instead of sitting in someone's inbox, and that you can prove what you did.
You handle the incident. Accorda makes sure it was caught, sorted properly, and easy to show.
Pull up your incident records for the last month and ask three questions. Could you show every incident that happened — including the ones that turned out to be nothing — not just the reportable few? For each one, could you say what category it was, how serious, and who owned the follow-up? And if a similar incident had quietly happened three times, would anyone have noticed?
If those answers come easily, your triage is doing its job. If they don't, that's not a reflection on your team — it's a sign the incident needs a better place to land, and a consistent way to be sorted once it's there. That's a fixable problem, and fixing it is the difference between having a pile of incident notes and having an incident system.
Incident management — NDIS Quality and Safeguards Commission
Reportable incidents — NDIS Quality and Safeguards Commission
Incident management — Aged Care Quality and Safety Commission (strengthened Quality Standards)
An introduction to the SIRS — Aged Care Quality and Safety Commission
This article is general information only, current as at September 2026, and is not legal or compliance advice. Regulatory requirements can change.
Start today
Try Accorda free for 14 days. Every feature, no credit card, no auto-charge.
