How to Write NDIS Progress Notes: The Complete 2026 Guide for Support Workers

Last updated 2026 · SupportNotes · Made in Australia

What is an NDIS progress note?

An NDIS progress note (often called a shift note or case note) is a short, factual record of what happened during a support shift. Every time you work with a participant, you write down what you did, how they were, anything that needed following up, and how the shift connected to the goals in their NDIS plan.

It might feel like paperwork, but a progress note is really three things at once. It is a care record, so the next worker knows what is going on. It is evidence that the support was actually delivered, which matters at audit and at the participant's plan review. And it is a safety record, because patterns in your notes — a fading appetite, a new bruise, a behaviour that keeps repeating — are how problems get spotted early.

The NDIS Practice Standards require registered providers to keep accurate, up-to-date and contemporaneous records of the supports they deliver. In plain English: write it down, write it truthfully, and write it soon. Your note is the proof that the shift happened the way you say it did.

• Care record — the next worker reads it before their shift
• Evidence — proof to the NDIS Commission that the support was delivered
• Safety record — early warning of health, mood or behaviour changes
• Goal tracking — shows the participant is moving toward their NDIS goals

What goes in an NDIS progress note? (the 8 elements)

There is no single official template for NDIS notes, but a complete note answers eight questions. If any one is missing, the note is incomplete. Think of these as your checklist before you hit save.

You do not need long paragraphs for each — a sentence or two is plenty. The goal is that someone who was not on shift, including an auditor years later, can read your note and understand exactly what happened and why it mattered.

• When — the date, plus start and end times of the shift, not just the date
• Who wrote it — your full name and role, so the record is traceable to you
• Who it is about — the participant's name (never a note that could fit anyone)
• What you did — the specific supports provided (e.g. 'assisted with showering and dressing', not 'personal care')
• How they responded — what you observed and heard: alert, tired, chatty, declined a task, needed prompting
• Concerns or changes — anything new: a skin mark, reduced appetite, a refusal, a near-miss
• Follow-up — what happens next, who you told, what to watch for on the next shift
• Goal link — which NDIS plan goal this shift worked toward (this is the element most often missed)

How do you write a note in objective, factual language?

The single biggest difference between a weak note and a strong one is objectivity. Write what you saw and heard, not what you assumed someone was feeling or thinking. You cannot verify another person's emotions — you can only verify their words and actions.

If a participant tells you how they feel, you can write it, in their own words and in quotation marks. If you are only guessing, leave the guess out and describe the behaviour instead. 'Sarah was upset' is an interpretation. 'Sarah was tearful, spoke quietly and said "I want to go home"' is an observation an auditor can trust.

The same rule applies to behaviours of concern. Avoid loaded words like 'aggressive', 'difficult' or 'naughty'. Describe exactly what happened, what you did in response, and the outcome. This protects the participant's dignity and protects you, because it shows you followed the plan.

• Write observations, not opinions — what you saw, heard and measured
• Quote the participant directly when recording how they feel
• Avoid judgement words: 'difficult', 'aggressive', 'good day', 'seemed happy'
• Do not speculate about causes you did not witness
• Never alter or backdate a note — correct an error with a new dated entry

Before and after: three real note rewrites

Here are three common shifts written two ways — the rough version most workers jot down, and the NDIS-aligned version. Notice the difference is rarely length. It is specificity, objective wording, and the goal link.

If you want twenty more rewrites across personal care, community access, medication and behaviour support, see our companion guide of NDIS progress note examples. For the underlying structure, the 8-element shift notes template breaks each field down.

• Community access — Rough: 'Took Sarah to the shops, she was a bit anxious but it was fine.' → Aligned: 'Attended local shopping centre for community access (10:30am–12:30pm). Sarah became visibly distressed (wringing hands) at the busy food court. Worker used agreed calming strategy (quiet seating, breathing exercise); Sarah settled within 8 minutes and completed shopping independently. Supports goal: "Build capacity to manage busy community settings."'
• Medication support — Rough: 'Gave meds as usual, no problems.' → Aligned: '8:00am — Participant self-administered Metformin 500mg and Ramipril 5mg with water, as per current medication plan dated 12/02/2026. Worker observed and confirmed both doses taken. No side effects reported. Medication chart signed. Supports goal: "Self-manage medication with supervision."'
• Personal care — Rough: 'Michael was a bit difficult this morning but we got there.' → Aligned: 'Michael initially declined his morning shower, stating "not yet." Worker offered a 20-minute delay; Michael agreed. Showered with verbal prompting only, no physical assistance. Dressed upper body independently, needed help with buttons. Skin intact, no redness. Supports goal: "Maintain personal hygiene with reducing support."'

How long after a shift do you have to write notes? (the 24-hour rule)

Write your note as soon as possible — ideally before you leave, while the shift is fresh. The widely used sector convention is to complete notes within 24 hours. The NDIS Practice Standards do not set out an exact deadline in hours, but they do require records to be contemporaneous, which means written at, or very close to, the time the support happened.

There is a practical reason beyond compliance: a note written days later is less reliable, harder to remember accurately, and weaker as evidence. Notes written in a bulk catch-up at the end of the week, or backdated, are a red flag in any audit. If you genuinely could not write a note at the time, record the actual date you wrote it and why there was a delay — honesty is always safer than a false timestamp.

Every shift needs a note, even quiet ones. If a shift was completely routine, a brief three-to-four-sentence note still has to name the supports, the participant's presentation, and the goal. 'No note' is never an acceptable record — and if a participant cancelled or was not home, that is still worth writing down.

• Best practice: write the note before you leave the shift
• Sector convention: complete within 24 hours
• Standard required: records must be contemporaneous (written at or near the time)
• Routine shifts still need a short factual note
• Never backdate — record the real date and explain any delay

How do you link a note to NDIS goals?

Goal linking is the element most workers skip — and the one that matters most at plan review. Every support you deliver should trace back to at least one goal in the participant's NDIS plan. When you name the goal in your note, you turn a record of 'what we did' into evidence of 'what the funding achieved'.

Before your shift, know the participant's current goals — they are in their support plan or service agreement, which your organisation should give you. Use the plan's exact wording where you can, so a planner or auditor can match your note straight to the goal. Do not write the vague version, 'worked toward goals'. Name the goal.

Over six months, a stack of goal-linked notes tells a clear story of progress that helps the participant get the right funding at their next review. For a deeper walkthrough, see our guide to goal-linked progress notes.

• Weak: 'Activity supports participant's NDIS goals.'
• Strong: 'Supports goal: "Travel independently on public transport." Participant bought a transport card unassisted for the first time.'
• Quote the plan's exact goal wording where possible
• Link every note to at least one funded goal

Progress notes vs incident reports: what's the difference?

These are not the same document, and one never replaces the other. A progress note records what happened during the shift, including any incident, as part of the ongoing care record. An incident report is a separate, formal document required under the NDIS (Incident Management and Reportable Incidents) Rules 2018 whenever a reportable or serious event occurs.

When something goes wrong — a fall causing injury, a medication error, an allegation of abuse or neglect, a behaviour that causes harm, or use of an unauthorised restrictive practice — you do two things. You write a factual progress note describing what you saw and how you responded, and you also lodge a formal incident report through your organisation's system. Reportable incidents must be notified to the NDIS Quality and Safeguards Commission within set timeframes (commonly 24 hours or 5 business days depending on severity).

In your progress note, reference the incident report number so the two records connect. Never try to use a progress note as a substitute for an incident report. Our incident report guide walks through each section with examples.

• Progress note — routine record of every shift, including incidents
• Incident report — separate mandatory form for reportable/serious events
• Both are needed when something goes wrong — write both and cross-reference
• Reportable incidents are notified to the NDIS Commission within set timeframes

How long must you keep NDIS progress notes? (the 7-year rule)

NDIS providers are required to keep participant records, including progress notes, for at least seven years. For records about a child, the period generally runs until the young person turns 25, whichever is longer. The note you write today could be requested in an audit, a complaint investigation, or a compliance review years from now.

That has real consequences for how notes are stored. Paper notes must be kept securely and stay readable for the full period — fires, floods and office moves are genuine risks over seven years, so many providers digitise. If you use care-management software, make sure you can still export and access records even if you switch platforms. And when a participant leaves your service, keep their records for the retention period; do not delete them.

Participants also have the right to access records about themselves under the Privacy Act 1988. Write every note as though the participant, their family and an auditor will all read it — because one day they might.

• Minimum retention: 7 years (longer for children — generally until they turn 25)
• Store securely and keep records readable and retrievable
• Keep exports if you change software platforms
• Do not delete records when a participant exits your service

The fastest way to write better notes

Good notes are a skill, and the good news is the structure is the same every time: facts, objective wording, and a goal link. Once you have the pattern, your notes get faster and your shifts end on time instead of with thirty minutes of paperwork.

You do not have to start from a blank box every shift. Jot your rough notes the way you naturally would — even in point form on your phone — and tidy them into NDIS-aligned wording afterwards. The free SupportNotes tool does exactly that: it takes your rough notes and reshapes them into clear, objective, NDIS Practice Standards-aligned progress notes in seconds. It runs on our own Australian server, never sends your text to ChatGPT, and never invents facts — you stay the author and you review every note before you submit it.

If you run or work for a provider preparing for certification, our SIL Rescue Kit bundles 65 audit-mapped policies, forms and registers — including documentation templates — so your whole evidence trail is ready before the auditor arrives.

• Write rough notes first, then refine — do not aim for perfect on the first pass
• Use the same 8-element structure every time so it becomes automatic
• Try the free SupportNotes tool to reshape rough notes in seconds — your facts stay yours
• Providers preparing for audit: the SIL Rescue Kit covers the wider documentation set

Frequently asked questions