NDIS SIL Registration Documentation: Everything You Actually Need to Submit

Regulatory detail current as at September 2026. Sources: NDIS Practice Standards and Quality Indicators (Version 4, November 2021); National Disability Insurance Scheme (Quality Indicators for NDIS Practice Standards) Amendment (Supported Independent Living) Guidelines 2026; National Disability Insurance Scheme (Incident Management and Reportable Incidents) Rules 2018; National Disability Insurance Scheme (Complaints Management and Resolution) Rules 2018; NDIS Quality and Safeguards Commission registration application guidance.

There are two documentation lists in NDIS SIL registration. The official one, which tells you what standards apply. And the practical one, which is what an approved quality auditor actually opens, reads and tests against your service.

They are not the same length, and the gap between them is where small operators lose weeks.

This post covers both. What each item is, what it is for, and what auditors specifically examine. It is the more technical of our two registration guides. If you want the process end-to-end first, start with How to Register as an NDIS SIL Provider Before 1 October 2026.

Why documentation is the primary registration bottleneck

Most unregistered SIL operators are not running an unsafe service. They are running a service whose quality lives in the heads of three or four people who have been doing it for years.

That works operationally. It fails at audit, for a specific reason: supported independent living sits on the certification pathway. Certification is not a document check. It is a two-stage process in which an auditor reads what you have written and then goes looking for whether it is true: in your records, in your rosters, in conversations with your workers and, with their consent, your participants.

So the bottleneck is not writing. It is the distance between what you do and what you can show.

Three consequences follow.

Templated documentation often fails. Not because templates are prohibited (they are not), but because a template describes a generic service. If your policy says incidents are reviewed at a monthly management meeting and you do not hold a monthly management meeting, the template has created a non-conformity in an area you were previously fine.

Depth is not the goal; accuracy is. A short policy that describes your actual practice, supported by records, outperforms a forty-page manual that describes somebody else's.

The evidence usually already exists. Shift notes, rosters, text messages, signed agreements, the incident form you filled in. Most preparation is finding and organising that material, not manufacturing it.

Practice Standards documentation (the foundation)

Two modules apply to every SIL provider. Others apply depending on what you deliver.

The Core Module

The Core Module has four parts. The table below maps each to the documentation an auditor will expect.

Within governance, these are the systems that get tested hardest:

• Risk management — a documented system proportionate to your size and scale, covering incident management, complaints, financial management, governance, human resources, information management, work health and safety, and emergency and disaster management. It must include infection prevention and outbreak control where relevant, and you must hold professional indemnity, public liability and accident insurance.
• Quality management — a system that defines how you meet legislation and the standards, is reviewed and updated, and includes a documented program of internal audits proportionate to your scale. The internal audit program is frequently written and never run. Auditors check.
• Information management — participant consent to collect, use, retain and disclose information, including what happens without consent where required by law; how participants access and correct their information; storage, security, retention and disposal.
• Continuity of supports — how you cover worker absence with a suitably qualified person, and arrangements to deliver support without interruption through the service agreement period.
• Emergency and disaster management — plans developed by the governing body in consultation with participants and their support networks, tested and adjusted, reviewed periodically, communicated to workers and participants, with each worker trained in them.

The supported independent living module

The supported independent living module commenced on 1 July 2026 under the National Disability Insurance Scheme (Quality Indicators for NDIS Practice Standards) Amendment (Supported Independent Living) Guidelines 2026, which inserts a new module covering four outcomes.

( confirm the exact outcome and indicator wording against the published module before finalising documentation built to it.]

Where you deliver SIL in a specialist disability accommodation dwelling, the Core Module's service agreements standard also requires documented arrangements between you, the participant and the SDA provider, setting out who is responsible for how concerns about the dwelling are addressed, how conflicts involving participants are managed, how changes to circumstances or support needs are agreed and communicated, how vacancies in shared living are filled with each participant's needs taken into account, and how behaviours that may put a tenancy at risk are managed.

Supplementary modules

Add these where they apply:

• High Intensity Daily Personal Activities Module — complex bowel care, enteral feeding, severe dysphagia, tracheostomy, urinary catheter, ventilator, subcutaneous injections, complex wound management. Each requires a participant-specific plan, policies including a worker training plan, and training delivered by an appropriately qualified health practitioner or a person meeting the relevant high intensity support skills descriptor.
• Implementing Behaviour Support Plans Module — where regulated restrictive practices are used in your service. This is common in SIL and frequently overlooked.

Evidence-of-practice — the audit-day differentiator

Ask an experienced auditor what separates a clean certification audit from a difficult one and the answer is rarely the policy manual. It is whether the provider can show the practice.

What evidence-of-practice means

Policy documentation states an intention. Evidence-of-practice is the artefact created when the intention was carried out: the completed form, the signed plan, the dated note, the roster showing who was on shift, the record of the conversation.

Auditors weight it more heavily for a plain reason. Policies can be obtained and copied. Records are produced only by doing the work.

How to build evidence for practice you already deliver

Most small SIL operators already meet a large share of the Core Module. The work is making it visible. Three steps:

1. List what you already produce. Rosters. Shift notes. Handover records. Incident forms. Complaint emails. Signed service agreements. Training certificates. Text message threads with participants' families. Meeting notes, even informal ones.

2. Map each artefact to the standards it evidences. One artefact usually covers several. A shift note with a participant's decision recorded in it can evidence person-centred supports, supported decision-making and responsive support provision at once.

3. Fix the consistency, not the volume. Auditors sample. If they take four months of incident records and two have no outcome recorded, the finding is about your system, not those two forms. Consistency across a sample beats depth in one file.

What evidence-of-practice looks like in a SIL service

The pattern is consistent: strong evidence has a date, a name, and an outcome.

---

If building this evidence framework from scratch is more than you can take on alongside running the service, that is the problem Splana Groundwork was built for. It produces documentation and an evidence framework based on how your operation actually runs, rather than generic templates you then have to make true. Splana Groundwork is a tool for building and maintaining audit-ready documentation. It supports your compliance work but does not replace human review — all documentation should be reviewed by a qualified compliance professional before submission.

Join the Splana Groundwork waitlist

---

The worker screening register

Every worker in a risk-assessed role must hold a valid NDIS Worker Screening clearance, verified through the NDIS Worker Screening Database. In a SIL service, that is effectively everyone delivering direct support, and often more.

A register that survives audit records, for each worker:

• Full name and role
• The risk assessment for that role, and why it was assessed that way
• Clearance number and status
• Expiry date
• The date you verified it against the database, and who verified it

Common gaps:

• Workers who applied for a clearance and started before it was granted
• Clearances that expired while the worker kept working
• New starters added to the roster but not the register
• No record of when verification happened, only that it did
• Contractors and agency staff treated as outside the register

Ongoing maintenance: diarise expiries at least three months ahead, re-verify on a set cycle rather than on memory, and reconcile the register against your roster monthly. The reconciliation is the control that catches everything else. The Core Module also requires you to keep each worker's contact details and details of any secondary employment current.

Incident management documentation

Your incident management system must meet the requirements of the National Disability Insurance Scheme (Incident Management and Reportable Incidents) Rules 2018, and the Core Module adds requirements around participant information, worker training and continuous improvement.

The full chain

Auditors test the chain end to end, not the first link:

1. Report — what happened, when, who was involved, who recorded it and when
2. Immediate response — what was done for the participant, including medical attention where relevant
3. Notification — where the incident is reportable, notification to the Commission in the required manner and timeframe
4. Investigation — proportionate to the incident, with findings recorded
5. Outcome — what was decided, and what the participant was told
6. Review and improvement — what changed in practice, policy or training as a result

Registers that stop at step one are the most common incident finding we see, and the easiest to fix before an audit.

Documentation for incidents that have not happened

You also need the procedural layer: the system document itself, the participant-facing information about how incidents involving them are managed, worker training records showing staff are trained in and comply with the procedure, and evidence of regular review of the policy.

How auditors test it

By asking a support worker what they would do. If your procedure says one thing and your worker says another, the finding is against the system, not the worker. Train to the document you actually hold, and keep the document short enough that people remember it.

Additional documentation that's frequently overlooked

Restrictive practices. If any regulated restrictive practice is used in your service — including practices providers do not always recognise as restrictive, such as locked doors, environmental restrictions or routine PRN medication for behaviour — you need behaviour support plan arrangements, authorisation consistent with your state or territory requirements, worker training in safe use, and monthly reporting to the Commission under the National Disability Insurance Scheme (Restrictive Practices and Behaviour Support) Rules 2018.

Staff training records. Not just certificates: a system that identifies, plans, facilitates, records and evaluates training, including what your own policy calls mandatory. The most common finding is a mismatch between the training your policy requires and the training your records show.

Quality management system documentation. Specifically the internal audit program. Writing that you conduct internal audits and never conducting one is a self-inflicted non-conformity.

Complaints handling records. Including the complaints you resolved informally. A complaints register with no entries reads as a system nobody uses, not a service nobody complains about. You also need evidence that participants were told how to complain, including avenues external to you, and that workers are trained in the procedure.

Emergency and disaster management. The plans, the consultation with participants and their support networks, the testing, the review points, and worker training in implementing them.

Mealtime management. Where any participant requires it, assessment by appropriately qualified health practitioners, a mealtime management plan reviewed at least annually, worker training, and plans accessible where meals are prepared.

How to organise documentation for the application

What goes in the application: entity and key personnel details, suitability declarations, the registration groups you are seeking, and your self-assessment against each applicable standard with supporting evidence noted. You have 60 days to complete an application once you start it, after which it is deleted.

What is held for the audit: everything else. On submission you receive an initial scope of audit document setting out what will be examined.

Structure it so an auditor can find things. A workable arrangement:

1. One folder per module, subfoldered by standard
2. Inside each, the policy first, then the evidence, named with dates
3. A single index that maps each standard to where its evidence sits
4. A separate participant folder structure, consistent across every participant

The index is worth the hour it takes. Auditors form a view of your systems from how quickly you can produce a document.

Version control. Every document should carry a version number, an approval date and a review date. When your operation changes, whether a new site, a new participant with different needs or a staff structure change, update the documentation in the same week, not at the next audit. Documentation describing a service you no longer run is a finding even where the current service is compliant.

Frequently asked questions

What documents do I actually submit with the NDIS registration application? Entity and key personnel details, suitability declarations, your chosen registration groups, and a self-assessment against the applicable Practice Standards with supporting evidence noted. The bulk of your documentation is examined at audit.

Which NDIS Practice Standards apply to SIL providers? The Core Module and the supported independent living module that commenced on 1 July 2026, plus any supplementary module matching the supports you deliver — for example High Intensity Daily Personal Activities, or Implementing Behaviour Support Plans where regulated restrictive practices are used.

Can I use templated policies? Yes, but they must be made accurate for your service before audit. Certification tests whether practice matches the document, so an unedited template creates risk rather than removing it.

What is evidence-of-practice? The record produced when you carried out what your policy describes — a dated, named artefact with an outcome. Auditors weight it more heavily than policy documentation.

How far back do records need to go? Far enough for an auditor to sample a pattern. If your service has been running for years, expect a sample across recent months rather than a single example.

---

Not ready to join a waitlist?

If you would rather score your current position before making any decision, the free 8-minute Registration Readiness Diagnostic shows exactly where you sit on the eight most-tested audit criteria.

Take the free Registration Readiness Diagnostic

---

Join the Splana Groundwork waitlist

Splana works with small NDIS providers on registration and compliance. We publish this level of detail because the documentation question is the one operators ask us first and the one the official guidance answers least usefully. If this post saves you a fortnight of guessing, it has done its job.

Related reading: What Documents Do You Need to Register as an NDIS SIL Provider? The Practical Checklist · 1 October 2026: What Unregistered SIL Providers Need to Do Right Now

Sources and further reading

Regulatory detail current as at September 2026. Verify against the primary sources below before relying on it.

• NDIS Quality and Safeguards Commission — Mandatory registration (Reform Hub) — commencement of mandatory registration for SIL and digital platform providers, and the new classes of support 0138 and 0137.
• NDIS Commission — SIL transition pathways (SIL-1 to SIL-6) — which pathway applies to your situation and the 1 October 2026 application date.
• National Disability Insurance Scheme (Quality Indicators for NDIS Practice Standards) Amendment (Supported Independent Living) Guidelines 2026 (F2026N00443) — the supported independent living module (Part 8A / Module 5A, ss 72B–72E).
• NDIS Commission — Apply for registration — PRODA and Applications Portal mechanics, self-assessment, suitability, auditor engagement and the 60-day completion limit.
• NDIS (Incident Management and Reportable Incidents) Rules 2018 and NDIS (Complaints Management and Resolution) Rules 2018.
• ndis.gov.au news — what happens to participants whose provider does not register.

Audit fees and Commission processing timeframes are not published; obtain more than one auditor quote. For the wider registration process beyond SIL, see our pillar guide, How to become a registered NDIS provider. To gauge where you stand, take the Registration Readiness Diagnostic, or see Splana's registration services.