Compliance and case management
An audit is not a test of your work. It is a test of your records.
Organisations rarely fail an audit because the work was bad. They fail because the evidence was scattered: in email, in a shared drive, in a form somebody filled in on paper and scanned three weeks later.
Generic compliance products solve a generic obligation. Yours is specific, it comes from your regulator or your accreditation, and the closer the product gets to fitting it, the more configuration it needs to get the rest of the way.
The real requirement
Evidence should be a by-product of the work, not a second job.
The test of a compliance system is not whether it can store a document. It is whether the evidence gets captured at the moment the work happens, by the person doing it, without them thinking of it as paperwork.
Every system that fails does so the same way: capturing evidence is a separate task, so it is done later, in bulk, from memory. Then an audit asks for something specific on a specific date and the gap becomes visible.
Case management is the same problem with a person attached
A case is a sequence with obligations, deadlines and a record of decisions. Whether it is a complaint, an investigation, a client matter or a support plan, what matters is that the next action is visible, the deadline is tracked, and the reasoning behind each decision is recoverable a year later.
Where the obligations come from
Your regulator, not a product's idea of compliance.
We build the workflow and the evidence trail around obligations you define. We do not interpret your obligations for you, and any vendor claiming their product makes you compliant is selling you a comfortable feeling rather than a control.
What software can genuinely do is make the right thing the easy thing: prompt at the right moment, capture at the right moment, and make the gap visible while there is still time to close it.
The scope
What gets built, and what we leave alone.
What gets built
- Cases or matters with your stages, obligations and deadlines
- Evidence captured at the point of work, on a phone if that is where the work happens
- Document and record retention with the periods your obligations actually require
- A decision log, so the reasoning behind an outcome is recoverable a year later
- Reminders before an obligation lapses rather than a report after it did
- Register views: incidents, complaints, training, qualifications, expiries
- Audit export, so preparing for an audit is a download rather than a fortnight
- Role-based access with a real access log
What we will not build
- Interpretation of your legal obligations. We build to obligations you or your adviser define
- Certified regulatory lodgement, where a certified product and its certification are the point
- Award or industrial instrument interpretation
- Anything that would let a vendor, us included, claim your compliance is our responsibility
Say this out loud to any vendor. Software does not make an organisation compliant. It makes compliance visible, prompted and evidenced. Anyone who tells you otherwise is selling you the wrong thing.
The sum
The compliance stack, times sixty.
Do it on your own number
Count the compliance platform, the forms tool, the document store, the training register and the consultant time spent assembling evidence before each audit.
Common questions
Answered plainly.
Does custom software make us compliant?
No, and be wary of anyone who says it does. Software makes the right action easy, prompts it at the right time, and captures the evidence as a by-product. Your obligations remain yours, and we build to obligations you or your adviser define.
How much does compliance software cost to build?
From $9,000 for most organisations, fixed before anything starts. Complex cases with heavy evidence requirements run from $18,000. There is no per-user fee, which matters for organisations where a lot of people need occasional access.
Can field staff capture evidence on a phone?
Yes, and it should be the default. Evidence captured at the moment of work is accurate; evidence captured that evening from memory is a liability wearing the costume of a record.
What about record retention periods?
Built to the periods your obligations require, with the deletion or archival handled rather than left to somebody remembering. Retention is one of the most commonly missed requirements in home-grown systems.
How does audit preparation change?
It becomes an export instead of a project. That is the single clearest return on this kind of build, because most organisations currently spend days or weeks assembling evidence that was always there but never in one place.
Where to next
Bring your last audit finding.
Or the evidence request that took a fortnight to answer. Twenty minutes on that tells us exactly where the record keeping breaks and whether a build would have closed it.