What Providers Need for NDIS Claims Evidence

By NoteGate Research Team

Published 24 April 2026 · 7 min read · NoteGate™

NDIS payment claims are not unconditional. Providers must keep full and accurate records of the supports they deliver, and a claim that the records do not support may need to be repaid (NDIS record keeping requirements; Provider Payment Assurance Program). NoteGate's view is that a claim is best supported by evidence that the support was delivered, was consistent with the participant's plan, and was provided by a suitably qualified worker. When the NDIA audits a provider's claims - whether through a targeted review, a compliance audit, or a participant complaint - the documentation record is the primary evidence.

Understanding what NDIS claims evidence requirements actually mean in practice is essential for every registered provider. This guide explains what claims documentation should show, what documentation is worth keeping to support a valid claim, and why the quality of individual shift notes is directly linked to claims compliance.

What Claims Documentation Should Show

When claims are reviewed, these are five useful questions to be able to answer for each claimed service (NoteGate's framing, not an NDIA list):

1. Was the support actually delivered? - Is there a contemporaneous record of the support being provided?
2. Was the support consistent with the participant's plan? - Does the documentation show the support was linked to a funded goal or support category?
3. Was the support provided at the level claimed? - Do records support the duration and nature of the support claimed?
4. Was the support provided by a qualified worker? - Were worker qualifications and employment records maintained?
5. Was the participant present and receiving the support? - Is there participant signature, worker attestation, or objective record of attendance?

The shift note is the primary document that answers questions 1, 2, and 3. A shift note that is vague, generic, or not linked to the participant's plan creates uncertainty about all three. When a claims auditor encounters a body of vague notes, they may require the provider to justify every claim those notes support - a time-consuming and risky process.

What Documentation Must Exist for Each Claim

Shift note or service note

A contemporaneous record of the support delivered, written at or near the time of the shift. The note must be specific enough to identify the nature and duration of the support, link it to the participant's plan, and reflect the worker's actual observations rather than generic filler. This is the core document in claims evidence.

Rostering and attendance records

Time and attendance records showing when the worker was on-site or on-shift with the participant. These records must align with the claimed service dates and duration. Discrepancies between rostering records and claimed times weaken the evidence for a claim.

Worker qualification records

For regulated support types (e.g., complex support needs, specialist disability accommodation), workers must hold required qualifications. Providers must maintain records demonstrating that the worker who delivered the support held the required qualifications at the time of service.

Participant service agreement

A current service agreement between the provider and participant (or nominee) authorising the support being claimed. The agreement must be signed, current, and consistent with the participant's active plan budget.

Incident records (where applicable)

For supports involving a reportable incident, the incident must be documented and reported to the NDIS Commission within required timeframes. Incidents should be documented and reported within the required timeframes; see the reportable incidents guide.

The Shift Note as Claims Evidence

A common risk is documentation quality: supports were delivered, but the notes do not prove it. This has three practical consequences:

Vague notes cannot prove necessity

A note that says "supported participant with daily tasks" does not prove that the support was necessary for a participant with a specific disability and specific funded goals. A useful test is whether the note shows why this support needed funding rather than informal help. If the note does not demonstrate why funded support was specifically required, the claim is vulnerable.

Generic notes suggest overclaiming

When every shift note for a participant looks identical - same language, same descriptions, same apparent level of support - auditors question whether the level of support claimed actually varied. Overclaiming is a compliance breach. Notes that demonstrate genuine variation in support level over time are more defensible than uniformly identical records.

Unlinked notes cannot demonstrate plan alignment

Claims must be consistent with the participant's funded plan. Notes that describe activities without referencing the participant's goals or support categories cannot demonstrate that the claimed support falls within the funded plan. This creates a straightforward audit finding even when the support was delivered.

Building a Claims-Defensible Documentation System

The documentation standard required for NDIS claims evidence is the same standard required for audit-ready shift notes: specific, goal-referenced, contemporaneous, and complete. The practical question is how to maintain this standard consistently across a provider workforce of workers with varying skills, attention, and time pressure.

The only reliable mechanism is quality enforcement at the point of submission. When workers cannot submit a shift note until it meets minimum quality standards - and receive specific correction guidance when they do not - the documentation record becomes claims-defensible by construction. Providers do not need to retrospectively review notes for claims compliance; the gate at submission has already performed that function.

NoteGate enforces this standard on every note before it enters the system of record. Each validated note includes a quality score, goal reference, timestamp, worker identifier, and participant linkage - the core elements a claims auditor looks for. See how to make progress notes audit ready for the full quality standard, or use the NDIS audit documentation checklist to assess your current records before a review.