The NDIS Quality and Safeguards Commission doesn't audit your intentions. It audits your records.
For many providers, the gap between what actually happens during a shift and what ends up in the documentation is wider than they'd like to admit. Progress notes get written hours after the shift ends, sometimes the next day, from memory. They're vague, inconsistent, or missing altogether.
When an audit arrives, or when a participant's NDIS plan comes up for review, that gap becomes a real problem.
What the Commission actually looks for
At a minimum, compliant shift documentation should capture:
- What support was delivered, and how it connects to the participant's stated goals
- Any notable changes in the participant's health, mood, or behaviour
- Incidents, even minor ones, and what action was taken
- Who delivered the support and when (not just a date: an actual time)
The standard isn't burdensome. The problem is that most providers have no system to make it consistent. Documentation quality varies by staff member, by shift type, and by how tired someone is at the end of a long day.
The memory problem
A support worker who finishes a four-hour shift, drives home, picks up their kids, and then opens a laptop to write their progress notes is working from a degraded memory of what happened. Important details get omitted, not through carelessness, but because the human brain doesn't store events in audit-ready format.
The fix is simple in principle: documentation should happen at the point of care, or immediately after the shift ends, on the device the worker already has in their pocket.
What good documentation looks like in practice
Here's the difference between a progress note that creates compliance risk and one that doesn't.
Insufficient:
"Client was well today. Assisted with personal care and meals. No concerns."
Compliant:
"Provided assistance with shower and breakfast as per care plan. [Client name] reported feeling some knee discomfort, noted for coordinator follow-up. Engaged with conversation about upcoming family visit; positive mood throughout. Shift completed without incident."
The second note takes two minutes longer to write. But it records a health observation, shows person-centred support, and demonstrates that the worker is engaged, not just present.
Making it the default
The challenge isn't getting staff to understand why documentation matters. Most already do. The challenge is removing every possible friction from the act of doing it.
That means:
Prompts at shift end. When a shift is marked complete, the worker should see a documentation prompt before they can clock out. Not as a punishment — as a reminder that it's part of the job.
Structured fields, not a blank text box. A blank text box produces inconsistent notes. A form with guided fields (mood, health observations, goals addressed, incidents) produces consistent, complete records every time.
Offline capability. Not every shift happens somewhere with good signal. Documentation tools that require internet access get skipped in rural and remote settings.
Incident escalation built in. When something notable happens, the worker shouldn't have to figure out who to call. A built-in escalation path means nothing slips through.
The audit-readiness question
A useful test: if the NDIS Commission called tomorrow and requested records for the last 90 days of shifts for three participants, how long would it take you to compile them?
If the answer is "hours" or "I'd need to contact several staff members," the documentation system isn't working.
If the answer is "I'd pull the reports from the platform right now," you're in good shape.
The goal isn't to pass audits. It's to deliver good care and have a clear record that you did. Those are the same thing.