Support coordination reporting: what goes to whom, and when

A support coordinator reports in three directions. The participant gets a plain account of what has been arranged and what changed. The payer, often a plan manager, gets claims and invoices that match the service agreement. The NDIA gets a progress report against the goals in the plan when it asks for one, usually before a plan reassessment.

In short

• Support coordination reporting has three audiences: the participant, whoever pays the invoices, and the NDIA.
• The participant is the first audience. They should get a written summary at a rhythm set in the service agreement.
• A plan manager pays providers and keeps financial records, so they get claims and invoices, never progress notes.
• The NDIA wants progress against the goals in the plan, most often before a plan reassessment.
• There is no national template. The obligation in each case sits in the participant's plan and in your service agreement.

What a support coordinator has to report, and to whom

A support coordinator reports progress and decisions to the participant, financial detail to whoever pays, and progress against goals to the NDIA when it is requested. Those three jobs do not share a format, a frequency or an audience, and treating them as one report is the most common reason a provider ends up doing the work twice.

It helps to set the three out side by side:

Who receives it	What they want	When
The participant, and their nominee or guardian if they have one	What was arranged, who is now providing support, what changed, what is next, what the participant needs to decide	At the rhythm written into the service agreement, and whenever something material changes
The payer: a plan manager, the NDIA, or a self-managing participant	Claims and invoices with dates, hours, the support item claimed, and a service agreement that covers them	Each billing cycle
The NDIA	Progress against the goals in the plan, what supports are working, what is recommended next	When the plan or the planner asks, commonly before a plan reassessment

Two things sit outside that table. First, there is no single national template for a support coordination report that we can point you to, so the obligation in any one case comes from the participant's plan and your own service agreement rather than from a form. Second, where the provider is registered, reportable incidents and complaints about the supports you provide go to the NDIS Quality and Safeguards Commission under its own rules and timeframes, as at November 2026. The Commission also publishes the NDIS Code of Conduct and the NDIS Practice Standards, which as at November 2026 include a module for specialist support co-ordination, and those obligations stand apart from anything you agree with a participant.

The participant is the first audience

The participant should get a written account of their own support coordination that they can read on their own, and the frequency belongs in the service agreement. This is the report most often left informal, and it is the one the participant actually lives with.

What a good participant summary does:

• names every provider now involved, and what each one does;
• says what has been arranged since the last summary, and what has not yet been arranged;
• flags anything that stalled, and who is waiting on whom;
• states what the participant needs to decide, in a question they can answer;
• avoids internal short forms. If a sentence needs a glossary, rewrite the sentence.

Two practical points. Write the summary in the participant's own words wherever you can, because the summary is also the record they will take to their next plan meeting. And agree the frequency in writing. Monthly suits a busy plan with several new providers; quarterly suits a settled one. What matters is that the rhythm was chosen and written down, rather than assumed.

What the plan manager needs, and what they do not

A plan manager needs the money trail and nothing more: a claim or invoice with the date, the hours, the support item, and a service agreement behind it. Progress notes, personal detail about the participant and clinical information are not a plan manager's business, and sending them is a privacy problem rather than a thoroughness win.

Plan management is one of three ways a participant's funding can be managed. As at November 2026, the NDIS describes three options: self-management, where the participant, their nominee or representative pays providers and keeps the financial records; plan management, where a registered plan manager pays providers and manages financial records for them; and NDIA management, where the NDIA pays providers and manages the records. A participant can use one option across the whole plan or combine them, and they can ask to change how the plan is managed without waiting for a new plan.

That matters to a support coordinator for a simple reason. The management type decides who receives your invoice, and it can change mid-plan. If you hold one field per participant for the management type and keep it current, the invoice goes to the right place the first time. If you do not, the invoice bounces, and the participant hears about it.

When the NDIA asks for a report

The NDIA asks a support coordinator for a progress report against the goals in the participant's plan. The request, the format and the due date come from the plan or the planner rather than from a standing rule you can look up, so read the plan wording and ask the planner before the report is due rather than after.

A progress report that gets used tends to cover:

• each goal in the plan, quoted as the plan words it;
• what was tried, and what came of it;
• which supports are working and which are not, with the reason;
• what the participant says about all of the above;
• what you recommend for the next plan, and the practical basis for it.

Write it so a reader who has never met the participant can follow it. The person reading your report is making a funding decision from paper.

Support coordination and plan management are different jobs

Support coordination and plan management are two different jobs: support coordination builds and holds the service arrangements, and plan management pays for them. A support coordinator finds providers, sets up agreements, resolves problems and builds the participant's own capacity to do more of it over time, while a plan manager handles claims, pays invoices and keeps the financial records.

The funding sits in different places too. Plan management funding is separate from a participant's other NDIS supports and can only be used to pay a plan manager, as at November 2026, while support coordination sits with the capacity building supports.

Two consequences are worth holding on to. A participant can have both roles, one, or neither, so never assume there is a plan manager to send an invoice to. And neither role is the other's reporting line: a plan manager does not sign off on your coordination, and you do not report progress through them.

Setting up a reporting practice you can hold across a caseload

A reporting practice works when the same case note can feed all three reports without being rewritten. Decide once, per participant, who gets what and when, and record that answer where the whole team can see it.

The fields worth holding for every participant:

• plan start and end dates, and the next reassessment date;
• management type, and who the invoice goes to;
• the participant reporting rhythm agreed in the service agreement;
• the date of the last participant summary and the last NDIA report;
• the goals, quoted from the plan.

On a caseload of five, a spreadsheet does this. On a caseload of fifty, the question stops being whether anyone is working hard and becomes whether anyone can see the whole picture at once. Our notes on keeping track of every participant's plan and reviews go through that in more detail, and if you are weighing up tools, the plain checklist for NDIS reporting software is written for the same reader. MERIT Lumina is built for NDIS providers who need that view in one place, and it can connect to the exports you already produce.

Common questions

What is the difference between a support coordinator and a plan manager?

A support coordinator arranges and maintains a participant's supports, while a plan manager pays for them and keeps the financial records. The support coordinator talks to providers and to the participant about what the supports are doing; the plan manager handles claims and invoices. A participant can have both, and the two roles report on different things to different people.

How often does a support coordinator report to the participant?

There is no national frequency set for reporting to a participant, so the rhythm is the one written into the service agreement. Monthly is common on a plan with several new providers, and quarterly on a settled plan. The important part is that the frequency was agreed and written down, so the participant knows when to expect it.

Does a support coordinator report to the NDIA, the plan manager, or both?

Both, for different things. Progress against the goals in the plan goes to the NDIA when it is requested, usually ahead of a plan reassessment, while claims and invoices go to the plan manager when the participant's funding is plan-managed. If the plan is self-managed or NDIA-managed, the invoice goes to the participant or to the NDIA instead.

What should a support coordination report include?

A support coordination report should quote each goal from the plan, say what was tried and what came of it, name which supports are working and which are not, include what the participant says, and set out what you recommend next. Write it so someone who has never met the participant can follow it, because that is often who reads it.

Can a participant ask to see their support coordinator's notes and reports?

Yes, a participant can ask, and a request for their own information should be treated as normal rather than exceptional. Write every note on the assumption the participant will read it, which tends to improve the notes. Where a note holds information about another person, get advice before releasing it rather than refusing outright.

Sources

• Guide to your management options, NDIS, as at November 2026
• NDIS Code of Conduct, NDIS Quality and Safeguards Commission, as at November 2026
• NDIS Practice Standards, NDIS Quality and Safeguards Commission, as at November 2026
• Reportable incidents, NDIS Quality and Safeguards Commission, as at November 2026
• Complaints about supports and services you provide, NDIS Quality and Safeguards Commission, as at November 2026