Every provider has found one. A certificate of currency that expired months ago, for a contractor who has been on site the whole time. Nobody was negligent. The document simply sat in an inbox with a date nobody was watching.

Expiry is the most predictable risk in a provider’s supplier base, and the most commonly missed. It is predictable because every document carries its own deadline the day it arrives. It is missed because the deadline is stored as text in a PDF rather than as a date in a system that can act on it.

What actually has to stay current

The list is longer than most providers expect, and it differs by supplier type:

• Insurances. Public liability, professional indemnity, workers compensation, product liability, motor vehicle for transport providers.
• Worker screening and checks. Aged care worker screening, police certificates, working with children where relevant, statutory declarations for overseas history.
• Professional registration. AHPRA registration for clinicians, allied health credentials, trade licences, food safety supervisor certificates.
• Company standing. Business registration, subcontractor arrangements, and for construction and maintenance, essential services certification.
• Financial security. Bank guarantees and retention amounts on capital and refurbishment work.

Multiply that by a supplier base of a few hundred and the tracking problem stops being something a spreadsheet handles well, because a spreadsheet cannot chase anybody.

Why the spreadsheet fails

It is rarely the spreadsheet itself. It is the three assumptions built around it.

That someone opens it. A tracker only works if a person reviews it on a rhythm. When that person is on leave, doing double shifts or has left the organisation, the rhythm stops and nothing announces that it has stopped.

That the supplier will send the renewal. Most will, eventually, when asked. The asking is the work, and it lands on whoever noticed, usually late.

That the roster knows. Even when the compliance team knows a certificate has lapsed, that knowledge often does not reach the person allocating shifts or approving a site visit. The control exists on paper and not at the point of risk.

A date in a document is a fact. A date in a system is a control.

What a working control looks like

Four things have to be true:

1. The requirement is recorded against the supplier and the contract, so the system knows what this supplier must hold, not just what they happen to have sent.
2. The expiry date is a field, captured when the document is loaded.
3. The reminder goes to both sides, early enough to act on, and repeats as the date approaches.
4. The gap is visible to the people who make decisions, on a list they already look at, not buried in a report nobody runs.

How TracPro handles it

• Insurance and bank guarantee tracking against each supplier and contract, with types, values and expiry dates as structured data.
• Escalating reminders before expiry, so a lapse requires several ignored warnings rather than a single missed email.
• Supplier self-service. Suppliers log in as external users and upload their own renewed certificates. Your team reviews and approves rather than chasing.
• Inductions and site requirements recorded alongside the agreement, so contractor onboarding evidence lives with the contract.
• Probity Guardian in the AI Suite, which sweeps the portfolio for missing or expired insurance, guarantee and approval evidence and puts it in one list.
• Reports and scheduled exports so the compliance position can go to the board or quality committee without anyone rebuilding it.

The half day that pays for itself

Take your current tracker, whatever it is. Count how many entries have an expiry date in the past, and how many have no date recorded at all. That second number is usually the larger one, and it is the real measure of the exposure.

Loading those requirements into a system with reminders attached is a half-day exercise for most providers. The value is not the tidy list. It is that the next lapse becomes a task with a name and a date on it, weeks before it becomes an incident.

General information about contract management practice, not legal or compliance advice. Requirements differ by state, service type and funding program.