How to build an NDIS complaints register that keeps the response moving

A complaints register should help you keep a promise to the person who raised a concern: someone is responsible, the next contact is visible, and the outcome will be explained.

It should also help you see repeated problems. If several people find your information difficult to use, separate entries may be pointing to one process that needs attention.

The register is an index and tracking tool within your complaints process. It does not replace listening, assessing risks, investigating fairly or taking action. The structure below is a practical suggestion, not a mandatory Commission spreadsheet.

Start with a process people can access

Registered providers must have a documented complaints management and resolution system. The Commission expects effective complaints practices from all providers, and describes accessible and anonymous ways to raise concerns. Do not make completing your form a condition of being heard. NDIS Commission: complaints about supports and services you provide.

Someone might complain in a conversation, through a communication device, by email or with help from a trusted person. Record the concern through your usual process without making the person repeat it unnecessarily.

If information suggests immediate harm or a possible reportable incident, use the relevant response and escalation process promptly. Opening a complaint row does not complete the separate incident assessment or any external notification. Those processes may need to run together, with linked references. NDIS Commission: incident management.

Decide what belongs in the register

Use a short summary that identifies the issue and requested response. Keep detailed accounts, correspondence and supporting records in appropriately restricted storage, linked by a complaint reference.

Avoid labels such as “difficult participant” or “serial complainer.” Describe the concern. “Person says the cancellation explanation is unclear and requests a plain-language response” gives the next reviewer useful information without prejudging the complaint.

Record whether the person making the complaint is also the person affected. If someone speaks on another person's behalf, identify their role and the relevant communication or authority arrangements rather than assuming they can make every decision for that person.

Anonymous concerns still need a reference and assessment. Mark contact details as unavailable; do not invent them or automatically close the complaint because a reply cannot be sent.

Build a manageable set of fields

Start with the following columns or grouped fields:

Add fields only when someone uses them to make a decision or fulfil a responsibility. A register with forty mostly blank columns can hide the important next action.

Set contact dates from the applicable requirements, your procedure and the commitment made to the person. A sample date in this article is not a legal response deadline or permission to delay an urgent concern.

A fictional worked row

This example is invented. It does not describe a real provider, participant or complaint.

The row makes the person's request visible without claiming that a replacement document has already solved the problem. In the restricted record, the owner notes how the concern was acknowledged, what the person said would help and who will prepare the response.

The owner then checks the replacement with the person in the agreed way. If it still does not work, the register remains open with a revised next step. Sending a different file is evidence of an action, not evidence that the information became accessible.

Use statuses that describe work

A useful short sequence is: received, assessment underway, response underway, awaiting specified information, outcome communicated, and closure reviewed. These are suggested labels; use language your team understands.

“Awaiting information” needs an owner, a description of what is missing and a review date. It should not become a parking place for complaints that feel difficult.

Keep a dated history of meaningful changes. Record when a commitment changes and why, including how the person was informed. Preserve the earlier date rather than continually replacing it with a future one.

If several issues sit within one complaint, show which are resolved and which remain open. A successful response to one point does not settle the others.

Record decisions fairly

Keep allegations, observations and findings distinguishable. “The person reports that…” identifies an account; “the review established…” needs supporting evidence.

Where a worker is the subject of a complaint, follow the appropriate fair process. A register should not treat an allegation as a settled finding or automatically distribute it to everyone. The Commission's complaints guidance addresses procedural fairness and impartial decision-making. Complaints about supports and services you provide.

Record who made the decision, the information considered and any unresolved limitation. Where the complaint concerns the usual decision-maker, use the service's alternative escalation arrangement. Do not invent independent oversight that your organisation does not have.

Close with an explanation, not just a tick

Before closure, check whether the outcome has been communicated in a way the person can use. Record the response they gave, including disagreement. Lack of a reply is not proof of satisfaction.

Explain any available review or external complaint options without making internal closure a barrier to using them. The Commission's guidance includes informing participants how to complain directly to the Commission. Complaints guidance.

A wider improvement action may continue after the complaint response is complete. Keep its status separate and linked. For example, the person may receive the explanation they needed while a broader review of inaccessible templates is still underway.

Protect access and learn from patterns

Limit detailed complaint access to people with a legitimate role in handling it. A management summary can show themes, overdue responses and improvement actions without exposing the full account or unnecessary identifying details.

Consider access to exports and emailed spreadsheets as well as the original file. Use your applicable retention requirements; do not delete records simply because the status changes to closed.

For periodic review, ask what the numbers mean. A rising complaint count might indicate a new problem, easier reporting or both. A low count does not demonstrate that everyone is satisfied. Look at the substance, response quality and what participants say about raising concerns.

Test your first register before rolling it out

Enter a fictional concern and follow it through the proposed process. Check that you can:

• Record an anonymous or verbally raised complaint.
• Identify who owns the next response.
• Link urgent escalation without losing the complaint itself.
• Retrieve the underlying record with appropriate access.
• Preserve an earlier promise when a date changes.
• Record disagreement and unresolved issues honestly.
• Keep improvement work visible after the response is communicated.

Then use one real complaint through your authorised process and review whether the fields helped. Adjust the register around the work people actually need to do.

To see how an issue can stay connected with its next action and review, watch the ProviderQMS walkthrough.

Official sources reviewed 14 September 2026. The register design and fictional dates are practical examples, not prescribed legal timeframes or a guarantee of complaint resolution.