NDIS Case Note Template
An editable Word template for recording NDIS support activities, participant involvement, goal links, observations, escalation routing, and follow-up.
Progress Notes / Template
Example content
Preview the structure before opening the file
English structure excerpt · blank prompts, not a completed record
- Record details
- Participant name · NDIS number
- Support delivered
- Planned support or activity · Support actually delivered
- Factual observations
- Participant response · Progress or barriers observed
- Incident and escalation routing
- Incident, near miss, medication issue, or safeguarding concern identified · Immediate action taken
- Follow-up
- Next action · Action owner
Read all template prompts
Need a separate Communication Note?
Use de-identified facts to draft a Communication Note, then review and edit it yourself. You can write your facts in Chinese and choose English output. This does not review an NDIS case-note file or replace your service record.
Draft a Communication NoteSee what CaresLink AI can and cannot doAI sign-in required. Current Points and data handling are shown in the Portal. The Word download remains free.
Using this resource
Describe the activity actually delivered and its relationship to the support item and participant's goals.
Keep the case note consistent with the service date, duration and other authorised support evidence; do not backfill unobserved progress.
A case note is one record, not automatic payment approval. Check current NDIA evidence requirements and your incident process separately.
Who it is for
NDIS support workers, coordinators, and provider teams that need a factual case note structure for support delivery records.
When to use it
Use after an NDIS support interaction when the provider process requires a case note, progress note, or session record.
What this template helps with
A clearer record trail for everyday follow-up
Review notes
This template is a plain-language operational starting point. Check its fields, wording, and internal consistency before using it in a provider's own documentation system.