Twelve questions every registered NDIS provider should ask before signing a software contract — claiming, rostering, plan management, compliance, AI governance, and exit clauses.
Start with your operating model, not the demo
NDIS software demos look similar at first glance. The differences emerge when you map the platform against how your team actually works — number of sites, plan management pathways, SIL or group programs, the funding mix today, and what you plan to add in the next twelve months.
Without that map, buyers tend to choose on UI polish or sales rapport and discover gaps after go-live.
Twelve questions to ask every vendor
1. Does claiming support both PACE and PRODA in the same module, and how are batches reconciled with NDIA remittance?
2. Are plan management pathways (self, plan-managed, NDIA-managed) treated as first-class — or as edge cases on the standard claim flow?
3. How are the NDIS Price Guide and registration groups updated, and how long after an NDIA change do customers see the new rules?
4. Can rostering enforce SCHADS Award 2010 penalty rates, loadings, and allowances on timesheets — or is payroll a separate integration?
5. What is the workflow for restrictive practices and behaviour support plans, including the immutable register a regulator expects?
6. How does the platform support NDIS Practice Standards evidence mapping for audit, and can you export it?
7. Is there one person record across NDIS, aged care, and allied health — or separate participant/patient/client files?
8. What family/representative portal features exist, and how granular are the permissions?
9. What AI capabilities exist, and what content is sent to external services? Are clinical notes encrypted and excluded?
10. Where is data hosted, and how is failover handled (the answer should reference Australian regions)?
11. What is the data export format on exit, and how quickly is data returned?
12. What is the published price by program — and what add-ons or per-claim fees are not in the headline number?
Red flags during due diligence
Vendors who cannot describe their PACE update cadence in days, or who route every clarification to a sales engineer, often have product maturity gaps under the demo. Likewise, vendors who treat compliance evidence as a PDF the customer assembles by hand are betting that you will never have a tough audit.
AI claims without a clear answer on what data leaves the country, what is logged for billing, and how human review is enforced should not appear in a regulated provider's short list.
How to run a meaningful pilot
Pick one site, one plan management pathway, and one fortnightly claim batch. Use real-but-pseudonymised data — not the vendor's demo participants. Track time spent on claim rework, missed compliance steps, and coordinator satisfaction across two cycles.
A platform that wins the pilot reduces rework and frees coordinator hours for participant-facing work; a platform that loses produces shinier dashboards but the same operational drag.