How to write an NDIS feedback and complaints register (2026 template + example)

Why SIL providers need a complaints register in 2026

Under the NDIS (Complaints Management and Resolution) Rules 2018 and the NDIS Practice Standards, every registered NDIS provider — including all Supported Independent Living (SIL) providers — must have a documented system for receiving, acknowledging, managing, and resolving complaints and feedback. The strengthened framework being progressively implemented through 2025–2026 places even greater emphasis on participant voice, transparent records, and demonstrable learning from complaints.

An approved quality auditor assessing your organisation against the Core Module (specifically the Feedback and Complaints Management quality indicator) will look for a live, up-to-date register as primary evidence. Absence of a register — or a register with incomplete entries — is one of the most common non-conformances raised against SIL providers at audit.

Beyond audit obligations, a well-maintained register is a governance tool. It allows leaders to spot patterns, respond quickly when a participant's safety or rights are at risk, and demonstrate to the NDIS Commission that the organisation takes quality improvement seriously.

What the NDIS Practice Standards require

The Core Module of the NDIS Practice Standards sets out that providers must:

• Establish and implement a complaints management and resolution system accessible to participants and their supporters.
• Acknowledge complaints within a reasonable timeframe and keep the complainant informed of progress.
• Investigate complaints thoroughly, impartially, and without detriment to the person who complained.
• Use complaints and feedback to drive continuous improvement.
• Ensure participants are told about their right to complain to the NDIS Commission at any time, regardless of the provider's own process.

The NDIS Commission can also receive complaints directly and may require your register as part of a compliance investigation. Providers who cannot produce a register risk compliance notices, conditions on registration, or in serious cases, suspension.

Step-by-step: how to build your complaints register

1. Choose your format. A register can be a spreadsheet, a database field in your care management software, or a dedicated paper log. Whatever the format, it must be securely stored, backed up, and accessible only to authorised staff. Digital is strongly preferred for SIL because multiple support workers and managers may need to update or view entries.
2. Define your mandatory fields. Every entry must capture the information listed in the next section below. Build these as column headers or form fields before your first entry so nothing is missed retrospectively.
3. Create an intake procedure. Staff need a clear, single-page protocol for what to do the moment they receive a complaint or piece of feedback — in person, by phone, in writing, or via a third party. The protocol should specify who records the entry, within what timeframe (many providers set a same-business-day rule), and who must be notified (e.g., the house supervisor, operations manager, or safeguarding lead depending on severity).
4. Assign a unique reference number. A simple format such as CPL-2026-001 (CPL = complaint, year, sequential number) allows you to track correspondence, link documents, and reference cases in meeting minutes without identifying participants in non-secure settings.
5. Record initial acknowledgement. Log the date and method by which you acknowledged the complaint to the complainant. Under the Practice Standards, acknowledgement should occur promptly — most providers commit to one to two business days in their complaints policy.
6. Document the investigation. Record who investigated the matter, what steps were taken (interviews, file reviews, observation), any interim protective actions (e.g., rostering changes), and findings. This does not need to be a lengthy narrative in the register itself — a brief summary with a reference to the investigation report is sufficient.
7. Record the outcome and any improvement actions. Note how the complaint was resolved, whether the complainant was satisfied, and what systemic changes (if any) resulted. Link to the relevant quality improvement log or continuous improvement plan.
8. Close and sign off. Record the closure date and the name/role of the person who authorised closure. Complaints that cannot be fully resolved internally must be referred to the NDIS Commission — note this in the register.
9. Review the register regularly. Schedule a monthly or quarterly management review to identify trends: recurring themes, specific support workers, particular times of day, or certain participant cohorts. Document this review so auditors can see complaints are informing continuous improvement.

Mandatory fields: what every entry must include

Example register entry

The following is a realistic, illustrative example of a completed register entry. All names are fictitious.

Common audit failures and how to avoid them

• Incomplete fields. Auditors check every column. Missing acknowledgement dates or closure dates are immediate non-conformances. Use a required-field rule in your spreadsheet or software.
• Verbal complaints not recorded. Many SIL providers only log written complaints. The Practice Standards cover all complaints regardless of how they are received. Train all support workers to hand verbal complaints to a supervisor for logging the same day.
• No evidence of improvement actions. Recording "staff reminded" is insufficient. Link every complaint to a specific, measurable action with a completion date and the name of who is responsible.
• Register not reviewed at management level. The register should appear as a standing agenda item in management meetings. Minute the discussion so there is an audit trail.
• Participant not told about the Commission. Every complainant must be informed of their right to contact the NDIS Commission. Record that this information was provided.
• Confidentiality breaches. Registers containing full participant names must be stored with appropriate access controls. Use participant IDs in shared environments.

Connecting complaints to continuous improvement

A register that ends at "closed" misses half its value. At each management review, analyse your complaints data to answer: Are there repeat themes? Are certain support workers named repeatedly? Is there a specific house or time of day with elevated complaints? Use this analysis to update policies, amend training calendars, or revise support plans.

Document your analysis in a continuous improvement log — this is a separate but linked record that auditors expect to see alongside the complaints register. Together, the two documents show that your organisation does not just manage individual complaints but learns from them systematically.

If you are building your SIL compliance documentation from scratch or preparing for a verification or certification audit, the 136-document SIL compliance kit available at ndiscompliant.com.au includes a pre-formatted complaints and feedback register, a complaints policy and procedure, an investigation report template, and a continuous improvement log — aligned to the 2026 Practice Standards.

Quick-reference checklist

• Register exists and is actively maintained (not a blank template)
• All fields completed for every entry
• Verbal and informal complaints recorded, not just written ones
• Acknowledgement date logged for every complaint
• Complainant informed of right to contact NDIS Commission
• Investigation documented and linked to register entry
• Outcome recorded with substantiation finding
• Improvement actions specific, measurable, and completed
• Register reviewed at management level at least quarterly
• Register stored securely with restricted access
• Commission referrals recorded where applicable