NDIS Incident Action Plans: Corrective Actions and Effectiveness Reviews
Learn how to turn NDIS incident findings into accountable corrective actions, participant-informed safeguards, implementation evidence, and effectiveness reviews.
Published by Governance and Safeguarding Team
An Investigation Is Not Complete When the Report Is Signed
Incident review should lead to safer support, not only a completed form. Corrective actions need to address findings, include the affected participant's perspective where appropriate, identify accountable owners, and be checked later to see whether they worked.
Registered providers must separately assess and manage any reportable-incident notification duties under current NDIS Commission requirements. Internal improvement activity does not replace regulatory reporting.
Start With the Finding and Contributing Factors
State the evidence-based problem before choosing an action. Look beyond individual error to communication, environment, rostering, training application, plan accessibility, equipment, supervision, policy design, and governance controls. Avoid conclusions that are not supported by the investigation.
Write an Action That Can Be Verified
- The specific change to be implemented.
- The person accountable for delivery.
- The due date and priority.
- Resources, consultation, or approval required.
- How the participant will be involved or informed.
- Evidence that will show implementation.
- The measure and date for effectiveness review.
Example Corrective Action
"Finding: two workers followed an outdated transfer instruction after the participant's mobility plan changed. Action: service coordinator will archive superseded plan versions, publish the current physiotherapist-approved instruction in the participant system, and obtain acknowledgement from all assigned workers by 17 July. Participant will review the plain-language summary with the coordinator. Evidence: system version history and worker acknowledgements. Effectiveness review: quality lead will sample the next six transfer notes and ask the participant whether support matches the agreed approach on 31 July."
Training Alone May Not Fix a System Problem
Refresher training can be appropriate, but repeated incidents may show that workers cannot find current information, rostering does not match competency, forms prompt the wrong behaviour, or managers do not review warning signs. Match the action to the identified cause.
Involve the Participant Without Transferring Responsibility
Ask what outcome would help the participant feel safer, how they want updates, and whether proposed changes fit their preferences. The provider remains responsible for its systems and should not make the participant responsible for preventing recurrence.
Review Effectiveness, Not Completion
A revised policy or completed training register proves implementation, not impact. Review service observations, participant feedback, incident trends, worker practice, audit samples, complaints, and other relevant evidence. If the action is ineffective, record why and decide the next change.
Common Action-Plan Weaknesses
- Actions say "remind staff" without addressing the cause.
- Every task is assigned to a team rather than one accountable owner.
- The participant receives no outcome update.
- An action is closed when a document is issued.
- No effectiveness date or evidence source is defined.
Connect incident records with the guide to NDIS progress notes, incidents, behaviours, and safeguarding. For unresolved system findings, use the audit findings remediation framework.
This article was written by AccuNote's Governance and Safeguarding Team for general documentation education. Providers should follow current NDIS incident management and reportable-incident rules, procedural fairness, privacy, participant communication, and emergency requirements.