specific-planner-instructions
Specific Planner Instructions
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
In the NDIS PACE system, "Specific Planner Instructions" are operative notes entered by NDIA planners within a plan's Support Details section. Following a generic boilerplate description, these unique, participant-specific instructions dictate exactly which item codes or support levels (such as Level 2 Support Coordination versus Level 3 Specialist Support Coordination) a participant is authorised to use. This concept matters immensely to NDIS support coordinators because it functions as the PACE equivalent of Legacy "Allocated Items," establishing the digital locks that govern funding flexibility. Understanding these instructions is crucial for coordinators to correctly structure service agreements, manage sub-budgets, and ensure billing claims align with the planner's exact restrictions.
Detail
The Structure of Specific Planner Instructions
In the PACE system, each Support Category in a participant's plan includes a "Support Details" section. Within this section, planners enter text that typically follows a two-part structure:
- Boilerplate text: Generic language describing the support category's purpose and scope (e.g., "This funding is for Support Coordination to help you navigate the NDIS system")
- Specific instruction: A unique sentence or phrase that establishes the rules for that particular participant's funding
It is the second part — the specific instruction — that determines the plan's flexibility profile. Providers must carefully parse this text to identify which item codes are explicitly authorised.
Decoding the Specific Instruction
The language used in the specific instruction section is the key to understanding a PACE plan's constraints. Common patterns include:
- Broad language (e.g., "Support Coordination"): Indicates default R106 flexibility, permitting Level 1, Level 2, and Psychosocial Recovery Coaching
- Explicit specialist reference (e.g., "Specialist Support Coordination"): Opens registration group R132, permitting Level 3 supports
- Dual reference (e.g., "Support Coordination and Specialist Support Coordination"): Creates a Configuration C dual-budget scenario with both Level 2 and Level 3 authorised
The presence or absence of specific terminology directly maps to which registration groups and item codes are accessible under the plan.
Relationship to Digital Locks
Specific Planner Instructions function as the primary mechanism for applying digital locks in the PACE system. Unlike the Legacy system's explicit "Allocated Items" table, PACE relies on this text-based approach. When a planner writes restrictive language into the Support Details, they are effectively ring-fencing the funds to specific support types. The PACE portal will reject claims for item codes that fall outside the planner's stated instructions, enforcing the digital lock at the billing level.
Implications for Service Agreements
Because Specific Planner Instructions govern the legal boundaries of what can be billed, providers must ensure their Service Agreements accurately reflect these constraints. A service agreement that promises supports not authorised by the planner's instructions creates a compliance risk. Providers should:
- Document the exact wording of the Specific Planner Instructions
- Map the instructions to the permissible item codes
- Ensure service delivery aligns with these mapped codes
- Update service agreements if the plan is reassessed and instructions change
Legislative Basis
| Document | Reference | Relevance |
|---|---|---|
| NDIS Act 2013 | Section 33(2)(b) | Requires statement of participant supports to detail reasonable and necessary supports |
| NDIS Act 2013 | Section 33(2A)(b) | Details categorisation of funded supports into groups |
This article is Provisional — derived from NbLM research summary. Requires Andrew's research to verify the legislative connections and operational mechanics.
Related Articles
- concepts/digital-lock — digital lock mechanism concept
- concepts/allocated-items — Legacy system equivalent
- concepts/my-ndis-portal — PACE portal where instructions appear
- concepts/registration-group-r106 — R106 registration group
- concepts/registration-group-r132 — R132 specialist registration
- concepts/dual-budget-scenario — Configuration C dual-budget plans
- concepts/ndis-service-agreements — Service agreement alignment requirements
- topics/legacy-pace-plan-flexibility — RS-09 T1 on plan flexibility
- topics/digital-lock-mechanism — RS-09 T3 on digital lock anatomy
Open Questions
- Do specific planner instructions ever explicitly mandate "Psychosocial Recovery Coaching" or "Level 1 Support Connection," or do these consistently default to being available whenever the general R106 registration group is funded without a strict Level 3 restriction?
- How empirically rigid is the PACE claim validation logic if a provider attempts to bill for Psychosocial Recovery Coaching against a specific planner instruction that only explicitly mentions "Coordination of Supports"?
Entity Tags
For context graph extraction. Do not edit manually — updated by lint.
entity: specific-planner-instructionstype: Conceptdomain: Operationalconfidence: Provisionallinks: [[concepts/digital-lock]] via related, [[concepts/allocated-items]] via equivalent
Change History
| Date | Change | Source |
|---|---|---|
| 2026-05-01 | Initial article created from NbLM primer | Ingest — RS-09 Primer |