Preparing for NDIS Plan Reassessment — Evidence Checklist for Providers

Published 24 April 2026 · 9 min read · NoteGate™

When a participant's NDIS plan comes up for reassessment, the quality of the evidence your organisation has on file determines whether they retain their current funding, receive an increase, or face a reduction. Preparing for NDIS plan reassessment is not a last-minute task — it requires a documentation culture built into every shift, every week.

This guide covers what the NDIA looks for in reassessment documentation, what records providers should gather, and how to build an evidence pack that withstands scrutiny. It also explains why the quality of individual shift notes — not just their volume — is what distinguishes providers who consistently achieve good reassessment outcomes from those who do not.

What the NDIA Looks For in Reassessment Evidence

The NDIA's reassessment process aims to answer one question: does this participant still require these supports at this level to achieve their goals and pursue an ordinary life? Your documentation must answer that question with observable, specific evidence — not clinical opinion or generic observations.

Reassessment reviewers look for four things in provider documentation:

1. Functional evidence linked to funded goals

Notes must show what the participant can and cannot do, and how support is enabling goal progress. "Assisted participant with personal care" is not evidence. "Participant required physical assistance for showering sequence due to left-side weakness — prompted through 6 of 8 steps independently" is evidence. The goal reference must be explicit or clearly inferable from the note.

2. Change over time

The NDIA wants to see whether support needs have changed — increased, decreased, or stayed consistent. A set of notes that all say the same thing regardless of date signals that workers are copying documentation rather than observing. Reviewers look for genuine temporal variation that reflects real support delivery.

3. Risk and safety documentation

Incidents, near-misses, behavioural events, medication changes, and health variations must be documented as they occur. These events are often the strongest evidence that supports remain necessary at their current level. Gaps in incident documentation are a major red flag in reassessment review.

4. Contemporaneous records

Notes written at or near the time of the shift carry significantly more evidentiary weight than retrospective summaries. NDIS auditors and reviewers are trained to identify late entries and backdated documentation. Every note should carry an accurate timestamp.

Building Your Reassessment Evidence Pack

A reassessment evidence pack for a participant typically includes documents from three sources: your internal documentation system, treating professionals, and the participant or their nominee. As a provider, you control the first category entirely.

Provider documentation to include

• Participant progress report covering the current plan period (ideally NoteGate-generated from validated shift note data)
• Shift note history — a complete record of all validated notes for the plan period
• Goal progress summaries showing measurable movement (or documented lack of movement) against each funded goal
• Incident and risk event log — all incidents, near-misses, and behavioural events with outcomes
• Support schedule history — actual supports delivered versus funded supports
• Worker handover notes documenting continuity of care observations

Documents to request from treating professionals

• Updated functional capacity assessment (occupational therapist or allied health)
• Specialist reports from psychiatrists, psychologists, or behaviour support practitioners where relevant
• GP or specialist letters confirming diagnosis stability or change
• Behaviour Support Plan review or update

Checklist: Provider evidence pack

Why Note Quality Determines Reassessment Outcomes

The most common reason providers lose reassessment arguments is not that the support was not delivered — it is that the records do not demonstrate what was delivered and why it was necessary. Vague notes that say "participant had a good session" or "support provided as per plan" contribute almost nothing to a reassessment case.

Each shift note is an opportunity to build the evidentiary record that supports the participant's funding at the next review. Providers who enforce documentation quality standards on every note — not just for audits — accumulate a body of evidence that makes reassessments straightforward. Providers who do not find themselves scrambling to retrospectively justify supports they delivered but did not document well.

This is why documentation enforcement at the point of submission — before a note enters the system of record — produces better reassessment outcomes than retrospective documentation review. By the time a reassessment approaches, the evidence is already built.

Common Documentation Gaps That Undermine Reassessments

• Vague language — "Participant was assisted" without specifying what assistance was required, why, and to what level
• No goal references — Notes that describe activities without linking them to funded NDIS goals cannot demonstrate necessity
• Inconsistent observations — Notes that describe the same level of function across every shift regardless of actual variation
• Missing incident documentation — Safety events that were not formally recorded or followed up
• Gaps in the record — Periods of support delivery with no corresponding notes
• Late entries — Notes clearly written after the fact, undermining contemporaneity claims

Each of these gaps is detectable by NDIA reviewers and gives grounds to question whether documented supports match funded supports. A quality gate that enforces documentation standards at the point of submission eliminates most of these gaps before they become problems.

How NoteGate Builds Reassessment Evidence Automatically

NoteGate validates every shift note against the participant's specific clinical rules before it enters the system of record. Notes that are vague, missing goal references, or fail on other quality dimensions are rejected — the worker must correct them before submission. The result is a body of validated, specific, goal-referenced notes that accumulate over the plan period.

When a reassessment approaches, NoteGate's report module generates a participant progress report directly from that validated note data — goal progress summaries, quality trend charts, incident flags, and handover notes. The evidence pack is assembled automatically from records that were enforced to standard at the point of creation.

This is the difference between preparing for a reassessment and having already prepared for it throughout the plan period. See how NoteGate makes progress notes audit ready, or read the NDIS audit documentation checklist for a full pre-audit review guide.