NDIS Progress Note Examples: Good vs Non-Compliant, By Support Type
Last updated 2026 · SupportNotes · Made in Australia
A good NDIS progress note answers four things in plain English: what support you gave, how the participant responded (facts, not feelings you guessed), what you did about anything that came up, and which of their NDIS goals it links to. A non-compliant note is vague ("had a good day, all good"), records opinions instead of observations, or never mentions a goal. Below are copy-and-adapt before/after examples for personal care, community access, daily living, medication and behaviour support — each one showing exactly why the good version passes. Write it once, write it right, and an auditor (or the next worker on shift) can trust it. Short on time? Paste your rough note into the free SupportNotes rewriter and get an audit-ready version in seconds.
What makes an NDIS progress note 'good' (and what gets it flagged)?
You are not writing an essay. You are leaving a record that the next worker, the participant's family, and one day an NDIS auditor can read and trust. A good note is specific, factual, and ties back to the person's funded goals. A flagged note is the opposite: vague, full of opinions you can't prove, and silent on goals.
There is no single mandated format under the NDIS — the NDIS Practice Standards expect registered providers to keep accurate, timely records of the supports delivered, but they leave the exact layout to you. So the difference between a good note and a non-compliant one is almost never about length. It is about four habits you can build in a week.
- Say what you actually did. "Assisted with showering and dressing" beats "provided personal care."
- Record what you observed, not what you assumed. "Ate half of breakfast" is a fact; "seemed depressed" is a guess.
- Note what you did about anything that came up — the strategy you used and whether it worked.
- Name the NDIS goal. Use the wording from their plan where you can. This is the part most workers skip, and the part that matters most at plan review.
- Write it at the end of shift, not days later. Notes written soon after are more accurate and far easier to trust.
Personal care: before vs after
Personal care notes get flagged most often because workers write "assisted with personal care" and stop. That single line tells an auditor nothing — it doesn't show what level of support the person needed, whether that's changing over time, or which goal it serves.
Notice how the good version below records the level of help (verbal prompting vs hands-on), a safety observation (skin check), the participant's own choice, and the goal. None of it is long. It is just specific.
- Why it passes: shows the exact level of support, so progress is visible over time.
- Why it passes: records a safety observation (skin check) without making a medical judgement.
- Why it passes: respects dignity — the participant's choice is documented, not dismissed as 'difficult.'
- Need a full set for this support type? See our deep dive on personal care progress note examples.
Community access: before vs after
Community access shifts are about building capacity, so the note needs to show what the participant did themselves and what support helped. "Took her to the shops, all fine" proves nothing was learned and nothing was funded for a reason.
When something tricky happens — like distress in a busy place — the good note records the trigger as an observation, the strategy you used, and the outcome. That is exactly what an auditor wants to see.
- Why it passes: the trigger is described as what you saw, not 'she got upset about nothing.'
- Why it passes: it names the strategy and whether it worked — useful for the next worker.
- Why it passes: it shows growing independence, which is the whole point of the funding.
- More models like this: see our community access progress notes guide.
Daily living and skill development: before vs after
Daily living notes should capture the small wins. A participant cracking two eggs with less prompting than last week is real, fundable progress — but only if you write it down in a way that shows the trend.
The good example below is short and still complete. It names the task, the level of prompting, the participant's words, and the goal, and it sets up the next step so the following worker knows where to pick up.
- Why it passes: it compares to last week, so skill development is visible.
- Why it passes: it separates what he did alone from what needed support.
- Why it passes: the 'next shift' line turns a note into a plan the team can follow.
Medication support: before vs after
Medication notes carry the most risk, so they need the most precision. "Gave meds, no problems" is a compliance gap waiting to be found — it doesn't say what, how much, when, or whether the person took it.
Always record medication against the participant's current medication management plan, note your role (prompted, supervised, or administered — within your scope and training), and document any refusal or side effect. If a dose is missed or wrong, that is also an incident — see incident reporting vs progress notes.
- Why it passes: names the medication, dose, time and the plan it follows.
- Why it passes: states the worker's role clearly — observed self-administration, not 'gave.'
- Why it passes: records the medication chart was signed, closing the audit loop.
- Stay inside your scope: only administer or assist with medication if you are trained and authorised to. See the medication record guide.
Behaviour support: before vs after (and when it becomes an incident)
Behaviour-of-concern notes are where emotional, judgemental language causes the most damage. Words like 'aggressive,' 'meltdown,' or 'attention-seeking' are interpretations, not observations — and they can harm the participant's dignity and your provider's compliance position.
Describe what you saw and heard, the antecedent (what happened just before), the behaviour support plan step you followed, and the outcome. Remember: if anyone is harmed, or a restrictive practice is used, it is also a reportable matter and needs a separate incident report — the progress note alone is not enough.
- Why it passes: every behaviour is observable and measurable, never labelled.
- Why it passes: it records the antecedent, the plan step used, and the outcome.
- Why it passes: it cross-references the formal incident report so the two records link.
The fastest way to write notes like these every shift
You don't have to remember all of this at the end of a 10-hour shift. Jot your rough facts — even in point form on your phone — then let the tool do the formatting. The free SupportNotes rewriter takes your rough shift notes and reshapes them into NDIS Practice Standards–aligned wording in seconds. It never invents details: your facts in, a clean professional note out, kept on an Australian server.
You stay the author and you review every note before you save it. Think of the tool as the structure-and-grammar layer, and these examples as the model you're aiming for. If you run a SIL house and want the full documentation set — shift note templates, medication charts, incident forms and more — the SIL Rescue Kit pack covers the documents auditors actually ask for.
- Free to start, no card needed — paste a rough note and get an audit-ready version.
- Works for every support type above: personal care, community access, daily living, medication, behaviour.
- Pair it with the shift notes template so your team writes the same way every time.
Frequently asked questions
What does a good NDIS progress note look like?
A good NDIS progress note states the date, time and duration, your name and role, and the participant's name — then it records what support you provided, how the participant responded (observable facts, not assumptions), anything you did about a concern, and which NDIS goal the support links to. It is written soon after the shift and stays factual. Most effective notes are roughly 80–200 words: long enough to be complete, short enough to read quickly.
What is the difference between a good and a non-compliant progress note?
A non-compliant note is vague ('had a good day, all good'), records opinions you can't verify ('seemed happy,' 'was difficult'), or never mentions a goal. A good note is specific about what you did, describes what you actually observed, and links the support to the participant's funded NDIS goals. The difference is rarely about length — it's about specificity, objectivity and goal linkage.
Do I need a different format for personal care vs community access notes?
No — the same core elements apply to every support type: what support you gave, how the participant responded, what you did about anything that came up, and the goal it links to. What changes is the detail you emphasise. Personal care notes focus on the level of support and dignity; community access notes show independence and any strategies used; medication notes need precise drug, dose, time and plan details. Use one consistent structure and adapt the content.
Can I copy these NDIS progress note examples directly?
Use them as models, not as text to paste unchanged. Every note must reflect what actually happened on your shift with your participant. Copying a fixed example word-for-word across shifts creates inaccurate records, which is a serious problem in an audit. Adapt the wording to the real facts each time — or paste your own rough notes into the free SupportNotes rewriter to reshape them into this kind of professional format.
When does a progress note also need an incident report?
Whenever something goes wrong: a fall causing injury, a medication error, behaviour resulting in harm, use of a restrictive practice, or any allegation of abuse or neglect. In those cases you write a factual progress note describing what happened AND lodge a separate incident report through your organisation's system. Reportable incidents must also be notified to the NDIS Quality and Safeguards Commission within the required timeframes. Never use a progress note as a substitute for an incident report.
How quickly should I write my progress notes?
As soon as possible after the shift, ideally at the end of it — not days later. The NDIS Practice Standards expect accurate, timely records, and notes written soon after events are more reliable and easier to trust in an audit. If you're pressed for time, capture rough facts on shift and tidy them straight after using a tool like the SupportNotes rewriter, then review before saving.
Turn your rough notes into an audit-ready note — free
Paste how you really write. Get a clear, objective, NDIS-aligned note in seconds. Private — runs on an Australian server, never sent to ChatGPT.
Paste your note → free