Everyday Documentation for Support Workers: A Practical Guide

A shift note that reads "had a good day, no concerns" tells the next worker almost nothing. A shift note that reads "ate full breakfast and lunch, joined the walking group for 20 minutes, mentioned twice that his knee was sore going up stairs" tells them exactly what to watch for tomorrow. Same shift, wildly different value, and the difference is entirely in how the worker chose to write it.

What makes a case note actually useful?

Specificity and fact. A useful case note describes what was observed and what was done, in plain, concrete terms, rather than a vague summary or a worker's interpretation dressed up as an observation. Where the person's own words matter, "I don't want to go today" versus a worker's paraphrase of "seemed reluctant", using their actual words is more accurate and more useful to whoever reads the note next.

When should documentation actually happen?

As close to the event as possible, ideally throughout the shift rather than compressed into the last ten minutes. Notes written close to the moment are simply more accurate than notes reconstructed from memory at the end of a long day, when small but important details have already started to blur. Treating documentation as an ongoing habit, a quick note after each significant moment, rather than a single end-of-shift task also makes the job itself feel less like an admin burden tacked onto the real work.

What's the difference between fact and opinion, and why does it matter?

A fact is something directly observed, said or done. An opinion is an interpretation of what that might mean. Both have a place in good documentation, but they need to stay clearly separated. "Refused lunch" is a fact. "Seemed to be punishing staff by refusing lunch" is an opinion, and presenting it as if it were an observed fact can shape how the next reader, including a clinician or an auditor, understands a situation that might have a completely different explanation.

What does this look like for incident records and handovers specifically?

• Incident records: what happened, when, who was involved, what was done immediately after, and what was reported to whom. Facts first, in sequence, without minimising or catastrophising
• Shift handovers: what matters for the next worker specifically, changes from the person's usual pattern, anything flagged for follow-up, anything escalated and its current status
• Both: written promptly, factually, and in a way that would make sense to someone who wasn't there

How CORA's course fits into this

CORA's course Everyday Documentation, part of the Disability Understanding & Daily Life stream in the course library, covers writing case notes, incident records and shift handovers that meet NDIS requirements, treating clear, factual documentation as a daily skill rather than an end-of-shift afterthought. It builds a worker's understanding and judgement, and does not replace an organisation's specific documentation systems or templates.

To map this alongside the rest of the Disability Understanding stream for a team, try the Pathway Builder, free and no sign-up required, or request a demo.

Sources and further reading

• NDIS Practice Standards, NDIS Quality and Safeguards Commission

This page is general information for support workers and providers, not legal advice. Always follow your organisation's specific documentation policies and systems.