Industries · NDIS providers
The paperwork is taking your support workers away from the people they support.
A governed suite of AI agents that absorbs the evidence, claiming and coordination burden of an NDIS provider, on sovereign Australian infrastructure, with participant choice and control untouched. Your workers return to support. Your evidence stands up in an audit. Your claims clear inside the window.
Where the margin went
The price is set. The wage is set. Only your operating discipline is still yours.
The Scheme has been re-regulated harder than aged care, and the new machinery lands directly on provider cash flow. A second enforcement arm sits alongside the Commission. The claim window compresses from two years to 90 days. Claim records must be held for seven years, with a civil penalty for failure. Price limits become charge caps a provider breaches by exceeding, rather than ceilings a payment stops at. None of that added a dollar to a shift.
Sector figures from National Disability Services, State of the Disability Sector Report 2025, and from the Ability Roundtable benchmarking group and published NDIA plan utilisation data.
This is not a demand problem. Participant numbers are still rising. It is an operating problem, and the utilisation range is the proof: the same work, the same award, the same price cap, and a forty-point spread between providers. Benchmarking also shows utilisation does not improve as participant numbers grow, which means growth will not fix it. The providers still operating at the end of this decade will not have found better prices. They will have built better operations.
The line we will not cross
Choice and control is not ours to optimise.
Start with what we will not build. We will never build an agent that profiles a participant, scores a participant, predicts what a participant will choose, or produces anything that nudges a participant's decisions about their own supports. Choice and control is the principle this Scheme was built on, not a feature of it. An AI that made you better at steering participants would be a design failure no matter what it did to your margin. Our agents point inward, at your operations. They never point outward, at the people you support.
And we will never simulate a human support relationship. The worker in the room, the clinical judgement, the safeguarding call, the hard conversation with a family. That work is yours, permanently.
| Stays human, always | Absorbed entirely |
|---|---|
| The support worker in the room | Drafting the case note from that worker's own account, for their signature |
| Every decision a participant makes about their supports | Nothing. We produce no input to participant decisions |
| Behaviour support practice and clinical formulation | The administrative shell only: authorisations, versions, expiries, deadlines |
| Safeguarding judgement and the decision to escalate | Capturing the incident, starting the clock, holding the deadline |
| The difficult conversation with a participant, family or nominee | Scheduling it, and the routine updates that are not it |
| Clinical and professional opinion | The evidence that opinion draws on |
| Approving a claim | Assembling and validating it against support items, funding periods and evidence |
On behaviour support we are specific. The NDIS Commission does not endorse the use of AI in developing or reviewing behaviour support plans. This suite does not draft, review, summarise or suggest any behaviour support plan content. It handles authorisation tracking and reporting deadlines and nothing else. That boundary sits in the architecture, not in a policy document you would have to trust us to follow.
The problem that is not being named
Your team is already using AI. That is the risk.
In its February 2026 position statement on AI in behaviour support plans, the NDIS Commission said that where a provider uses AI, it expects information to be appropriately de-identified and no personal information of participants to be disclosed to AI systems. The privacy duty in the Code of Conduct applies wherever participant information is handled. Meanwhile, in providers across the country, support workers are pasting shift details into consumer chatbots and coordinators are drafting reports in public tools, because the documentation load is real and the pressure is real.
You cannot fix that with a policy memo. The memo does not reduce the documentation, so the behaviour continues without oversight, which is worse than the version you can see. The only resolution is a sanctioned environment where the work genuinely gets easier and the participant's information never leaves your control. That means de-identification at the model boundary, Australian jurisdiction, and full provenance on every record.
Anyone selling you a public AI tool to handle participant data is selling you a breach with a subscription attached.
The suite
One participant, start to finish, and the agents that carry the load.
Seven agents follow a participant through your organisation in the order they actually move. Nine more run continuously underneath: the money, the evidence, the workforce and the people around the participant. This is a menu of what the sector needs, not a build order you have to commit to. The numbers are for reference on a call, nothing more.
Referral, intake and plan verification
Referrals and enquiries triaged, plan status, funding management type and available funding periods verified, capacity matched, and every referral tracked through to first service. More than three quarters of providers are turning work away without a reliable view of what they can actually take, and under a compressed claim window a delayed commencement is delayed revenue. Your intake manager accepts or declines. The agent never ranks a participant by profitability.
Service agreements and funding periods
Agreements generated and versioned, agreed supports mapped to the correct support items under the current catalogue, funding-period allocation modelled, and any scheduled service that would exceed a funding period flagged before it is delivered. Price limits are now charge caps a provider breaches by exceeding, and claims are rejected when a funding period is exhausted even where the plan still holds funds.
Roster of care and support matching
The roster of care built and maintained against agreed supports, continuity breaks flagged, and cost modelled against the applicable price cap before a shift is committed. Continuity is the participant's experience and your margin at the same time. A coordinator confirms the roster, and a stated participant preference is an input the human applies, never a variable the agent optimises against.
Commencement readiness
Onboarding packs assembled, workers briefed, first-shift readiness checked, and consent and documentation completeness confirmed before service starts. A service that commences on incomplete documentation creates a claim you cannot evidence later, which under seven-year retention is a problem that surfaces years later.
Case notes and service delivery evidence
Notes drafted from the worker's own account, linked to the support item, the roster line and the participant's goals, with the draft, the correction history, the reviewer and the approval preserved as separate checkpoints. Approval never erases the original, so you can always show how a record was produced. This is the single largest documentation drain, the most common audit failure point, and the place informal AI use is already happening.
Progress reporting and reassessment evidence
The evidence base for progress reports and reassessment submissions assembled from existing service records and linked to goals. A reassessment request now has to explain what changed and produce supporting evidence, and that evidence is material you already hold and currently cannot retrieve efficiently. The practitioner or coordinator writes the professional opinion. The agent never writes it and never generates a report presented as a clinician's own view.
Exit, transfer and closure
Transfer documentation, records handover to a new provider, final claiming inside the window, and retention obligations carried through. Exits are where final revenue is lost without visibility and records obligations are breached. Every bereavement and transition conversation stays with your people.
Running underneath, continuously
Claiming and the 90-day window
Claims assembled and validated against support items, funding periods and delivered-service evidence, the note-to-claim cycle driven inside the window, rejections remediated, and seven-year retention integrity maintained. An invoice not claimed inside 90 days of delivery stops being a timing problem and becomes a permanent write-off. Finance approves every claim.
Plan budget and funding-period forecasting
Budget consumption monitored against funding periods, exhaustion and underutilisation forecast, and the provider alerted in time to have a human conversation with the participant or their coordinator. National average plan utilisation sits around 75 per cent. The participant decides how their budget is used, always. The provider raises it, the agent never directs it.
Utilisation and non-billable time
Paid non-billable time measured and attacked: travel gaps, unfilled shifts, admin blocks, cancellation exposure, and the margin effect of each one modelled. This is the largest operating lever in disability services and the one growth will not fix. It looks at shift patterns and operating structure, never at individuals as performance targets.
Award interpretation and rostering cost
The award interpreted against every rostered shift, including broken shifts, sleepovers, active nights, minimum engagement and travel, with any shift whose cost exceeds the applicable price cap flagged before it is worked. The gap between award cost and price limit is where margin erodes without visibility, one shift at a time, and it is usually found in payroll a fortnight too late.
Incidents and complaints
Incidents captured at the point of awareness, the notification clock started, category triaged, deadlines tracked, and notification content assembled for human review, with complaints intake and resolution tracked alongside. The most consequential compliance failure in this sector is the gap between a verbal report and a system entry. Your delegate determines category, response and whether to notify. The agent never notifies a regulator on its own and never judges safeguarding.
Restrictive practice administration
Authorisation status tracked by state and territory, plan versions and expiries held, reporting deadlines managed, and monthly unauthorised-use reporting assembled. Multi-state authorisation fragmentation is pure administrative cost that providers carry and no one funds. This is the highest-governance agent in the suite, and the exclusion around clinical content is absolute.
Worker screening and credential currency
Worker screening status, banning orders, qualifications, orientation module completion, mandatory training and supervision currency held against one worker record, with the requirement set defined per worker and per placement rather than as a single checklist applied to everyone. Issue and expiry are captured when a document is received, alerts are raised before the lapse, and currency is checked against the published roster so an expired clearance surfaces before the shift rather than at audit. As registration widens, worker compliance becomes a registration risk rather than an administrative one. Employment, disciplinary and rostering decisions stay with your people.
Practice Standards evidence and audit readiness
Evidence assembled continuously against the applicable Practice Standards and quality indicators as service happens, self-assessment supported, and audit packs generated. Providers do not fail audits for lacking policies. They fail on the gap between what they say they do and what they can evidence, and that gap is a documentation problem with a deadline attached.
Family, nominee and coordinator liaison
Routine status updates, service change notifications, scheduling and escalation routing to the right human. Coordination load falls on the people least able to spare it. Your care or service manager owns every substantive conversation, and the agent never communicates with a participant about their choices.
Every one of these is work your organisation already performs manually today. The suite is a map of that work, not a commitment you have to take whole.
Worker compliance
A register is only as current as the last person who updated it.
Worker compliance rarely fails because a team is careless. It fails because currency depends on a person remembering to open a register that only they keep current. That register is accurate up to the last time someone sat down with it, and nothing announces the gap between then and now. In a registered environment, that gap is an expired clearance on an active roster, or an unevidenced requirement at audit.
- One record of a worker, not five. Today the record is distributed across payroll, email threads, a manual register, your induction platform and a document store, and no single system owns it end to end. The suite establishes one worker record that those systems feed, without replacing any of them.
- Currency becomes a monitored state. Issue and expiry are captured at the point a document is received, and the alert is raised before the lapse rather than discovered after it. No one has to remember to check.
- Requirements are placement-specific, not uniform. A worker transporting participants requires a current licence, vehicle registration and insurance. A worker on a particular placement may require participant-specific training such as positive behaviour support. The suite holds the requirement set per worker and per placement, rather than one checklist applied to everyone.
- Collection and renewal are driven, not pursued. Requests are issued, documents received and filed, and dates recorded at the point of receipt. Your team confirms authenticity where that judgement is required; the administrative cycle around it is absorbed.
- Credential status reaches the roster before the shift. The failure that matters is an expired clearance on a worker who is already rostered. Currency is checked against the published roster in advance, so the conflict surfaces before the shift rather than at audit.
- Audit evidence is a current state, not a reconstruction. Evidence is assembled continuously as documents arrive, so producing it for an auditor is an export rather than a concentrated effort under time pressure.
- The load stops scaling with headcount. Every additional worker currently adds permanent maintenance to a stretched team. Monitoring is the point at which that ceases to be true.
Every decision stays with your people. The agent monitors, requests, records and alerts. Your team verifies, decides and signs. What changes is that compliance becomes a continuous state you can evidence on any day, rather than a position you reconstruct when someone asks for it.
Sovereignty and governance
Private AI as a controlled asset. Participant data never leaves your control.
Routing participant information through a public model is uncontrolled exposure: offshore reach, retention you cannot bound, and no audit trail when someone asks what happened. In this sector it is worse than a risk, because the regulator has already written down what it expects. A private sovereign environment is the opposite, and it is the only version a board should accept here.
- Australian storage, jurisdiction and personnel. Participant data stays inside your controlled environment, under Australian law, operated by Australian people.
- De-identification at the model boundary. Participant identifiers are separated from content before any model processing and re-associated only inside your environment. The model never receives an identified participant.
- Consent as a first-class object. Who holds decision-making authority, for what, under which arrangement, with expiry and review dates. Nominees, guardians, child representatives and supported decision-making arrangements are all carried, and every agent checks consent before it acts.
- Provenance on every record. Every action logged, every record tagged as AI-drafted or human-verified, with the original draft, correction history, reviewer and decision preserved. Approval never erases the original.
- Human sign-off gates. Nothing clinical, financial or regulatory leaves the system without a named person approving it, and that approval is part of the record.
- Architectural exclusions, not policy ones. Behaviour support plan content, clinical opinion and participant-facing decisioning are excluded in the architecture, where they cannot be subsequently relaxed.
- Designed to stay outside the medical device line. Clinical decision support software is exempt only where it supports a recommendation to a health professional, does not process images or device signals, and does not replace clinical judgement. Every clinically adjacent agent is designed against all three, and the boundary is re-tested at every design review.
- Model change control. Versioned models, change logs and regression testing before anything reaches production.
How we deploy
Over your systems. Never a wholesale replacement.
The suite sits over the client management, rostering, payroll and finance platforms you already run, reading from them and writing back under human sign-off. Keep the system your coordinators know and the finance stack your CFO trusts. Providers under this much regulatory pressure will not tolerate a migration, and they should not be asked to.
We start where the payback is clearest and the exposure is lowest: the finance and operations agents, claiming, utilisation, award interpretation and funding periods. They touch no participant-facing surface at all. Evidence and coordination agents follow, which is also what gives your workers a sanctioned tool in place of the consumer one they are already using. Anything clinically adjacent comes last and under the heaviest governance, because that is the order that earns trust rather than spends it.
No wholesale replacement. No migration. Each stage proves itself before the next one starts.
This is built for core supports providers, for SIL and SDA providers moving through mandatory registration, for allied health and therapy practices absorbing price cuts, and for multi-service and multi-state organisations carrying authorisation fragmentation across jurisdictions. If evidence, claiming and utilisation are deciding your margin, this is built for you.
The hard questions
Answered plainly.
Does this threaten participant choice and control?
No, and the architecture is built so that it cannot. No profiling, no scoring, no prediction of participant choices, and no output that touches a participant's decisions about their own supports. The agents face your operations, not your participants. If we ever built one that pointed the other way, you should stop using it and tell us why.
Will this replace our support workers?
No. It replaces the paperwork standing between them and the work they came to do. The doctrine is published on this page and it does not move: the worker in the room, the clinical judgement, the safeguarding call and the difficult family conversation are never automated and never simulated.
What about behaviour support plans?
We do not touch them. The NDIS Commission does not endorse the use of AI in developing or reviewing behaviour support plans, so our agents handle authorisation tracking, version control, expiries and reporting deadlines, and nothing else. That exclusion is architectural rather than a policy commitment, which means it is not something a future configuration change can subsequently undo.
Where is our data held?
In Australia, under Australian jurisdiction, operated by Australian personnel, inside your controlled environment. Participant identifiers are separated from content before any model processing, so the model never receives an identified participant. Every agent action is logged and provenance-tagged as AI-drafted or human-verified.
Our participants have nominees and guardians. How does consent work?
Consent is a structured object in the system rather than a checkbox on a form. It carries who holds authority for what, under which arrangement, with expiry and review dates, and it covers nominees, guardians, child representatives and supported decision-making arrangements. Every agent checks it before it acts, and a participant, nominee or advocate can be told plainly what you use AI for and what it never touches.
Will the NDIS Commission accept it?
It is built to be read by a regulator rather than to get past one. The architecture is designed against the expectation the Commission set out in its position statement on AI in behaviour support plans, on de-identification and participant information, and against the Practice Standards, the Code of Conduct and Australia's AI Ethics Principles, with explicit human decision rights, model change control and a complete evidence trail. Whether any particular deployment satisfies your obligations is a matter for your governing body and your regulator, not for us to assert.
Does it work with the systems we already run?
Yes, and it does not replace them. The suite sits over your client management, rostering, payroll and finance platforms, reading from and writing back to them under human sign-off. Integration maturity varies a great deal across the platforms in this sector, so we verify what your particular system actually exposes during the engagement rather than assuming it in a proposal.
Our people will not adopt it.
They adopt what removes the work they least want to do, and in this sector that is documentation. Many of them are also already using AI informally, without sanction and without protection, because the pressure is real. This gives them a tool that makes the work easier and does not put your registration at risk. Adoption follows relief rather than training.
What happens when a credential expires while a worker is rostered?
The conflict is raised before the shift, not after it. Currency is checked against the published roster in advance, so an approaching or lapsed clearance appears against the rosters it affects while there is still time to act. The agent does not remove a worker from a roster and does not make an employment decision. It surfaces the conflict to the person who holds that decision, and records what was surfaced and when.
Start with a conversation, not a commitment.
We will map your evidence, claiming and utilisation position against the participant lifecycle, show you where the suite deploys first, and give you something your board and your auditor can both read. No pricing pressure, and no outcome promises. Process commitments only.