26/07/2026
Disability Support Worker Documentation Pack
A practical NDIS documentation pack checklist covering support logs, case notes, incident records, handovers, consent, risk review, and document controls.
Guide record
How this guide is reviewed
CaresLink reviews guides for plain language, practical operational use, and consistency with official sources linked on the page.
- Published
- 26/07/2026
- Reviewed
- 26 July 2026
A disability support worker documentation pack is a controlled set of records used across service delivery. It is not one official NDIS bundle, and every provider will not need the same forms.
The NDIA says providers need complete and accurate records of NDIS supports delivered. Its examples include invoices, support logs, rosters, case notes, and service agreements.
The right pack depends on the support delivered, the provider's registration context, participant arrangements, and internal systems. Use this guide to map each record to a clear job before adapting any template.
Start with the record purpose
A form is useful only when workers know why it exists, when to complete it, and where the final record belongs.
| Record purpose | Common record | What it should help show |
|---|---|---|
| Confirm service delivery | Support log, roster, or invoice details | Participant, date, support type, time or quantity, and worker |
| Describe the support interaction | Case note or progress note | Activity, participant involvement, goal link where relevant, observation, and follow-up |
| Manage an incident | Incident record and incident register | What happened, immediate response, internal escalation, review, and resolution |
| Transfer open information | Handover note | Relevant change, unfinished task, alert, owner, and next action |
| Set service expectations | Service agreement | Supports, delivery arrangements, prices, responsibilities, changes, and ending services |
| Record information-sharing choices | Consent record | Purpose, information covered, parties, limits, date, and withdrawal or review process |
| Review changing needs or hazards | Risk or support-plan review | Change identified, current control, agreed action, owner, and review date |
These are practical categories, not a universal list of mandatory form names. Check the official documentation guidance for the support type you deliver.
Core records for a frontline support workflow
1. Support log or service delivery record
A support log confirms an individual support was delivered. The NDIA record-keeping page lists minimum identifying information, including the participant, NDIS number, delivery date, quantity or hours, and support type.
The same page says support logs need a participant, child representative, nominee, or legal guardian signature. Check the documentation guidance for the support category and your provider process before setting the final fields.
2. Case note or progress note
A case note explains the support interaction. It can record the activity, how it related to a support item or participant goal, progress, and future session plans.
Some teams call this a progress note. Define the term locally and keep the note factual. Do not add a diagnosis, unsupported opinion, or unnecessary personal detail.
3. Incident record
A routine note should not carry the whole incident process. The NDIS Commission says registered providers need an incident management system with written procedures for identifying, recording, reporting, responding to, and reviewing incidents.
Not every incident is a reportable incident. A provider's authorised person must assess the event against current Commission definitions and timeframes.
4. Handover note
A handover note helps the next worker understand a relevant change, open task, message, or follow-up. It is an internal continuity record, not a replacement for a case note, incident record, medication record, or support plan.
Keep the handover short. Name the next action and owner so the receiving worker does not need to guess.
5. Service agreement
The NDIA highly recommends service agreements with participants. A written service agreement is required when providing specialist disability accommodation.
Do not describe one generic service agreement as mandatory for every support. Check the participant arrangement, support type, pricing rules, and any other requirements that apply.
6. Consent and information-sharing record
Consent records can help show what information may be collected, used, retained, or disclosed. Registered providers should review the information-management indicators relevant to their registration and services.
A consent form should not collect more information than the workflow needs. It should also explain how consent can be reviewed, changed, or withdrawn.
7. Risk and support-plan review record
Risk and support planning records help teams track a changed circumstance, current control, agreed action, and review date. Their structure should match the service, participant plan, worker role, and provider risk process.
A template cannot assess a clinical issue or decide a safeguarding response. Route concerns through the provider's current escalation pathway.
What may be completed after a shift?
There is no single answer for every provider or support. The workflow should respond to what happened during that shift.
| Shift situation | Record to check | Practical action |
|---|---|---|
| Routine support delivered | Support log and case or progress note | Make the service details consistent across the roster, note, log, and invoice |
| Incident or possible harm | Incident process plus any routine service record | Record the immediate response and escalate through the provider's incident system |
| Relevant change or new concern | Case note plus change, risk, or support-plan review process | Record facts, notify the right owner, and set a follow-up |
| Information must pass to the next worker | Handover note | Share only relevant information and identify the open action |
| Participant changes an information-sharing choice | Consent or information-management record | Record the change through the approved process |
Keep the pack controlled
A folder full of forms is not yet a working documentation pack. Add simple controls so workers can find and use the current version.
Give every template an owner.
Show the version, review date, and approved storage location.
Define when the form is used and when another process takes over.
Keep field names consistent across notes, logs, rosters, and invoices.
Train workers with neutral examples and short practice scenarios.
Limit access to people who need the record for their role.
Review recurring gaps and update the workflow, not only the wording.
Editable Word templates can help a small team test a structure. Completed participant records should still be stored through the provider's approved information system.
A practical starter sequence
Start with the records workers use most often. Then connect them to provider-level controls.
Define the support log or service delivery evidence first.
Standardise the case or progress note.
Confirm the incident and escalation pathway.
Add a short handover format for open information.
Review service agreement and consent records.
Assign owners for risk review, training, version control, and storage.
CaresLink provides editable starting points for several of these records. The templates are general operational resources only and need local review before use.
Frequently asked questions
Does every NDIS provider need the same documentation pack?
No. The record set depends on the supports delivered, registration context, participant arrangements, claims process, risks, and internal systems.
Is a progress note the same as a support log?
No. A support log usually confirms delivery details. A case or progress note explains the support interaction, participant involvement, observations, and follow-up.
Is a service agreement mandatory for every NDIS support?
The NDIA highly recommends service agreements. Its record-keeping page says a written agreement is required for specialist disability accommodation. Check other requirements that may apply to your service.
Does an internal incident form replace Commission notification?
No. Registered providers must assess reportable incidents against current Commission definitions and notification timeframes.
How long should NDIS records be retained?
Retention periods vary by record type and applicable law. Do not apply one period to every document. Check current NDIS rules, privacy requirements, and other Commonwealth, state, or territory obligations.
Can a small provider use editable Word templates?
Yes, as drafting and workflow starting points. Review access, privacy, version control, storage, signatures, and local procedures before using them with participant information.
Is this an official or compliant NDIS pack?
No. CaresLink provides general operational resources only. It does not verify a provider, approve documents, or provide legal, clinical, compliance, or professional advice.
Build the workflow before adding more forms
Begin with the service record, case note, incident pathway, and handover. Make those records consistent before adding more templates.
Then assign document owners and review dates. A smaller pack that workers understand is more useful than a large library with no clear workflow.
Disclaimer
These resources are provided for general operational documentation and educational purposes only. They do not constitute legal, clinical, medical, compliance, or professional advice. Organisations should review and adapt all documents according to their own policies, procedures, registration requirements, funding arrangements, and regulatory obligations.