● NDPRO Operations ● For behaviour support providers

Keeping practices audit-ready and their practitioners growing.

Two things every behaviour support practice has to get right. NDPRO does both β€” from the same day's work, without anyone typing it twice.

Built for behaviour support teamsΒ·Connects with your Splose accountΒ·Your data stays in AustraliaΒ·Works anywhere in AustraliaΒ·Built for behaviour support teamsΒ·Connects with your Splose accountΒ·Your data stays in AustraliaΒ·Works anywhere in AustraliaΒ·
01 β€” Audit readiness

When the auditor calls, the evidence is already there.

Not a folder someone builds in a panic the week before. Each participant's file builds as your team works β€” referral, pathway, restrictive practice, evidence. The practice-level registers behind it build the same way: policies, incidents, worker credentials.

Where it starts
01

Referrals that don't sit waiting

Eight clear steps from a referral arriving to a pathway starting. Funding figures are read off the referral letter and badged for you to confirm β€” you check a figure instead of typing one, and nothing is accepted silently. Every step is stamped with who did it and when.

You always know where every new participant is, and who owns the next move.

Open referrals
5
Practitioner assignedStep 3 of 8
Waiting longest3 days
From the referral letter
Plan datesread from letter
Fundingread from letter
Capacity buildingread from letter
Plan manageryou type it
02

Every participant on the same clear journey

Interim plan, comprehensive plan, review β€” the dates work themselves out from the engagement date, so nobody is holding a deadline in their head.

No more finding out a plan was overdue after it was overdue.

Interim BSP due
7 days
Comprehensive BSP+6 months
Next review+12 months
Where this participant is
Assessment completeDone
Interim planIn progress
Comprehensive planNot started
03

Restrictive practices, tracked properly

One register holds every practice: who authorised it, the day it expires, and whether everyone delivering the plan has been trained on the current version. Change a plan and the retraining tasks appear on their own.

Your obligation stays yours. Remembering it doesn't have to be.

Authorisation expires in
21 days
Renewal startedNot yet
Trained on the current plan
Day programStill on v2
Support teamv3
Schoolv3
04

One board for what needs you today

Pathway risk, restrictive practices, credentials and insurance, and the plan and authorisation horizon β€” the Operational Risk board, counted as today's priorities, the next 14 days, and beyond. It rebuilds every time you open it, so there is nothing to generate and nothing to refresh.

Nothing here can be dismissed. An item clears when the thing itself is fixed.

Today's priorities
3
Within 14 days7
Beyond 14 days12
On the board right now
RP / State AuthorisationAwaiting panel
Credentials & InsuranceExpiring
Behaviour Plan dueIn progress
The payoff
05

Hand the auditor a finished file

The Audit Readiness Review shows how ready every participant's file is β€” worst gaps first. One click builds the workforce audit pack: every active worker, contractor or employee, with their NDIS Worker Screening Check, insurance and qualifications, plus the evidence documents themselves, in a single PDF you read before anyone else does.

Audit week stops being a fire drill. You're reviewing, not assembling.

Participant files ready
86%
Missing evidence2 files
Needs a decision3 files
Workforce audit pack
Every active workerIncluded
Evidence filesAttached
Time to produceOne click
02 β€” Practitioner capability

A team that gets better, and can prove it.

Capability, supervision, CPD and your own way of working β€” kept as a live record, not as a spreadsheet someone updates once a year. The same record answers your auditor and shows your practitioners how far they've come.

06

PBS capability, on the record

Your capability framework as a living register. Practitioners assess themselves; a supervisor confirms it. The system keeps those two things apart on purpose, so a confirmed skill means a confirmed skill.

You can answer "who on my team can do this?" without guessing β€” and show who confirmed it.

Confirmed this quarter
6
Functional assessment Β· T.L.Confirmed
PBS planning Β· R.P.Awaiting supervisor
Where the team sits
Proficient or above7 of 11
Developing3
Not yet demonstrated1
07

Nobody quietly drops off the supervision list

Every session recorded with the cases discussed, and a list that sorts by who has waited longest. A practitioner sees that a session happened and what was covered β€” the supervisor's own note is not part of that view.

You can see who has gone longest without a session, and who has had none.

Longest since last session
32 days
R.P.32 days ago
T.L.4 days ago
Last 30 days
Sessions logged14
Participants discussed23
Never supervisedNobody
08

A CPD ledger that's current, not reconstructed

Each practitioner keeps a running ledger against a target they set for the year β€” courses, reading, supervision, training. They log the hours as they go, so nothing is rebuilt at renewal.

You don't chase it. Each practitioner keeps their own, ready when renewal is.

T.L. Β· this CPD year
12.5 / 30
Target they set30 hours
On the same timeline
Supervision sessionsAdded
Required readsAdded
HoursThey log
Proof, not hope
09

Your way of working, written down

SOPs, plan templates, restrictive practice procedures and policies in one library β€” with required reads a new starter has to confirm. You get a list of who has confirmed and who hasn't.

A new practitioner learns your practice's way, not their last employer's β€” and you can show who confirmed each required read, and when.

Required reads confirmed
18 / 20
Restrictive practice procedure2 outstanding
Incident reportingAll confirmed
New starter Β· week one
Identity & checksDone
Policies & readingIn progress
First supervisionBooked
03 β€” Your data

Your participants’ data stays in Australia, and it stays yours.

You are the data controller for every participant record in your practice. Adding NDPRO means adding us to your own obligations, so here is exactly how it is held.

What is in place

  • Hosted in Sydney, Australia, and never sent overseas
  • Encrypted at rest and in transit
  • Isolation enforced twice and independently, in the application and inside the database itself
  • Identity comes only from the verified session, never from a field the browser can edit
  • Participants are addressed by opaque tokens across fourteen ID purposes, not by database identifiers
  • Sensitive actions record who did what before the action completes, and refusals are recorded too
YOUR ACCOUNT Β· SYDNEY DatabaseDocuments NDPROApplication access
The exit

And you can leave with all of it

It stays in Australia β€” so the question is never whether you can get your data out, only what you want out of it today. The workforce audit pack downloads as a PDF and the audit trail as a CSV, whenever you want, not only at offboarding. You do not own your practice’s operational record if you cannot take it and walk.

A Data Processing Agreement covering the Privacy Act 1988 including the 2024 amendments, the NDIS Practice Standards and the NSW Health Records and Information Privacy Act, signed before any data flows.

04 β€” Questions

Frequently asked

Do we have to leave Splose?

No, and you should not. Splose stays the source of truth for your calendar, billing, intake forms, service agreements and progress notes. NDPRO reads from it and never writes back.

Will my practitioners actually use it?

That is the right question, and it is the one that killed your last system. The honest answer is that NDPRO is a second login, so it has to be worth opening. Supervision sessions and required reads land on their CPD timeline as they happen, so nothing is reconstructed at renewal; their capability progression is visible; and they upload a credential renewal from their phone in under a minute. Ask us to demo the practitioner’s screen first, not the Director’s.

We have already built this in Airtable. Why change?

Then you are further ahead than most, and your schema becomes the blueprint rather than something we throw away. What Airtable structurally cannot do is refuse a change until the record of it exists, stop someone approving their own sign-off, derive a deadline so six screens agree, or scope a practitioner to their own caseload inside the database.

What happens to our data if NDPRO goes away?

It does not move. It stays in Australia, and you can export the workforce audit pack and the audit trail at any time. What happens to it if we cease operating is written into the Data Processing Agreement, not promised on a website.

How long until we are live?

Your practice is set up by hand, by us, and there is no self-serve switch. Your data is connected on the first day of setup, so the work starts producing the record immediately rather than after a migration project.

It all runs on the same day's work.

Your team records what they do once. Out of that comes the evidence an auditor asks for, and the record of a practice that is better this year than it was last year. Nobody keeps a second set of books.

Stay audit-ready. Keep growing.

Referrals, pathways, restrictive practices, credentials and supervision — one connected platform for behaviour support.

Book a walkthrough →
N NDPRO

The operations layer for NDIS behaviour support practices.