Incidents and safeguarding

The two clocks on a reportable incident

Almost nobody misses a reportable-incident deadline because they did not know the rule. They miss it because the incident happened on a Friday evening, the person who knew the rule was not rostered on, and by the time anyone looked at it on Monday the first clock had already run out.

Before you rely on this

This is a plain-English explanation, not legal or industrial-relations advice, and not a substitute for the sources it links. Rules and rates change. Check anything you are about to act on against the source, or ask someone qualified.

Where this comes from.

Checked against these on 26 August 2026. They are the authority; this page is a summary of them.

NDIS Commission. Reportable incidents

There are two deadlines, not one

This is the part that most often surprises people. A reportable incident does not have a deadline — it has two, and meeting the first does not discharge the second.

The first is the initial notification: a short, fast alert to the NDIS Commission that something has happened. The second is the detailed report, which follows and carries the fuller account — what occurred, what you did, what you are doing about it.

Providers who treat the notification as 'the report' are the ones who get a follow-up from the Commission asking where the rest of it is.

The clock starts when you become aware, not when it happened

The trigger is awareness, and specifically the awareness of the people the rules define as key personnel. That is a more slippery moment than it sounds.

An incident that occurred on Saturday night and was described in a shift note that nobody read until Tuesday did not start its clock on Saturday. It started when the right person knew. That is a better rule than the alternative, and it is also the reason a note buried in a system nobody reads is a genuine risk rather than merely untidy: the moment somebody senior reads it, the clock has already begun.

Business days are harder than they look

The detailed report's deadline is counted in business days, which sounds simple and is not, for two reasons.

Public holidays are local. Australia has no single set. A provider with houses in two states will have branches whose deadlines fall on different dates for the same incident, because a holiday in one is a working day in the other.

A long weekend moves the date. It does not shorten the time available. Counting five calendar days and calling it five business days quietly costs you the difference — which is exactly the mistake a spreadsheet makes, and exactly the week you can least afford it.

The failure is organisational, not individual

The pattern here is worth naming, because it changes what you do about it. Every provider knows these windows. The knowledge is not what fails.

What fails is that the clock lives in a person's head, and people go on leave, work rotating rosters and hand over imperfectly. A deadline that depends on the right individual being at work on the right day is not a control — it is a hope with a policy document attached.

The version that works is the one where the deadline is a property of the record itself, and where something other than a person is watching it.

How CareOp handles this

A reportable incident carries both deadlines from the moment it is recorded, and the business-day one is counted in that branch's own timezone against its own public-holiday table. A scan runs inside the database every hour, moving deadlines along and escalating an alert that nobody has picked up — first louder to the same group, then to the people who own the organisation, and then it stops, because an alert that repeats forever is one everybody learns to swipe away. None of it needs a browser open or a task alive on an office laptop.

How incidents and safeguarding work

Terms used on this page.

The sources, again.

NDIS Commission. Reportable incidents

Every primary document an Australian provider needs is indexed and dated on the reference library.

The other guides.

Get your evenings back. The admin's covered.

Try it free — up to 5 people