If you’re a support worker, you’ve probably had a note sent back at least once. Maybe more. It’s frustrating — you were there, you did the session, you know what happened. But the note didn’t pass.
The thing is, most rejected notes aren’t rejected because of bad care. They’re rejected because of bad documentation. The session was fine. The paperwork wasn’t. Here are the six reasons that come up again and again.
No connection to NDIS plan goals
Every session you deliver needs to relate back to the participant’s NDIS plan goals. If your note describes what happened but doesn’t mention which goals the activities supported, it looks like the session wasn’t goal-directed — and that makes it hard to justify the funding. Providers and plan managers look for this first.
Too vague or too short
“Went to the shops. Had a good time.” That’s not a progress note — it’s a text message. Notes need specific details: what did you do, how did the participant respond, what choices did they make, what progress did you observe? Without specifics, there’s nothing for the next worker to build on and nothing for an auditor to verify.
Missing incident documentation
Something happened during the session — a fall, an aggressive episode, a near-miss — but the note doesn’t mention it, or mentions it without the required detail. Under NDIS rules, incidents need to be documented with what happened, when, who was involved, what actions were taken, and whether it’s reportable. A one-line mention isn’t enough.
Clinical language the worker didn’t actually use
Some workers try to make their notes sound more professional by adding clinical terms they wouldn’t normally use. “The participant presented with dysregulated affect” when you actually observed that she was grumpy. Over-clinical language can be a red flag for providers — it suggests the note doesn’t reflect what really happened. Auditors want authenticity, not jargon.
Session details don’t match the service agreement
If your note says you did 3 hours of community access but the booking was for 2 hours of personal care, something doesn’t add up. The session type, duration, and location in your note need to match what was agreed in the service agreement. Mismatches create claiming problems and audit flags.
No participant voice
NDIS documentation needs to be person-centred. That means the note should reflect the participant’s choices, preferences, and decisions — not just what the worker did. If your note reads like a list of tasks you completed without any mention of how the participant was involved, directed, or responded, it doesn’t meet Practice Standards requirements.
The pattern behind rejected notes
Notice that none of these six reasons are about the quality of care you delivered. Every single one is about how the note was written. The session could have been brilliant — but if the documentation doesn’t capture goals, incidents, participant voice, and session details in the right structure, it gets sent back.
This is the problem structured documentation solves. When your note follows a framework that prompts for goals, participant choices, incident details, and session context — the rejection reasons disappear. Not because you changed how you work, but because the structure catches what you might forget to include.
Stop getting notes sent back
Clio generates structured, compliant NDIS progress notes from your shift description. Goals are linked automatically. Incidents are flagged and documented. Every note follows the CLIO Framework — built around what auditors actually look for.
Try Clio for free →