ndis-outcome-domains

Provisional article — seeded from NbLM. Requires Andrew's research to verify and expand.

Grounding Summary

The eight NDIS Outcome Domains are a fundamental classification framework used by the NDIA to measure goal attainment and the overall performance of the scheme. They represent the final link in the "NDIS Trinity," establishing a direct cost-benefit relationship where a participant's stated goal requires a Support Category that must ultimately result in a specific NDIS Outcome.

Detail

For support coordinators, mastering this framework is essential because the outcome domain is hardcoded into the fourth position of every PACE item code (such as the '8' for Choice and Control in level 2 support coordination: 07_002_0106_8_3). By explicitly connecting a participant's needs to these domains, coordinators provide the NDIA with the "golden thread" of evidence needed to prove exactly how a requested support will practically improve the participant's life.

The concept of outcome domains is embedded directly into the toolkit's Support Coordinator Translation Matrix. This matrix acts as a translation bridge, forcing coordinators to systematically map every raw participant goal and impairment barrier to a specific PACE Support Category and its corresponding NDIS Outcome Domain (1–8) to ensure the resulting budget request is legally robust and funding-ready.

Legislative Basis

Reference Provision Relevance
NDIS Act 2013 s34(1)(a) Goal pursuit Requires that the support will assist the participant to pursue the goals, objectives, and aspirations included in their participant statement.
NDIS Act 2013 s34(1)(b) Social and economic participation Requires that the support will assist the participant to undertake activities that facilitate their social and economic participation.

Open Questions

  • How exactly will the data mapped to these NDIS Outcome Domains be utilized by the new Needs Assessors under the 2026 New Framework and the National Disability Data Asset (NDDA)?
  • Is there any flexibility for coordinators to map a single PACE Support Category to an alternative Outcome Domain based on unique participant circumstances, or are all item codes strictly locked to their default outcome domains by the NDIA payment system?

Entity Tags

  • entity: ndis-outcome-domains
  • type: Concept
  • domain: Framework
  • confidence: Provisional

Change History

Date Change Source
2026-04-20 Provisional article created from primer during ingest of RS-02-T6-operationalizing-support-coordinator-role-2026-04-18.md Auto-generated
2026-04-23 Backlink added — referenced by RS-03 Theme 6 Auto-updated during ingest E-M5