Guide
Behaviour support software in Queensland: keep the approval route visible
In short: For a Queensland behaviour support practice, software should help staff preserve the context of the relevant restrictive-practice approval route. Evaluate how a record distinguishes the practice, setting, responsible decision-maker, decision evidence and review actions. Confirm the applicable pathway through current Queensland guidance; a generic approved label cannot establish that the right authority made the decision.
A Queensland Director comparing software needs more than an expiry-date reminder. If an authorisation record changes hands, the next reviewer should understand which decision it represents and why that decision applies to the recorded situation.
This guide is published by NDPRO, a commercial software provider. Its proposed review method helps assess record organisation. It does not decide which legal approval pathway applies.
Why a single approval field is insufficient
Queensland guidance distinguishes approval routes according to the practice, duration and setting. QCAT's published approval matrix concerns adults with intellectual or cognitive disability and sets out different roles for QCAT, guardians and defined exceptions. It should not be generalised to every NDIS participant.
The Office of the Public Guardian separately explains its restrictive-practice decision roles, including short-term and respite or community-access circumstances. Start with the relevant official guidance and qualified advice for the situation.
The operational implication is straightforward: preserve the basis of the recorded route so another person can review it.
A practical approval-route review
Ask a supplier to demonstrate these questions using synthetic records. This table proposes review information; it is not a claim that NDPRO includes an automated pathway selector.
| Review question | Evidence to locate | Warning sign |
|---|---|---|
| What circumstances were assessed? | Practice, setting and relevant scope recorded by the responsible professional | A state name is the only context |
| Who confirmed the route? | Responsible role and reference to the guidance or advice used | The software silently chooses an authority |
| What was decided? | Decision reference, decision-maker, conditions and applicable dates | Every decision uses an unexplained “approved” label |
| Has the situation changed? | Change description and owner of the required review | An old decision is copied forward automatically |
| Who acts next? | Named owner and a review date | A reminder has no accountable recipient |
Synthetic example: a change of setting
A fictional Queensland team receives notice of a proposed change in the setting where support is delivered. Its existing record contains a decision and an expiry date.
In the demonstration, ask the supplier to preserve that original record while assigning a review of the proposed change. The reviewer should be able to find who confirmed the relevant route, what evidence they considered and what remains unresolved. The system should not imply that the previous decision automatically covers the new circumstances.
Then change the staff member responsible. Can the incoming owner explain the next action from the record alone? This tests evidence continuity without asking software to make a legal determination.
Keep the national workflow alongside the state record
Specialist and implementing-provider duties remain distinct. State decisions do not themselves complete Commission lodgement or reporting. Follow the Commission's current implementing-provider guidance, including its October 2026 portal arrangements, and retain the actual submission or decision references.
Bring a Queensland scenario to an NDPRO walkthrough
NDPRO focuses on behaviour support operational oversight. Ask to inspect the current authorisation record and demonstrate how your team would represent the decision context, responsible owner and follow-up. Confirm any required fields, access boundaries and export contents before relying on them. NDPRO does not select the lawful approval route or obtain authorisation on a provider's behalf.
What can you inspect in an NDPRO walkthrough?
In a 30-minute walkthrough, review a fictional participant pathway with BSP milestones, key dates and the status of later-target requests. Inspect the RP overview's recorded authorisation and expiry fields and follow-up flags. You can also review supervision cadence and session-log screens, individual capability assessment and review status, and the available capability PDF report options.
These views support a discussion about how your practice organises work. Internal target requests do not grant regulatory extensions, and authorisation records do not replace decisions made through the relevant state process. Ask us to demonstrate the exact workflow and output your team needs before relying on it.
Evidence reviewed: 20 October 2026, Director view in an NDPRO test workspace using fictional fixtures. The review covered current screens and controls; it did not test saving records, PDF generation, notification delivery or permissions across roles.
Book a 30-minute Director walkthrough.
Use the software evaluation worksheet and authorisation tracking guide to compare options. For teams crossing jurisdictions, review the distinct NSW panel handoff and Tasmania application handoff.
For the distinction between a current decision and a pending application, read Queensland short-term and ongoing restrictive practice approval.
Official sources checked 20 October 2026. Recheck the current pathway when the circumstances or guidance change.