stated-supports
Provisional article — seeded from NbLM. Requires Andrew's research to verify and expand.
Grounding Summary
Stated supports restrict the budget to specific categories or item codes within the NDIS PACE system. This contrasts with flexible supports, which allow participants to choose any item code within a funded category.
Detail
Stated supports are an essential risk management tool for coordinators, particularly when specific therapeutic interventions or specialist services must be preserved and not repurposed. The Participant Statement Toolkit includes "Block 3: PACE Budget Architecture Recommendations" where coordinators explicitly outline whether a support category should be Flexible or Stated.
When Stated Supports Are Used
Stated supports are applied as an exception to the flexible-by-default funding rule when there is a documented risk requiring funds to be ring-fenced. Making a support Stated means those funds cannot be spent flexibly — they are restricted to the specific category or item code. This is distinct from a Digital Lock, which restricts funds to a specific provider ABN; a Stated support restricts to a category or item code but does not specify a provider.
How Coordinators Justify a Stated Designation
Coordinators document three elements in the Participant Statement (Block 5) to justify a Stated request:
- Support / Item Code: The exact PACE item code requiring restriction
- Control Requested: "Make Stated" with the applicable category or item code scope
- Risk Rationale: The specific vulnerability justifying the restriction — for example, preventing a participant from redirecting critical therapeutic funding to unrelated support categories
PACE Portal Enforcement and Warning Text
RS-06 research (T2) adds specific operational detail about how PACE enforces Stated designations. In the PACE system (accessed via the MyNDIS provider portal), the Allocated Items table makes Stated restrictions visible and enforceable. The portal explicitly warns users: "Stated supports are intended solely for the purpose of that support" — they cannot be swapped for other supports. This removes the ambiguity that existed in Legacy plans, where a support might be calculated as stated (based on mathematical heuristics) without visual enforcement.
Stated Supports and Registration Group R132
RS-06 research (T4) highlights a common pattern for Level 3 Specialist Support Coordination. Because Level 3 is an intensive specialised support requiring R132 registration, planners almost universally apply a Stated designation to Level 3 allocations within Category 07. This protects the Level 3 budget from being inadvertently depleted by lower-tier supports (Level 2 coordination or PRC) that share the same funding category.
This Stated lock operates in addition to the R132 registration ring-fence — together, they create a two-layer protection: the registration prevents unqualified providers from billing Level 3 at all, while the Stated designation prevents the budget itself from being spent on other supports even by R132-registered providers.
Legislative Basis
| Reference | Provision | Relevance |
|---|---|---|
| NDIS Act 2013 s33(2A)(b) | Support categorisation | Mandates the categorisation of reasonable and necessary supports into one or more groups of supports. |
| NDIS Act 2013 s33(2A)(c) | Funding amounts | Requires specifying a funding component amount for each group of supports. |
Related Articles
- concepts/digital-lock — references
- concepts/flexible-supports — references
- concepts/support-categories — requires
- topics/operationalizing-support-coordinator-role — identified by
- sources/RS-02-T6-operationalizing-support-coordinator-role-2026-04-18.md — source
- topics/2024-ndis-funding-budget-amendments — discussed by
- topics/bridging-legacy-systems-pace-framework — discussed by
- topics/risk-based-budget-controls-exceptions — discussed by
- topics/pace-vs-legacy-plan-flexibility — discussed by (RS-06 T2: PACE portal warning text — "Stated supports are intended solely for that support")
- topics/registration-group-ring-fencing — discussed by (RS-06 T4: Stated designation protecting R132 Level 3 funds from lower-tier depletion)
Open Questions
- How do Stated supports differ operationally from Digital Locks in the MyNDIS portal?
Entity Tags
entity: stated-supportstype: Conceptdomain: Operationalconfidence: 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 | Backlinks added — referenced by RS-03 Themes 2, 6, 7 | Auto-updated during ingest E-M5 |
| 2026-04-23 | E-M6 enrichment — exception-based approach, when/why used, and risk documentation protocol added from RS-03 T7 | Sonnet E-M6 |
| 2026-04-27 | E-M5: Backlinks added — topics/pace-vs-legacy-plan-flexibility, topics/registration-group-ring-fencing (RS-06 T2, T4) | Sonnet E-M5 |
| 2026-04-27 | E-M6 enrichment — PACE portal warning text, R132 two-layer protection mechanism added from RS-06 T2 and T4 | Sonnet E-M6 |