23 overdue policies.
6 weeks to registration renewal.
A Melbourne NDIS provider discovers their compliance file during internal review. What they find, and what the Compliance Agent does about it.
The situation before install
A Melbourne provider with 6 years of operation and a team of 28 support workers. Two directors. No dedicated compliance officer. Compliance tracking managed through a shared spreadsheet and calendar reminders that had been inconsistently maintained for 18 months.
The provider had passed their previous audit without incident. That audit was during a period when the operations manager had personally managed the preparation over 6 weeks. She had since left the business.
Gaps found during internal review
- —Incident Management Policy — last reviewed 22 months prior (NDIS requires annual review)
- —Behaviour Support Policy — no version history, original draft date unknown
- —Medication Management Procedure — two staff had not completed required sign-off
- —Worker Screening records — one staff member's clearance had lapsed 6 weeks prior
- —Reportable Incidents register — entries for prior 4 months missing mandatory fields
What the Compliance Agent does
Every policy, procedure, and certification in the register tracked against its review cycle. Review dates, responsible staff, and sign-off status maintained automatically. No spreadsheet upkeep required.
60-day, 30-day, and 7-day warnings sent to responsible staff with direct links to the relevant document. Unresolved alerts escalate to the director automatically. Nothing falls through a gap because someone deleted a calendar reminder.
On-demand evidence package generation — current policy versions, review history with timestamps, staff acknowledgements, worker screening records. Produced in minutes, not weeks.
6 weeks, documented
The gap revealed
A director scheduled an internal policy review meeting to prepare for NDIS registration renewal. When the team pulled the policy register, they found 23 documents flagged for overdue review. Two of those were marked as critical by the compliance framework. No one had been tracking review dates systematically — it had been a shared calendar reminder that two people deleted.
Install
Compliance Agent deployed with the full policy register uploaded. Each policy assigned a review cycle (annual, biennial, or triggered by regulatory change). Responsible staff assigned per document. Automated escalation configured: 60-day warning, 30-day warning, 7-day final alert — escalating to director if unresolved.
First wave of alerts
The agent generated a prioritised overdue list ranked by renewal impact. 8 policies flagged as critical — requiring update before the audit date. Responsible staff received individual alerts with review instructions and a direct link to the current policy document. 4 were reviewed and updated within the week.
Evidence package generated
Director requested a draft evidence package for the renewal auditor. The Compliance Agent produced a structured document set: current versions of all policies, review history with timestamps, staff sign-off records, and worker screening status. Time to generate: under 3 minutes.
Mock audit
An independent NDIS auditor conducted a mock compliance review. Evidence package submitted at the start of the session. The auditor reviewed 11 policy areas. No corrective actions issued. One observation noted: the new compliance tracking system was cited as a model worth adopting broadly.
Registration renewed
NDIS registration renewed without condition. Director estimated 40 hours of staff time saved versus the prior renewal cycle, where the compliance preparation was entirely manual.
The outcome
“Our last compliance preparation took 6 weeks of staff time. This time it took 3 weeks and the file was cleaner. The agent runs in the background now — I get the alerts, my team handles the reviews, and I know exactly where we stand on any given day.”
Director, NDIS provider — Melbourne
Registration renewed without condition. 40 hours of staff time saved versus the prior renewal cycle. Ongoing compliance monitoring now automated — the next renewal will require preparation time measured in days, not weeks.
July 2026 — NDIS registration changes
New NDIS practice standards and registration requirements take effect from July 2026. SIL providers face additional documentation obligations. Providers who have not updated their compliance frameworks will be required to do so at renewal — with shorter notice periods than prior cycles. The Compliance Agent is configured to track against the updated standards as they are published.
The guarantee on this install
The Compliance Agent guarantees that no policy review date is missed after install — automated alerts fire at 60, 30, and 7 days prior to each deadline. If a review date passes without the responsible staff member being notified, Build n Bloom diagnoses the failure and rebuilds the alerting system at no cost.
One-time install. No retainer required.
Book a diagnostic to assess your compliance exposure before the July 2026 changes.
Book Operational DiagnosticFree 30-minute session. No pitch before the diagnostic.