How to write NDIS shift notes (with examples)

By Kim Matthews · Founder, Sparks Scribe

Writing shift notes should not take longer than the shift itself, but for a lot of independent support workers, that is close to what happens. After a long day you still have to turn what you did into something clear and professional. The good news, and I have watched this play out with the workers I support, is that better notes are not longer notes. They are just clearer.

What is a shift note, and why does it matter?

A shift note is a short, factual record of a support shift: what you did, how it went, and anything worth flagging. It matters for two plain reasons. First, it is your evidence that the service was actually delivered, which is what a plan manager, a participant, or the NDIA would look for if an invoice were ever queried. Second, it protects you. If something is disputed weeks later, a clear note written on the day is worth far more than your memory of it.

Most independent support workers are sole traders working under the NDIS Code of Conduct, not registered providers going through formal audits. That does not let you off the hook on records. The Code is about safe, respectful, accountable support, and being able to show what you did, honestly and clearly, is part of that.

What should an NDIS shift note include?

You can keep the checklist short. A solid note covers:

• What support you provided during the shift
• How the person engaged, in factual terms
• Any changes, concerns or incidents
• Anything that should be noted for next time

Where it is relevant, tie what you did back to the person's plan goals or their service agreement, so the note shows not just that you were there, but that the support was purposeful. Keep names, dates and times accurate, and stick to facts rather than impressions.

A simple structure you can reuse

You do not need a clinical framework to write a good note. Most shifts fit a plain three-part shape: what I did, how it went, what happens next. If you write to that shape every time, your notes stay consistent and quick.

Some workers prefer a more formal structure, and SOAPIE (Subjective, Objective, Assessment, Plan, Implementation, Evaluation) is one that auditors recognise for clinical documentation. It is useful if your work is more complex, but it is not required for most support shifts, and a clear plain-language note is perfectly acceptable. Pick the structure you will actually keep to.

Before and after: a weak note and a clear one

The fastest way to see the difference is to compare two notes for the same shift.

The second note is not much longer, but it records what was actually done, how the person engaged, and that nothing went wrong. If someone read it in six months, they would understand the shift. The first tells them nothing.

Write objectively: what to say, and what to leave out

Compliant notes are objective. Write what you observed, not what you assumed about it, and keep judgement words out.

The first records a fact anyone could verify. The second is a label, and labels are exactly what you do not want in a record that might be read by the participant, their family, or a plan manager. Focus on what happened, not your opinion of it.

Type it or say it, the words stay yours

No rule says a note has to be typed. Speaking a note and typing a note are equal input paths, and on a day when you are tired and driving between shifts, dictation is often faster and just as valid. What matters is that the observations and the words are yours. A tool can tidy the format, but you are the one who decides what happened. Think of any software here as a second set of eyes, not a second author.

How long should a shift note be?

Long enough to record the shift, and no longer. A few specific, factual sentences beat a page of padding every time. If you find your notes drifting long, it is usually because they have wandered into opinion or repetition. Cut back to what you did, how it went, and what needs following up.

Common mistakes that make notes weak

Most weak notes fail in one of four ways: they are too vague, too emotional, too long, or written too late. Vague notes record nothing useful. Emotional notes record your reaction instead of the facts. Over-long notes bury the point. And notes written days later are simply less accurate. Keep them specific, neutral, and close to the shift.

Where Sparks Scribe fits (and my disclosure)

Full disclosure, because I say it on every page here: I build one of the apps in this space, Sparks Scribe. It exists for exactly this problem, the professional note that has to be written after a long day. You type or speak what happened the way you would tell a mate, and Scribe arranges it into a clean, structured note. It formats your words, it does not invent content, so the record stays yours. On its Safeguards plan it also acts as a second set of eyes, quietly checking each saved note and flagging anything that may need attention, and every note is stored on Australian servers with one-tap PDF export. You can look at it for yourself at sparkscribe.app. Whether you use it or a notebook, the advice above holds.

Frequently asked questions

Still choosing your tools? See my honest comparison of the best apps for independent NDIS support workers in Australia.

← Back to The Support Worker Guide