What evidence supports an NDIS claim?
- Published
- 9 September 2026
- Last updated
- 9 September 2026
- Sources last verified
- 9 September 2026
The short answer
A claim is supported by a set of records that agree with each other, not by one document. In practice that means the participant’s plan, an agreement covering the support and its price, a record that the support was delivered, and a claim line consistent with both. A progress note is usually the delivery record — it is not, on its own, the whole answer, and any tool that tells you otherwise is overselling.
Applies to: Providers claiming NDIS funds. What is relevant varies by support type and by your registration status.
What the official source says
Everything in these blocks is the responsible agency’s own position, with a link to check it. Everything outside them is ShiftNote’s operational reading, which is a different kind of statement.
What the rule says
What a provider must be able to show behind a claim is not a single document. It depends on the support, and typically spans the participant’s plan, the service agreement, the record that the support was delivered, and the provider’s own operational records.
Applies to: Providers claiming NDIS funds.
Where this is not the whole answer
There is no published list that makes a progress note sufficient evidence for every claim. Treat any tool that says otherwise — including ours — as giving you a starting checklist, not a legal answer.
- Official source
- Guide to getting paidNational Disability Insurance Agency
- How we checked it
- Checked against the agency’s published summaryLast verified 4 September 2026
The NDIA’s guidance on payment requests, service bookings and what a provider must be able to show behind a claim.
Read the official source(opens in a new tab)- Official source
- NDIS Practice Standards and Quality IndicatorsNDIS Quality and Safeguards CommissionCore module — Provider governance and operational management (Information management)
- How we checked it
- Checked against official guidanceLast verified 4 September 2026
The standards a registered provider is audited against, including the information-management standard covering storage, security, retention and disposal of participant records.
Read the official source(opens in a new tab)What the rule says
Registered providers must maintain an information management system that stores participant records with defined access, security, retention and disposal processes, proportionate to the supports they deliver.
Applies to: Registered NDIS providers audited against the Practice Standards.
- Official source
- NDIS Practice Standards and Quality IndicatorsNDIS Quality and Safeguards CommissionCore module — Provider governance and operational management (Information management)
- How we checked it
- Checked against official guidanceLast verified 4 September 2026
The standards a registered provider is audited against, including the information-management standard covering storage, security, retention and disposal of participant records.
Read the official source(opens in a new tab)- Official source
- National Disability Insurance Scheme (Quality Indicators for NDIS Practice Standards) Guidelines 2018Commonwealth of Australia
- How we checked it
- Checked against the agency’s published summaryLast verified 4 September 2026
The instrument containing the quality indicators auditors use to assess a provider against each Practice Standard.
Read the official source(opens in a new tab)The four things that have to agree
Almost every substantiation problem is a disagreement between records that should say the same thing.
| Record | What it establishes | Where it usually breaks |
|---|---|---|
| The participant’s plan | That the support is something this participant is funded for | Plan dates lapse mid-arrangement and nobody notices until claiming |
| A service agreement | That the support and its price were agreed | Agreement covers a different item or an older price than the claim |
| A delivery record | That the support actually happened, and what it was | No note exists, or the note describes something other than what was billed |
| The claim line | What was billed, for how long, against which item | Duration billed does not match the duration the record evidences |
Why the progress note is doing more work than people realise
Of those four, three are typically produced once and filed: the plan, the agreement, the claim. The delivery record is produced fresh, at the end of a shift, by whoever was there — often on a phone, often tired, often in a second language.
It is the only one of the four that is written by a different person every time, and it is the one that has to describe reality. That is why it is where the failures concentrate, and it is why "the claim was formatted correctly" tells you almost nothing about whether the claim is defensible.
The three ways evidence fails, in order of cost
Each needs a different response, and treating them as one red flag sends people to the wrong task.
- Nothing behind the claim. Delivered and billed, but no record was written, or the record is in a system nobody reconciled against the claims. Response: find out whether a record exists at all.
- The record contradicts the claim. Six hours claimed against a note describing one; personal care billed against a note about a trip to the shops. Response: work out which of the two is wrong. One of them is.
- The record is thin. It exists and does not contradict anything, but it does not evidence much either — no duration, no outcome, no link to what the support was for. Response: add the detail while somebody still remembers the shift.
What a defensible delivery record contains
Not a legal standard — a practical one, drawn from what the failures above actually turn on.
- What support was delivered, described specifically enough to recognise the support item from the words alone.
- How long it took, stated explicitly. This is the single most common omission and the first thing anyone checking a claim looks at.
- What the participant did and how they responded, in observable terms rather than conclusions.
- What the support was working toward, where the participant has goals on file.
- Anything that went wrong, and any follow-up — including an explicit "none", because a blank is ambiguous.
- Who wrote it and when, which is a property of the system rather than of the writing.
What ShiftNote can identify
- Whether the record linked to a claim describes the support that was claimed.
- Whether the duration the record evidences matches the duration claimed.
- Whether the support is connected to a goal in the participant’s plan, where goals are on file.
- Whether the record contains anything that contradicts its own claim — a cancelled shift, a participant who was not home, a support that did not happen as billed.
- Whether a service agreement is recorded as covering the support.
What ShiftNote cannot determine
- Tell you whether a claim is legally payable, or predict a decision by the NDIA. Every output is a heuristic reading of your own records.
- Read a record it does not have. Notes written elsewhere have to be brought in before anything can assess them.
- Verify that a support was actually delivered. It reads what the worker attested to; it does not witness anything.
Common questions
- Is a progress note enough on its own?
- No, and anyone telling you it is has an incentive to. The note is usually the delivery record, which is one of four things that have to agree. It is the one most likely to be missing or inconsistent, which is why it gets the attention — not because it is sufficient by itself.
- How detailed does a note have to be?
- Detailed enough that someone who was not there can tell what support was delivered, for how long, and how the participant responded. Longer is not better; specific is better.
- What if the worker has left and the note is thin?
- Do not have someone else write it up as though they were there. A record fabricated after the fact is a much worse problem than a thin one. Record what you can establish, note what you cannot, and make the decision about the claim with that in front of you.
Change history
- 9 September 2026 — First published.
ShiftNote provides software and operational information, not legal advice. Providers remain responsible for understanding the requirements that apply to their own circumstances.
Related guides
See where your own claims stand
The free audit runs in your browser — your claims file never reaches our server — and shows claim-window exposure from your own dates.