How to keep track of every NDIS participant's plan and reviews

A growing NDIS provider keeps track of every participant's plan and reviews by holding one register: plan start and end dates, plan budget, service hours delivered, next review date and the person responsible for each participant. Read it on the same day every week. Detail is lost when that information sits in four places and nobody looks across them.

In short

• Keeping track of every participant means one register: plan dates, plan budget, service hours delivered, next review date and an owner, read weekly.
• The register is the thing that scales. Memory and goodwill work at 20 participants and quietly fail at 120.
• Watch three numbers per participant: days until the plan ends, budget drawn down, and the date of the last case note.
• Most warning signs are silences: no review booked, drawdown far ahead of time elapsed, or no case note for weeks.
• The reassessment date sits in each participant's own plan, so read the plan and the NDIA's current guidelines rather than assuming a standard length.

What a participant register should include

A participant register should include, for every active participant, enough to answer "is anything slipping?" without opening another system. In practice that is one row per participant and about ten columns.

• Participant identifier, and the service or program they sit in.
• Plan start date and plan end date.
• Plan management type, because who pays an invoice changes who you chase.
• Plan budget by support category, and the amount claimed to date.
• Service hours agreed in the service agreement, and service hours delivered this month.
• Next review or reassessment date, taken from the plan itself.
• Date of the last case note.
• The staff member accountable for this participant.
• Any open incident, complaint or restrictive practice record.
• The date the row was last updated.

Two columns matter more than people expect. The last column, "last updated", tells you whether the register is still worth trusting. The accountability column stops a participant falling between two teams, which is the most common way a review date is missed in a provider that has just grown.

Keep the register in one place that the whole leadership team reads. A spreadsheet is a fine start. The problem with spreadsheets is not accuracy, it is that the version everyone trusts and the version that is current are often not the same file. If you move to a reporting platform later, it can connect to the exports you already produce from your rostering and claiming systems, so the register is built from the same source every week rather than retyped.

How to track service hours delivered against each plan budget

Track service hours delivered against each plan budget by comparing two things each month: the hours actually delivered against the hours the service agreement expected, and the money claimed against the plan budget for that support category. One number without the other will mislead you.

Hours tell you about service delivery. Budget drawdown tells you about the plan's funding. They come apart in both directions:

• Hours delivered are on target, but drawdown is high. Check the line items being claimed and the price used, and check for duplicated claims.
• Drawdown is low, but hours are on target. Check that claims are actually being submitted, and that cancellations are being handled the way the agreement says.
• Both are low. The participant may not be receiving the support they planned for, and that is a conversation with them and their support coordinator, not a billing problem.

A plain way to read drawdown is to compare the share of the plan spent with the share of the plan's duration that has passed. If a participant is six months into a twelve month plan with 80 per cent of a core support category claimed, that is worth a look this week, not at the next review. In our example company, a register of 120 participants shows nine participants over 75 per cent drawdown at the halfway point of their plans. Those figures are example data from a demonstration dataset, not results from any provider.

Set the check to run monthly for every participant and weekly for anyone already flagged. The participants who need attention are a small, changing group, and a monthly pass over everyone is what finds them before a review date arrives.

Warning signs that a participant's plan is slipping

The warning signs that a participant's plan review is overdue, or that their supports are drifting, are nearly always visible in dates and gaps rather than in anything dramatic. These are the ones worth putting on a weekly list.

• A plan end date inside 60 days with no reassessment conversation recorded. This is the single most useful flag, because the work before a reassessment takes weeks, not days.
• A review date that is blank. A missing date is not the same as a distant one, and blank fields are where participants get lost.
• Budget drawdown well ahead of time elapsed, especially in core supports.
• Budget drawdown well behind time elapsed. Underuse can mean unmet need, cancelled shifts, or claims not lodged.
• No case note for a participant in several weeks while service hours are still being claimed for them. The claim and the record of support should tell the same story.
• A support category with funding and no service at all since the plan started.
• Repeated short-notice cancellations for one participant, which often sit in the roster and never reach management reporting.
• A change of circumstances noted in a case note with nothing recorded after it. A move, a hospital stay, a new diagnosis or a change of carer is often the point at which a plan stops matching the person's life.

None of these is proof of a problem. Each is a reason to open the file this week.

How support coordinators keep across many participants at once

Support coordinators keep across many participants at once by working from a short exception list rather than the full caseload. The caseload is read in full once a month, and the exception list every day or two.

Three habits do most of the work.

First, one place for dates. Every plan end date, review date and agreed review conversation lives in the same calendar or register, not in individual inboxes. A date that only one person knows is a date that disappears when that person takes leave.

Second, notes written the same day. Case notes written late lose the detail that mattered and often lose the date of the event. For plan management, claiming and reassessment evidence, the note written on the day is worth several written from memory.

Third, a standing weekly half hour. A coordinator and a manager read the exception list together, and each flagged participant gets one of three outcomes: an action with a name and a date, a note that explains why no action is needed, or an escalation. Nothing stays on the list without one of the three.

For a provider past about 50 participants, the thing to add is not more reporting. It is a single agreed view that both the coordinator and the executive read. When the operations report and the coordinator's own list disagree, people trust neither, and the detail goes back into people's heads. Our page on NDIS reporting explains what we hold in that view, and where NDIS admin time goes, and how to measure it covers how to measure the hours this work is taking you now.

Common questions

What are the warning signs that a participant's plan review is overdue?

The clearest warning sign is a plan end date approaching with no reassessment conversation recorded, and the second is a blank review date in your register. Supporting signs include budget drawdown far ahead of or behind the time elapsed in the plan, and a participant with no case note for several weeks while hours are still being claimed.

How often does an NDIS participant's plan get reviewed?

The reassessment date is set in each participant's own plan, so plan length varies between participants rather than following one fixed period. The NDIA publishes separate guidelines for plan reassessments and for plan variations, and its website notes that information is being updated to reflect new NDIS legislation, so read the participant's plan and the current guideline rather than relying on a remembered plan length.

What happens if a provider misses a participant's plan review date?

The immediate risk is practical: supports continue to be delivered against funding that may no longer be available, and the participant may be left without the evidence their reassessment needs. We cannot tell you what applies in your own case. What a provider can control is the lead time, which is why a flag at around 60 days before the plan end date is more useful than one at the end date itself.

What should a participant register include?

A participant register should include one row per active participant with plan start and end dates, plan management type, plan budget and amount claimed by support category, service hours agreed and delivered, next review date, the date of the last case note, the accountable staff member and the date the row was last updated.

How do I keep the register from going out of date?

Give one person responsibility for the register, rebuild it from the same system exports each week, and put the "last updated" date where everyone can see it. A register nobody has refreshed for a month is more dangerous than no register, because people still make decisions from it. More questions are answered on our FAQ.

Sources

• Our guidelines, National Disability Insurance Agency, including the Plan reassessments and Plan variations guidelines, as at October 2026