NDIS progress notes: template and examples

A simple structure for writing progress notes that are actually useful — to the next worker, to a plan review, and if they're ever asked for.

All examples below are entirely fictional — no real participant has been described on this page.

The template

Date and time

When the support was delivered — matters for both record-keeping and matching against claims.

Support delivered

What you actually did, in plain language — not just the support item name.

Observations

What you noticed — mood, engagement, anything out of the ordinary — described factually, not interpreted.

Progress toward goals

How what happened today connects to a goal in the participant's plan, if it does.

Any incidents or concerns

Anything that needs to be escalated or followed up — flagged clearly, not buried in the narrative.

Next steps

What should happen next time, or what another worker reading this note needs to know.

Worked examples

Example — community access support

Useful

10:00–12:00. Supported Jordan to attend their weekly swimming session at the local pool. Jordan was in good spirits and initiated conversation with the lifeguard independently, which is a step toward Jordan's goal of building confidence in community settings. No concerns during the session. Next session: continue practising independent check-in at reception.

Too thin

Took Jordan swimming. Went fine.

The first version records what was observed, links it to a plan goal, and gives the next worker something to act on. The second gives almost nothing to work from and nothing an auditor or reviewer could use to show progress.

Example — personal care support

Useful

08:00–09:00. Assisted Priya with morning personal care routine as per support plan. Priya required standby assistance only for showering today, a reduction from the full assistance recorded last fortnight. Noted and will mention at next plan review. No incidents.

Too thin

Helped with personal care, no issues.

The first captures a meaningful change in support need — exactly the kind of detail a plan review relies on. The second loses that entirely.

How Caretora helps

Progress notes in Caretora are written against the actual shift and participant, with structured prompts instead of a blank text box — so notes stay consistent across your whole team, not dependent on each worker remembering what to include.

Make consistent progress notes the default, not the exception.

Start a free 3-day trial — no charge until the trial ends.

Start free 3-day trial

FAQ

How long should a progress note be?

Long enough to be useful to someone who wasn't there — what happened, anything notable, and what's next — and no longer. A few sentences is usually enough; a wall of text is harder to read and doesn't make the note more defensible.

What should never go in a progress note?

Opinions dressed up as fact ("Jordan was being difficult" instead of describing what actually happened), other participants' identifying details, and anything you wouldn't be comfortable the participant or their family reading — because they're generally entitled to.

Do progress notes need to link to plan goals?

Not every single note will touch a goal directly, but where a session does relate to progress toward one, recording that link is one of the clearest ways to show a plan is actually being worked, not just serviced.

What if something goes wrong during a session?

Note it factually in the progress note, and follow your organisation's incident reporting process separately — a progress note isn't a substitute for a proper incident report when something meets that threshold.