Novida logoNovida

Building an Efficient Support Coordination Workflow: Templates and SOPs

Build a support coordination workflow that protects billable hours under frozen rates — SOPs, templates, a 14-day onboarding example and the 90-day claim rule

Map the participant lifecycle before you build anything

A workflow is only as good as the process it describes, so start by drawing the full participant journey. Almost every support coordination engagement moves through the same stages, and each stage is where a template or SOP belongs. Referral and intake — a plan lands, you confirm funding, capacity and fit.. Onboarding — service agreement, consent, initial…

Why SOPs matter more under frozen rates

Support coordination price limits have been frozen for a seventh consecutive year. As at the 2026-27 NDIS Pricing Arrangements and Price Limits (PAPL), Level 1 Support Connection sits around $80.06/hr, Level 2 Coordination of Supports around $100.14/hr, and Level 3 Specialist Support Coordination around $190.54/hr (confirm the current figures in the PAPL at…

The SOPs every practice should write first

An SOP is a short, dated document that says who does what, in what order, using which template, and where the record lives. You do not need dozens. Prioritise the ones that repeat most and where a mistake is costly. Intake and acceptance — how you check plan funding, capacity, geographic fit and any conflict of interest before saying yes.. Onboarding —…

Templates that save the most time

Templates are the reusable documents your SOPs point to. Build the high-frequency ones first. The table below maps common templates to their lifecycle stage and the main thing each one protects. Store templates in one controlled location, not scattered across email and desktops. If your practice uses case management or CRM software, hold the master versions…

Worked example: the first 14 days with a new participant

A workflow earns its keep when a plan arrives on a busy Friday and you do not have to think. Here is how a tight onboarding SOP plays out. Day 0 — Referral received. Run the intake checklist: confirm the plan has Level 2 Coordination of Supports funding, check hours against your capacity, and screen for any conflict of interest. Accept or decline in…

Design the workflow around billable and non-billable time

Support coordination is billed against a finite number of funded hours, so every workflow step should carry a tag: billable coordination, or non-billable practice overhead. Service agreements, internal file setup, your own SOP maintenance and unfunded travel beyond plan terms are overhead. Direct work on the participant's goals — contacting providers,…

Build claiming into the workflow — the 90-day window

From 1 December 2026 the claim window shortens from two years to 90 days (per the reforms under the Securing the NDIS for Future Generations program; verify against health.gov.au/securingtheNDIS and the Federal Register of Legislation). In practice, an unbilled service after 90 days is unpaid work. Your workflow must make claiming a routine, not an…

Bake compliance into the workflow, not on top of it

Conflict-of-interest scrutiny is tightening now. The NDIA is actively examining support coordination invoicing, particularly brokerage and multi-support arrangements where a coordinator has an interest in the providers being recommended. Your workflow should make the compliant path the default one. Put a conflict-of-interest check in the intake SOP, and a…

Frequently asked questions

What should a support coordination case note include?

At minimum: the date, who you contacted, the participant goal it relates to, what was actioned or agreed, the time spent, and a billable or non-billable tag. Write it the same day, not in a weekly batch, so detail is accurate and the claim is defensible if the NDIA queries it. Consistent notes are also the evidence trail an audit or the future commissioned panel will expect.

How do frozen price limits change how I build my workflow?

Because the price ceiling is fixed — a seventh year of frozen support coordination limits as at the 2026-27 PAPL — you cannot raise revenue per hour, so the workflow has to raise the share of your day that is billable and cut admin cost per hour. That means templated documents, same-day notes and scheduled claiming. Confirm the current price limits in the PAPL at ndis.gov.au before quoting them.

Do I need registration to run standard support coordination?

Mandatory registration for standard support coordination (group 0106) was paused in December 2025 with no new date, and requirements will align to the 2028 commissioned model. Specialist Support Coordination (group 0132) still requires registration, with a Core Module plus Specialist Module 4 audit. Verify your current obligation against the NDIS Commission at ndiscommission.gov.au.

When does the 90-day claim window start?

The claim window is set to shorten from two years to 90 days from 1 December 2026 under the Securing the NDIS for Future Generations reforms. In practice, an unbilled service after 90 days becomes unpaid work, so move to weekly or fortnightly claiming. Confirm the commencement and any transitional rules against health.gov.au/securingtheNDIS and the Federal Register of Legislation, as reform dates can shift.

How is the SC price limit different from the SCHADS award?

The support coordination price limit is the maximum you can bill a participant's plan; the SCHADS award (MA000100) sets what an employed worker is paid, via Fair Work. They are different numbers for different purposes — never price your practice by treating one as the other. Your workflow should track billable revenue against staff costs separately.

Related guides

Browse NDIS providers on Novida