NDIS / Disability
An incident needs to survive the handover.
A support visit, shift handover and incident review can involve different people and systems. The organisation needs a clear account of what happened, who took action and what requires follow-up.
A working example / Care & Community
The incident does not end when the shift does.
An illustrative design question based on this kind of work. This is not a client project, delivered product or claim that every organisation follows this process.
Incident handover record
What travels with the work
- 01Event
Support worker records what happened after a visit.
- 02Immediate safety
Supervisor confirms actions already taken.
- 03Review
Responsible staff assess reportability and timing.
- 04Next owner
A named person takes the notification and follow-up.
Which reporting path applies to this event?
Keep actions, notifications and review linked to the original incident.
Discovery notes
What has to be checked in the real operation.
The example above frames a design question. These conditions need to be checked with the organisation and its advisers before scope or software behaviour is decided.
- 01
NDIS Practice Standards require ongoing, auditable evidence across a core module and up to seven supplementary modules, depending on the supports provided.
- 02
Most reportable incidents require an initial notification within 24 hours and further information within five business days; unauthorised restrictive practices can follow a different path.
- 03
Restrictive practice records can involve authorisation, behaviour support plans, implementation and reporting; the path depends on the practice and jurisdiction.
- 04
Worker screening, staff supervision, and professional development must be documented and retrievable for audit at any time.
Keep the incident and its response together.
Examples to investigate, not off-the-shelf products or a claim that an integration is available.
Participant management systems
Intake, care planning, risk assessment, and ongoing lifecycle management for NDIS participants.
Incident reporting workflows
Structured incident capture with statutory deadline tracking, escalation paths, and audit-ready evidence export.
Policy management platforms
Policy creation, version control, staff acknowledgement, and audit-ready export aligned to the NDIS Practice Standards.
Staff compliance tracking
Worker screening, professional development records, supervision frameworks, and competency assessment.
Published obligations to check
Rules and timeframes for Care & Community work.
| Ref | Obligation | Figure |
|---|---|---|
| 1.1 | Ref 1.1: Reportable incident, initial notification (most types) | 24 hours |
| 1.2 | Ref 1.2: Reportable incident, further information and actions taken | 5 business days |
| 1.3 | Ref 1.3: Unauthorised restrictive practice, no harm caused | 5 business days |
| 1.4 | Ref 1.4: Practice Standards, core module | 1 |
| 1.5 | Ref 1.5: Supplementary modules, depending on supports delivered | up to 7 |
Bring us the sticking point.
Tell us how this work runs in your organisation. We can assess whether a software project makes sense, with the real rules and existing tools in view.
Send an enquiryRelated capabilities