NDIS progress notes are clear, dated records of the support delivered to a participant, how the participant responded and how the support connected to their goals. Good notes should identify the participant, worker, date, support type, duration, activities, outcomes, risks and required follow-up. They should be written soon after every shift using factual, respectful language.
For Australian NDIS providers, these notes are not just internal handovers. They help maintain continuity of support, demonstrate participant outcomes and provide evidence that claimed supports were actually delivered. The NDIA requires providers to maintain complete and accurate records, including support logs, rosters, case notes, invoices and service agreements.
[Insert image here: Support worker completing an NDIS progress note on a mobile device after a participant session.]
What Are NDIS Progress Notes?
NDIS progress notes are the day-to-day written record of a participant’s support.
A support worker completes a note after a shift, appointment or support session. The note explains:
What support was scheduled
What support was actually delivered
How the participant engaged or responded
Whether progress was made towards a goal
Whether anything unusual occurred
What another worker may need to know next
Some organisations use the terms shift notes, session notes or case notes. Although the language varies, the purpose is similar: to create an accurate record of the support delivered.
The NDIA states that case notes should describe the activities a participant completed and explain how those activities relate to the relevant support item and the participant’s goals. Notes may also document progress and plans for future sessions.
Direct answer: NDIS progress notes document the support delivered, the participant’s response, progress towards goals and any follow-up required. They should be factual, timely, identifiable and connected to the relevant funded support.
Progress notes also form one part of the broader participant file. Providers should connect them with current consent records, support plans, risk assessments and NDIS service agreements.
NDIS Progress Notes Requirements in Australia
There is no single official form that every provider must use. However, the NDIA’s record-keeping requirements specify minimum information that should appear across support records.
These minimum details include the participant’s:
Name
NDIS number
Date of support
Amount, quantity or hours delivered
Support type
A useful NDIS progress note should go further than the minimum.
What Should Be Included in NDIS Progress Notes?
Required element | What to record |
|---|---|
Date and time | When the shift or session began and ended |
Participant | Full name or approved participant identifier |
Worker | Name and identifiable electronic or written sign-off |
Support delivered | The specific support, activity or assistance provided |
Participant response | What the participant said, did or demonstrated |
Goal connection | How the activity related to an agreed participant goal |
Risks or concerns | Changes, hazards, health concerns or unusual events |
Incidents | A reference to any separate incident report completed |
Follow-up | Actions required by the next worker, coordinator or manager |
Completion time | When the note was entered into the record system |
The NDIS Practice Standards require participant information to be identifiable, accurately recorded, current and confidential. Providers must also maintain an information management system that records information accurately and in a timely manner.
That means a progress note should answer a simple question:
Could another worker, participant or auditor understand what happened without asking the original worker to explain it?
For a wider file-level review, use the NDIS participant file checklist.
NDIS Progress Notes Compliance Checklist
Before submitting a note, check that it is:
Written for the correct participant
Dated and time-stamped
Connected to the correct shift
Specific about the support delivered
Written using objective language
Linked to at least one relevant goal where applicable
Free from judgemental or unnecessary comments
Clear about incidents and follow-up
Consistent with the roster, service agreement and claim
Stored securely and accessible to authorised people
How to Write NDIS Progress Notes
Featured snippet answer: To write NDIS progress notes, record the participant, worker, date, support duration and activity delivered. Describe the participant’s response using observable facts, connect the support to an agreed goal, note any risks or incidents and identify follow-up actions. Complete the note promptly and make sure it matches the roster and payment claim.
A reliable structure makes the process easier for support workers.
Use This Four-Part Progress Note Structure
1. What was planned?
Identify the support scheduled for the shift.
Example:
Community access support from 9:00 am to 11:00 am, linked to the participant’s goal of increasing confidence when using public transport.
2. What happened?
Describe the activity and support actually delivered.
Example:
Travelled by bus with the participant to the local shopping centre. The worker provided one verbal prompt when using the ticketing machine.
3. How did the participant respond?
Record observable behaviour, words and outcomes.
Example:
The participant selected the correct bus independently and initiated the return trip without prompting.
4. What happens next?
Add any handover or follow-up.
Example:
During the next community-access session, practise planning the route using the transport application.
This structure is simple enough for a daily NDIS progress notes template and detailed enough to show what support took place.
NDIS Progress Note Template Australia
Participant:
NDIS number:
Date:
Shift start and finish:
Support worker:
Support type:
Planned support or participant goal:
Support delivered:
Participant response and outcome:
Risks, changes or concerns:
Incident report completed:
Yes / No / Not applicable
Follow-up or handover:
Worker sign-off:
Completion date and time:
A template should guide workers, not force every shift into identical language. Copying yesterday’s note and changing the date creates a record that looks generic and may not reflect what actually happened.
NDIS Progress Notes Examples
Example 1: Weak Note
Sarah had a good day. She was happy and enjoyed shopping. Everything was fine.
This note is short, but it provides little useful evidence. It does not identify the support delivered, objective observations, goal connection or outcome.
Example 2: Strong Community-Access Note
Community access support delivered from 10:00 am to 12:00 pm. The participant planned a shopping list and travelled to the supermarket with the worker. She located five listed items independently and asked a staff member for help finding one item. This activity supported her goal of completing community tasks with less assistance. No incidents occurred. Next session: practise completing the purchase within the agreed budget.
Example 3: Strong In-Home Support Note
Supported the participant with meal preparation from 4:00 pm to 5:30 pm. The participant selected a recipe, collected ingredients and completed the measuring tasks independently. One verbal prompt was provided when operating the oven. The participant stated, “I want to cook this again next week.” Kitchen safety steps were reviewed before the session ended.
Example 4: NDIS Progress Notes for SIL Providers
Night-shift support commenced at 10:00 pm. The participant requested assistance preparing medication in line with the documented medication procedure. At 11:15 pm, the participant reported feeling dizzy after standing. The worker supported the participant to sit safely, completed observations within the worker’s role and notified the on-call manager. A separate incident record was completed. Handover was provided to the morning worker.
For SIL providers, a progress note should not replace medication records, behaviour-support records or incident reports. Where an incident occurs, follow the organisation’s reporting process and the relevant SIRS compliance requirements.
Objective Language in NDIS Progress Notes
Objective language records what the worker saw, heard or did. Subjective language records an opinion, assumption or label.
Avoid this | Write this instead |
|---|---|
“The participant was aggressive.” | “The participant raised his voice and pushed the chair away.” |
“She was in a bad mood.” | “She declined the planned walk and said, ‘I would like to stay home today.’” |
“He was confused.” | “He asked the same question four times within ten minutes.” |
“She was lazy.” | “She declined to begin the activity after two prompts.” |
“Everything was normal.” | “No changes, concerns or incidents were observed during the shift.” |
Objective wording protects everyone involved.
It gives the participant a fair record, helps the next worker understand what occurred and provides the provider with a defensible account. The NDIS information-management standards also require participant records to remain accurate, current, confidential and appropriately accessible.
What Should You Not Put in a Progress Note?
Do not include:
Personal opinions about the participant
Insults, labels or judgemental descriptions
Unconfirmed diagnoses
Irrelevant information about family members
Information copied from another participant’s record
Details that belong in a separate confidential or clinical record
Statements that minimise a possible incident
Information you did not personally observe or verify
Workers should also avoid changing a note silently after submission. Any correction should preserve the original entry and create a visible audit trail.
NDIS Progress Notes Audit Requirements
NDIS auditors assess providers against applicable Practice Standards and quality indicators. These indicators include accurate information management, internal auditing, participant rights, incident management and evidence that systems are actually used.
During a practical review, progress notes may be checked for:
Completeness: Is there evidence for every relevant shift?
Timeliness: Were notes entered soon after the support?
Traceability: Can the provider identify the participant, worker and shift?
Consistency: Do the note, roster, invoice and claim match?
Objectivity: Does the note record facts rather than opinions?
Goal linkage: Does it explain why the support was funded?
Incident escalation: Were concerning events recorded through the correct process?
Security: Can only authorised people access or change the record?
The NDIA may review provider claims against complete and accurate records. Failure to produce adequate records during a payment-assurance review may result in money being repaid.
That is why “support delivered as usual” is not enough. It does not show what happened, how long the support lasted or whether it matched the claimed item.
For a wider audit view, read what NDIS auditors check.
What Records Must NDIS Providers Keep?
AEO answer: NDIS providers must maintain complete and accurate records of supports delivered. These may include invoices, support logs, rosters, case notes and service agreements. Records should identify the participant, NDIS number, support date, duration or quantity and support type. Additional records may include consent, incidents, complaints, credentials and relevant financial evidence.
The exact records required can vary by support category. Providers should check the official documentation requirements that apply to the supports they deliver.
NDIS Case Notes vs Progress Notes
Progress notes | Case notes |
|---|---|
Usually written after each shift or session | May include broader coordination and participant-history information |
Focus on support delivered and immediate response | May cover contacts, decisions, referrals and case-management actions |
Often linked directly to a rostered shift | May not always relate to one shift |
Emphasise progress towards goals | Can document a wider range of case activity |
In everyday NDIS operations, the terms are often used interchangeably. The label matters less than the content.
The record still needs to show what happened, who was involved and how the activity related to the participant’s support or goals.
Paper Notes vs NDIS Progress Notes Software
Area | Paper or generic documents | NDIS progress notes software |
|---|---|---|
Time of entry | Difficult to prove | Automatically time-stamped |
Structure | Depends on each worker | Guided prompts and templates |
Goal connection | Manually added | Can be linked to participant goals |
Legibility | May vary | Consistent digital text |
Retrieval | Manual search | Searchable participant record |
Amendments | Changes may be difficult to trace | Version history or audit trail |
Shift matching | Often manual | Connected to roster and worker |
Access control | Depends on storage process | Role-based permissions may be available |
The best option depends on the size and complexity of the provider.
A sole operator may be able to maintain quality records using a controlled template and secure storage. As the number of workers, participants and shifts grows, a purpose-built NDIS management software platform can reduce missing notes, improve consistency and make audit retrieval faster.
CareVisor connects participant information, rosters, shift notes, incident reports and documents in one platform. Its worker application includes participant notes, shift schedules, GPS clock-in and document uploads.
Current CareVisor Professional pricing starts at AUD $99 per month for four participants. The displayed price for 40 participants is AUD $250 per month, excluding GST, with unlimited staff accounts.
Providers can review the CareVisor features, compare current pricing or begin a 7-day trial.
Frequently Asked Questions
What Should Be Included in NDIS Progress Notes?
Include the participant, worker, date, support duration, support type, activities completed, objective participant response, link to goals, risks, incidents and follow-up actions.
How Often Should Progress Notes Be Completed?
Complete a note after every relevant shift or support session, preferably at or near the time the support was delivered. Timely entries are generally more accurate and easier to verify.
How Do I Access My Support Worker’s Progress Notes?
Participants can ask their provider how to access personal information held about them. The NDIS Practice Standards require providers to explain how participants may access or correct their information. Australian Privacy Principle 12 also generally requires covered organisations to provide access on request, subject to lawful exceptions.
Can a Support Worker Refuse to Share Notes With a Participant?
An individual worker may need to follow the provider’s authorised access process rather than handing over records directly. However, the provider should have a process through which the participant can request access. Access may only be restricted or redacted where a lawful exception applies.
Can AI Be Used to Write NDIS Progress Notes?
AI may help organise or improve wording, but it must not invent events, participant responses or outcomes. A worker should verify every detail before submission. Providers must also ensure any tool used protects participant confidentiality and complies with their consent, security and information-management obligations.
How Long Must NDIS Progress Notes Be Kept?
The NDIA’s current general record-keeping page does not state one universal retention period for every type of progress note. Retention can depend on the record type, provider obligations, contracts and applicable Commonwealth or state legislation. Providers should document their retention schedule and obtain compliance or legal guidance where needed. Worker-screening records, for example, have a specific seven-year retention requirement.
What Is a Simple Example of a Progress Note?
Support delivered from 2:00 pm to 4:00 pm for meal preparation. The participant selected a recipe and prepared ingredients with two verbal prompts. This supported the goal of increasing independent living skills. No incidents occurred. Next session: practise using the oven timer independently.
Key Takeaways
NDIS progress notes should show what support occurred, how the participant responded and how the activity related to a goal.
Notes must be factual, specific and written promptly.
Objective observations are stronger than labels or assumptions.
The note, roster, service agreement and claim should tell the same story.
An incident requires a separate incident-management process.
A consistent template improves quality, but copy-paste notes weaken evidence.
Digital systems can improve time-stamping, retrieval, access control and audit trails.
Providers should review note quality through regular internal file audits.
Conclusion: Make Every Shift Easier to Prove
Good NDIS progress notes do not need to be long.
They need to be clear.
A short note that identifies the support, records an observable outcome and connects the activity to a participant goal is more useful than a full page of vague wording.
Start by reviewing ten recent notes from different workers. Check whether each one identifies what happened, why the support was delivered, and what should happen next. Where the answers are unclear, improve the template and training before the same gap appears across hundreds of shifts.
CareVisor helps Australian providers connect progress notes with participants, goals, rosters, incidents and compliance evidence. Explore the complete NDIS service provider platform or start a free 7-day trial to see how structured, time-stamped records work in one dashboard.
