NDIS Progress Notes: Good vs Poor (And How to Make Yours Audit-Ready)

Why "Good vs Poor" Is Really "Pass vs Fail an Audit"

When support workers ask "what makes a good progress note?", they usually picture neatness — full sentences, no spelling mistakes, a tidy paragraph. That's not what an NDIS auditor is reading for. A "good" note, in the sense that matters, is one that proves the right support was delivered to the right person, at the right time, in line with their goals and their plans. A "poor" note is one that leaves all of that unproven — no matter how neat it looks.

The distinction is sharp because the consequences are real. The same scribbled line that you forget by the next morning can, eighteen months later, be the document that decides whether a participant was kept safe, whether a shift was legitimately billed, and whether your organisation keeps its registration. Auditors don't take "we definitely did the support, it just wasn't written down" as an answer. The NDIS Practice Standards and the records expectations published by the NDIS Quality and Safeguards Commission work on a simple principle: if it isn't documented, in practice it didn't happen.

So throughout this article, read "good" as "audit-ready" and "poor" as "a finding waiting to happen". That reframing changes how you write before you've learned a single technique.

The Bridge: Your Notes Are the Evidence Auditors Sample

Here's the part most documentation training skips. Progress notes feel like a chore at the end of a shift, disconnected from the "real" compliance documents — the policies, the service agreements, the risk assessments. In reality, your notes are the single most-sampled piece of evidence in an NDIS audit, because they're the only record that shows what happened on the ground, day after day.

During a certification or verification audit — and during any NDIS Commission reportable-incident or complaint investigation — the auditor follows a predictable path:

1. They select a sample of participants (often the ones with the highest support needs or the most complex plans).
2. They pull that participant's plan, goals, and any behaviour support or risk plan.
3. Then they read a run of your progress notes and check: does what's written here actually match the funded supports and the goals? Were risks and incidents recorded? Was medication, behaviour, or a restrictive practice handled and documented the way the plan requires?

That third step is where providers pass or fail. A behaviour support plan can be flawless on paper, but if the notes don't show staff implementing the strategies it describes, the auditor records a non-conformance. A service agreement can promise community access goals, but if every note reads "watched TV, quiet day", there's no evidence the funded outcomes were ever worked towards. Good notes close the loop between the plan and the lived support. That's the bridge: documentation isn't separate from compliance — for an auditor, your notes are the compliance.

The Five Tests Every Good Note Passes

Before the workshop, lock in the five things that separate audit-ready notes from poor ones. Every rewrite below traces back to these:

1. Factual, not interpretive. Write what you observed — what you saw, heard, or measured. Never write what you assume it meant. "Appeared anxious" is your opinion; "paced the hallway and asked three times when his sister was coming" is a fact.
2. Specific about time and action. Real times, real durations, real sequence. "In the morning" tells an auditor nothing. "From 8:15am to 8:40am" lets them verify the shift, the billing, and the support.
3. Records the participant's voice and choices. What did the person say? What did they choose? Choice and dignity are core to the NDIS Code of Conduct — and an auditor wants to see the participant as an active person, not a passive subject things were "done to".
4. Shows the support you provided. Not just what happened, but what you did — the prompt, the assistance, the strategy from the plan. This is the evidence the funded support was actually delivered.
5. Links to a goal, risk, or plan. Where relevant, connect the note to the participant's plan goal or to a behaviour/risk strategy. Goal-linked notes prove funded outcomes were worked towards; risk-linked notes prove duty of care.

Hold those five in mind. You'll watch each one rescue a failing note in the next section.

The Workshop: 6 Poor Notes Rebuilt Line by Line

These are composites of the kinds of notes that show up in real SIL files — names changed, scenarios typical. For each, read the poor version, then the rebuild, then the "why" so you can copy the move, not just the wording.

1. Personal care — the "good day" trap

2. Behaviour support — labels vs observations

3. Medication support — vague is dangerous

4. Community access — the goal that goes missing

5. Overnight / SIL — the "nothing happened" shift

6. Incident — when the note becomes a legal document

Poor Words vs Good Words: The Swap Table

If you change nothing else, change your words. These swaps fix the single most common reason notes get flagged — recording opinions instead of observations. Keep this table near you for the first month and the habit becomes automatic.

Your 8-Point Note Self-Scorecard

Run any note past these eight checks before you submit it. Eight ticks is audit-ready. Anything you can't tick is a gap an auditor would find — fix it before you sign off, not eighteen months later in an audit interview.

Want to know how your whole documentation system would hold up, not just a single note? The free SIL Readiness Scorecard walks you through the records an auditor samples — notes, incidents, medication, behaviour support, consent — and shows you where the gaps are before an auditor does.

How to Write Good Notes Faster (Without Cutting Corners)

The honest reason poor notes happen isn't laziness — it's time. After a long shift, writing a structured, objective, goal-linked note for every participant feels like a second job. So the corner that gets cut is detail, and detail is exactly what the auditor needs. The fix isn't "try harder", it's a better process:

• Write at the point of support, not from memory. A two-line jot during the shift ("3:20pm, bus cancelled, Maria raised voice, offered garden/music, chose garden 3:35pm") becomes an accurate note later. Memory at 10pm is where vague language comes from.
• Use a fixed structure so you're not reinventing the note each time. What happened → when → what the participant said/did → what support I gave → any risk → goal link. Same skeleton, every shift.
• Don't pad — a tight 4–6 sentence note that ticks the scorecard beats a paragraph of filler. Auditors value precision over length.
• Let a tool do the rewriting. This is the highest-leverage change. Paste your rough jottings into the free Notes Rewriter and it restructures them into objective, NDIS-aligned progress notes — fixing the language, adding structure, and prompting for the goal link — while keeping your facts untouched. It will never invent something you didn't write, which is the whole point: it makes a true note well-written, not a thin note longer.

Good notes aren't about better writing. They're about leaving behind a record that proves the right support reached the right person — the exact evidence an auditor opens your files to find. Get the five tests into your hands, run the eight-point scorecard, and let a tool carry the rewriting load, and "audit-ready" stops being a stressful event and becomes just how you write.