Guided tools that build your NDIS policies and procedures from your answers. Created by an NDIS auditor.
Explore the tools →In the world of NDIS support, things don’t (and won’t) always go to plan. A medication gets missed, a transport vehicle is late, a participant’s support needs are misunderstood or incorrectly documented.
When these things happen, the traditional management reflex is to ask ‘who’s fault was this?’
But for providers aiming for excellence, the question can be different: ‘why did our system allow this to happen, and how do we support our team to fix it?’ This is the basis of a just culture.
What is a Just Culture?
A Just Culture is a framework that distinguishes between human error (tripping) and at-risk behavior (cutting corners). It recognises that most incidents are caused by flaws in the overall system, not bad employees.
In a Just Culture, staff are encouraged to be radically honest about what happens day to day, particularly when something goes wrong, because they know they will be treated fairly. This embrace of transparency is the best way a provider can actually see the risks hiding in their operations.
The three types of behaviour
To build a Just Culture, we have to categorise incidents based on the intent and systemic context, rather than just the outcome.
1. Human error (a product of our system design)
- The scenario: A support worker forgets to sign a medication log because a participant was in the middle of a sensory crisis and the logbook was kept in a different room.
- The response: console and fix. We don’t punish the worker, we move the logbook or change the workflow. The system was the failure point, not the person.
2. At-risk behaviour (a choice where risk isn’t recognised)
- The scenario: A worker decides to take a shortcut on a manual handling transfer because ‘it’s faster and we’ve always done it this way,’ not realising the cumulative risk to the participant’s safety.
- The response: coach. We help the worker understand the ‘why’ behind the existing rule. We look at why they felt they had to rush. Was the roster too tight? Was not enough time scheduled?
3. Reckless conduct (conscious disregard for substantial risk)
- The dcenario: A worker knowingly ignores a clear safety protocol despite having the time, tools, and training to follow it. As a result, the participant is placed in direct danger.
- The response: accountability. In a Just Culture, this is the only area where formal disciplinary action is the primary focus.
How a Just Culture protects participants
It might seem like a Just Culture is about being nice to your staff, but the true purpose is protecting your participants.
When staff are afraid of being blamed, they stop reporting near misses, and they start to patch over mistakes. As a provider, this makes you operationally blind. Everything looks fine, incident rates look low, until a major incident occurs that you never saw coming.
By contrast, a Just Culture creates a high-reporting environment. When your team tells you about the small mistakes, you get the chance to fix the system before a small mistake becomes a huge one.
Case study: The wrong meal
Let’s look at how two different cultures handle an error where a participant with dysphagia was nearly given the wrong meal consistency.
The punitive culture: The manager reprimands the worker and emails the wider workforce a warning to do better. The worker feels humiliated and, next time they notice a minor mistake, they keep quiet to avoid the risk of further embarrassment. The system, which is actually a confusing labelling process in the kitchen, remains unchanged.
The Just Culture: The manager thanks the worker for identifying the near miss. They sit down together and realise the meal labels look identical in low light. The provider invests in colour-coded labels.
- The Result: Every participant in the house is now safer from choking risks, and the worker feels like a valued guardian of safety rather than a cog in a machine.
Moving the audit to the background
Auditors love a Just Culture. Why? Because it provides evidence that you’re a learning organisation.
When an auditor looks at your incident register and sees that you’ve analysed errors, coached staff, and changed your workflows, they see a provider that is in control and truly doing what they can to improve. Once you have this transparent culture in place, you can start effectively using your NDIS incident data to build a stronger organisation.
Building better systems shouldn’t be about passing your NDIS audit. Sure, it will help there too! But at the end of the day, it’s about becoming a provider where people, both participants and staff, can thrive without fear.
About the author
Penny Halpin
Penny is an NDIS Lead Auditor who has worked in certification since the first audits in 2018, and was previously a Senior Manager at an Approved Quality Auditor with technical review across thousands of audit reports. She built the Paperbark tools to help providers create documentation that reflects how they actually work.
More about Penny →