Behaviour support operations

Keep Splose. Make the next action visible.

NDPRO is a clinical operations and oversight platform for NDIS behaviour support practices. It can sit alongside Splose so Directors can review BSP dates, authorisation records, supervision and capability work while their practice keeps its established management system.

Book a 30-minute Director walkthrough →

Prepared 20 October 2026 · NDPRO editorial team

This page is written by NDPRO. It does not imply a partnership with, or endorsement by, Splose.

Start with the decisions your Director needs to make

Which plan milestone needs attention? Who owns the next authorisation follow-up? Which agreed supervision action remains open? Can the next person find the supporting evidence when a practitioner changes?

Evaluate a separate operations tool against these questions. Your existing system may already meet part of the need; identify the remaining gap before adding another record to maintain.

Agree which system owns each record

Practice management: Keep your established calendar, billing and clinical administration arrangements in Splose. Confirm their current configuration with your practice.
Operational oversight: Use the walkthrough to inspect how NDPRO connects dates, responsible people and evidence across the workflows you need to review.
Evidence files: Specify approved storage, document versions and access. A link is useful only if the appropriate reviewer can open it.
External decisions: Authorisation, plan lodgement and reporting remain the relevant provider's responsibilities. An internal status does not establish official acceptance.

What the optional Splose connection means

NDPRO's integration is designed to retrieve supported information from Splose without writing changes back. Setup depends on Splose API access and the clinic's authorised configuration. NDPRO can also be used without a connection.

Supported information in the integration design includes patient, case and appointment information, together with configured intake, incident and service-agreement forms. Confirm the exact fields and enabled form templates for your practice during setup.

Practitioners and invoices are not part of that synchronised scope. Clinical notes and sessions use links rather than a promise to copy all clinical content; appointment information is a separate supported domain. “Retrieval only” describes NDPRO's integration behaviour, not a guarantee that the API credential itself has read-only permissions.

Before connecting, agree the data scope, authorised access, update cadence, failure handling and initial verification. Do not assume that selecting an individual for import limits all earlier roster access. The clinic should understand what information is retrieved before enabling the connection.

A ten-practitioner demonstration

Bring a fictional NSW practice scenario: one plan milestone approaching, one authorisation evidence question unresolved and one supervision action awaiting review. Ask the demonstrator to show the source record, next action, responsible role and closure evidence for each.

Change an operational target and check whether the original due date remains visible.
Open an authorisation reference and distinguish the recorded status from the authority's decision.
Compare a practitioner's view with the Director's and supervisor's access.
Generate an example export and inspect what is included and excluded.
Show how a missing or delayed source update becomes apparent.

This is a synthetic evaluation scenario, not a customer result or a measured time-saving claim. Use the same evaluation worksheet with every product under consideration.

When a separate tool is worth evaluating

A well-maintained spreadsheet or work-management system may be sufficient if the practice can sustain its structure, access controls and review routine. A specialist tool is worth evaluating when the cost of maintaining that process across practitioners becomes material. Compare current demonstrations, setup effort and failure handling instead of counting feature labels.

Splose publishes its own behaviour support practice case study. Review its current capabilities directly; overlapping workflows do not by themselves establish that one system should replace the other.

Explore the underlying workflows

See the fit for your practice

Book a 30-minute Director walkthrough →

Discuss your current systems and the questions you need answered. Ask to see the supported connection and workflows before deciding.