NDPRO ← Back to guides

About

Who writes these guides, and how.

A guide about NDIS behaviour support obligations should say plainly who is behind it and why that is a reasonable source. This page is that answer, linked from every guide rather than left implied by a company name in a footer.

Santos Technology Pty Ltd · ABN 12 697 662 669


NDPRO at a glance

What it is
NDPRO is operations and compliance software for NDIS behaviour support practices in Australia.
Who it is for
Directors of behaviour support practices, and sole-trader behaviour support practitioners.
What it holds
The restrictive practice register with state and territory authorisations and their expiry, the participant pathway including interim and comprehensive plan dates, practitioner credentials, PBS capability and supervision records, and the evidence that goes with each.
What it does not do
It does not deliver behaviour support, give clinical advice, or lodge the monthly restrictive practice return to the NDIS Commission. NDPRO is not a registered NDIS provider.
Price
A$59 per active user per month, as stated on the Directors’ page.
Where data is held
Hosted in Sydney; participant data stays in Australia.
Works with
Standalone, with an optional read-only connection to Splose.
Company
Santos Technology Pty Ltd, ABN 12 697 662 669.
Contact
contact@santostech.com.au

NDPRO public software profiles

NDPRO is listed on G2 and SourceForge. These public profiles refer to the same behaviour support software described on this site.

1. What NDPRO is, and is not

NDPRO is a product of Santos Technology Pty Ltd, an Australian software company. We are not a registered NDIS provider or a registered behaviour support provider. We do not deliver behaviour support, and nothing on this site is clinical advice.

What we build is the record-keeping software a behaviour support practice uses to hold its restrictive practice register, practitioner credentials, PBS capability and supervision records, and the evidence an auditor asks for under Module 2A. The guides on this site come out of that: building a system that has to hold a compliant record correctly means reading the Commission's own rules closely enough to model them, not summarising a summary.

2. Why that is a reasonable basis, and where it stops being one

Designing what a restrictive practice register or a supervision record has to contain is a different exercise from writing about it as a journalist would, and closer to the exercise a practice itself goes through when it builds its own systems. That is the experience these guides draw on.

It is not clinical experience, and we do not present it as such. Where a guide states what the Commission's rules require, that claim rests on the Commission's own published document, cited and dated in the guide itself — not on our judgement. Where a guide describes what NDPRO does or does not do, that is a claim about our own product, which we can state directly.

3. How a guide gets written

4. Corrections

If something in a guide is wrong — a rule has changed, a citation is stale, or we have simply made a mistake — tell us at contact@santostech.com.au and we will fix it. NDIS Commission guidance is revised from time to time, and a guide that was accurate when written is not guaranteed to stay that way; the Commission's own current documents are always the authority, not this site.


Not affiliated with, endorsed by, or an interpretation of guidance from the NDIA or the NDIS Quality and Safeguards Commission.