NDIS Complaints Management Is One of the Most Commonly Failed Audit Requirements: Here Is Why

Complaints management under Module 2B of the NDIS Practice Standards is one of the most frequently cited gaps in provider compliance assessments. Auditors check your policy, interview your staff, and examine your complaint records. If any element is missing or incomplete, you risk a non-conformity finding. This is a plain-language guide to what a functioning complaints system actually requires — and what most providers are getting wrong.

Most NDIS providers have a complaints policy.

Most of those policies are not a complaints management system.

The distinction matters because Module 2B of the NDIS Practice Standards requires a complaints management and resolution system. Not a policy document. A system. One that receives complaints, records them, investigates them, resolves them, notifies the complainant of the outcome, and uses the learning from complaints to improve practice.

A four-page policy in a folder satisfies none of those requirements. What satisfies them is evidence that each of those things actually happened for each complaint your organisation received.

What Module 2B actually requires?

The complaints management requirements under Module 2B apply to all registered providers delivering supports other than specialist disability accommodation.

The standard requires that providers have a system that is accessible to participants. Accessible means participants know it exists, know how to use it, and are not discouraged from using it. A provider who makes the complaints process difficult to find, or who responds to complaints in ways that discourage participants from raising further concerns, is in breach regardless of what the policy says.

It requires that complaints are recorded. Every complaint, regardless of how minor it seems, needs a record. The date it was received. Who made it. What it was about. What happened in response. What the outcome was. What the complainant was told.

It requires that complainants are informed of the outcome and of their right to escalate to the NDIS Commission if they are not satisfied.

And it requires that complaints feed into the organisation’s continuous improvement system. The data from complaints should drive meaningful changes to practice.

That last requirement is the one most providers miss. A complaint is recorded and resolved. The file is closed. No connection is made to any change in practice. An auditor reviewing the complaint file will ask: what changed as a result of this complaint? If the answer is nothing, that is a continuous improvement gap.

What auditors are actually checking?

Auditors assess Module 2B by reviewing your policy, interviewing staff, and examining complaint records.

The staff interview question matters more than most providers realise. A worker asked “what would you do if a participant told you they were unhappy with their support?” should be able to describe the complaints process clearly. Not the policy. The process. Who do they tell? How does the participant make a formal complaint if they want to? What happens after that?

If workers cannot answer these questions, it signals that training has not been embedded, even if the policy was signed at induction. This is consistently one of the most frequently cited gaps in NDIS provider compliance assessments. Not a missing policy. Workers who do not know the process.

The complaint records examination is the third component. Auditors look for:

Complaints that have no resolution record. A complaint received and then no follow-up. That is a gap.

Complaints that were resolved but the complainant was not informed. Another gap.

Complaint data that shows no connection to any improvement action. The system is recording but not learning. Another gap.

And critically: patterns of complaints about the same issue. A provider who has received three complaints about the same worker’s conduct, each resolved individually, but with no investigation into whether there is a systemic issue, has failed the continuous improvement obligation.

Your NDIS client management software should hold complaint records against the relevant participant or worker profile, with a complete record from receipt through to resolution and improvement action. Not in a separate complaints spreadsheet that nobody links to participant records.

The continuous improvement connection:

The NDIS Practice Standards explicitly require providers to demonstrate continuous improvement. Sources of improvement data include incident trends, complaint analysis, worker feedback, participant surveys, and audit findings.

For complaints specifically, the requirement is that complaint data drives meaningful changes to practice. Providers who document their improvement journey — including what prompted each change, what was done, and what the outcome was — give auditors compelling evidence of a mature compliance culture.

What this means operationally: every resolved complaint should have a linked improvement action. Even if the improvement action is “no systemic issue identified, individual worker briefed.” That four-word note demonstrates that someone reviewed the complaint for broader implications and made a considered decision.

A complaint about a worker arriving late twice should produce: a resolved complaint record, a worker briefing note, and a review note determining whether the lateness was isolated or reflects a rostering or supervision issue. Three records. Linked. Demonstrating that the complaint informed practice, not just an apology.

NDIS compliance software that links complaint records to improvement actions — and holds both against the relevant profile — means the continuous improvement requirement is visible in the records rather than asserted in the policy.

**Try CTARS free at ctars.com.au.** See how complaint records, improvement actions, and practice standards evidence work in a connected system. No credit card.

What providers cannot do:

Providers cannot prevent, discourage, or obstruct a person from making a complaint. This is a serious breach. Doing so is not just a Module 2B failure. It is a potential Code of Conduct violation.

In practice, discouragement can be subtle. A manager who responds to a participant’s verbal concern by explaining why the concern is not valid, without offering to record a formal complaint, may be inadvertently discouraging the process. A worker who tells a participant “I will sort this out, you do not need to put in a formal complaint” is doing the same thing.

All providers, registered and unregistered, must comply with the obligation not to obstruct complaints. The April 2026 NDIS Amendment Act expanded the Commission’s powers to detect this kind of conduct. Participants can complain directly to the NDIS Commission at any time. A provider who has been discouraging formal complaints may have no record of the issues the Commission has already been informed about.

What a functioning complaints system looks like:

Participants know how to make a complaint and are told about the process at intake and in the service agreement. Every complaint is recorded with date, description, and the complainant’s details. Investigation steps are documented. The outcome is communicated to the complainant in writing. The right to escalate to the Commission is provided. Improvement actions are linked to the complaint record. The complaint data is reviewed periodically for patterns.

That is the system the NDIS Commission’s complaints handling guidelines require. It is also the system that, when it works properly, makes your service better. Complaints are participants telling you something is not meeting their standard. Organisations that treat that information as operational intelligence rather than administrative burden improve faster than those that treat it as a compliance checkbox.

Document management software that holds complaints records, resolution notes, complainant notifications, and improvement actions in a structured, retrievable format means this system is not an annual exercise before an audit. It is how your organisation processes feedback every time a participant has a concern.

Read more about NDIS reporting requirements and how structured systems produce the continuous improvement evidence Module 2B requires.

CTARS has supported NDIS and out-of-home care providers across Australia since 2010. ISO 27001 certified. Australian data storage. Built by clinicians.

See how it works on the product tour. Check the pricing page for what fits your service.

A complaint is a participant telling you something that needs to improve. Your records need to show you heard them and did something about it.

**Start your free trial at ctars.com.au.** Full platform. Complaint records, improvement actions, and continuous improvement evidence in one system. No credit card.

**Book a 30-minute demo.** Talk to someone who understands what Module 2B requires and how CTARS supports a functioning complaints management system.

Originally published on the CTARS blog at ctars.com.au/blog. If your last complaint was resolved with an apology and no linked improvement action, share this with your quality lead today.