Santos Technology SantosTechnology Pty Ltd Start a conversation

Guides

Where the obligation meets the software

Written for the people who carry the obligation: compliance leads, records officers, practice managers and the counsel who has to sign off. Each one answers a question properly, including the parts that argue against hiring anyone.

Start here

Buyer's guide · 14 min NDIS compliance software: an honest buyer's guide Three categories are sold under one name, and buying the wrong one is the expensive mistake. Names the products, and says when to buy nothing.

NDIS compliance and audit

Guide · 9 min What evidence do the NDIS Practice Standards actually require? Assessed on evidence, not intent. Why documented policy is the weakest form, and where providers are usually exposed. Guide · 8 min Evidence of control: what auditors mean, and why providers fail on it Most providers can show something was done. Far fewer can show it was under control at the time. Comparison · 7 min NDIS software: build, buy, or configure what you already have? Three options, not two. The one usually skipped is right more often than either extreme. Comparison · 9 min Custom build or off-the-shelf: which one an NDIS provider actually needs Most providers should buy. The three situations where custom is genuinely justified.

Privacy, records and retention

Guide · 11 min How do you de-identify documents under the Privacy Act 1988? Redaction rarely reaches the statutory bar. What “reasonably identifiable” actually requires. Guide · 8 min How long must an NDIS provider keep participant records? Seven years, or until a child participant turns 25. The harder problem is surviving staff turnover and system change.

If this is your situation

For you if You failed an NDIS audit and have corrective actions due Non-conformities are usually evidence failures, not practice failures. What to fix first, and what not to rush. For you if Your SIL and SDA arrangements do not fit the platform’s data model How to tell a configuration limit from a structural one before spending anything. For you if Your team maintains a spreadsheet beside the compliance platform Not a discipline problem. The most accurate specification document you will ever have.

Work

Case study Keeping 15+ behaviour support practitioners audit-ready 300+ plans under management, with compliance derived from clinical work rather than entered alongside it. Case study Redacting 10,000+ pages a month without a manual review bottleneck 300+ documents hand-checked with no identifier missed, saving over 100 review hours a month.

Carrying an obligation your software does not represent?

Two weeks inside your workflow produces a build plan, an accuracy baseline and a risk register. You keep all three either way.

Start a conversation