Risk

Certificate of Currency: a practical expiry-monitoring register

Anna Marie Saplad · Field notes for QLD builders

In 2024–25, unlicensed contracting was the #1 offence investigated by the QBCC — 864 cases, 46% of all investigations — and insurance-related non-compliance was also reported. Those figures do not establish how often subcontractor certificates expire, but they do reinforce the value of keeping the records a builder relies on organised and visible.

The uncomfortable maths

A certificate collected at engagement can later expire. A register gives the responsible person one place to see the recorded policy and expiry information and follow the builder's documented requirements.

The half-day register

1. List every active sub — one row each: company, trade, contact, insurer, policy number, expiry date.
2. Collect the documents required by the builder's policy. Record who supplied each document and when it was reviewed.
3. Set the agreed reminder cadence. The demonstration workflow uses 30, 14 and 7 days before the recorded expiry date. Any site-access decision remains with the builder under its documented requirements.

Why the 30/14/7 cadence works

Thirty days provides an early reminder, fourteen days supports a follow-up, and seven days flags the item for escalation under the builder's documented process. The cadence can be adjusted to the builder's contracts, policies and operational needs.

Stop tracking it by hand.

My demonstration workflow watches recorded expiry dates, prepares the agreed 30/14/7-day follow-ups, and flags exceptions for review. Under a retainer, I keep the workflow monitored and coordinate the follow-up, while the builder remains responsible for policy and site-access decisions.