activity-based-transport

Activity Based Transport

KB Type: Concept
Domain Area: Billing/Practice
Confidence: Provisional — requires Andrew's research to verify
Depth Hint: Standard
Version: 1.0 — 2026-04-25
Status: Provisional


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


Grounding Summary

Community-based practitioner transport in the NDIS is billed using two distinct item codes under Support Category 07. Activity Based Transport (07_501_0106_6_3) covers the direct support time when a practitioner physically accompanies a participant in the community. Provider Travel Non-Labour Costs (07_799_0106_6_3) covers the actual out-of-pocket expenses incurred during that accompaniment — kilometres, tolls, and parking. Both codes apply to Level 1 Support Connection, Level 2 Coordination of Supports, and Psychosocial Recovery Coaching (PRC) under registration group R106. Support Coordinators who also deliver PRC become direct supports, entitling them to both codes when physically accompanying participants. Standard Support Coordination is an indirect support — no community accompaniment, no transport claims. Precise use of both codes is essential: AI-generated pricing estimates are unreliable and must always be verified against the current published NDIS Pricing Arrangements.


Detail

The Distinction Between Direct and Indirect Supports

The fundamental distinction governing Activity Based Transport eligibility is whether a support is classified as direct or indirect. Indirect supports, such as standard Support Coordination, involve the practitioner working on behalf of the participant — making phone calls, reviewing service agreements, liaising with providers — without necessarily being physically present. These indirect activities do not generate claimable travel costs because the practitioner is not accompanying the participant.

Direct supports, by contrast, involve the practitioner working alongside the participant in community settings. Psychosocial Recovery Coaching is explicitly a direct support — the recovery coach attends appointments with the participant, practices social skills in situ, and builds community connections through physical presence. This direct delivery model generates legitimate travel costs that the NDIS recognises and funds through the Activity Based Transport item code.

The Two Transport Item Codes

NDIS transport billing for community accompaniment uses two codes, both under registration group R106 and Support Category 07:

07_501_0106_6_3 — Activity Based Transport (the direct support time):

Bills for the practitioner's time spent accompanying the participant in a community setting. Structure:

  • 07Support Category 07 (Capacity Building)
  • 501 — Sequence number for activity-based transport
  • 0106 — Registration group R106
  • 6Outcome Domain 6 (Social and Community Participation)
  • 3 — Support purpose indicator

07_799_0106_6_3Provider Travel Non-Labour Costs (km, tolls, parking):

Bills for the actual out-of-pocket travel expenses incurred during the accompaniment. Structure:

  • 07 — Support Category 07 (Capacity Building)
  • 799 — Sequence number for non-labour travel costs
  • 0106 — Registration group R106
  • 6 — Outcome Domain 6 (Social and Community Participation)
  • 3 — Support purpose indicator

A common error involves applying Outcome Domain 8 (Choice and Control) instead of Outcome Domain 6 for either code. The variants 07_501_0106_8_3 and 07_799_0106_8_3 do not exist in the current NDIS Support Catalogue and will result in claim rejection.

Implications for Service Agreement Documentation

To ensure compliance and transparent billing, the toolkit's service agreements and schedules of support must explicitly detail Activity Based Transport codes. Participants must genuinely consent to these specific non-labour charges, understanding that they apply only when the practitioner physically accompanies them in community-based direct support activities. Service agreements should distinguish between:

  1. Coordination work (indirect — no transport claims)
  2. PRC community accompaniment (direct — 07_501_0106_6_3 for support time; 07_799_0106_6_3 for km, tolls, and parking)

This documentation creates an auditable chain linking the support type, the item code used, and the participant's informed consent.

Compliance-Approved Use Case — Transporting Anxious Participants

RS-06 research (T3) adds a specific and important practical application. Strategically transitioning a highly anxious participant from a standard Disability Support Worker to a PRC for transportation and appointment support is fully compliant and, the research notes, "a highly effective utilisation of the NDIS Pricing Arrangements." This use case is valid because PRC is officially classified as a direct support (Outcome 6), which authorises ABT claiming for accompanying participants in the community.

This means coordinators who hold both SC and PRC qualifications can legitimately pivot to the PRC role when accompanying anxious participants to appointments — billing 07_501_0106_6_3 for the support time — provided the case notes document the coaching purpose and the participant's genuine consent.

Cross-Category Claiming When Category 07 Is Locked

RS-06 research (T5) introduces a billing scenario that directly affects ABT-adjacent claiming. When a participant's Category 07 budget is fully locked (Stated) and a provider cannot claim the standard non-labour travel code (07_799_0106_6_3), the PAPL 2025-26 V1.1 validates an alternative: 01_799_0106_1_1 from the participant's Core (Category 01) budget.

Note the distinction:

  • 07_799_0106_6_3 — Provider Travel Non-Labour Costs under Category 07 (blocked when Cat 07 is locked)
  • 01_799_0106_1_1 — Provider Travel Non-Labour Costs under Category 01 (bypasses the lock)
  • 07_501_0106_6_3 — Activity Based Transport (separate, for support time accompanying participant — not affected by this bypass)

Outcome Domain as the Structural Eligibility Gate

RS-09 research (T4) clarifies that ABT eligibility is not a billing rule appended to specific roles — it is a structural consequence of which NDIS Outcome Domain governs the support. This reframes the direct/indirect distinction from a descriptor to an architectural driver embedded in item code structure.

Every NDIS item code encodes an Outcome Domain in its fifth segment:

  • 07_501_0106_**6**_3 — Outcome Domain 6 (Social and Community Participation) → direct support → ABT eligible
  • Support Coordination item codes use Outcome Domain 8 (Choice and Control) → indirect support → ABT ineligible

Because Outcome 6 is definitionally community-based — it funds participation in the community — the NDIA treats supports under this domain as direct by nature. A provider delivering Outcome 6 supports is funded to be physically present with the participant. Outcome 8 supports, by contrast, are coordination and system navigation — inherently desk-based activities.

The structural implication is that ABT eligibility cannot be claimed or assumed — it must be read from the item code anatomy. A practitioner wearing both coordination (Outcome 8) and coaching (Outcome 6) hats in a single session cannot split the session to claim ABT for one part and coordination for the other. The billing code chosen for the session determines both the support type and the transport entitlement. Practitioners and billing systems must apply the discipline of billing the correct code for the work delivered — not the most convenient code.

Workflow Evidence and Case Note Documentation

Coordinators taking on PRC roles must properly document when they physically accompany participants in the community versus when they perform indirect administrative tasks. To satisfy auditors that Activity Based Transport was legitimately used for a direct coaching support rather than an indirect coordination task, case notes should explicitly record:

  • The participant was accompanied in community
  • The specific activity undertaken (e.g., attending medical appointment, shopping, social skills practice)
  • The travel incurred (kilometres, tolls, parking)
  • The link to the Recovery Plan goals being addressed

This evidence trail prevents claims from being flagged during payment assurance reviews.


Legislative Basis

Provision Relevance
NDIS Pricing Arrangements and Price Limits Specifies 07_501_0106_6_3 (Activity Based Transport) for community accompaniment support time under registration group R106.
NDIS Pricing Arrangements and Price Limits Specifies 07_799_0106_6_3 (Provider Travel Non-Labour Costs) for km, tolls, and parking during community accompaniment.
NDIS Support Catalogue Defines valid item codes, sequence numbers, and outcome domains — both transport codes use Outcome Domain 6.

Provisional — requires Andrew's research to verify specific pricing and code details.



Open Questions

  • Q-KB-011: How exactly does the newer PACE system handle and validate claims for non-labour travel costs compared to the previous Legacy bulk upload system — 2026-04-25
  • Q-KB-012: What specific workflow evidence or case note documentation must a coordinator provide to satisfy auditors that Activity Based Transport was legitimately used for a direct coaching support rather than an indirect coordination task — 2026-04-25

Entity Tags

entity: activity-based-transport
type: Concept
domain: Billing
confidence: Provisional
links: [[concepts/psychosocial-recovery-coach]] via enables
links: [[concepts/item-code-anatomy]] via references


Change History

Date Change Source
2026-04-25 v1.0 — Provisional article created from NbLM primer RS-05 Phase D
2026-04-25 v1.1 — Corrected transport code conflation: distinguished 07_501 (Activity Based Transport) from 07_799 (Provider Travel Non-Labour Costs); updated Grounding Summary, Item Code Structure, Service Agreement section, and Legislative Basis Q-015 resolution
2026-04-27 E-M5: Backlinks added — topics/prc-direct-support-activity-based-transport, topics/cross-category-provider-travel-costs (RS-06 T3, T5) Sonnet E-M5
2026-04-27 E-M6 enrichment — Anxious participant transport use case and cross-category lock bypass sections added from RS-06 T3 and T5 Sonnet E-M6
2026-05-01 E-M5: Backlinks added — topics/direct-indirect-support-classifications, topics/strategic-travel-cost-claiming (RS-09 T4, T6) Sonnet E-M5
2026-05-01 E-M6 enrichment — Outcome Domain as structural eligibility gate section added: item code anatomy drives ABT entitlement, single-session billing discipline, from RS-09 T4 Sonnet E-M6