For you if · The model does not hold the work
Your SIL and SDA arrangements do not fit the platform's data model
Most compliance platforms assume one participant, one service, one provider, one plan. Blended arrangements break that assumption, and the break is structural rather than a missing feature.
The reliable tell is a spreadsheet maintained beside the platform holding a relationship the platform has no field for. That spreadsheet is not a workaround to be eliminated. It is the specification for what needs to exist.
The arrangements that break the model
- Mixed SIL and SDA for the same participant, where obligations attach to different entities and reporting has to separate cleanly.
- Shared programs across participants in one dwelling, where an incident touches several people with different plans and consents.
- Subcontracted delivery, where the obligation stays with you and the evidence is created by someone else's staff in someone else's system.
- Consent withdrawn and re-given, where the platform holds a boolean and the reality has a history.
- Participants moving between arrangements, where continuity of record matters and the platform treats the change as a new record.
Blended arrangements are usually certification-pathway, which means on-site assessment, staff interviews and participant feedback rather than a document review. An auditor asking how an incident in a shared setting was handled across three participants' plans is asking a question your spreadsheet answers and your platform cannot.
Configuration limit or structural limit
Worth establishing before spending anything, and it is usually a short exercise.
| Symptom | Usually means |
|---|---|
| A field you need does not exist | Configuration. Check custom fields first |
| The report does not group the way you need | Configuration, or an export plus a pivot |
| One record cannot belong to two things at once | Structural. The data model does not allow it |
| History is overwritten rather than kept | Structural. Retrofitting history is a rebuild |
| Staff keep a spreadsheet to hold a relationship | Structural, almost always |
What usually gets built
Rarely a replacement. The platform handles the standard obligations well and absorbs regulatory change, which is worth keeping. What gets built is the narrow piece that holds the relationship the platform cannot represent, with the evidence trail the spreadsheet cannot produce, integrated so nobody maintains two sources of truth.
- Australian-hosted, inside your tenancy where that matters
- Architected against the Privacy Act 1988 (Cth)
- Audit trail and retention as first-class features rather than reporting add-ons
- You own the code, the infrastructure and the documentation from day one
Common questions
Do we have to replace our compliance platform?
Usually not, and I would generally advise against it. Replacing a platform that handles the standard obligations well is expensive and risky when the gap is narrow.
Can you integrate with the platform we already run?
That is normally the point. A system that creates a second source of truth makes the problem worse, so integration is a requirement rather than a feature.
How do we know this is worth spending on?
The two-week review answers it, and it is deliberately cheap enough to be worth running to find out the answer is no.
This guide is general information about how Australian regulatory obligations apply in practice. It is not legal advice, and requirements vary by registration group, jurisdiction and the supports you deliver.