Use this guide as a decision sequence.
Check the linked primary sources for your current circumstances. Record decisions, owners and evidence rather than treating general information as legal, clinical or employment advice.
1. Define what you will actually deliver
Write down the supports you intend to provide, who you will serve, where services happen and what your team is qualified to do. Map each proposed service to the current registration groups and pricing arrangements before building marketing pages or hiring widely.
Keep exclusions visible. A clear decision not to provide a clinical, high-intensity or restrictive-practice-related activity is as useful as a decision to provide it. Your policies, insurance, worker competencies and participant records should all reflect the same scope.
- List each service and delivery setting.
- Identify participant funding types you expect to accept.
- Map qualifications, insurance and specialist authority needed for each service.
- Record services that remain out of scope until a later review.
2. Make the registration decision deliberately
Registration requirements depend on the support, participant funding management and provider circumstances. For example, current NDIA guidance says Support Coordinators working with NDIA-managed participants need to be registered, while self-managed and plan-managed participants can use registered or unregistered Support Coordinators.
Do not use one person’s business model as proof of your own pathway. Record the source checked, decision date, registration groups, audit pathway and who will revisit the decision if your services change.
3. Build the minimum operating system before intake
A policy folder alone is not an operating system. Connect each policy to the form, register, responsible person and review trigger that makes it real. At minimum, establish participant rights, privacy and records, complaints, incidents and safeguarding, risk, continuity, service access and exit, document control and improvement workflows.
Use the instructions inside each template to establish the approved workflow. Test it with invented information before use, then keep training records separate from genuine participant records. You do not need a separate example file for every template.
- Assign an owner and review date to every controlled document.
- Test a referral from first contact through acceptance or decline.
- Test an incident, complaint and emergency scenario before service starts.
- Confirm where records live and who may access them.
4. Prepare the first participant pathway
Your first participant workflow should cover referral, capacity, consent, information sharing, funding confirmation, service agreement decisions, support planning, risk, emergency arrangements, notes, billing evidence, reviews, transitions and exit. Use service-specific documents where the responsibilities and risks differ.
A written service agreement is widely recommended but not universally mandatory under the NDIS. The NDIA identifies Specialist Disability Accommodation as the clear case where a written agreement is required. Regardless of format, both sides need a shared understanding of what will be delivered and how issues will be handled.
5. Run a readiness check, then improve from real evidence
Walk through the full service as if you were a participant, worker and reviewer. Check that decisions can be explained, records can be found, urgent issues reach the right person and incomplete actions remain visible. After launch, use complaints, incidents, feedback, supervision and file checks to improve the system rather than adding documents for appearance alone.