Chasing certificates across many subcontractors
In short
- The failure mode is always the same: certificates get collected once, at induction, and nobody owns the job of re-checking them as they age.
- A register with an expiry date per subcontractor and a reminder before each one lapses is the control. A folder of PDFs is not.
- Chasing works better as a standing process tied to renewal dates than as a one-off compliance sweep before an audit.
One subcontractor’s certificate is a two-minute check. Twenty subcontractors, each renewing on a different date, each occasionally changing broker or insurer, is a different problem entirely — and it is the problem that actually causes gaps, because nobody set out to skip a check, the process just could not keep up.
This page is about the process, not the individual check — what breaks it, and what keeps a growing subcontractor list actually current rather than accurate on the day it was first collected.
Why the folder approach fails
Collecting a certificate at induction and filing it answers one question, once: was this subcontractor covered on this date. It does not answer whether they are covered today, six months into a project, and nothing in a static folder prompts anyone to ask again.
The larger the subcontractor list, the more certain it becomes that some certificates have quietly expired without anyone noticing, simply because checking a folder of PDFs for outdated dates does not happen unless someone is specifically tasked with it.
What a working register looks like
The useful version is a list — a spreadsheet is enough — of each subcontractor, their insured entity name, the classes of cover required, and the expiry date on their current certificate. A reminder fires before each expiry, prompting a fresh request rather than a fresh check of the old document.
Renewal, not the calendar of any single project, is the trigger. A subcontractor working across several concurrent projects only needs to be re-checked once per renewal, not once per project they touch.
Making the chasing itself routine
Chasing works better as a standing weekly or monthly task — whoever owns the register runs the list of upcoming expiries and sends the request — than as a scramble before an audit or a principal’s compliance check. The scramble approach finds every gap at once, usually at the worst possible time.
Where a subcontractor repeatedly fails to respond to a renewal request, that is itself information. A pattern of non-response is worth escalating as a standing-down-from-site question, not just a paperwork nuisance.
Questions
- How many subcontractors before a spreadsheet stops being enough?
- That depends on the business, but the trigger is usually missed renewals, not a headcount. If certificates are being found expired rather than caught before expiry, the process needs a dedicated reminder step, whatever the list size.
- Should certificates be re-collected for every new project, or just at renewal?
- Renewal is the point that actually changes the underlying cover, so that is what the register should track. A subcontractor already current does not need re-checking for every new job they pick up in the same period.
- What if a subcontractor just stops responding to renewal requests?
- Treat non-response as a live gap rather than an administrative delay, and escalate it as a site-access question. A subcontractor who cannot produce current evidence of cover is, for practical purposes, uninsured until they do.
Sources
- Australian Business Register (ABN Lookup) — Free public tool to confirm a business’s registered entity name, ABN and status against the name printed on a certificate.
- business.gov.au — engaging contractors — Australian Government guidance on engaging contractors, the employee/contractor distinction, and contractor obligations including insurance.