How to Use Your NDIS Incident Data to Improve

In the NDIS sector, we often view the word ‘incident’ with fear or anxiety. For many providers, it triggers a reflex of compliance worry: Is the portal updated? Did we notify the Commission? Will this hurt us at audit time?

But if we shift our perspective, every incident, and every near miss, can be a valuable source of information and feedback. It is the system telling you exactly where it needs support, where your team needs more training, where a participant’s environment may no longer be serving them.

When you build a system designed for improvement rather than just compliance, you build a safer environment for participants and a more resilient business for your team.

From ‘who is to blame?’ to ‘how can we improve?’

The most significant shift a provider can make is moving from a culture of fault or blame, to a strengths-based culture.

In a fear-based system, staff might under-report incidents and near-misses because they don’t want to get in trouble. In a strengths-based system, staff report because they know their feedback will lead to a better outcome for the person they support and their team as a whole.

This strengths-based approach is the foundation of a healthy workplace. You can learn more about how a ‘Just Culture’ can strengthen safety for NDIS participants in our related guide.

The three pillars of the learning loop:

• The near-miss as a success: A reported near miss is evidence that you have a vigilant team, and importantly it’s an opportunity to fix a gap before anyone gets hurt.
• Root cause analysis: Moving past the surface level (the ‘what’ and the ‘who’) to understand the systemic reason an incident or near-miss occurred (the ‘why’).
• Evidence of action: Showing that you didn’t just document an incident report, but that the report actually changed the way you operate.

What does this look like in practice?

To understand how data can drive improvement in practice, let’s walk through an example scenario in a Supported Independent Living (SIL) setting.

The Incident Data:

Over a three-month period, we notice four incidents involving a certain participant. In each case, the participant became distressed and yelled at staff during the 5:00 PM shift change.

The ‘compliance’ approach:

1. File four separate incident reports.
2. Ensure they are signed off by the appropriate manager.
3. We tell the staff to remind the participant of the house rules.
4. Wait for an auditor (internal or external) to check that the forms are filled out correctly.

The strengths-based approach:

1. Identify the trend: Instead of looking at the reports in isolation, we review the incident forms and incident register in search of trends. They see a strong correlation with incidents involving this participant and the 5:00 PM transition.
2. Investigate the ‘why’: We speak to the staff and the participant. We discover that at 5:00 PM, the outgoing staff are rushing to finish notes, the incoming staff are talking loudly about the night’s tasks, and the doorbell is ringing. It’s a perfect sensory storm for the participant.
3. Implement systemic change: We adjusts the system after recognising the pattern and underlying issues. Handovers are now done in a quiet room away from the common area. Incoming staff arrive 15 minutes earlier to allow for a calmer transition.
4. Measure the outcome: In the following three months, incidents involving our participant at shift change have significantly reduced.

The result

• For the participant: Their home is a calmer, safer place. Their anxiety is reduced.
• For the staff: They feel less stressed during handovers and more competent in their roles.
• For the business: We’ve reduced the risk of participant harm and staff burnout, and protected our reputation.
• For the audit: When an auditor asks how we manage quality, we don’t just show them our Incident Report folder. We show them the case study of this participant, the change in policy, and the data proving the improvement. The audit is secondary to the improvements we’ve already achieved.

The strategic advantage of transparency

Building a system that actually uses your data (1) keeps people safe, and (2) creates a paper trail of integrity and improvement.

When you can demonstrate that you listen to your participants and your data, you build trust with families, the NDIS, your own team, and the wider public. Incident data is some of the most important information you have at your fingertips – use it as much as you can!