What makes an NDIS progress note actually good
Most progress notes are written in a hurry at the end of a long shift, and it shows. The difference between a note that protects you and one that doesn't isn't length or vocabulary. It's whether someone who wasn't there can tell what actually happened.
The short version
- Write what you saw and heard, not what you concluded.
- Tie the support back to the participant's goal. That's what makes it fundable and reviewable.
- Quote people rather than labelling them. "He said he didn't want to go" beats "he was uncooperative".
- Note anything that changed, and what you did about it.
- Write it before you leave. A late note about an incident looks worse than the incident.
The test a good note has to pass
Imagine the participant's coordinator reads your note in three months, at a plan review, with no memory of the shift. Or an auditor reads it cold. Or the participant's mother reads it, because she is entitled to.
Could each of them tell what support was delivered, how the participant responded, and what needs to happen next? If not, the note is decoration.
A progress note is not paperwork about the shift. It is the evidence the shift happened and did something useful.
The five things worth including
- What support you actually delivered. Not "personal care" but what that meant today.
- What the participant did and said. Observable, specific, in their words where you can.
- How it connects to a goal. Community access, independence, daily living, whatever their plan names.
- Anything that changed or concerned you. Skin, mood, appetite, mobility, a comment that worried you.
- What happens next. Who you told, what you're flagging, what the next worker should know.
Before and after
The most common weak note is not wrong, it's empty. Compare:
Weak
Attended shift with Margaret. Assisted with personal care and made lunch. She was in a good mood today. All went well, no issues.
Strong
Supported Margaret with showering and dressing. She washed her own hair with the long-handled brush and said "I've got this one." That's the second time this week she's managed it without prompting, which is progress toward her independence goal. Made lunch together; she chopped the vegetables seated. Noted some redness on her left heel, took a photo and messaged the coordinator. Next worker: check the heel before her walk.
Same shift. The second one evidences a goal, flags a health concern with an action, and hands over usefully to the next person. It took about ninety seconds longer to write.
What to leave out
- Opinions dressed as facts. "He was aggressive" is a conclusion. "He raised his voice and pushed the chair away when I suggested leaving" is what happened. Let the reader draw the conclusion.
- Labels you're not qualified to give. You are not diagnosing.
- Judgements about family. Record what was said and done, not what you think of them.
- Other participants' information. Never name someone else in a participant's record.
- Filler. "All good", "usual shift", "nothing to report". If a shift genuinely had nothing unusual, say what you delivered and how they responded, that is not nothing.
The incident-note trap
The notes that matter most are the ones written on the worst days, and they're the ones most often rushed. Two rules:
- Write it the same day. Not the next shift, not Sunday night. A note about an incident dated four days later invites the question of what else was reconstructed from memory.
- Facts and sequence. What happened, in order, what you did, who you notified and when. Do not speculate about cause and do not soften it. An honest, specific account of a bad shift is a defensible one.
Why the note gets lost, not written badly
In a lot of services the note is fine and the system is the problem. The worker texts it to the coordinator, who copies it into a spreadsheet, which someone attaches to an email at plan review. By then the detail is gone and nobody can prove when it was written.
A note is only as good as the trail attached to it: which participant, which shift, which goal, who wrote it and when. That's what turns a paragraph into evidence.
Common questions
How long should a progress note be?
Long enough that someone who wasn't there understands what happened, short enough that it actually gets written. Three to five specific sentences beat a page of generic description. Specificity is the measure, not length.
Can I write notes at the end of the week?
You can, but you shouldn't. Accuracy drops fast, and a late note about anything serious is hard to defend. Write at the point of care, while it's still in your head.
What if nothing happened?
Something always happened, you delivered support and a person responded to it. Record what you did and how they responded. "Nothing to report" is the one note guaranteed to be useless later.
Notes that land where they're needed
In CiaraLink, a support worker writes the note on their phone at the point of care. It attaches to the shift, the participant and the goal, and the coordinator and allied health team see it straight away. No re-typing, no lost detail.
This guide is general information for Australian care teams, not legal or compliance advice. CiaraLink is not affiliated with, or endorsed by, the NDIA or the NDIS Quality and Safeguards Commission. Follow your own organisation's policies and the current NDIS Practice Standards, and report incidents through your required channels.