Support-Coordination Report Drafter | Real Minds AI
NDIS & Disability /Drafting live field guide · 8 min

Support-Coordination Report Drafter

Turns weeks of scattered case notes and provider service logs into a draft progress report mapped to the participant's plan goals, with the source note cited behind every claim — the coordinator reviews and signs.

theater/demos/ndis_support-coordination-report-drafter.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 period's case notes, the plan and the provider service logs, drafts the progress report under the headings the NDIA expects with a source note cited behind every claim, and surfaces it for the coordinator to review and sign before it reaches the my NDIS provider portal.

Input 01
Notes, plan, service logs

The reporting period's case notes, the participant's current NDIS plan PDF, and provider service logs with hours and spend by funding category.

Agent 02
Maps goals, rolls up, cites

Maps each plan goal to the case-note passages that bear on it, rolls up hours delivered and budget utilisation by funding category, and drafts the report with the source note cited behind every claim and thin evidence flagged.

Output 03
A draft, every claim sourced

A structured draft under the expected headings with an evidence-confidence read, laid out for the coordinator to check each cited note, correct, and approve before a PDF is produced to lodge in the my NDIS provider portal.

Where it works well

It reassembles months of scattered notes into the report shape every time, and shows the note behind every line.

  • Done by hand a single mid-plan progress report is hours of reading and retyping — and the cross-check is the first thing dropped under deadline.
  • Best for a coordinator carrying a full caseload of PACE-reportable plans: 8-week implementation, mid-plan progress, end-of-plan review reports.
  • At a dozen reports a cycle, the recaptured hours go back into participant-facing coordination, not the paperwork.

The invisible tax on support coordination is the accounting for the work, not the work — reading months of case notes across different staff, cross-checking provider service logs, and retyping it all into the headings the NDIA expects.

Where it works badly

It is confidently wrong when the notes are thin or the plan is stale — and the draft looks more trustworthy than the data behind it.

  • Where a note reads "attended appointment" with nothing on what changed against a goal, the draft surfaces low-confidence — a report built on sparse notes is mostly a list of gaps.
  • It can note that a reportable incident was logged, but it is not an incident-management system and must not be treated as one.
  • If a goal was never written down distinctly from a general observation, the draft cannot manufacture progress against it — it makes that gap visible instead.
The honest test

If you cannot point, right now, to the current plan and the reconciled service logs for this exact reporting period, the draft will mislead you faster than a blank page would.

Feed it last quarter's plan PDF, or service logs missing the last fortnight's hours, and it drafts a clean report full of budget figures and "supports engaged" that no longer hold. That is the trap.

What it doesn't do — and shouldn't

It drafts. The coordinator reviews, corrects and signs. That boundary is deliberate.

WHAT IT DOES
Cites the source note behind each factual claim
Shows hours delivered and budget utilisation by funding category
Flags thin or contradictory evidence as low-confidence
WHAT IT WON’T
Decide whether a goal is genuinely progressing
Submit anything to the my NDIS provider portal
Discharge reportable-incident obligations

The report shapes a participant's funding and supports and carries the coordinator's name into the my NDIS provider portal. Registered providers also carry reportable-incident duties to the NDIS Quality and Safeguards Commission on a 24-hour clock — not something a drafting tool discharges. The accountable person stays on the decision because the consequence lands on them, not the tool.

What your data has to look like

Notes that separate a goal from an observation, the current plan, and service logs reconciled for the period.

44%
Typical readiness
across orgs we see, before the first job
Case notes that distinguish goal from observation
Needs shaping
The participant's current NDIS plan
Usual weak point
Provider service logs reconciled for the period
Needs shaping
A consistent participant identifier
Usually ready
The report type and current template
Usual weak point
The real first job

Getting notes to consistently separate goal-progress from general observation, and service logs reconciled and current, is usually the real first job — a matter of how information is captured day to day, not a tool you buy. That capture work is larger and more valuable than the drafting layer that sits on top of it.

Right fit if…
You write progress reports regularly across a full caseload of PACE-reportable plans
Your case notes already distinguish goal-progress from general observation
You can point to the current plan and reconciled service logs for the period
The report-writing tax is the heaviest drag on your participant-facing time
Walk away if…
Your case notes are sparse — "attended appointment" with no detail on goals
You carry old plan PDFs and service logs that lag a fortnight or more behind
You want it to handle reportable incidents or compliance, not just drafting
You need a tool that signs and lodges the report for you
Open questions

The worried-buyer questions, answered straight

It drafts recommendations as suggestions tied to the evidence it found, not decisions. A line like “review Core funding at plan review” is flagged for the coordinator to weigh, and any claim with thin or missing notes behind it is called out rather than smoothed over. Nothing is lodged in the my NDIS provider portal until the coordinator has read every cited note and signed. The tool surfaces; the person stands behind the report.
Partly, and it will show you where it’s guessing. It reads what’s there and cites the note behind each claim, so a vague or contradictory note surfaces as low-confidence rather than as a confident fabrication. But if a goal was never written down distinctly from a general observation, the draft can’t manufacture progress against it — that gap is exactly what the tool makes visible, and getting notes to separate goal-progress from observation is usually the first job worth doing.
No. It replaces the hours spent hunting through months of notes and retyping them into a report shell. The judgement — whether a goal is genuinely progressing, whether a support should change, what to recommend at plan review — stays with the coordinator, who reviews, corrects and signs. We accelerate the assembly, not the decision, and the recaptured hours go back into participant-facing coordination.
It only knows what’s in the notes, the plan PDF and the service logs you give it for that period. If a plan was reassessed recently or a provider hasn’t entered last fortnight’s hours, the draft reflects the old picture — the budget figures and “supports engaged” are only as current as your logs. The honest test: can you point, today, to the current plan and the reconciled service logs for this exact reporting period?
No. It runs against your own document store, not a public chatbot, and the participant’s notes and plan stay inside your environment. A participant’s NDIS number, plan and case notes are sensitive disability and health information, so the data boundary — where the documents sit and who can see them — is scoped as part of the build, not an afterthought. The demo here runs on fabricated data; Aisha Rahman is not a real participant.
The coordinator who signs it. That’s deliberate. The tool produces a draft with every claim traceable to a source note so the coordinator can verify quickly, but the report that reaches the NDIA via the my NDIS provider portal carries their name and their judgement, exactly as it does today. Reportable-incident duties to the NDIS Quality and Safeguards Commission stay with the registered provider, not the drafting tool.
What it takes to build
3–4 weeks · 4 phases
Reused from template~70%
Bespoke to this skin~30%
stack · Claude · private RAG · review UI
What it would cost

Fixed scope, fixed price, fixed dates.

01
Bite-sized first piece
One contained change, low risk
02
Pilot build
Most builds land here
03
Embedded support
Scale on proof

Considering this for your coordination team?

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

More in NDIS & Disability
Care Policy Concierge
View →
Care-Plan First-Drafter
View →
Reportable-Incident Signal Triage
View →
Care Policy AskMe
View →
How We Work Proof Talk to us
How We Work Proof Talk to us
Ask us anything