digital-lock

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

Flexible supports allow participants to choose any item code within a funded category, while Stated supports restrict the budget to specific categories or item codes. A Digital Lock is an additional mechanism within the PACE system that ring-fences funds to a single, specific line item — such as Specialist Support Coordination or Occupational Therapy — preventing the money from being repurposed.

These concepts are crucial for NDIS support coordinators because they provide the primary architectural tools to proactively manage participant risk. By recommending whether a category should be flexible or digitally locked, coordinators can safeguard vulnerable participants from financial exploitation, provider over-servicing, and ensure that critical therapeutic interventions are preserved. These concepts form the foundational structure of "Block 3: PACE Budget Architecture Recommendations" within the Participant Statement Toolkit.

Under the NDIS Act, funding within the Core and Capacity Building categories is designed to be flexible by default. Participants generally have the freedom to allocate funds across various supports without rigid restrictions, unless specific safety or financial risks are identified. Digital Locks are the exception to this rule — applied only when there is a documented risk that requires a specific item code to be ring-fenced to a specific provider's ABN.

Earlier template models forced coordinators to tabulate every support line item for its digital lock or stated status — an exhaustive ledger approach identified as administrative overkill. The exception-based approach simplifies this: coordinators leave flexible things alone and only complete the budget controls section when a high-risk exception requires a Stated designation or Digital Lock. This means practitioners only do the heavy lifting in the budget section when a participant's safety genuinely requires it.

To recommend a Digital Lock in the Participant Statement (Block 5), coordinators must document three elements for the NDIA planner:

Providers have historically used a heuristic to infer whether a participant's Category 07 budget is digitally locked to a specific support: checking whether the budget total is an exact mathematical multiple of a known hourly rate. If the budget divides cleanly, the logic suggests it was constructed with a specific line item in mind. RS-05 research (T6) confirms this heuristic is fragile and should not be relied upon. NDIA planners routinely include small buffers for activity-based transport or partial hours in the budget, which breaks the clean multiple without changing the underlying intent. This produces false negatives — a locked budget that doesn't resolve to a clean multiple — leading providers to attempt claims that will be rejected.

PACE replaces this heuristic. Under the PACE system, providers can reference the explicit "Support Detail" section of the participant's plan, which specifies which line items are approved. This makes the mathematical heuristic redundant. Providers are advised to empirically test PACE claim validation behaviour through a controlled claim attempt rather than inferring it from the budget total. The "exact multiple" check remains relevant only for Legacy (MyPlace) plans where the Support Detail section does not exist.

RS-07 research introduces the Participant Risk Profile as the formal input that drives digital lock recommendations. Practitioners can no longer merely submit support lists — they must actively assess a participant's vulnerability profile and make explicit, evidence-based recommendations to the NDIA planner about which specific supports require ring-fencing.

The granularity of digital locks in PACE is significant: a lock can be applied to an entire Support Category or drilled down to a specific line item. A line-item lock on Specialist Support Coordination (R132) ensures that critical, specialised funds cannot be absorbed into general capacity building. A category-level lock on Category 07 ring-fences coordination funding from other uses. Practitioners should match the lock granularity to the specific risk identified — broader category locks for general exploitation vulnerability, specific line-item locks for critical therapeutic interventions that must be preserved.

RS-09 research (T1, T3) provides the portal-level anatomy of how PACE actually implements digital locks, adding operational depth beyond the RS-06 findings about the Allocated Items table.

In PACE plans, the primary lock mechanism is the Specific Planner Instructions text embedded in the "Support Details" section — not the Allocated Items table itself. The instructions follow a two-part pattern: generic boilerplate followed by a unique participant-specific sentence. That second sentence is the operative lock. Providers must parse it to determine which item codes are permissible:

The Allocated Items table surfaces the result (Stated vs. Flexible labels), but the Specific Planner Instructions are the cause. Understanding the textual mechanism — not just the portal warning — is essential for providers who need to reason about edge cases before making a claim attempt.

The natural R132 lock adds a third dimension: Level 3 Specialist Support Coordination carries a structural digital lock by virtue of its R132 registration requirement. Even without a formal "Stated" designation, providers who do not hold R132 cannot bill Level 3 regardless of budget availability. When a planner does formally state Level 3, they are layering an explicit budget lock on top of the pre-existing registration lock.

RS-06 research (T2) adds important operational detail about how PACE enforces locks. PACE plans feature a prominent "Allocated Items" table that explicitly categorises each support as stated or flexible. When a support is listed with a "Stated" status, the PACE portal displays an explicit warning: "Stated supports are intended solely for the purpose of that support" — they cannot be swapped for other supports.

When a digital lock is applied at the item-code level — for example, if 100% of a Category 07 budget is allocated exclusively to Level 2 Coordination (07_002_0106_8_3) — the portal ring-fences those funds to that specific code. Attempts to claim other items within the same category, including the standard non-labour travel code (07_799_0106_6_3), will be rejected with "Insufficient Funds" or "Support Not in Plan" errors because the portal sees $0 flexible budget available for those items.

RS-06 research (T5) identifies a compliance-approved workaround for providers facing locked Category 07 budgets who still need to claim non-labour travel costs. The NDIS Pricing Arrangements and Price Limits 2025-26 V1.1 explicitly validates item code 01_799_0106_1_1 — a Category 01 (Core) code under Registration Group R106. Because this code draws from the participant's Core budget rather than Capacity Building, it bypasses the Category 07 lock entirely.

To use this workaround: