NDIS Practice Standards Mapping Guide for SIL Providers

How to map SIL policies, forms, registers, and implementation evidence to the NDIS Practice Standards.

Published 28 May 2026. Source framework: NDIS Quality and Safeguards Commission guidance, NDIS Practice Standards, and practical provider documentation workflows.

What "mapping" actually means

Mapping is the practice of stating, on each document, exactly which NDIS Practice Standard outcome it satisfies — and being able to show the record that proves it. Auditors work the other way around from how providers think: they start from the Practice Standard outcomes and ask "where does this provider address Outcome 2.4?" If your incident policy doesn't say it addresses Outcome 2.4, the auditor has to hunt, and hunting auditors find gaps. Mapping turns a pile of documents into an audit-navigable system.

The Core Module outcomes you map against

Most SIL documents map to the four divisions of the NDIS Practice Standards Core Module: Rights and Responsibilities, Provider Governance and Operational Management, Provision of Supports, and the Support Provision Environment. Each policy, form, and register should carry a header line naming the specific outcome it covers — for example, "This policy addresses NDIS Practice Standards Core Module Outcome 2.4 — Incident Management."

The new SIL module changes the map in 2026

From 1 July 2026, SIL providers are also assessed against the new supplementary SIL module, built around four outcomes: Supported Decision-Making, Safety, Workforce Competence and Consistency, and Housing and Support Security. Your mapping table now needs a second column for these SIL-specific outcomes. Our four-outcome explainer sets out what evidence each one expects, and the registration group 0138 explainer covers why the SIL module now applies to you.

Policy without a register fails the map

The mapping exercise exposes gaps you can't see in a document list. A risk policy with no live risk register maps to nothing an auditor can sample. A complaints policy with no complaints register and response records is half a map. A training policy with no training matrix is incomplete. Mapping forces the policy + form + register triad into the open for every outcome.

Build the mapping table

The practical artefact is a single table — outcome down one axis, your documents across the other — with a cell for the policy, the form/register, and the participant- or worker-file evidence that proves it. Fill it in honestly and the empty cells are your work list, ordered by risk. An auditor handed this table can verify your coverage in minutes instead of reconstructing it from scratch, which reads as competence.

Worked example: Outcome 2.4 Incident Management

Policy: your incident management policy citing Outcome 2.4. Form: the incident report form. Register: the incident register, current, showing incidents logged, reviewed, and notified to the Commission where required. File evidence: a closed incident with a documented review and corrective action. Four pieces, one outcome, one row of the map — that is what "mapped" looks like in practice.

Keep the map current

Mapping is not a one-off. When the Commission updates the Practice Standards — as it is doing for SIL before 1 July 2026 — update the affected rows, re-check the indicator wording against the final module, and record the change in your document-control table. Keep superseded versions in a controlled archive rather than silently overwriting, so the map shows a maintained system, not a frozen snapshot.