NDIS Quality Improvement System: How to Build and Maintain a Compliant CI System

What is a Continuous Improvement system in NDIS?

A Continuous Improvement (CI) system is the set of processes, tools, and habits an organisation uses to identify opportunities for improvement, act on them, and verify that those actions have been effective. In the NDIS context, it is the operational expression of Outcome 2.3 — Quality Management under the NDIS Practice Standards Core Module.

The outcome statement for 2.3 requires providers to demonstrate that they have a quality management framework that:

• Collects and analyses data about quality from multiple sources
• Identifies and acts on opportunities for improvement
• Monitors the effectiveness of improvements made
• Is reviewed and updated over time
• Involves participants, workers, and other stakeholders in quality processes

The NDIS Commission's auditors assess this outcome looking for a functioning, living system — not a document that describes what the system should do. The CI Register should have entries. The internal audit reports should exist. The management meeting minutes should reference quality data. Evidence of these activities in the months before your audit is what demonstrates genuine compliance.

The PDCA cycle in an NDIS context

The Plan-Do-Check-Act (PDCA) cycle is the internationally recognised quality management framework that underpins continuous improvement across industries. In an NDIS provider context, each phase maps directly to operational activities:

The PDCA cycle is not a one-time process — it is a continuous loop. Every improvement action you complete generates new data about what's working in your organisation, which in turn feeds the next cycle of improvement. The CI Register is the documentary record of these cycles.

Sources of improvement data

A strong CI system draws improvement data from multiple sources — not just formal complaints. Providers who only add items to their CI Register when something goes badly wrong are missing the majority of improvement opportunities available to them.

A CI Register that only contains items from complaints and incidents is a restricted view of the improvement landscape. Auditors assessing Outcome 2.3 look for breadth — they want to see that the provider is drawing improvement intelligence from many sources, not just reacting to crises.

The Continuous Improvement Register: what to capture

The CI Register is the operational core of your quality management system. It must be a live document — updated regularly, reviewed at management meetings, and accessible to the auditor. Each entry should capture:

• Date identified
• Source (complaint / incident / audit / feedback / staff suggestion / near miss)
• Reference number (e.g., linked to the incident or complaint reference)
• Description of the issue or improvement opportunity
• Root cause (where identified)
• Planned action to address the issue
• Person responsible for the action
• Target completion date
• Actual completion date
• Evidence of completion (policy updated, training delivered, process changed)
• Effectiveness review (was the action effective? Has the issue recurred?)
• Status (Open / In Progress / Completed / Closed)

The effectiveness review column is the one that most providers omit — and that auditors specifically look for. Simply recording that an action was completed is not enough; the system must demonstrate that you checked whether the action actually worked. For example, if you added a new step to your MAR audit process to address a medication error, the effectiveness review should confirm whether subsequent audits found the process was followed and errors reduced.

Internal audit programme

An internal audit is a structured review of a specific area of your operations against the requirements of the NDIS Practice Standards. It is distinct from external certification or surveillance audits conducted by AQA auditors — you conduct your internal audits yourself (or have a designated person within your organisation do so).

What an internal audit programme includes

• Annual audit schedule: A plan showing which areas will be audited, by whom, and when. Typically mapped to the NDIS Practice Standards outcomes.
• Audit checklists: Structured checklists for each area being audited, based on the Practice Standard quality indicators.
• Completed audit reports: Documented findings from each completed audit, including conformances and non-conformances.
• CI Register entries: For each non-conformance found, a corresponding CI Register entry with corrective action.

Who conducts internal audits?

Internal audits should be conducted by someone with sufficient independence from the area being audited — ideally not the person responsible for the processes being reviewed. For small providers, this might mean the Practice Manager audits worker documentation while the CEO reviews financial management practices. The internal auditor does not need to be an external consultant, but should have enough knowledge of the Practice Standards to identify genuine gaps.

Prioritising high-risk areas for frequent review

Not all areas need to be audited with equal frequency. Prioritise quarterly mini-audits for high-risk areas:

• Medication Administration Record completeness and accuracy
• Progress note quality and timeliness
• Worker Screening Register currency (no expired clearances)
• Training Register currency (no lapsed mandatory certifications)

Lower-risk areas (document control register currency, governance records) can be reviewed annually.

How to turn a complaint into an improvement

One of the most powerful quality improvement mechanisms available to a small NDIS provider is the complaint. Most providers experience complaints as purely negative events to be managed and resolved. A quality-mature provider experiences them as data — valuable signals about where systems are failing.

The process for converting a complaint to an improvement action:

1. Resolve the complaint for the individual: Follow your complaints process — acknowledge, investigate, respond, and close. The individual complainant's experience must be addressed first.
2. Assess for systemic issues: After resolution, ask: "Does this complaint reveal a problem that affects other participants, not just this one?" If a participant complained that their support times were changed without notice, is this happening for other participants too?
3. Conduct a root cause analysis for systemic issues: Why did this happen? What process, policy, or practice gap allowed it?
4. Add a CI Register entry: Record the systemic issue, its root cause, and the planned action to address it.
5. Implement the action: Update the policy, procedure, or practice. Communicate the change to affected staff.
6. Close the loop: Record the completion date, evidence, and your effectiveness review (did the problem stop occurring?) in the CI Register.

When an auditor asks "can you give me an example of how a complaint led to an improvement in your organisation?", having a CI Register entry that traces a complaint through to a completed policy update — with an effectiveness review — is the gold standard answer.

Management review meetings

Your CI system does not operate in isolation — it must be integrated into your management governance structure. The NDIS Practice Standards expect that quality data is reviewed at management level on a regular basis, not just filed away by an administrative worker.

Minimum management review meeting requirements

Most providers hold a dedicated quality management review meeting quarterly. The agenda for this meeting should include:

• Review of the Incident Register: patterns, trends, any unresolved serious incidents
• Review of the Complaints Register: patterns, resolution times, recurring issues
• Review of the CI Register: status of all open actions, completion of due actions, effectiveness reviews for closed actions
• Training Register currency: any upcoming renewal deadlines, new staff induction status
• Worker Screening Register: any clearances approaching expiry
• Internal audit findings: review of completed audits, status of non-conformance actions
• Participant feedback summary: results from any feedback collected since the last meeting
• Identification of new CI items arising from the review

Every management review meeting must be minuted. The minutes should record attendance, items discussed, decisions made, and actions allocated. These minutes are a primary piece of evidence that auditors request when assessing Outcome 2.3.

Demonstrating CI at certification audit

When your auditor arrives to assess Outcome 2.3, they will want to see evidence that your CI system has been operating genuinely — not assembled for the audit. The evidence set that satisfies this outcome includes:

• Quality Management and CI Policy (describing the system)
• Completed CI Register with a minimum of 6–12 months of activity
• Mix of CI sources (complaints, incidents, audit, feedback — not just one type)
• Completed CI actions (not just open items with future due dates)
• Effectiveness reviews for completed actions
• Internal audit programme (schedule) with at least one completed audit report
• Management meeting minutes referencing quality data
• Evidence of participant involvement in quality processes (satisfaction surveys, feedback forms)

Timing matters. An auditor reviewing a CI Register with 15 entries added in the two weeks before the audit — and nothing before that — will likely not accept this as evidence of a functioning system. Start your CI Register the moment you begin operations and maintain it consistently.

Corrective action vs preventive action

Quality management frameworks distinguish between two types of improvement action:

Corrective action addresses a problem that has already occurred. It is reactive — something went wrong, and the corrective action is designed to prevent it from happening again. For example: a medication error occurred because the MAR was difficult to read; the corrective action was to reformat the MAR template to make it clearer.

Preventive action addresses a potential problem that has not yet occurred. It is proactive — you identified a risk or weakness before it caused harm, and the preventive action is designed to address the root cause before it does. For example: during an internal audit, you noticed that workers were not always documenting participant money transactions immediately; the preventive action was to retrain all workers and add a reminder card to the Participant Money Register.

A mature CI system includes both types of action. Providers whose CI Registers contain only corrective actions — responses to incidents and complaints — are operating a reactive quality system. Adding preventive actions from internal audits and risk assessments demonstrates a proactive quality culture that auditors value.

Building a CI culture in your organisation

The most common failure in NDIS quality management systems is the gap between the policy (which describes a functioning CI system) and the reality (where improvement actions are added reluctantly and completed inconsistently). Building genuine CI culture in a small organisation requires both leadership and practical systems.

Leadership behaviours that drive CI culture

• Respond positively to problems: When a worker reports a near miss or identifies a procedural gap, thank them. If workers learn that raising problems leads to criticism, they stop raising them.
• Follow through on CI actions: Every action that appears in the CI Register must be completed as promised. A register full of overdue actions sends the message that quality is not a real priority.
• Share improvement outcomes: When a CI action is complete and the improvement is verified, communicate the outcome to the team. "We changed the handover form based on your feedback — here's how it's working better."
• Ask for input regularly: Include a standing agenda item in team meetings: "What could we be doing better? What's getting in the way of good support delivery?"

For support workers, the daily practice of quality improvement is most visible in their documentation. Consistently high-quality progress notes — factual, person-centred, goal-linked — are themselves a form of continuous improvement practice. Encourage your team to use the free NDIS Notes Rewriter tool to develop and maintain this habit.

A functioning continuous improvement system is not a bureaucratic overhead — it is the mechanism by which your organisation gets better at what it does. Every incident that generates a CI action, every complaint that leads to a policy improvement, and every internal audit that surfaces a correctable gap is an opportunity to deliver safer, higher-quality supports to participants. That is ultimately what the NDIS Practice Standards are asking for — not paperwork, but genuine improvement.

Build your CI Register from day one of your operations. Maintain it consistently. Review it at management meetings. Complete the actions. Review their effectiveness. When your auditor arrives and examines your CI Register, it should tell the story of an organisation that is genuinely invested in getting better.