Most providers brace for complaints — the best ones use them. Here's what good complaints handling looks like across NDIS, aged care and childcare, and what auditors check.
The Accorda Team · 28 June 2026
Most providers brace for complaints. The better ones have learned to value them.
A complaint is uncomfortable, but it's also one of the clearest signals you'll ever get about where your service is falling short — and one of the things a regulator looks at most closely when they want to know how a provider really operates. Handled well, complaints make your service better and your compliance stronger. Handled poorly — or quietly buried — they become one of the most common findings an auditor makes.
This post is about what "good" actually looks like: what the standards require, what an auditor checks, and the traps that catch otherwise careful providers. It's cross-sector — complaints obligations sit at the heart of the NDIS Practice Standards, the strengthened Aged Care Quality Standards, and the National Quality Framework alike — so whether you're an NDIS provider, an aged care service, an allied health or dental practice, or an early learning service, the principles hold.
First, a distinction that trips a lot of providers up: complaints and incidents are not the same thing, and you shouldn't run them through the same process by default.
An incident is something that happened — an injury, an error, an allegation of harm. A complaint is an expression of dissatisfaction — someone telling you they're unhappy with a support, a worker, a decision, or how they were treated. Most complaints are not incidents. They're feedback, and they get a feedback process: acknowledge, look into it, resolve, follow up.
But the two can intersect. If a complaint raises something serious — an allegation of abuse, neglect or exploitation — it may cross the line into reportable-incident territory, with its own legal notification timeframes. The mistake is to conflate them in either direction: treating every complaint as a crisis, or failing to recognise when a complaint is actually flagging a reportable incident. Knowing where that line sits is part of running both systems properly. (Our companion piece on meeting reportable-incident deadlines covers the incident side in detail.)
Across the care sector, a documented complaints system isn't optional — it's a baseline expectation.
Under the NDIS, complaints management is a Practice Standard in its own right, and the detail is set out in the NDIS (Complaints Management and Resolution) Rules 2018. The NDIS Commission expects all providers — including unregistered ones — to manage complaints effectively, and registered providers must have a documented complaints management and resolution system as a condition of registration. That system has to be accessible (people can complain in writing, verbally, or with support), proportionate to the size of your service, and built so people feel safe raising concerns. Providers are also expected to tell participants they can complain to the NDIS Commission directly, as an independent pathway.
Aged care carries the same expectation through the strengthened Quality Standards, with an emphasis on feedback and complaints being used to improve care. And early learning services under the National Quality Framework have their own complaints obligations, including notifying the regulatory authority about certain kinds of complaints within set timeframes.
Different frameworks, one shared message: have a real, documented, accessible complaints process — and be able to show it works.
The standards stop short of dictating one exact workflow, but the shape of a strong complaints process is consistent. It runs roughly like this.
Capture every complaint — including the informal ones. A complaint counts whether it arrives by email, in a meeting, or as an offhand remark from a family member at pick-up. Log it: the date received, who raised it, what it's about, and how it came in. Verbal and informal complaints are exactly the ones that go unrecorded, and exactly the ones auditors probe for.
Acknowledge it promptly. Your policy should state your acknowledgement timeframe, and you should meet it. The complainant should know their concern has landed and what happens next.
Assess and triage. Work out the nature and seriousness. Is this a service-quality concern, or does it touch on harm and need to be escalated as a reportable incident? This is where the complaint/incident line gets drawn.
Investigate with procedural fairness. Look into it properly — gather the relevant facts, talk to the people involved, and give anyone who's the subject of a complaint a fair chance to respond. Document the steps.
Resolve and close the loop. Reach an outcome, take any corrective action, and — crucially — tell the person who complained what you found and what you did. A complaint that's resolved internally but never communicated back is, to an auditor, an open loop.
Record the whole trail. Each complaint should show its date, nature, the actions taken, the resolution, and the outcome — and complaints records generally need to be retained for years, in line with the Practice Standards and privacy law. The record is what turns "we handle complaints well" from a claim into evidence.
Two failures show up again and again, and both are avoidable.
The first is the policy that doesn't match practice. You have a complaints policy that promises acknowledgement in two business days and a clear investigation process — but the actual records show complaints sitting for weeks, or no record of the complainant being told the outcome. An auditor doesn't assess your policy against an ideal; they assess your practice against your policy. A gap between the two is a finding.
The second is the suspiciously empty register.
A provider with no complaints on record isn't a provider with no problems — it's usually a provider that isn't capturing them. Auditors know the difference.
A service that's operated for two years with zero recorded complaints will draw immediate scrutiny, because it almost always means complaints are being deflected, resolved informally and never logged, or simply not recognised as complaints. A healthy complaints register — with concerns raised, handled, and closed out — reads as a sign of a functioning, honest service. An empty one reads as a red flag.
Here's the reframe that changes how this feels. Auditors don't just want to see that you handled each complaint — they want to see that your complaints taught you something.
The standards expect you to review your complaints system periodically — at least annually is the common benchmark — and to look across your complaints for patterns. Three families raising the same concern about communication isn't three isolated complaints; it's one systemic issue with a fix attached. Feeding complaint outcomes into a quality improvement process, and being able to point to a change you made because of what people told you, is some of the strongest continuous-improvement evidence you can offer. It's the difference between a service that processes complaints and one that learns from them — and, as we cover in What Auditors Are Really Looking For, the modern audit is increasingly built around exactly that kind of proof.
So where does Accorda fit? Honestly — and worth being precise about — Accorda isn't a complaints logbook, and a strong complaints process still depends on your team capturing and resolving concerns properly. What Accorda does is shore up the parts of complaints compliance that quietly fail between audits.
It keeps your complaints policy current and audit-ready: you can draft or review a complaints management policy with the AI policy assistant, and when the rules shift, Regulatory Radar flags that your complaints policy may need updating rather than letting it drift out of date. It makes your training provable — staff sign-offs show, with a date against each name, that your team has actually read the complaints process they're expected to follow, which is one of the specific things auditors ask staff about. Your team can ask the assistant "what do I do when someone makes a complaint?" and get a plain-English answer drawn from your own policy, with the source attached. And when a complaint rises to a reportable incident, that's where Accorda's incident workflow takes over — capturing it, flagging reportability, and tracking it to close-out within the legal timeframes.
In other words: Accorda won't run your complaints process for you, but it keeps the policy, the training evidence, and the escalation path in order — so the compliance scaffolding around your complaints is always provable.
Want your complaints policy current and your staff sign-offs audit-ready in one place? See how Accorda helps at accorda.com.au.
NDIS Quality and Safeguards Commission — Complaints about supports and services you provide
NDIS Quality and Safeguards Commission — Effective Complaint Handling Guidelines for NDIS Providers
Aged Care Quality and Safety Commission — Strengthened Aged Care Quality Standards
ACECQA — National Quality Standard
This article is general information for Australian care and regulated businesses and isn't legal or compliance advice. Requirements differ by sector, registration and service type, and they change over time. Always check the current standards and rules that apply to your service. Last updated June 2026.
Start today
Try Accorda free for 14 days. Full features, no credit card, no auto-charge.
