Guide 02 · NDIS platform providers
Do platform providers have to register for the NDIS, and what counts as a platform?
Short answer: The local canon says “From 1 July 2026, all new providers seeking to deliver SIL or operate as an NDIS digital platform will need to be registered.” It also records a transition for providers currently delivering SIL or operating as a platform provider in an unregistered capacity. The provider-specific question is what the platform does, which entity operates it and which supports are involved. Source and access date: NDIS release and Commission Reform pathway, accessed 12 August 2026.
What the local canon says
The official wording recorded in the due-diligence file is:
“From 1 July 2026, all new providers seeking to deliver SIL or operate as an NDIS digital platform will need to be registered.”
Source and date: NDIS, “Crackdown on sales of NDIS businesses as mandatory registration set to expand from 1 July”, published 30 June 2026; accessed 12 August 2026.
The same due-diligence record also preserves this transition wording:
“Providers currently delivering SIL or as a platform provider in an unregistered capacity will not need to be registered as at 1 July 2026, however will need to take action during the transition period to remain in the NDIS market to deliver these services and supports.”
Source and date: NDIS Quality and Safeguards Commission, “Reform pathway - 2026”, accessed 12 August 2026.
Describe the platform before choosing a pathway
A useful scope description is factual rather than promotional. Write down whether the organisation matches participants with providers, hosts records, coordinates workers, manages bookings or delivers supports. Record who employs or contracts the worker, who holds the participant relationship, who invoices, and which entity would be the applicant if registration is required. Note the states and sites involved, the support types and whether SIL is part of the service model.
This description is not a regulator decision. It is a way to stop a broad word from hiding the facts that matter to a registration or audit-preparation discussion. A technology supplier that does not deliver or coordinate NDIS supports may need a different analysis from a platform that actively enables the delivery of supports. The source wording above is the boundary; the provider-specific application is still a question to check.
For an existing unregistered platform provider, the local source records a transition action rather than a universal “registered by 1 July” conclusion. The source also does not let this guide invent an October date for every platform provider. Keep the applicable source, correspondence and internal checkpoint together, and ask which action the current pathway requires for the actual model.
What to do this week
- Map the model: write the entity, platform functions, contracts, worker relationship, participant relationship, supports, sites and registration status.
- Separate roles: mark what the platform does itself, what an independent provider does and what a third party decides. Keep the evidence for each boundary.
- Locate source material: retain the dated NDIS release, Commission pathway material and any provider-specific correspondence. Record what remains unclear.
- Build the evidence index: list the policy index, contracts or role descriptions, worker controls, incident/complaint/risk records and platform-related operating evidence that can be supplied in minimum-necessary form.
Common mistakes
- Assuming every digital tool is a platform provider, or that every platform has the same support scope.
- Applying the SIL-specific 1 October wording to an unregistered platform provider without a source or provider-specific confirmation.
- Describing the business as “just technology” when the operating model also coordinates workers, matches supports or handles participant-facing functions.
When a written readiness view helps
The free scorecard is useful when the platform question sits beside broader readiness questions. It can record the supplied status, scope, policy currency, registers, worker records, handling practice and evidence organisation. It cannot decide what a regulator will accept, and a green or amber signal is not an approval or audit result.
Related: the SIL registration guide and the 1 October checkpoint guide. Regulatory sources accessed 12 August 2026.
Want your platform scope written down before the next decision?
Start the free scorecard and use the written context field to describe the platform functions, entity and supports. The result will show the unresolved scope rather than silently deciding it.