How to Write Goal-Linked Progress Notes: A Community Participation Worker's Guide (With NDIS Examples)

Last updated 2026 · SupportNotes · Made in Australia

What is a goal-linked progress note?

A goal-linked progress note is a shift note that ties what you did to a specific goal in the participant's NDIS plan. Instead of just logging that an activity happened, you record how the support moved the person closer to a goal they (or their support network) chose — building independence, growing community connections, improving daily living skills, or increasing confidence in the community.

This matters because under the NDIS Practice Standards (the Provision of Supports part of the Core Module), your progress notes are the evidence that supports are delivered toward each participant's documented goals. An approved quality auditor reading the file should be able to follow the thread: plan goal → support delivered → participant's response → next step. If your note can't show that thread, the work you did is invisible on paper — even if you did a brilliant shift.

You're a community participation worker, so your shifts look different from a SIL house. You're out: a coffee group, the gym, catching the train, a TAFE class, shopping, a community garden. The goal you're working toward is usually something like 'increase community participation', 'build social connections', or 'travel more independently'. Your note's job is to make that goal visible in every entry.

Why "attended activity" gets flagged

The most common note in community access work is some version of: "Took John to the social group. He had a good time. Dropped him home." It feels complete after a long shift. It isn't.

Here's what an auditor — or your team leader, or the participant's plan reviewer — sees in that note: no goal, no measurable progress, and subjective words ("good time") that you can't back up. It doesn't show why NDIS funding was spent. At plan review, this is the kind of note that makes a planner ask, "Is this support actually helping?" Worse, vague notes are the ones that come back to bite you if there's ever a complaint or incident — there's no record of what really happened.

• No goal named — the reader can't tell what the shift was for
• Subjective language ("good time", "lovely", "as usual") that isn't evidence
• No participant action recorded — only what YOU did
• Written in a way that could describe any person on any day
• Nothing about what happens next shift

The 4-part pattern that makes a note goal-linked

You don't need fancy clinical training to write an audit-ready note. You need one repeatable shape. Run every community-access note through these four parts and it will link to the goal automatically.

Keep it factual and third-person ("[Participant] did…", not "we had a great time"). Record what you saw and heard, not what you assume the person felt. "Smiled and stayed for the full hour" is observable; "enjoyed it" is a guess.

• GOAL — name the plan goal this shift worked toward (e.g. "Goal: increase independent community participation")
• SUPPORT — what you actually did to help (prompted, modelled, encouraged, stood back)
• PROGRESS — what the participant did toward the goal, in observable terms (ordered, asked, waited, paid, travelled, initiated)
• NEXT — what to try or watch next shift, so the next worker continues the thread

Before / after examples from your shifts

These are the situations you actually work — community access, social groups, travel training, skill-building in the community. The "before" is the rushed end-of-shift version. The "after" is the same shift, written goal-linked. Notice nothing is invented — the facts were always there, the after version just captures them.

Quick fixes if English isn't your first language

You don't need big words to write a strong note. Auditors prefer short, plain, factual sentences — they're clearer and harder to argue with. If English is your second language, lean into simple structure. The 4-part pattern above does the heavy lifting; you just fill the blanks.

Swap feeling-words for action-words. Instead of guessing how someone felt, write what they did. This is also safer for you — you can only be sure of what you saw.

• Use "[Participant] did…" sentences — one action per sentence
• Replace "happy / enjoyed / good" with what you saw: "smiled", "stayed", "asked again", "laughed with others"
• Replace "helped" with the exact support: "prompted", "showed", "reminded", "stood back"
• Always start with the goal word so the link is obvious
• If unsure of a word, keep the sentence short — short is professional, not lazy

A 30-second free tool that links the goal for you

If you're writing 5–8 notes at the end of a double shift, the goal-link is the first thing that slips. That's exactly the problem we built a free tool to solve. You type your rough note — the messy "took John to group, good day" version — and it rewrites it into an objective, third-person, goal-linked progress note in about 30 seconds.

It flags subjective words and shows you the objective swap, confirms the note links to a goal, and keeps the participant's data in Australia (it never leaves the country). It's free to try, no credit card, and it's built specifically to protect support workers at audit time — not to write fiction. Use it as a second pair of eyes when you're tired.

Try it free on the homepage and turn your next "attended activity" note into proof of progress.

Frequently asked questions