A useful policy explains the commitment; its procedure tells people who acts, when, how and what record proves it happened. Write around a real service scenario, test it with the worker who must use it, then approve and control the version.
Start with a task, not a downloaded heading
Choose one situation your service needs to handle: a complaint arrives during an evening shift, a worker cannot attend, or a participant asks to see a record. Name the person affected and the outcome you want. This keeps the document connected to practice.
For registered providers whose scope includes the Core module, the Commission’s governance and operational management standards are an important source for systems covering information, risk, complaints, incidents, people and continuity. Check applicability before treating a heading as a requirement for every service.
Use this eight-part document structure
- Purpose: the outcome this document supports.
- Scope: services, people and circumstances covered, plus exclusions.
- Policy: the commitment and principles.
- Responsibilities: accountable role, delegate and after-hours cover.
- Procedure: trigger, ordered actions, decisions and escalation.
- Records: form, register, storage location and access.
- Related requirements: exact current source and linked internal documents.
- Control: owner, approver, version, approval date and review trigger.
Write a role you actually have. “Quality department” is not useful for a sole trader with no such department. A sole trader may hold several roles; independent advice or review can still be arranged for conflicts.
Worked example: turning “we respond promptly” into a procedure
Fictional Example Supports wants a usable complaint acknowledgement process. Its internal operating target is the next business day; this example does not establish a legal deadline.
| Decision | Example procedure |
|---|---|
| Who receives it? | Any worker records the person’s preferred contact method and informs the service lead |
| Who checks urgency? | The service lead assesses immediate safety or support needs and uses the relevant escalation process |
| What does the person hear? | The lead acknowledges the concern in an accessible format and explains the next step |
| What is recorded? | Complaint reference, received time, action owner and agreed update date |
| What if the lead is unavailable? | The nominated delegate takes responsibility; details are in the current contact list |
The procedure should not force someone to complete your form before they can raise a concern. Offer support to communicate. Keep personal details in the restricted case record, not an unrestricted improvement spreadsheet.
Test it with a tabletop exercise
Give a worker this scenario: “A person raises a complaint at 7 pm and asks not to speak to the usual manager.” Ask them to find the first action, alternative contact and record location. Observe where they guess. Rewrite those points and repeat.
Record the test date, participants, document version, confusion found and change made. This is evidence that you checked usability; it does not prove every real complaint will be handled correctly.
Release the document properly
Approve one master version. Replace or archive superseded copies so workers can identify the current one. Explain changes to affected workers and confirm understanding in a practical way. Link the policy to the form and register it refers to.
A review date is a backstop. Also review when your service changes, a relevant rule changes or an incident exposes a weakness.
Before you call it finished
Can a new worker locate the correct contact without asking the author? Do the named forms exist? Does your software support the access and record controls promised? Have you tried the after-hours path?
If any answer is no, improve the procedure before adding more pages. A longer policy is not automatically a stronger system.
Next: build an evidence register to connect the written process with examples of its use.
Sources & checking
- NDIS Commission: governance and operational management · checked 2026-09-23
ProviderQMS editorial guidance and fictional examples. Source checking is not a professional endorsement. Our editorial method.