Support Coordinator Case Note Examples: Write Billable, Audit-Ready Notes in Minutes

Last updated 2026 · SupportNotes · Made in Australia

What makes a support coordination case note billable and audit-ready?

You finish a 20-minute call with a participant's plan manager, close the tab, and move to the next thing. The note you leave behind is the only proof that work happened - and the only thing that makes that time claimable. If it's vague, the time is hard to claim. If it can't link back to a plan goal, it's a problem at audit. This is the quiet pressure every support coordinator carries: do the work, then prove the work, dozens of times a day.

An audit-ready note does three jobs at once. It shows the activity was connected to a goal in the participant's NDIS plan. It shows the time was a reasonable and necessary use of their Support Coordination or Specialist Support Coordination funding. And it shows the participant's choice and control sat at the centre of the decision. When all three are visible in a few plain sentences, the note is billable and it stands up to review.

The fastest way to hit all three every time is a fixed four-part structure. You stop wondering what to write, and you start filling in slots.

• Purpose - which plan goal or need this activity serves
• Action - what you specifically did, with the date and time spent
• Outcome - what changed, was decided, or was learned
• Next step - the follow-up, owner, and timeframe

The Purpose-Action-Outcome-Next-Step structure (your four sentences)

Think of every note as four short answers. You don't need flowing paragraphs - reviewers prefer plain, factual sentences. If English is your second language, this structure does the heavy lifting for you. Use the sentence starters below and you'll never stare at a blank box again.

Here are the openers that make a note write itself:

• Purpose: "To progress [name]'s goal of [goal]..."
• Action: "...I [called / emailed / researched / coordinated] [who] for [how long] to [what]."
• Outcome: "As a result, [what was agreed / found / actioned]."
• Next step: "Next, I will [task] by [date]; [name] will [task]."

Before and after: rough notes turned audit-ready

Most notes that fail review aren't dishonest - they're just thin. They record effort but not purpose or outcome, so the link to the plan goal is invisible. Below are real-world rough notes a coordinator might dash off between appointments, rewritten with the four-part structure. Notice how the rewrite adds almost no time but completely changes whether the note is claimable.

Example 1 - Provider follow-up.

Example 2 - Participant check-in.

Example 3 - Plan review prep.

• Rough: "Called OT about report. Still waiting."
• Audit-ready: "To progress Sam's goal of returning to work, I called the OT (10 mins) to follow up the functional capacity report due for his plan review. The OT confirmed the report will be sent by 14th. Next, I will upload it to Sam's file and forward to his planner once received."
• Rough: "Spoke to Aisha, all good."
• Audit-ready: "I phoned Aisha (15 mins) to check her new cleaning supports are working toward her goal of a safe home environment. Aisha said the worker is reliable and she feels more confident at home. No issues raised. Next, I will check in again in four weeks; Aisha will call sooner if rosters change."
• Rough: "Getting ready for review."
• Audit-ready: "To prepare for David's plan review on the 20th, I reviewed his goal progress and current budget usage (25 mins) and drafted a summary of supports that worked. As a result, I identified an underspend in Capacity Building to raise with his planner. Next, I will send David the draft summary for his input by Friday."

Words and phrases that protect your claim

Small wording choices decide whether a reviewer reads a note as a justified support coordination activity or an unexplained block of time. The phrases below signal goal-linkage, reasonable necessity, and participant choice - the exact things the NDIS Practice Standards expect you to demonstrate.

Build these into your sentence starters and the justification is baked in, not bolted on.

• "To progress [name]'s goal of..." - shows the activity links to the plan, not just general help
• "so that [name] could choose / decide / compare..." - shows choice and control
• "a reasonable and necessary step to..." - mirrors the funding test
• "with [name]'s consent" - shows the participant directed the action
• "to build [name]'s capacity to..." - shows you're coaching, not doing-for (core to Support Coordination)
• Avoid filler like "touched base," "as discussed," or "general support" - they read as time without purpose

Quick fixes for the notes that get questioned

When a quality reviewer or your team leader flags notes, it's almost always one of a handful of patterns. Knowing the pattern means you can fix it in seconds. Run your notes against this checklist before you submit a claim.

If a note fails any line, add one sentence - usually the missing purpose or the missing outcome - and it's back to billable.

• Effort without outcome: you wrote what you did but not what happened - add the "As a result..." line
• Activity without goal: nothing ties it to the plan - add "To progress [name]'s goal of..."
• Copy-paste notes: identical wording across days or participants is a red flag - keep the structure, change the content
• Missing time: no duration means no defensible claim - always log minutes or start/end times
• No next step: leaves the file looking abandoned - always name the follow-up, owner, and date
• Vague names: "the provider" or "the planner" - name who you actually contacted

Where case notes fit in the NDIS Practice Standards

Case notes aren't just admin - they're your primary evidence under the NDIS Practice Standards. The Support Coordination module expects you to strengthen a participant's ability to coordinate and implement their supports, connect them to services, and build their capacity and choice over time. Your notes are how you prove that's what actually happened.

Good records also support the broader standards around participant outcomes and the management of records: information should be accurate, kept up to date, and stored securely. You don't need to quote the standards in a note - you need to show, in plain language, that the support was goal-linked, participant-led, and reasonable. The four-part structure makes that automatic.

One practical habit: write the note as soon after the activity as you can, while the detail is fresh. A note written three days later is more likely to be thin, and thin notes are the ones that get questioned.

Write your next note in under a minute

The whole point of a fixed structure is speed. Once Purpose-Action-Outcome-Next-Step is muscle memory, a strong, billable note takes well under a minute - and you stop second-guessing whether it'll pass review.

If you'd like the structure to do even more of the work, try the free case note builder. Paste your rough note or answer the four prompts, and it returns audit-ready wording with the goal-linkage and time built in - so you can spend your day coordinating supports, not rewriting notes.

• Start every note with "To progress [name]'s goal of..."
• Always log the date and minutes spent
• End every note with a named next step and date
• Keep sentences short and factual - plain English passes audits
• Try the free case note builder at the link to generate audit-ready notes in seconds

Frequently asked questions