Guide
Behaviour support software in NSW: make the RPA handoff reviewable
In short: For a NSW behaviour support practice, software evaluation should include how the team coordinates evidence around the state's restrictive practices authorisation process. Ask to trace a plan version, the responsible implementing provider, panel preparation, decision conditions and follow-up. An internal status must remain distinguishable from a decision recorded through the official process.
A NSW Director choosing software needs to see what happens when a practitioner has finished their part but the next person has not. The useful question is whether another team member can identify the outstanding action, its owner and the evidence needed to close it.
NDPRO publishes this guide as a commercial software provider. The review method below is our proposed operational checklist, not a government form or a determination of authorisation requirements.
What is specific to NSW?
NSW DCJ provides an RPA system and independent specialists for panels convened by registered providers. Its guidance separates implementing-provider responsibilities for consent and an appropriate authorisation mechanism from practitioner responsibilities for relevant plan lodgement. See DCJ's roles and responsibilities.
The official RPA user guides cover application, panel assignment, decisions and implementation reviews. Use those instructions for official actions. A product dashboard is a separate oversight record.
A Director's panel-handoff review
Use this proposed checklist to test a supplier with synthetic information. The evidence may live in different approved systems; the review should make its location and responsible owner clear.
| Review point | Ask to see | Follow-up when missing |
|---|---|---|
| Current plan | The version being considered and the practitioner responsible | Resolve which version the panel will receive |
| Consent and application preparation | Responsible implementing-provider contact and evidence location | Assign the outstanding evidence request |
| Panel arrangements | Who is coordinating the panel and the next confirmed step | Record the owner and review date |
| Decision | Actual decision reference, conditions and relevant dates | Keep the record awaiting verification |
| Subsequent change | The proposed change and who will check its effect on the existing decision | Preserve the prior decision's context |
These are evaluation questions, not a statement that every field or official-system integration exists in NDPRO.
Synthetic example: a plan changes before the panel
A fictional NSW practice updates a plan after its first evidence handoff. The clinical lead is away. A useful oversight record lets the replacement reviewer find the revised version, identify who needs it and determine whether the panel coordinator has acknowledged the change.
Test the workflow by leaving the acknowledgement missing. Can the reviewer identify the gap without marking the application approved? Then provide a fictional decision with a condition. Can the next owner explain the condition and its follow-up without relying on the departing practitioner's memory?
Score the demonstration on traceability and ownership. A colourful status is insufficient evidence that an external decision was made.
Keep state decisions and Commission actions distinct
State authorisation, plan lodgement and federal reporting are separate actions. The Commission's implementing-provider guidance describes the two-portal reporting arrangements from 12 October 2026. Retain the plan's lodgement context and follow the applicable official instructions.
Evaluate NDPRO with your NSW workflow
NDPRO focuses on operational oversight for behaviour support practices. Bring the synthetic handoff above to a walkthrough and ask to see current authorisation records, responsibility tracking and evidence access. Confirm the available fields and permissions against your team's needs. NDPRO does not grant state authorisation or replace the official RPA process.
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.
For a broader evaluation, use the software comparison worksheet, authorisation tracking guide and Splose companion explanation. Practices spanning states can also review the Queensland and Tasmania handoffs.
For the approaching-expiry scenario, read NSW RPA review or new submission.
Official sources checked 20 October 2026. Confirm current requirements for the particular practice, person and setting.