allocated-items

Allocated Items

KB Type: Concept
Domain Area: Operational
Confidence: Provisional — requires Andrew's research to verify
Depth Hint: Standard
Version: 1.0 — 2026-05-01
Status: Provisional


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


Grounding Summary

"Allocated Items" is a mechanism primarily used in Legacy NDIS plans to apply a "digital lock" to specific support item codes, restricting how a participant can spend their funding within a broader support category. If a plan lists no allocated items (e.g., "Allocated Items(0): None"), the funding remains flexible, allowing the participant to choose among eligible item codes within the same registration group. For NDIS support coordinators, identifying whether a plan contains allocated items is critical because it dictates whether a participant has the flexibility to pivot between different levels of support — such as shifting funds between Level 2 Coordination and Psychosocial Recovery Coaching — or if they are strictly confined to a single item code. In the newer PACE system, the function of allocated items has evolved into "Stated" supports and specific planner instructions.


Detail

How Allocated Items Work in Legacy Plans

In the Legacy system, accessible via the MyPlace portal, the "Allocated Items" section appears under each Support Category in a participant's plan. When an NDIA planner explicitly lists a specific item code in this section, they are applying a digital lock that restricts the participant to that exact support. For example, if a plan allocates Category 07 funding and lists item code 07_002_0106_8_3 (Level 2 Coordination of Supports) under Allocated Items with a "Stated" status, the participant cannot use those funds for Level 1 Support Connection or Psychosocial Recovery Coaching, even though all three share the same registration group (R106).

Flexible vs. Stated Allocated Items

The key indicator of flexibility in a Legacy plan is the Allocated Items count. When a plan displays "Allocated Items(0): None," it signals that no digital lock has been applied. The participant retains full flexibility to allocate funds across any eligible item codes within the registration group. Conversely, if the plan shows "Allocated Items(1): Stated" or higher, the participant's choice is restricted to the explicitly listed item codes.

Relationship to PACE System

The PACE system, accessed via MyNDIS, has fundamentally restructured how digital locks are applied. Rather than using an explicit "Allocated Items" table, PACE plans utilise "Specific Planner Instructions" embedded within the "Support Details" section. These instructions serve the same function — governing which item codes are permissible — but the mechanism is more text-based and requires providers to carefully parse the planner's written instructions to determine the plan's flexibility profile.


Legislative Basis

Document Reference Relevance
NDIS Act 2013 Section 33(2A)(b) Requires categorisation of supports into one or more groups
NDIS Act 2013 Section 33(2A)(c) Requires a funding component amount for each group
NDIS Act 2013 Section 33(2)(d) Dictates management of funding for supports

This article is Provisional — derived from NbLM research summary. Requires Andrew's research to verify the legislative connections and operational mechanics.



Open Questions

  1. How exactly does the PACE system validate claims when a planner uses specific limiting terminology (e.g., "Specialist Support Coordination") in the "Support Details" versus when an explicit "Stated" line item is formally applied in the system?
  2. When an older Legacy plan is migrated to PACE without a full reassessment, how does the portal automatically handle historical "Allocated Items" — are they converted directly into "Stated" PACE line items, or do they default to flexible category funding?

Entity Tags

For context graph extraction. Do not edit manually — updated by lint.

  • entity: allocated-items
  • type: Concept
  • domain: Operational
  • confidence: Provisional
  • links: [[concepts/digital-lock]] via related, [[concepts/legacy-crm]] via governs

Change History

Date Change Source
2026-05-01 Initial article created from NbLM primer Ingest — RS-09 Primer