NDIS & Disability /Document Generation live field guide · 8 min

NDIS Progress Note to Claim

Turn a support worker's session note into a draft NDIS claim — the right support item, the matching plan goals, and the compliance checks already done, for a person to approve.

Open the live demo

theater/demos/ndis_note-to-claim.html · sandbox · read-only

Open

FIG. 1

The live demo, running on fabricated data. Open it to step through the full flow — every output is shown for a person to approve before anything happens.

How it would work

Reads the support worker's progress note, drafts the matching NDIS line item and the plan-goal evidence, runs the pre-claim checks, and lays it all beside the note for a billing officer to approve before anything reaches the portal.

Input 01

One session note

A single support worker's progress note — session type, duration, location, activities completed, plan goals addressed, the participant's response — plus the participant's NDIS number and active plan goals.

Agent 02

Codes, prices, checks

Suggests the support category and the NDIS support item, prices it against the current limit, quotes the note sentences that evidence each plan goal, and runs the six pre-claim compliance checks.

Output 03

A draft, working shown

A draft claim — item code, rate, hours, total, goal evidence and the checklist — laid beside the source note for a billing officer to review, edit, or flag, and approve before it is submitted to the NDIS portal.

Where it works well

It does the note-to-claim cross-reference every time, in full, and shows the sentence each line came from.

Done by hand it is 10–15 minutes of price-guide and plan cross-referencing per session — and the goal-evidence link is the first thing skipped under volume.
Best for providers running recurring core supports — community participation, daily living, capacity building — where the same handful of items repeat and notes are the real record.
At a high volume of sessions a week, the recaptured cross-referencing time goes back into reviewing claims and participant work, not re-keying the price guide.

The slow, invisible work is the gap between what a support worker wrote and what the claim says — tracing one session note to a support item, a price limit, and the plan goals it legitimately worked toward, by hand, per session.

Where it works badly

It is confidently wrong when the note is thin — and a plausible-but-unsupported goal link is the worst outcome under a payment-integrity review.

Weak where claims are not note-driven — block-funded supports, quotable items, or plan-managed arrangements with bespoke agreements that aren't a clean item-times-hours sum.
It cannot manufacture evidence a note never captured; thin notes produce thin drafts, and the right fix is the note template, not the tool.

The honest test

Open ten of your own progress notes at random — if you can't read each one and say which support item and which plan goal it maps to, your first job is the notes, not the tool.

Give it "good session, Emma happy" and there is nothing to link to Plan Goal 3.2 and nothing to substantiate the hours. It either drafts low-confidence or invents a plausible link the note never supports. That is the trap.

What it doesn't do — and shouldn't

It drafts the claim and runs the checks, then stops. A person approves. That boundary is deliberate.

WHAT IT DOES

Surfaces the support item code, the rate and the hours it drew from the note

Quotes the note sentence that evidences each plan-goal link

Runs the six pre-claim checks and flags any that fail

WHAT IT WON’T

Submit the claim to the NDIS portal

Decide which plan goals a session legitimately worked toward

Stand behind the hours billed on its own say-so

A claim carries payment obligations and the NDIS Practice Standards; a wrong item or unsupported hours can trigger a payment-integrity review by the NDIS Quality and Safeguards Commission and the NDIA. The accountable person — whose name is on the claim — stays on the decision because the consequence lands on them.

What your data has to look like

Notes that record duration, location, activity and goal separately — and a price guide current to the service date.

Typical readiness

across orgs we see, before the first job

Notes that link activity to plan goal

Needs shaping

Documented duration, location and response

Usual weak point

Current NDIS price limits, in force on the service date

Usual weak point

The participant's active plan goals

Needs shaping

The NDIS Support Catalogue to code against

Usually ready

The real first job

The note template is almost always the weak point — most don't separate a goal from an observation, or enforce duration and location as fields. Reshaping how notes are captured, and keeping the price guide current to each service date, is usually the real first job — larger and more valuable than the drafting layer on top. The AI sits on clean capture; it cannot substitute for it.

Right fit if…

You run high volumes of recurring core supports — community participation, daily living, capacity building

Your progress notes already record duration, location, activity and the participant's response

Your notes name which plan goal each activity worked toward, in language that distinguishes goal from observation

You can point to the current, in-force NDIS price limits for the service date

Walk away if…

Your notes are thin — three lines that don't say what happened or which goal it served

Most of your claims are block-funded, quotable, or bespoke plan-managed arrangements

Plan goals and price limits only live in PDFs or last year's files nobody owns

You need a tool that submits claims or certifies them compliant for you

Open questions

The worried-buyer questions, answered straight

It can suggest the wrong support item or read a duration loosely — which is exactly why it never submits. Every draft shows the item code, the rate, the hours and the note sentence it drew them from, side by side, so your billing officer catches a mismatch before approving. Under an NDIS payment-integrity review the claim has to trace back to the note; the tool makes that trace easy to check, it does not claim unchecked.

On the three-line notes it will struggle, and that is the useful signal. It can only link an activity to a plan goal and pass the pre-claim checks if the note records the duration, location, the activity and the participant’s response. Thin notes produce thin, low-confidence drafts — which tells you the note, not the claim, is the thing to fix first.

No. It drafts; they decide. Which support item, which plan goals a session legitimately worked toward, and the final submission all stay with the person accountable for the claim under the NDIS Practice Standards. What it removes is the 10–15 minutes of cross-referencing the price guide and the plan per session, so that capacity goes back into review and participant work.

Current to the service date. The NDIS Pricing Arrangements and Price Limits change at least annually and have been reissued mid-year — the 2025-26 arrangements were updated in November 2025 — and a participant’s plan goals change at each reassessment. Point it at a stale price table or an expired plan and it drafts confidently against the wrong figures, so the data it reads must be the version in force on the day of service.

The note is participant health and disability information, sensitive personal information under the Privacy Act and the NDIS Code of Conduct, so it is handled under the engagement’s data terms, not pasted into a public chatbot. We scope where the model runs and what is retained before any real notes touch it. The demo here uses fabricated participant data only — Emma Nguyen is not a real participant.

No. It assembles the draft and runs the six pre-claim checks — duration, location, goal links, participant response, worker-to-participant ratio, and rate within the current price limit — then stops. A billing officer approves, edits, or flags it; only then does it go to the PACE portal. The retained note stays the evidence the claim traces back to under NDIS record-keeping expectations.

What it takes to build

3–4 weeks · 4 phases

Reused from template~65%

Bespoke to this skin~35%

stack · Claude · NDIS price guide · review UI

What it would cost

Fixed scope, fixed price, fixed dates.

Bite-sized first piece

One contained change, low risk

Pilot build

Most builds land here

Embedded support

Scale on proof

Considering this for your provider?

The honest place to start is a bite-sized first piece — one contained change, low risk. Tell us where the note-to-claim work hurts; we'll play it back, scope it, and show you what's possible.

Book a call How we work