Why your complaints register is an audit priority

The NDIS Commission treats a provider's feedback and complaints handling system as a direct window into how seriously that organisation takes participant rights. During a certification or verification audit, an approved quality auditor (AQA) will dedicate meaningful time to your complaints register — not merely to confirm it exists, but to interrogate whether it is actively used, consistently maintained, and driving genuine improvement.

Under the strengthened NDIS Practice Standards that apply from 2026, the obligations around feedback and complaints have been reinforced across multiple standard areas. SIL and high-intensity support providers face particular scrutiny because of the inherent power imbalance in 24-hour residential settings. Getting your register right before an audit is not optional — a non-conformance here can result in a corrective-action requirement that delays registration or renewal.

The regulatory foundation

The complaints-handling requirements flow from several interlocking sources:

Together these instruments mean your register is not simply an administrative record — it is a compliance instrument that must demonstrate a live, functioning system.

What an auditor checks: the eight areas of scrutiny

When an AQA reviews your register during a desktop review or on-site audit, they will work through the following areas methodically.

1. Does the register exist and is it current?

This sounds basic, but auditors regularly find registers that were created at initial registration and then effectively abandoned. The register must be up to date at the time of audit and show entries from throughout the registration period — not a flurry of entries made in the weeks before the audit date.

2. Are all complaints and feedback captured — not just formal complaints?

A common non-conformance is a register that only records written, formal complaints. Auditors expect to see verbal complaints, anonymous feedback, concerns raised through advocacy services, and feedback received via participant surveys all entered into or cross-referenced by the register. The NDIS Commission's complaints guidance makes clear that a complaint is any expression of dissatisfaction that requires a response — regardless of the channel through which it was received.

3. Does each entry contain the required fields?

Auditors expect each register entry to contain, at minimum:

4. Were complaints acknowledged within a reasonable timeframe?

The NDIS Complaints Management Rules require acknowledgement within a reasonable time. While the Rules do not specify an exact number of days (providers must set their own reasonable timeframe in their policy), auditors will benchmark your practice against your own stated policy. If your policy says acknowledgement within two business days and your register shows a pattern of five-day delays, that is a non-conformance against your own documented standard.

5. Was the complainant informed of their right to escalate to the NDIS Commission?

Every complaint response must inform participants (and their representatives) that they may escalate unresolved complaints to the NDIS Commission at any time. Auditors look for evidence of this in your register entries or in the template letters linked to each complaint. Failure to communicate this right is one of the most frequently cited non-conformances in complaints-handling audits.

6. Do outcomes demonstrate genuine investigation — not just closure?

Auditors are trained to distinguish between a closed complaint and a resolved complaint. Entries that simply record "closed — no further action" without documenting what was investigated and why that conclusion was reached will be queried. For SIL providers, where complaints may involve allegations of abuse, neglect, or restrictive practice misuse, auditors will also check whether the matter triggered an NDIS incident report in accordance with the NDIS (Incident Management and Reportable Incidents) Rules 2018.

7. Is there evidence of continuous improvement?

The Governance and Operational Management Practice Standard requires that complaints and feedback data be used to drive quality improvement. Auditors will look for a documented link between complaint themes identified in the register and changes made to policies, procedures, staff training, or support delivery. This link is typically demonstrated through a quality improvement plan or a corrective-action register — but the critical point is that the connection must be explicit and evidenced, not simply asserted.

8. Is the register accessible to participants?

Under the Rights and Responsibilities standard, participants must be able to access information about their right to provide feedback and make complaints. Auditors may ask how participants are made aware of the complaints process and whether easy-read, translated, or other accessible formats are available. The register itself does not need to be handed to participants, but the system it represents must be visibly participant-centred.

Common non-conformances — and how to fix them

Non-conformance The fix
Register not updated between audits Assign a named staff member with a monthly review responsibility; record the review date in the register itself.
Verbal complaints excluded Train all staff to record verbal complaints within 24 hours using a standardised form; include verbal entries in the register.
No escalation rights documented in responses Add a standard paragraph to every acknowledgement letter referencing the NDIS Commission hotline and website.
Complaints closed without investigation notes Require a minimum-three-sentence investigation summary before any entry can be marked closed.
No link to quality improvement actions Add a mandatory "CI action triggered Y/N — reference" field to every register entry; review aggregate themes quarterly.
Policy timeframes not met in practice Audit your own register against your policy before the AQA does; identify and address systematic delays before the audit date.

A practical step-by-step: preparing your register for audit

  1. Pull a complete export of your register and check that every entry from the registration period is present — not just the last six months.
  2. Cross-reference against your incident register. Any complaint that describes harm, abuse, or unauthorised restrictive practice should have a corresponding reportable incident entry.
  3. Review each entry for completeness against the required fields listed above. Flag any entries missing acknowledgement dates, investigation notes, or closure details.
  4. Check your response letters or call notes to confirm that the NDIS Commission escalation pathway was communicated in every case.
  5. Map complaint themes to your quality improvement plan. If the register shows three complaints about medication administration over six months but your QI plan has no corresponding action, add one now.
  6. Confirm your complaints policy names a specific staff member (by role, not name) responsible for complaints oversight, and that the person in that role knows they are responsible.
  7. Prepare a one-page summary of complaint volumes, themes, resolution rates, and improvement actions for the current registration period. Auditors appreciate this — it demonstrates that leadership actively reviews the data.

Template: minimum register entry fields

The excerpt below illustrates the minimum fields a compliant entry should contain. Adapt the format to your existing system — what matters is that the information is captured, not the specific layout.

Complaint ID: 2026-0043
Date received: 14 June 2026
Received via: Telephone (participant's support coordinator)
Complainant: Support coordinator on behalf of Participant [ID]
Subject matter: Participant states scheduled community access was cancelled
  without notice on three occasions in May 2026.
Acknowledged: 15 June 2026 — written acknowledgement emailed to coordinator;
  NDIS Commission escalation rights included in acknowledgement.
Investigator: Service Manager — Supported Living
Investigation notes: Reviewed staff scheduling records and participant daily
  notes for May 2026. Confirmed three cancellations due to unplanned staff
  leave. Rostering procedures did not include a backup-contact escalation step.
Outcome: Apologised to participant and coordinator. Rostering procedure updated
  to require backup-contact escalation within two hours of unplanned leave.
  Staff briefed at team meeting 20 June 2026.
Closed: 22 June 2026
CI action: Yes — refer QI-2026-017 (Rostering escalation protocol)

Pulling it together for 2026 readiness

The 2026 strengthened framework places greater emphasis on participant voice as an evidence source — auditors are increasingly asking participants and their advocates directly whether they felt their complaints were taken seriously and resolved fairly. A well-maintained register is necessary but not sufficient: providers must also be able to demonstrate, through participant interviews and survey results, that the system works from the participant's perspective.

If you are preparing a full suite of SIL compliance documents — including a complaints policy, register template, acknowledgement letter, escalation procedure, and quality improvement integration framework — the 74-document audit-ready SIL compliance kit at ndiscompliant.com.au covers all of these in a single package built to the current NDIS Practice Standards.

Start your internal audit now, fix the gaps the checklist above identifies, and your register will be an asset rather than a liability on audit day.

Important: This article provides general guidance about NDIS compliance requirements. It is not legal or professional advice. Requirements may change as the NDIS Commission updates its policies and Practice Standards. Always verify current requirements with the NDIS Quality and Safeguards Commission or a registered NDIS consultant before making compliance decisions.