NDIS plan review reports — why your provider needs better notes

Plan reviews are where NDIS funding gets decided. The NDIA looks at what progress has been made toward the participant’s goals, what supports are working, what needs to change, and whether the current funding level is appropriate. The evidence for all of this comes from the participant’s support documentation — which starts with your progress notes.

The chain from your note to the plan review

Here’s how it works: you write a progress note after each session. Over 12 months, that’s hundreds of notes across multiple workers. When plan review time comes, someone — usually a coordinator or team leader — needs to compile all of those notes into a summary report that shows goal progress, support effectiveness, and recommendations.

If your notes are vague (“went to the shops, had a good time”), there’s nothing to compile. The plan review report ends up thin and generic. The NDIA sees no evidence of progress. The participant’s funding may not increase — or worse, it gets reduced because there’s no documented justification for the current level.

If your notes are specific (“Jake used his budget list at Woolworths independently for the first time and stayed under budget by $3”), the plan review report writes itself. There’s clear evidence of skill development, independence, and goal progress. The funding case is strong.

What a good plan review report contains

A plan review report typically includes a summary of each goal and the progress made toward it, specific examples and milestones from session notes, an overview of the types of support provided and how they were delivered, any incidents or safety concerns during the period, and recommendations for the next plan — including whether goals should continue, be modified, or be replaced.

Every one of these sections depends on the quality of the underlying notes. If the notes don’t mention goals, the report can’t show goal progress. If the notes don’t document specific moments of independence or skill development, the report has nothing to cite. If incidents weren’t properly documented, the safety section is incomplete.

The time problem

Compiling a plan review report manually is brutal. A coordinator might need to read through 200+ notes from multiple workers, extract the relevant information, organise it by goal, identify patterns, and write a coherent summary. This takes hours — sometimes a full day for complex participants. Many providers don’t have the time, so the reports end up rushed, generic, or late.

This is where structured notes make a fundamental difference. When every note follows the same framework, links to specific goals, and documents outcomes in a consistent format, the plan review report can be generated automatically. The data is already there, already organised, already linked to the right goals. The report is just a compilation of what was already documented.

Your notes are someone else’s evidence

As a support worker, it’s easy to think of progress notes as something you write for your provider. But the audience is bigger than that. Your notes are read by coordinators compiling reports, by plan managers justifying claims, by auditors checking compliance, and ultimately by the NDIA deciding whether this participant’s funding should continue at its current level.

When you document a specific moment — Jake checked his bank balance on his phone for the first time, Misa shared her food with another child at the park, Sarah ordered her own coffee without prompting — you’re not just recording what happened. You’re building the evidence base that protects the participant’s funding and demonstrates that the supports are working.