The Update Nobody Sends: NDIS Participant Updates Between Visits
Nobody cancels a service because they were updated too often. They cancel because they stopped hearing anything, and started filling the silence themselves.
In NDIS service delivery, the update is the product as far as the family and the coordinator are concerned. They cannot see the shift. They cannot see the progress note. What they can see is whether anybody told them what happened, and whether it arrived before they had to ask.
The silence between visits
A participant sees a support worker four times a week. A coordinator manages dozens of participants and hears from your organisation only when something goes wrong or a plan review is due. A family member gets a phone call if there is an incident, and otherwise relies on a monthly invoice as the record of a service they paid for.
That is not neglect — it is what happens when communication is nobody’s job. It is not billable, it is not rostered, and it lands on whoever finishes their shift first.
What a coordinator actually needs
Not a newsletter, and not a mood. Four facts, short enough to read on a phone:
- What happened — which supports were delivered, on which days, by whom.
- What changed — a goal that progressed, a behaviour that shifted, a piece of equipment that stopped working.
- What is next — the plan for the coming fortnight, including anything the participant asked for.
- What needs a decision — a support running out, a review approaching, something the coordinator needs to act on.
If an update does not contain at least one item from the last two, it is a status message, not an update.
Why it slips, every week
Because it happens at 4:50pm, in competition with a handover, and because writing it means reading notes from four different shifts first. Most providers solve this by moving the update to monthly, then to “on request”, then to the plan review.
An update written monthly is not a record of the service. It is a summary of what somebody can still remember.
What an agent does about it
The Automated Client Update Agent writes from the shift record, not from memory. At a schedule you set — weekly, fortnightly, before each plan review — it assembles what was delivered, what the notes record as changed, and what is coming, then sends the same short update to the coordinator, the family and anyone else on the consent list.
The AI Client Intake Agent covers the other end of the same conversation: enquiries answered immediately, needs captured, funding type recorded, and a human placed in front of the ones that need one. Together they close the loop — the first message and the hundredth.
What not to automate
Clinical judgement, funding promises and anything that sounds like a commitment to a support you have not rostered. The agent drafts from what is written down; if the note does not say it, the update does not claim it. A coordinator who catches an inflated update once will discount every update after that.
What we build
We build automation and digital employees for Australian NDIS providers. Participant communication is one of twenty specialised AI agents, and it reads from the same shift and claim data as bulk claiming and rostering. See the NDIS provider setup.
Start with one month of updates
Send us what a coordinator currently receives from you over a month. We will show you the gap between what was delivered and what was communicated — and what the same month would read like written from the shift notes.
Pingback: What Breaks an NDIS Bulk Claim, and How to Catch It
15 November 2026Pingback: The Reportable Incident Clock for NDIS Providers
15 November 2026