Compliant NDIS Shift Notes: The Good Day Problem | NoteGate

What makes a shift note compliant with the NDIS Practice Standards?

By NoteGate Research Team · Published 10 October 2026 · Last reviewed 10 October 2026

Short answer: the NDIS Practice Standards set no shift note format. They ask that participant information is accurately recorded and current, so a compliant note shows what support was delivered, how it relates to the participant’s plan and goals, and what the participant did or said, in specific, objective terms. A note that says “client had a good day” shows none of that.

Key takeaways

What makes a shift note compliant with the NDIS Practice Standards?

A compliant shift note accurately records what happened on the shift, in enough specific detail that someone who was not there can see what support was delivered and how it served the participant’s plan. The core module of the NDIS Practice Standards asks for participant information that is “identifiable, accurately recorded, current and confidential”, and for records kept “in an accurate and timely manner”. It sets no template. For what a note should include, see what an NDIS shift note must include.

A compliant note showsWhy an auditor looks for it
What support was deliveredIt is the evidence that the funded support happened
How it relates to the plan and goalsIt shows supports match what was agreed, not only that time was spent
What the participant did, said or choseIt shows the participant’s voice and response
Facts, not opinionsAn objective note can be relied on later. See the objective standard
Anything the next worker needsIt supports continuity and risk awareness
Entered promptlyTimely records are more accurate and more credible

Why does “client had a good day” fail as evidence?

Because it describes a feeling, not a support. An auditor reading it cannot tell what the worker did, whether the participant’s goals were worked on, or whether anything went wrong. The Commission says auditors review participant records and speak to workers and participants, so a vague note has to be explained by someone who may not remember the shift (types of audits). The sections below show three weak notes beside stronger versions.

Fictional examples. No real participant data.

Weak

Client had a good day. No issues.

Stronger

Supported P-01 on a 40-minute walk to the local shops, as planned for the community access goal. P-01 chose the route and paid for a drink at the cafe with minimal prompting from me. Mood was upbeat throughout. No incidents. Next worker: P-01 asked to try the library on Thursday.

Weak

Assisted with lunch. Ate well.

Stronger

Prepared lunch with P-02 following the mealtime plan: soft diet, seated upright. P-02 ate the full sandwich and half the fruit over about 25 minutes, with no coughing observed. P-02 chose the filling. Fluids offered twice, both accepted.

Weak

Client was agitated this afternoon but settled.

Stronger

At about 2.30 pm P-03 raised their voice and paced after a change to the afternoon routine. I followed the steps in the support plan, spoke calmly and offered the quiet room. P-03 settled in about 10 minutes and chose to listen to music. No restrictive practice used. Behaviour recorded in the behaviour log.

What makes the stronger notes stronger is the same in each: a named support, what the participant did or chose, a link to the plan, and specific detail. See more NDIS progress note examples.

How does a quality gate at submission stop vague notes?

A quality gate checks each note against the participant’s own profile before it can be saved, and returns a note that falls short to its author with specific corrections, while the shift is still fresh. NoteGate scores each note before it can be saved. A note below the standard cannot be saved, and no supervisor can override it. Workers write their own notes. NoteGate never writes shift notes or incident reports.

The bar moves with risk: a note that is enough for a low-complexity participant can fall short for a participant with active risk flags. Fixing a note at the point of writing is cheaper than finding it at audit, because by then the shift is months old. See how pre-save note checking prevents non-conformances and shift note validation.

Does this apply to SIL and community nursing?

Yes. Shift notes are the records auditors see most often, and SIL providers face certification audits where records are viewed and workers and participants interviewed. Community nursing providers working to DVA requirements have their own progress note expectations: see DVA community nursing documentation requirements and mandatory SIL registration.

Frequently asked questions

Is there a mandatory NDIS shift note template?

No. The NDIS Practice Standards set outcomes, not a format. Providers choose their own structure, so long as records are accurate, current and show the support delivered.

Is “client had a good day” ever acceptable?

On its own, no. It does not show what support was delivered or how it related to the plan. It can sit inside a note that also names the support, the participant’s response and the goal.

Can software write a compliant shift note for a worker?

NoteGate does not. Workers write their own notes and NoteGate checks them before they are saved. It supports documentation governance and does not determine compliance.

How soon after a shift should the note be written?

The Practice Standards ask for records kept “in an accurate and timely manner” and do not define timely. Writing it before the shift ends is the safest practice.

Sources

Related

Return a vague note while the shift is fresh

Book a 20-minute walkthrough, or choose a plan.

Book a 20-minute walkthroughChoose a plan