An NDIS Incident Management Workflow That Works: From the Shift to Sign-Off

⏱ 8 min read👤 CareIQ Team
Most incident problems are not caused by a bad form. They happen in the gaps: the worker who means to write it up after the shift, the manager who never sees it, the follow-up that nobody owns. A clear workflow closes those gaps. Here is one that works for NDIS providers of any size.

1. Report on shift, while it is fresh

The single biggest improvement most providers can make is getting incidents reported during the shift rather than at the end of the week. Details fade fast. A worker who can report from their phone in a few minutes - what happened, who was involved, where, and what they did - produces a far better record than one who fills in a form days later.

✓ Make it easy

If reporting an incident takes longer than writing a text message, workers will put it off. Keep the first report short; detail can be added in review.

2. Triage: how serious is it?

Every incident needs a severity so the right person sees it at the right speed. Agree simple levels (for example low, moderate, high, critical), with examples of each, and make sure high-severity incidents reach a manager immediately rather than waiting in a queue.

At this point your organisation also decides whether the incident is reportable to the NDIS Quality and Safeguards Commission. That decision and the notification stay with the provider; your system should make the information needed for it easy to find.

3. Review: get the full picture

The reviewing manager fills in what the first report could not: witnesses, injuries (a body map helps), immediate actions taken, and who was told - family, guardian, support coordinator, health professionals. For behaviour incidents, capture the antecedent, behaviour and consequence so the data is useful to the behaviour support practitioner later.

4. Actions with owners and dates

"Monitor" is not an action. Every incident should end with specific actions, each with an owner and a due date: update the risk assessment, refer to an OT, retrain staff on a procedure, change the roster. Then check they were done.

5. Sign-off

A manager signs off when the review is complete and actions are in place. The sign-off - who, when - is part of the evidence an auditor will look for.

6. Learn from the pattern, not just the event

One incident tells you what happened. Twenty tell you why. Review incidents by participant, house, time of day and type every month. Behaviour incidents especially reward this: the same antecedent at the same time of day is a pattern you can act on.

The incidents that never get reported

Some incidents only ever appear as a line in a progress note: "slipped in the bathroom but was fine", "refused medication and became upset". Nobody filled in an incident form. Reviewing notes for that kind of language is valuable but slow by hand. In CareIQ, Care Signals assists coordinators by flagging possible risk language in progress notes for human review, so those incidents can be followed up. A person always reviews and decides.

Putting it into one system

Each step above is easier when it lives in one place with the participant's record, roster and notes. That is how CareIQ approaches incident management - and it keeps getting better as providers use it. See the NDIS incident management software page for how it fits together.

Get every incident recorded properly

Report on shift, review, act and sign off in CareIQ. 2-month free trial, no setup fee, no lock-in contracts.

See how it works