How Good Case Notes Become Your NDIS Audit Evidence

The Documentation-to-Compliance Link, in One Sentence

Here it is, plainly: your case notes are the evidence an NDIS auditor samples, so a support that isn't written down well cannot be counted as having been delivered. That's the whole link. Everything else in this article is detail on how to make each note carry the weight an auditor puts on it.

It catches good providers off guard because the support often was excellent. The participant had a genuinely good day, made real progress, was kept safe. But the auditor wasn't in the room. They arrive weeks or months later, open a file, and have to reconstruct what happened from the words on the page. If the words are vague — "assisted as usual", "good day" — the auditor can't verify anything, and a delivered support quietly becomes an unproven one. The phrase that gets used in non-conformity reports is some version of: unable to establish from the records that the funded support was delivered in line with the participant's plan.

So the job of a case note isn't to describe the shift to yourself. It's to leave behind proof for a stranger who will read it later with a checklist in hand.

What an Auditor Actually Does With Your Case Notes

It helps to picture the mechanics. During a certification or verification audit, the assessor doesn't read every note you've ever written — there isn't time, and they don't need to. They sample. They pick a handful of participants, pull their files, and follow a thread: plan goal → funded support → service agreement → case notes → incident records → invoicing. The case notes sit right in the middle of that chain, and they're where the thread most often breaks.

For each sampled participant, the auditor is silently asking a short list of questions as they read:

• Did the funded support actually get delivered — on the days and at the level the plan and agreement say?
• Does the support connect to a goal in the participant's NDIS plan?
• Is the participant exercising choice and control, and is that visible in the record?
• When something went wrong, was it recorded, managed and escalated correctly?
• Are the records accurate, complete, dated, signed and written close to the event?

Notice that every one of those questions is answered — or not — by your case notes. The auditor isn't grading your handwriting or your prose. They're checking whether the record proves the thing they need it to prove. A good case note answers the question before it's asked. A weak one forces the auditor to write a finding because the answer simply isn't there. If you want the full picture of what an assessor expects file by file, our companion guide on what to prepare for every Practice Standard maps it out; this article zooms into the case note itself.

The Five Tests That Turn a Note Into Evidence

Across thousands of sampled files, the difference between a note that counts and a note that gets flagged comes down to five qualities. A note that passes all five is audit evidence. Miss any one and you've left a gap.

Anatomy of a Note That Survives an Audit

Let's make this concrete. Below are the parts of a case note an auditor leans on most, each shown as a weak version and a strong version. The weak ones aren't lazy — they're how most of us write when we're tired at the end of a shift. The strong ones aren't longer; they're just specific.

The support delivered

Record the real task and how the participant engaged. The funding category ("personal care", "community participation") tells an auditor nothing about whether the support happened.

Participation and independence level

This is the field auditors most often find missing — and it's the one that proves capacity building, the whole point of much NDIS funding. State the level of support for each task.

Goal link

Name the goal from the plan and describe observable progress or a real barrier. "Worked on goals" asserts a benefit without proving one. Our guide to writing goal-linked progress notes goes deeper on phrasing this consistently across a team.

Wellbeing and observation

Document what you saw and what the participant said — not your interpretation. "Was anxious" is a guess an auditor can't rely on; the behaviour you observed is fact they can.

Incidents and significant events

If something happened, record it factually with exact times and the action taken. If nothing did, say so — a blank field reads as an oversight, not as "all clear". And remember the note is only the start: a reportable incident also follows your provider's incident process, covered in incident management for SIL providers.

Following One Support All the Way to the Auditor's Tick

To really see the documentation-to-compliance link, it helps to trace a single support from the plan to the moment an auditor accepts it. This is exactly the path an assessor walks when sampling a file.

Now imagine step 4 said only "community access — good session." The plan goal still exists. The funding still exists. The invoice still exists. But the link in the middle — the proof that this support worked toward this goal on this day — is missing. The chain breaks exactly where the case note should hold it together, and the auditor has to record that the support couldn't be verified from the records. Same shift, same worker, same good intentions — completely different audit outcome, decided entirely by the note.

Where This Comes From: the Practice Standards

None of this is invented house style. The expectation that your records prove what happened flows directly from the NDIS Practice Standards. The Core Module includes an outcome on information management requiring providers to keep accurate, complete and timely records of the supports delivered to each participant — and to store and retrieve them securely. Other outcomes — on individual support planning, the delivery of supports, and the management of incidents — all rely on those records as their proof.

Sitting underneath that, the NDIS funds supports against the goals in each participant's plan. So when the Practice Standards ask for evidence that supports were delivered and worked toward plan goals, the case note is where that evidence is created. The retention rules from the NDIS (Provider Registration and Practice Standards) Rules then require you to keep those records for at least 7 years — or until a participant who was a minor turns 25 — which is why "we did it but the note's gone" is not a defence an auditor can accept. For how files get sampled on the day, the SIL audit preparation guide walks through the process.

Six Things That Kill a Note's Evidentiary Value

These are the patterns that turn up again and again in flagged files. Each one quietly drops a note from "evidence" back to "reminder".

• Categories instead of detail. "Provided personal care" proves nothing happened beyond a billing label. Record the actual support and how the participant engaged.
• Vague filler. "Good day", "as usual", "settled and happy" — auditors read these as the absence of a record, not the presence of one.
• Missing participation level. Without "independent / prompted / assisted", there's no way to show capacity building, so progress can't be evidenced.
• Copy-paste notes. Identical entries across days are flagged as a documentation-integrity issue — they suggest nobody actually observed the shift. Even routine days differ.
• Interpretation in place of observation. "Was aggressive" is a conclusion; "raised his voice and pushed the chair away when asked to wait" is evidence. Auditors trust the second, not the first.
• Late, unattributed entries. Notes written days later, undated, or with no clear author break the "timely" and "attributable" tests at once. If a note must be late, mark it clearly as a late entry with the real time.

If you want a quick read on how your current notes stack up against these before an assessor does, the free SIL Readiness Scorecard flags the documentation gaps that most often become non-conformities. For more worked examples by support type, our progress note examples library and the case note examples for support coordination are good companions to this page.

The Defensible Case Note Checklist

Run this in your head before you sign off any note. If you can tick all eight, the note will stand up when it's read months later by someone you've never met.

• Identified: participant, worker, date and exact shift times are all on the note.
• Specific: the actual support is described, not just the funding category.
• Levelled: the participation/independence level is recorded for each support.
• Goal-linked: the relevant NDIS plan goal is named, with observable progress or a real barrier.
• Observable: what you saw and what the participant said — no interpretations or diagnoses.
• Incident-clear: any incident recorded with times and actions, or "no incidents this shift" stated explicitly.
• Timely: written at or near the end of the shift, dated and time-stamped.
• Signed: attributed to you and consistent with the service record / invoice for that date.

Get those eight right, every shift, and you've done more for your audit readiness than any last-minute scramble before assessment day. The compliance isn't a separate task you do later — it's built one note at a time, by the workers who were actually there.