Support Coordinator Monthly Report: What to Write (Plus a Free Template)

Last updated 2026 · SupportNotes · Made in Australia

What is a support coordinator monthly report — and who reads it?

A support coordinator monthly (or periodic) report is your written record of the work you did for a participant, mapped to the goals in their NDIS plan. It is the document that turns a busy month of phone calls, provider chases, and check-ins into evidence the NDIA can actually use.

Two audiences read it. First, the NDIA — the planner or delegate who will look at your reporting when the plan comes up for reassessment, deciding whether the current funding worked and what the next plan should hold. Second, the participant and their family, who deserve a clear picture of progress in language they understand. Write for both: factual enough for a delegate, warm and readable enough for the person whose life it describes.

There is no single government-mandated template you are forced to use. What the NDIA consistently asks for is goal-linked, evidence-based reporting — so the smartest structure is one that ties every line back to a plan goal.

• Primary reader: NDIA planner/delegate (uses it at plan reassessment)
• Secondary reader: the participant and their support network
• Core expectation: progress shown against the participant's plan goals, with evidence
• Funding source: the Capacity Building — Support Coordination budget in the plan

What should you include in the report? (The 5 must-have sections)

If you only remember one thing, remember this: every claim needs a goal it serves and evidence behind it. Build your report from these five sections and you will rarely be asked for more.

Notice that four of the five sections are about outcomes, not activity. A delegate doesn't need to know you sent eleven emails; they need to know what those emails achieved for the participant's goal.

• 1. Participant + plan snapshot — name, NDIS number, plan dates, reporting period, your hours used vs remaining
• 2. Goal-by-goal progress — list each plan goal, then state what changed this month with evidence
• 3. Supports implemented — which providers/services you set up, connected, or reviewed
• 4. Risks, barriers and changes — anything that stalled progress, a hospital admission, a provider that fell through
• 5. Recommendations for the next period — what supports and funding you believe the participant will need, and why

Rough note vs audit-ready: real before-and-after examples

The gap between a note that gets queried and a note that gets accepted is almost always specificity. 'Doing well' is an opinion. 'Attended 3 of 4 physio sessions and now walks 20 metres unaided' is evidence a delegate can rely on. Here are common support-coordination notes, rewritten.

Read each 'after' aloud. It is longer, yes — but it answers the questions a planner would otherwise have to email you about, which actually saves you time at reassessment.

• Rough: 'Spoke to participant, all good.' → Audit-ready: 'Phone check-in 12/05. Participant reports stable. Confirmed SIL roster is meeting needs; no unmet supports raised this period.'
• Rough: 'Chased OT report.' → Audit-ready: 'Followed up [OT provider] x2 (email 03/05, call 09/05) for the functional capacity report needed to evidence the assistive-tech request at reassessment. Report now received and attached.'
• Rough: 'Participant struggling.' → Audit-ready: 'Participant disclosed increased isolation since support worker left. Identified risk to social-participation goal. Actioned: sourced 2 replacement providers, intro meeting booked 20/05.'
• Rough: 'Set up cleaning.' → Audit-ready: 'Engaged [Provider] for 2hrs/fortnight domestic assistance under Core, addressing the daily-living goal. First service 15/05; participant confirmed satisfaction at follow-up.'
• Rough: 'Need more hours next plan.' → Audit-ready: 'Recommend Support Coordination hours increase next plan: participant entering hospital-discharge planning plus 3 new provider transitions, both coordination-heavy. Current allocation projected to exhaust by [month].'

How do you phrase goal progress so the NDIA can act on it?

Goal-progress phrasing is where most reports either shine or stall. The NDIA is looking for a clear line from goal → action → outcome → recommendation. Use a simple sentence pattern and your reports become almost impossible to query.

Try this frame for each goal: 'Toward the goal of [goal], the participant has [specific change] as a result of [support]. Evidence: [observable detail or date]. To continue this, the next plan should fund [support].' It reads naturally and it carries everything a delegate needs in one breath.

Avoid words you can't measure — 'improved', 'better', 'progressing' — unless you immediately follow them with the proof. And never report a clinical conclusion you aren't qualified to make. You can write 'participant reports less pain'; you should not write 'participant's condition has improved' as if you diagnosed it.

• Anchor every paragraph to a named plan goal — not to your activity
• Pair each progress claim with a date, a count, or an observable fact
• Report what you saw or what the participant told you — attribute it ('participant reports…')
• Stay in your lane: coordinate and observe; don't diagnose or assess clinically
• End each goal with a forward-looking funding recommendation

Staying compliant: documentation that protects you and the participant

Good reporting is also risk management. If you are a registered provider delivering support coordination, the NDIS Practice Standards expect sound governance, risk management, and a focus on participant outcomes — and your file notes are the proof that those things actually happened. Even unregistered coordinators are accountable for accurate, contemporaneous records.

Three habits keep you safe. Write notes close to when the event happened (contemporaneous notes carry far more weight than memory three weeks later). Separate fact from opinion clearly. And record consent and participant choice — show that the participant chose their providers and directed their supports, which is central to the NDIS principle of choice and control.

Never fabricate or estimate to fill a gap. If a session didn't happen, say it didn't and why. A report with honest gaps is trusted; a report that's too tidy invites scrutiny.

• Write contemporaneous notes — same day where you can
• Keep fact and opinion visibly separate
• Document participant consent and choice of provider
• Record risks the moment you identify them, plus your action
• Attach supporting documents (reports, quotes) rather than describing them from memory

A copy-and-adapt monthly report structure

Here is a clean skeleton you can lift straight into your own template. Fill it in goal by goal and you'll have an audit-ready report in well under the time it takes to write a messy one you'll have to defend later.

Keep it tight. A delegate would rather read two pages of evidence than six pages of narrative. If a section has nothing to report this period, write 'No change this period' — that's an answer, not a gap.

• Header: Participant name, NDIS number, plan start/end, reporting period, coordinator name + provider
• Hours: Support Coordination hours used this period / remaining / projected to last until
• Per goal: [Goal text] → Actions taken → Outcome + evidence → Barriers → Next steps & funding recommendation
• Supports table: Provider | Service | Budget category | Status (new / ongoing / ceased)
• Risks & incidents: What, when identified, action taken, current status
• Summary recommendation: What the next plan should fund and the one-line reason for each

Build your next report in minutes (free)

You shouldn't have to rebuild this structure from scratch every month. Our free report builder walks you through each section — participant snapshot, goal-by-goal progress, risks, and recommendations — and prompts you to swap vague phrases for evidence as you go, so what you hand the NDIA is audit-ready the first time.

Try the free support coordinator report builder at the homepage. Start with one goal, paste in your rough notes, and watch them turn into delegate-ready wording. No sign-up needed to begin.

• Guided sections so you never miss a must-have
• Built-in prompts to turn 'doing well' into evidence
• Goal-linked structure the NDIA expects — every time

Frequently asked questions