July 1 is 22 days away.
We've been talking to NDIS providers across Perth, Melbourne, and Sydney over the last six weeks. The consistent split is not between large and small providers, or experienced and new ones. It's between providers who systematised their compliance workflows before this deadline and those still managing documentation manually.
The ones in the second category are not doing less work. They're doing more — and producing less reliable output.
The question that tells you which side you're on
Ask your operations manager: can you produce a current, audit-ready policy register for every NDIS Practice Standard right now — not by end of week, not after a review session — right now?
If the answer is not "yes," the compliance documentation is either scattered across shared drives, held in individual team members' inboxes, or has not been reviewed against the current standards since the last audit.
That is the gap. Not one document — the systematic ability to know, at any moment, what is current and what is overdue.
What the July 1 changes actually require
Three operational areas shifted materially under the mandatory registration framework:
Incident documentation. Every reportable incident must be logged in Commission-compliant format at intake. Retrospective completion — filling in records after the fact — is not compliant. The documentation has to be right when it's created.
Policy currency. All policies must align with current NDIS Practice Standards. Static documents that haven't been formally reviewed since your last audit are a known risk. The Commission is not asking whether you have policies — they're asking whether they're current.
Coordinator evidence. Referral relationships that were previously informal need documented engagement history. Providers without systematic outreach records will find it difficult to demonstrate active market presence during an audit.
Three workflows that separate the prepared from the exposed
Workflow 1: Automated policy currency tracking
Prepared providers have a system that monitors document review dates against a compliance calendar and flags overdue reviews before they become audit issues. The system generates the review task, tracks completion, and updates the register when the review is done.
Manually, this is a spreadsheet with a person responsible for keeping it current. The person gets busy. The spreadsheet gets stale. The audit happens.
A Compliance Agent runs this workflow automatically — no person responsible, no spreadsheet, no staleness.
Workflow 2: Commission-ready incident intake at first contact
Prepared providers have an intake process that captures every required field the first time — severity classification, parties involved, immediate actions taken, notification timeline — in Commission-compliant format.
Manually, this is a phone call followed by a Word document. The document gets completed some time later. Some time later is not at intake.
A Triage Agent receives the intake, classifies severity, routes to the appropriate on-call contact, and generates the Commission-ready documentation in one pass.
Workflow 3: Systematic coordinator engagement records
Prepared providers can produce, on request, documented outreach history for their active coordinator relationships — contact attempts, responses, meeting notes, referral outcomes. The record exists as a byproduct of the outreach process, not a separate documentation task.
Manually, this is a mix of email threads, CRM notes, and whoever's memory is best on the day.
A Referral Agent runs outreach sequences through a structured pipeline where every contact is timestamped and every outcome is recorded. The engagement history is a byproduct.
What this actually costs
The providers we speak to consistently underestimate the administrative overhead of manual compliance management. When we map it properly in a diagnostic, 12–18 hours per week is a common figure for a provider running 8–15 homes.
At $40/hr, that's $480–$720 per week. $24,000–$36,000 per year. For documentation management alone.
The agents that run these three workflows cost less per month than one week of manual compliance labour. The agents don't take leave, miss reviews, or produce inconsistent documentation under pressure.
Three weeks is enough
July 1 is not too close to act. Three weeks is enough time to install a Compliance Agent, get it operational, and have it running before the deadline. Not in a theoretical state — operational, with a 48-hour micro-win milestone that proves the core function before the install is considered complete.
If you want to know exactly where your compliance gaps are before the deadline, the Operational Diagnostic maps every manual compliance workflow in 30 minutes and gives you a written recommendation regardless of outcome.
Book the free Operational Diagnostic →
Richard Opondo is co-founder of Build n Bloom. He spent five years as an NDIS operations manager before building the agents he wished he'd had. Read more →