Findable is the hard part
Compliance paperwork has to exist, be correct, and be findable years later by someone who was not on the job. Most software handles creation and quietly fails retrieval — which is the one that matters when an insurer, a regulator or a customer asks.
A compliance document has to be produced, has to be right, and has to be retrievable. Every product demo covers production. Correctness you can check yourself. Retrieval is the one nobody tests until they need it.
The test to run during a trial is not "can I create a certificate". It is "can somebody who was not on that job find the certificate from eighteen months ago in under two minutes". Try it before you commit — it is the field test most shortlists skip, and it is on the buyer’s checklist for that reason.
When the system cannot retrieve well, somebody starts a folder. A spreadsheet with links, a shared drive organised by date, a filing cabinet. It works, because the person maintaining it knows where things are.
That folder is a leak and a risk at once. It is unpaid work every week, and it is a single point of failure the day that person is unavailable and an insurer wants a document. If you have one, that is the actual problem to solve — not the certificate generation.
The document attached to the job that produced it, generated from data already captured rather than re-typed, and findable by job, customer, address, date or asset.
Trade language matters and getting it wrong signals you have never been on site. Sparkies produce a CoES, not a compliance certificate. Builders lodge a progress claim, not a milestone invoice. Plumbers record a variation, not a change order. Any system that renames these has been built by someone who was not listening.
We will not tell you a system makes you compliant. Software can make the paperwork consistent and retrievable; whether your obligations are met is between you, your regulator and your adviser.
Nor have we been assessed against the Australian Privacy Principles, which we state plainly on the ownership page. If your obligations require an assessed supplier, that is a real reason to use someone else and we will say so on the first call.
If you produce a handful of certificates a month and can find them, you do not have this problem. Frequency is what makes it pay, and the threshold is higher than frustration suggests.
And if the underlying process is unclear — if nobody is quite sure which document is required when — automating it produces confident, consistent, wrong paperwork. Errors that are expensive and hard to detect are the specific case to avoid here.
The prior step in that case is writing down which document is required at which point, on one page. That is an hour of somebody’s time, useful whether or not anything gets automated, and it frequently reveals that two people in the business held different beliefs about it.
Where documents are generated from job data, this also depends on the job data being clean at capture — which is the same flow problem arriving from another direction.
There is no reliable published Australian figure for how long producing and retrieving compliance documents takes in a small business, and we are not going to borrow one from a vendor whitepaper to make this page more persuasive. Most numbers you will see quoted for this were produced by companies selling the fix.
What we would do instead is count it on one of your jobs. Follow a single job end to end, note every time a human touches this step, and multiply by what that person costs loaded. That is a real number about your business and it takes an afternoon.
You can run the arithmetic yourself first — the leak calculator uses ABS, Average Weekly Earnings, Australia, May 2026 for the wage default and ATO, Super guarantee, current rate for super, and returns a range rather than a single confident figure. If the range comes back under our minimum engagement, that is a real answer and you should stop there.
No. It makes the paperwork consistent and findable, which helps considerably when someone asks. Whether you meet your obligations is a question for your regulator and your adviser, and any vendor who answers it differently is overreaching.
Not published, because we do not have measured before-and-after numbers we can stand behind yet, and a case study without them is a story. Kindra AI was founded in 2025. When the measurements exist they will appear here with the sample size attached.
20 minutes. We find where the money's going. No pitch.
Book a free Leak Check