When an incident happens, a regulatory clock starts — and it's often just 24 hours. Here's how to capture, triage and close out incidents so you never miss a reportable deadline.
The Accorda Team · 23 June 2026
The moment something goes wrong in a care setting, two clocks start at once.
The first is the one everyone feels: care for the person involved, make them safe, calm the situation. That instinct is strong and it usually works.
The second clock is quieter, and it's the one that catches providers out — a regulatory countdown that, for the most serious incidents, gives you just 24 hours. It doesn't wait for the dust to settle, for the right manager to be back on shift, or for someone to find the time to write things up properly. And in many cases it starts the moment a staff member becomes aware of the incident, not when you're ready to deal with it.
This article is about that second clock: the deadlines you're actually working against, where incident handling tends to break down, and what it takes to log, triage and close out incidents without missing one.
Every incident asks two things of you. Respond to it — make people safe, provide support, start putting things right. And account for it — record what happened, work out whether it has to be reported, notify the regulator within the timeframe, investigate, and act so it doesn't happen again.
The first job is care, and care providers are good at it. The second is compliance, and it's where the pressure quietly builds: a tight deadline, a judgement call about whether an incident is "reportable," and a paper trail that has to hold up months later. Get the care right but the reporting late, and you can still end up facing a compliance finding.
The exact obligations depend on your sector, but the shape is the same everywhere: a short, strict window that starts on awareness.
NDIS providers. Under the NDIS (Incident Management and Reportable Incidents) Rules 2018, most reportable incidents — death, serious injury, abuse or neglect, unlawful sexual or physical contact, and sexual misconduct — must be notified to the NDIS Commission within 24 hours of the provider becoming aware. The unauthorised use of restrictive practices has a separate window of 5 business days, unless it caused harm, in which case the 24-hour clock applies. A fuller report follows. Crucially, the clock starts when a manager or key personnel become aware — not when the incident occurred — so a delay between a worker noticing something and escalating it can quietly eat your whole window.
Aged care providers. Under the Serious Incident Response Scheme (SIRS) — which continues under the Aged Care Act 2024 and now extends to Support at Home providers — reportable incidents are classified by priority. A Priority 1 incident must be reported to the Aged Care Quality and Safety Commission within 24 hours; a Priority 2 incident within 30 days. Again, awareness starts the clock.
Childcare and early learning. Under the National Quality Framework, serious incidents must be notified to the regulator within 24 hours through the national system.
The most common cause of a late notification isn't a hard incident. It's the gap between a staff member noticing something and the right person actually doing something about it.
There's also a second obligation that's easy to overlook: across all of these schemes, you must have an incident management system in the first place — covering every incident, not just the reportable ones. The aged care regulator puts it bluntly: an incident management system "is not a spreadsheet with a record of incidents."
When providers miss a deadline or stumble in an audit, it's rarely because nobody cared. It's almost always one of these:
The lag. A worker reports something verbally at the end of a shift. It sits. By the time it reaches the person responsible for notifying the regulator, hours of the window are already gone. This single gap is the most common source of late notifications.
The hesitation. "Is this actually reportable?" Staff aren't sure which category an incident falls into, so they wait, or under-report, or call a Priority 1 a Priority 2. Misclassification is a known and frequent compliance failure.
The blank page. Writing up an incident properly is daunting in the moment, so it gets put off — and a delayed write-up is a delayed everything-else.
The trail that falls apart. Months later, an auditor wants to see not just that an incident happened, but how it was triaged, who investigated it, what corrective actions were taken, and that it was closed out. If that history lives across emails, paper forms and memory, it doesn't hold together.
The fix isn't working harder under pressure. It's a system that removes the friction at each of those failure points:
Capture that's fast enough to happen now. If logging an incident takes thirty seconds — even spoken aloud rather than typed — it gets recorded at the point it happens, and the clock is acknowledged instead of quietly running in the background.
Help deciding if it's reportable — with a human making the call. A prompt that assesses an incident against the right framework and flags "this looks reportable, here's why" turns a nervous guess into an informed decision. The determination still belongs to a person; the help is in not missing it.
A clear path to close-out. Every incident moves through a visible workflow — reported, triaged, investigating, actions open, closed — with corrective actions assigned to a named owner rather than floating in someone's inbox.
Reminders tied to the deadline. Not a generic nudge, but an alert that knows a reportable incident is open and keeps escalating until it's actually been lodged.
A complete, exportable record. One place that holds the account, the assessment, the actions, the close-out, and the policy the incident relates to — ready to hand to an auditor without a scramble.
Accorda's incident management is built around exactly that path.
An incident can be logged in seconds — you can even speak it, and have it turned into a structured report. As you do, Accorda's AI suggests the triage fields (type, severity, the related policy) with a plain-English reason for each, and assesses whether the incident looks reportable against your sector's framework. That assessment is advisory: it flags and explains, but a person confirms the determination and signs it off. Nothing is reported on your behalf without a human in the loop.
From there, each incident carries a clear status through to close-out, with corrective actions owned by named people. Reportable incidents are alerted within their legal timeframes and keep escalating — to the owner, then to admins — until they've actually been lodged, so an open reportable incident can't quietly slip past its window. Every incident is linked to the policy it relates to, and the whole thing — account, assessment, actions, history — can be exported as a clean PDF or rolled into an audit evidence pack in a click. Records are kept tamper-evident, which matters when the trail itself is what's under scrutiny.
Meeting the notification window is only half the obligation. Both the NDIS Practice Standards and SIRS expect you to learn from incidents — to conduct a post-incident review, understand the root cause, act on it, and use incident data to drive continuous improvement. That's not box-ticking; it's the part that actually makes care safer, and it's the part an assessor looks hardest at.
A good incident system makes that natural rather than onerous. Because every incident is captured, triaged and closed out in one place, the patterns become visible, the corrective actions are tracked to completion, and the evidence that you took it all seriously is simply there — not reconstructed in a panic before an audit.
You'll never stop incidents happening. But you can stop them turning into compliance problems — by capturing them the moment they occur, knowing straight away whether they're reportable, and carrying them through to close-out with the trail intact.
That's what Accorda's incident management is for, and it sits alongside policy management, Regulatory Radar and one-click audit evidence, so the whole picture stays in one calm place built for Australian care providers.
Want to see how quickly an incident can be logged and triaged? Start your free 14-day trial at accorda.com.au — no credit card required.
This article is general information for Australian care and regulated businesses and isn't legal or compliance advice. Reporting obligations and timeframes vary by sector and incident type — always check the current requirements that apply to your service.
Start today
Try Accorda free for 14 days. Full features, no credit card, no auto-charge.
