Preparation starts with delivered support
Bring the agreement, schedule, timesheet and delivery references together before staff prepare a line.
For NDIS provider owners and administration teams in Australia
AI automation for NDIS providersPrepare each line from the evidence of support.
Follow scheduled, recorded and evidenced hours through independent checks. See why two different discrepancies keep an affected preparation pack out of the export.
Built around your working day
The records should agree before a line is prepared.
Agreements, schedules, timesheets and delivery notes should tell the same story before staff prepare an invoice or claim. We connect those records and expose disagreements so your authorised team can review the evidence without changing the source to make it fit.
Your current tools matter. your participant records, rostering, timesheet and accounting systems are useful starting points for scoping. We check the actual records, access and supported actions in your account before promising a connection.
What changes for you
Disagreements remain visible
Show missing evidence and conflicting hours as separate review reasons without changing the source records.
Unresolved lines stay out
Keep affected records excluded from preparation until authorised staff resolve the evidence and record their decision.
Example system · Simulated business data
Every claimed hour starts with evidence.
Follow scheduled, recorded and evidenced hours through independent checks. See why two different discrepancies keep an affected preparation pack out of the export.
Schedule, timesheets and supplied delivery evidence each total 24 hours.
SC-09 / v1 · example reviewThe complete architecture
Selected stage Conditional path Held or changed
Blue connections show the scenario path. Stage selection changes explanation only. Dashed paths need a new decision.
01 / Permission gate
Set access and record purpose
Restrict the preparation workflow to the information and staff roles needed for its purpose. Use participant and agreement references without widening access to unrelated records. An example authorised reviewer checks the administrative sources. The packet is prepared for the next staff step and no claim is submitted.
Prepared with an example human decision
Permission-scoped source register / simulated
24 hmatched administrative hours
SC-09-v1 · preparation packet
| Source or item | Recorded value | Decision |
|---|---|---|
| NP-EX-A | 16 scheduled / 16 evidenced | Timesheet 16 h |
| NP-EX-B | 8 scheduled / 8 evidenced | Timesheet 8 h |
| Total | 24 h in each lane | Sources agree |
| Export status | Prepared for staff review | Not submitted |
An example authorised reviewer checks the administrative sources. The packet is prepared for the next staff step and no claim is submitted.
- Attach agreement, schedule, timesheet and delivery references to each line.
- Record the example reviewer decision on the pack version.
- Keep any later submission outside this website demonstration.
Inspecting access · scenario output stays tied to its recorded decision
Inspect shared state, version history and event trace
Schedule and agreement
Schedule is 16 hours for NP-EX-A and eight for NP-EX-B under example agreement references.
Timesheets
16 + 8 = 24 recorded hours.
Delivery evidence
16 + 8 = 24 evidenced hours.
Authorised review
Administrative packet checked by the example reviewer. No actual names, NDIS numbers or support codes.
This is administrative claim preparation for staff review. It does not establish eligibility, funding, price limits, consent validity, service quality, claim compliance or payment. Nothing is submitted.
Read the complete system walkthrough
01 / Permission gate
Set access and record purpose
Restrict the preparation workflow to the information and staff roles needed for its purpose. Use participant and agreement references without widening access to unrelated records.
What you receive Permission-scoped source register.
02 / Version checks
Align the agreement and period
Match agreement and schedule versions to the preparation period. A current roster cannot silently replace the evidence of what was delivered earlier.
What you receive Agreement and schedule register.
03 / Independent rules
Check each evidence lane
Check schedule quantities, timesheet arithmetic, delivery completeness and access records separately. Keep the original values even when they disagree.
What you receive Source-linked hours comparison.
04 / Rules and review
Keep distinct discrepancies distinct
Compare timesheets to evidence and to schedule as separate checks. A difference in one comparison is not an explanation for the other, and neither justifies changing a source.
What you receive Discrepancy queue.
05 / Authorised staff
Prepare only the reviewed packet
Authorised staff review the evidence and outstanding issues. Unresolved affected records stay out of the prepared export. This demonstration never performs a submission.
What you receive Versioned preparation packet.
This is administrative claim preparation for staff review. It does not establish eligibility, funding, price limits, consent validity, service quality, claim compliance or payment. Nothing is submitted.
The decision stays with your team
Useful evidence. Clear responsibility.
This is administrative claim preparation for staff review. It does not establish eligibility, funding, price limits, consent validity, service quality, claim compliance or payment. Nothing is submitted.
NDIA describes complete and accurate records of delivered supports and identifying information needed in those records. A matched example pack is not a claim of eligibility or compliance. NDIA record-keeping requirements ↗
Primary source checked . This original example illustrates a design, not a delivered client result.
What it costs
Scope the whole handover.
Record permissions, agreement versions, schedule and timesheet identifiers, delivery evidence and reviewer responsibilities determine scope. Start with a preparation pack before considering a submission operation.
We map the current process, agree the review points and put the scope, fixed fee and payback estimate in writing. Software and usage costs are considered separately. Your own baseline determines the business case.
Automation builds
From $3,500 AUDOne process, rebuilt to run without you. Monitoring and documentation included.
Typical projects
$3,500 to $12,000 AUDSeveral connected processes across two or more systems, where the data needs cleaning first.
Complex AI agent systems
$12,000 to $25,000 AUDAgents that read unstructured information, decide and write back, with human review and a full audit trail.
Ongoing care plans
$750 to $2,500 AUD per monthPriced on how much you run and what your business loses the day one of them stops.
When something breaks
Know what stopped and what is still safe to continue.
Missing delivery evidence must not become an inferred support record. We monitor absent arrivals, empty matches and failed preparation writes, retaining source differences and a review queue rather than auto-correcting the hours.
We design checks for a run that fails, a run that returns nothing and a run that never starts. The care scope names the person who receives an alert, the information they need and how a held record returns to review.
You own the workflows and accounts. Handover includes the record identifiers, review rules and recovery instructions. No lock-in is required to keep your work.
See ongoing supportBefore you decide
Your questions, answered
Does the system submit NDIS claims?
This example does not submit anything. It prepares administrative evidence for authorised staff. Any later submission operation would need its own scope, supported access, controls and explicit approval.
Does a matched record mean it is compliant or payable?
No. Matching quantities is one administrative check. Eligibility, funding, pricing, delivery quality and claim requirements need the responsible provider’s review.
What happens when a timesheet exceeds the evidence?
Preserve both values and hold the affected preparation pack. The example also compares the timesheet to the schedule separately, because the two differences are not interchangeable.
Can AI fill in missing support notes?
It must not infer that a support was delivered or manufacture source evidence. We prepare a missing-record request for authorised staff and keep the unresolved item excluded.
What records would a build need?
We scope agreement and schedule versions, timesheets, delivery evidence, identifying fields and staff decisions. NDIA guidance describes relevant record types, but the exact workflow depends on your service and circumstances.
Can this connect to our rostering and accounting tools?
We verify each required record and operation in your accounts, including permissions and export support. A tool name does not establish an authorised claims integration or a complete data path.
For work with several evidence lanes, version changes and explicit review gates, our n8n operating model explains the orchestration decisions. The platform choice still depends on your access, maintenance capacity and data path.
A useful first conversation
Bring one process that keeps getting stuck
Show us where the records arrive, who makes the decision and what the next person needs. We will map a useful first scope with you.
Book a call