NDIS Operations Diagnostic
Providers between $750k and $1.5M are in the most dangerous revenue band in NDIS. Large enough to have real operational complexity. Small enough that one bad audit finding can end the business.
At 26-50 participants, you are running a real operation. You have rostering, incident management, compliance obligations, claims processing, and coordinator relationships that need to function without you personally monitoring every one.
The data from 200+ provider audits is consistent: providers between $750k and $1.5M lose an average of $200,000+ per year across preventable gaps in referral capture, claims rejection, compliance remediation, and roster non-compliance. That is 15-25% of revenue disappearing through operational holes -- before accounting for penalty exposure that can reach six figures per breach.
The question is not whether you have gaps. Every provider does. The question is whether you know what each gap is costing you -- right now, today.
The Stress Test
For each scenario, select whether you have a documented, tested process in place. "Sort of" counts as No.
An incident is reported at 2am Saturday. What happens?
An on-call support worker reports a participant altercation at a SIL property. There is no coordinator on shift. The NDIS Commission requires 24-hour reporting for serious incidents. The incident needs to be documented, classified by severity, and escalated to the right person within that window.
The most common audit non-conformity is incomplete incident management logs -- systems that exist on paper but are not embedded in practice, superficial root cause analysis, and missing 24-hour reporting compliance. If your current process is "call the manager's mobile and hope they answer" -- that is not a process. That is a liability.
A support coordinator calls about a SIL vacancy. How fast do you respond?
Coordinators manage 40-80 participants each. They send vacancy inquiries to 3-5 providers simultaneously. The provider who responds with bed availability, participant compatibility info, and next steps within 2-4 hours gets the referral. The provider who responds next week gets nothing. Each SIL participant is worth $80,000-$150,000 per year in plan funding. One lost referral is not a missed email -- it is six figures of annual revenue gone.
Across the sector, the average first-response time to coordinator inquiries is 27 hours. The median time for providers who actually win the referral: under 4 hours.
An auditor asks for your evidence file today. How long to produce it?
The NDIS Quality and Safeguards Commission does not announce spot checks. When they request your evidence package for a specific Practice Standard, you need to produce current policies, staff training records, incident logs, and participant feedback in a structured format.
If assembling this takes your compliance officer more than 4 hours, you have a documentation architecture problem. If it takes more than 24 hours, you have a compliance exposure that auditors will flag as a finding.
A claim is rejected post-submission. How do you find out?
10-15% of NDIS claims are rejected on first submission. At your revenue band ($750k-$1.5M), that is $75,000-$225,000 in first-submission rejections per year. Most rejections are for trivial reasons: missing documentation, unit discrepancies, incorrect support category codes, or provider not listed as "my provider" for the participant's plan.
Every one of those is catchable before submission. If you learn about rejections after the NDIA returns them -- often 30-60 days later -- you are losing cashflow and rebilling staff time on claims that should never have been submitted wrong.
A staff member calls in sick for a night shift. What is the process?
SCHADS Award clause 25.5 requires minimum break periods between shifts. Clause 10.4 governs overtime thresholds. When you backfill a night shift at short notice, the replacement worker's existing roster must be checked against these constraints before the shift is confirmed.
Fair Work penalties reach up to $93,900 per breach per employee per pay period. Weekend and public holiday penalty rate non-compliance accounts for 45% of all SCHADS underpayment claims. Broken shift allowances, minimum engagement periods (at least 2 hours per portion), and failure to update annual rate changes (every July) are the other top exposures. Reference: Disability Services Australia entered an Enforceable Undertaking with Fair Work for incorrect overtime application and underpayment. If your backfill process is "ring around until someone says yes," you are generating breaches every month.
A participant's plan is about to expire. Who tracks it?
When an NDIS plan expires, all service bookings tied to that plan stop. If the plan review is delayed and no interim arrangement is in place, you cannot bill for services delivered during the gap. For a SIL participant at $1,500-$2,500/week, a 4-week gap is $6,000-$10,000 in unfunded service delivery.
With 26-50 participants, plan expiries should be flagged 90 days out, 60 days out, and 30 days out. If nobody in your operation owns this tracking, plans will lapse and revenue will stop with zero warning.
A coordinator asks for your current vacancy list. Where is it?
Support coordinators manage placement decisions for dozens of participants. When they need a SIL bed or a community access slot, they go to the providers who can give them a clear answer immediately. If your vacancy data lives in someone's head, or in a spreadsheet last updated three weeks ago, you are invisible to coordinators who are actively placing participants.
Providers who maintain a real-time vacancy list and distribute it proactively to their coordinator network capture 3-5 more referrals per month than those who do not.
A restrictive practice is used. Where is it documented?
Under the NDIS (Restrictive Practices) Rules 2024, all regulated restrictive practices must be authorised, documented, and reported to the NDIS Commission. This includes environmental restrictions, seclusion, chemical restraint, mechanical restraint, and physical restraint.
If a restrictive practice is used and the documentation trail is incomplete -- no behaviour support plan reference, no contemporaneous record, no reporting to the Commission within 5 business days -- penalties reach up to $93,900 per breach. The NDIS Commission's 2025-26 enforcement priorities explicitly list "reduction and elimination of regulated restrictive practices" as priority number one. This is where they are looking hardest.
Your insurance renewal is due. Who tracks the expiry?
NDIS registered providers must maintain professional indemnity, public liability, and workers' compensation insurance as a condition of registration. If any policy lapses, your registration is non-compliant. The Commission can suspend registration with no grace period.
This sounds basic. It catches providers every year. In the 2023-24 reporting period, 14% of compliance actions initiated by the Commission involved lapsed or inadequate insurance coverage.
A family member complains about service quality. What is the process?
The NDIS Practice Standards (Core Module 6) require a documented complaints management system that is accessible, responsive, and produces resolution outcomes within defined timeframes. Complaints must be acknowledged within 2 business days and resolved within 21 days.
If your complaints process is "the manager handles it informally," you fail the Practice Standard. The Commission audits complaints handling as a leading indicator of provider quality. A finding here triggers deeper audit activity across all modules.
Your Results
$0
0 operational gaps identified
Every provider we have run this with has the same reaction: "I knew it was bad. I did not know it was this bad." The numbers are always worse than the feeling.
For context: nearly 50% of NDIS providers already report a financial loss. 81% say current prices are unsustainable. The gaps in this stress test are not hypothetical costs -- they are the margin that determines whether you survive the next 12 months. (Source: NDS State of the Disability Sector Report 2025)
Every dollar above is money leaving your operation through gaps that have documented, repeatable fixes.
Prioritised Fix List
Fixes ranked by (cost of gap) multiplied by (speed to close). High-cost gaps that can be closed quickly go first. Low-cost gaps that require slow structural change go last.
Q1: Fix Immediately
High cost, quick to close
Q2: Fix This Quarter
High cost, requires infrastructure
Q3: Schedule This Month
Moderate cost, quick to close
Q4: Build Into Operations
High cost, requires ongoing discipline
| Rank | Gap | Annual Cost | Time to Close | Category |
|---|---|---|---|---|
| 1 | Coordinator response time | $80,000 | 4-6 weeks | Revenue |
| 2 | Restrictive practice documentation | $93,900 | Ongoing | Compliance |
| 3 | Vacancy list and distribution | $45,000 | 4-6 weeks | Revenue |
| 4 | Plan expiry tracking | $40,000 | 3-4 weeks | Revenue |
| 5 | Claim pre-validation | $75,000 | 2-3 weeks | Cashflow |
| 6 | Evidence file readiness | $25,000 | 6-8 weeks | Compliance |
| 7 | Complaints handling system | $25,000 | 1-2 weeks | Compliance |
| 8 | After-hours incident protocol | $15,000 | 1-2 weeks | Compliance |
| 9 | SCHADS-compliant rostering | $93,900 | 2-3 weeks | Labour |
| 10 | Insurance expiry tracking | Registration risk | 1 day | Compliance |
90-Day Operations Roadmap
Here is exactly what to fix, in what order, and how long each fix takes. Compliance gaps first -- because a single audit finding can consume more management time than three months of growth work. Revenue systems second. Automation third.
Document your incident management protocol. Define severity levels (critical, high, medium, low), escalation paths for each, and required documentation fields. Test it with a simulated 2am incident. If your team cannot execute it without calling you, it is not a protocol.
Build your evidence file architecture. Create a single location (digital, structured) where every Practice Standard has a corresponding folder with current policies, training records, and compliance evidence. Set 90-day review reminders on every document.
Implement a complaints handling system that meets Core Module 6. Intake form, acknowledgment within 2 business days, resolution pathway, outcome documentation. This is not complex -- it is a process with defined steps and timeframes.
Audit your restrictive practice documentation against the 2024 Rules. Ensure every authorised practice has a current behaviour support plan reference, contemporaneous use records, and Commission reporting within 5 business days. Set up insurance and registration expiry tracking with 90/60/30-day alerts.
Create a real-time vacancy tracker. Every SIL bed, community access slot, and support coordination opening should be visible in one document that updates when a placement changes. Assign ownership of weekly updates to a specific role.
Build your coordinator contact list. Identify every support coordinator who has referred to you in the last 12 months, every coordinator managing participants in your service area, and every coordinator at LACs covering your region. This list should contain 40-80 names for a provider your size.
Set a response time target for coordinator inquiries: under 4 hours during business hours. Define who responds, what information they provide (availability, compatibility notes, next steps), and how unanswered inquiries are escalated at the 2-hour mark.
Begin proactive vacancy distribution. Send your updated vacancy list to your coordinator network every Monday. Include one line per vacancy: location, participant profile fit, and contact for next steps. Measure response rate.
Implement pre-submission claim validation. Before any claim is submitted to the NDIA, check: line item matches service agreement, service date falls within active plan period, no duplicate claim exists, and claim amount aligns with price guide. This single check catches 80% of rejections.
Build a plan expiry dashboard. Every participant's plan end date, last review request date, and current status (active, review requested, review scheduled, lapsed) in one view. Flag any plan expiring within 90 days that does not have a review request submitted.
Implement SCHADS pre-publish roster checks. Before any roster is published, validate: minimum break periods between shifts (clause 25.5), overtime thresholds (clause 10.4), and maximum hours (clause 21). Flag breaches before they become payroll problems.
Review and measure. Calculate actual claim rejection rate for the month. Count coordinator inquiries and response times. Verify zero lapsed plans and zero SCHADS breaches. Set monthly review cadence for all three systems.
Providers who execute this sequence close $200,000+ in annual operational gaps within a single quarter -- and eliminate penalty exposure that can reach six figures per breach. The compliance work in Month 1 protects the business. The referral pipeline in Month 2 drives the growth. The automation in Month 3 sustains both without adding headcount.
This is the operating model that gets a $750k provider to $1.5M. Not more staff. Not more hours. Better systems.
This roadmap works. Every step is documented. Every fix is proven. But it requires 3 months of dedicated operational focus from a team that is already stretched.
The agent stack closes these gaps in weeks, not months -- and runs permanently. Incident intake, coordinator response, claim validation, roster compliance, evidence generation. Each agent does one job. Each job runs 24/7 without adding headcount.
The roadmap above is the manual path. The Capacity Blueprint shows you the automated one.
From 1 July 2026, ALL SIL providers must be registered. Certification-level audit required -- not verification. SIL is classified as high-risk. Cost: $5,000-$15,000+. Timeline: 3-6 months. This is not optional. If you are delivering SIL services and have not started the registration process, the 90-day roadmap above is no longer a recommendation. It is a prerequisite for continuing to operate.
Scenario 11
A navigator calls your office. They're looking for a SIL provider in your area who specialises in high-complexity behavioural support. They need to place a participant within 14 days. They check your NDIS Provider Finder listing -- it says "community access, daily living, supported independent living" with no specialisation detail. They check your compliance record -- one open finding from a mid-term audit. They check your response time -- you responded to their last inquiry in 3 days. They move to the next provider on the list.
The NDIS Navigator model is replacing Support Coordinators with government-funded Navigators. Testing begins mid-2026. Gradual rollout 2026-2028. This is the single largest structural change to how participants find providers since the scheme launched.
Navigators will not call providers they know personally. They will search systematically: by specialisation, locality, compliance track record, capacity, and response speed. The informal relationships that currently drive referrals -- a coordinator who likes working with you, a word-of-mouth recommendation from another provider -- will carry less weight in a system designed around structured search and data-driven placement.
Incident management gaps signal compliance risk. Slow response times signal unreliability. No coordinator relationships mean no track record of successful placements. Rejected claims indicate financial instability. A missing vacancy list means a navigator cannot even confirm whether you have capacity.
Each "No" answer above is not just a cost today. It is a disqualification signal in the navigator era.
The 90-day roadmap above does not just fix today's problems. It builds the operational profile that navigators will use to find you. Compliance readiness. Response speed. Documented capacity. Claims integrity. Every gap you close now becomes a reason a navigator chooses you over the provider who did not prepare.
The providers who close these gaps in the next 12 months will own the navigator era. The providers who don't will watch referrals go to competitors who prepared.
Immediate Action
You do not need agents, consultants, or budget to start. These three changes take less than an hour combined and produce measurable results this week.
Set a response time SLA. Today.
Every coordinator inquiry gets a response within 4 hours. Put it in writing. Tell your team. This single change puts you ahead of 80% of providers.
Write your after-hours incident process on one page.
Not a policy document. One page. "When an incident happens after hours: (1) call [name], (2) log it in [system], (3) notify [who] within [timeframe]." Print it. Put it on the wall in every home. If you can't write it in 10 minutes, you don't have a process.
Send one email this week.
Pick one coordinator you haven't spoken to in 3+ months. "Hey [name] — checking in. We've got [capacity] available in [area]. If anything comes up on your end, happy to be a quick option." Under 40 words.
The Reality Check
The three fixes take an hour. Sustaining them takes discipline.
The response time SLA gets forgotten in Week 3 when things get busy. The incident process gets bypassed when someone's on leave and nobody remembers who to call. The coordinator email doesn't get sent because something more urgent came up.
That's the pattern. The fix is obvious. The maintenance is where it breaks.
The agent stack doesn't forget, doesn't get busy, and doesn't skip weeks. It runs the response time SLA, the incident documentation, and the coordinator outreach permanently.
Case Study
Your Move
Hit reply on the email that brought you here with your stress test total — the annual cost number from the 10 scenarios. I'll send you the specific fix order based on what we see at your revenue band.
Next Step
The stress test shows you where the gaps are. The Capacity Blueprint shows you exactly how to close them -- with a full operational diagnostic, prioritised agent recommendations, and a guaranteed deployment plan tailored to your operation.
30 minutes. Your numbers. A specific recommendation.
Book Your Capacity BlueprintFree diagnostic session -- no obligation, no pitch deck, no "let me send you some info."
Your own inputs produce the recommendation.