Plan review coming up? Here's what coordinators wish you knew

Plan reviews are the single highest-leverage moment in a participant's NDIS year. A good one secures funding that makes the next twelve months calmer. A bad one quietly removes supports that took two years to build. The difference is almost never about how compelling the participant is in the meeting itself. It is about what's in the file by the time the planner opens it. The eight weeks before the review are when that file gets built. Here's how to use them.

Week 8: Pull the current plan and read it like a stranger

Print the current plan. Read it as if you've never seen it before. Highlight every line item. Next to each one, write three things: how much was funded, how much was spent, and what changed in the participant's life because of it.

This is uncomfortable. Most participants don't know exactly what's in their plan, and most families have never sat down with all of it on one table. Do it anyway. The planner will have read it. You should have too.

Common surprises at this stage:

• A line item that was never used at all (which the planner will likely remove)

• A line item that was overspent, with no documentation explaining why

• A goal in the plan the participant doesn't recognise or doesn't agree with anymore

Each of these is fixable if you find it at week 8. None of them are fixable in the meeting.

Week 7: Ask every provider for a one-page report

Every active provider should be able to give you a one-page summary of what they've done over the plan period. Not an invoice list — an actual report. Goals worked on, progress made, what they recommend for the next plan.

Email each one. Be direct: "Our plan review is on [date]. Can you send a one-page summary by [date two weeks out]?" If a provider can't do this, you've learned something useful about them. If they can, you've just collected the evidence that justifies your next plan.

For coordinators reading this: this is the moment we earn our keep. We chase the reports, we redact them where needed, and we make sure they tell a consistent story.

Week 6: Get the clinical letters started

Anything that needs a doctor's signature takes longer than you think. If the participant needs a new functional capacity assessment, a GP letter about a deteriorating condition, an OT report on home modifications — start now.

GPs are not the bottleneck because they're slow. They're the bottleneck because they need a clear ask. Walk in with a one-paragraph note that says: "We have an NDIS plan review on [date]. Could you write a letter confirming [specific thing], including [specific medical detail]?" A GP who knows what's needed will write the letter in twenty minutes. A GP who has to guess will write nothing for six weeks.

Week 5: Write the goals down, in the participant's own words

The participant's goals will be in the new plan whether you write them or not. The question is whether they'll be in the participant's words or the planner's words. The first version is much more useful in twelve months' time.

Sit with the participant. Ask three questions:

1. What's something you couldn't do a year ago that you can do now?

2. What's something you want to be able to do a year from now?

3. What's something that scares you about the next year?

Write down what they say, in their language. Don't translate it into NDIS terminology. "I want to go to my cousin's wedding in Auckland without my mum having to come" is a better goal than "increase independence in community participation activities."

Week 4: Map the supports against the goals

Now line up the goals against the supports being requested. Every support should connect to a goal. Every goal should have at least one support attached to it.

This is the document the planner will mentally write during the meeting. If you write it for them first, you save them work and you keep control of the narrative. If you don't, the planner writes their own version, and theirs may not match yours.

Week 3: Pre-meeting with the coordinator

If the participant has a support coordinator, this is when the long meeting happens. Three hours, not one. Run through every line item, every goal, every report. Identify the two or three things that are most at risk of being cut, and decide how you'll defend them.

For families without a coordinator: ask one provider — usually the one who knows the participant best — for an extended call. Most will say yes, even if it's not strictly billable. This is part of the unbilled work good providers do.

Week 2: The dry run

Sit at a table with the participant. Pretend you're the planner. Ask the questions a planner asks: How is this person's day-to-day life? What's working? What isn't? What would change if we didn't fund [specific support]?

Listen to how the participant answers. If they freeze, or give very short answers, or say "I'm fine" to everything — that's normal, and it's why we do the dry run. Practise the answers that matter. Not scripted, but rehearsed.

Week 1: Logistics, and the things people forget

The week of the review is for the small things, not the big things.

• Confirm the meeting format (phone, video, in-person) and the time

• Make sure the participant has eaten and is rested for the appointment

• Bring printed copies of every provider report, in a folder, in order

• Bring one trusted support person — not three

• Have a backup phone number for the planner in case the video link fails

If the meeting is being held remotely, do a test call the day before. Planners are sympathetic about technical hiccups but the meetings are tightly scheduled, and ten minutes lost to a frozen screen is ten minutes you don't get back.

Traps to avoid

A short list, in no particular order:

• Don't oversell recovery. If the participant has had a good year, the planner may use that as a reason to reduce supports. Be honest about what's still hard.

• Don't bring brand-new requests with no evidence. A new support that nobody has documented before the meeting is the easiest line for a planner to refuse.

• Don't let the participant minimise. Many participants, especially older men and people from cultures where stoicism is expected, will downplay their needs in the meeting. Prep them on this directly.

• Don't argue with the planner. Disagree, calmly. Provide evidence. Move on. Plans that get reduced are often plans where the meeting became adversarial.

After the meeting

The plan won't arrive that day. Use the gap to write a one-page summary of what you asked for, what you said, and what the planner indicated. When the new plan lands, you'll want to compare it line by line against this summary. Reviews and appeals get won on documentation, not memory.

If you'd like a coordinator to walk you through this checklist for a specific plan review, the CCSS team can sit with you and your file. We do this every week.