Building a contractor register that actually catches expired insurance

Most facilities teams have a contractor list of some kind — names, trades, phone numbers, maybe a folder of certificates somewhere. Far fewer have a register that actually surfaces when a contractor's insurance is about to lapse, or when an accreditation has already expired, before that contractor turns up on site and does work you'd struggle to defend afterward if something went wrong.

Why a static list isn't enough

A list of contractors with certificates attached at the point they were onboarded is accurate on day one and steadily less accurate after that. Public liability insurance renews annually; accreditations lapse; a contractor who was fully compliant when first engaged two years ago may not be today, and nothing about a static list forces anyone to notice.

What actually needs tracking, per contractor

The specifics worth tracking go beyond a name and a trade: current insurance cover and its expiry date, relevant trade accreditations and their expiry, any site-specific inductions completed, and a record of past work quality if that's tracked at all. Missing any one of these turns the register from a genuine control into a directory that happens to also hold some paperwork.

• –Public and employer's liability insurance, with the actual expiry date, not just confirmation it existed at onboarding
• –Trade-specific accreditations and qualifications relevant to the work they're engaged to do
• –Site induction and access requirements, especially where different buildings have different rules
• –A record tying past jobs to the contractor, so recurring quality issues are visible over time

Catching expiry before it becomes a problem

The value of a contractor register is almost entirely in whether expiring documents actually surface before they lapse, not in whether the documents are stored somewhere. A register that requires someone to manually check every contractor's paperwork periodically will, in practice, get checked rarely and then get skipped when things are busy — which is exactly when a gap in insurance is most likely to go unnoticed until a claim exposes it.

This connects directly to managing contractors while they're actually on site — a contractor whose paperwork lapsed without anyone noticing is a much bigger problem if it's also unclear who signed them in and what they were doing while there.

It also matters for the same reasons evidencing compliance matters more broadly — being asked, after an incident, to show that a contractor was properly vetted and current at the time of the work is a much easier position to be in with a genuinely tracked register than with a folder of certificates nobody's checked in months.

The certificate that expired in March

Contractor documents are the classic silent expiry. Insurance is verified at onboarding, filed, and renews annually on a date that lives with the contractor rather than with you. A contractor working on site with lapsed cover is a problem that exists for months before anybody discovers it, and it is usually discovered by an insurer or an auditor rather than internally.

What makes this tractable is treating the expiry date as the tracked item rather than the document. The certificate is evidence; the date is the thing that needs watching, with enough notice to chase before it lapses rather than after.

Common mistakes

• –Verifying documents at onboarding and never again
• –Storing certificates without extracting and tracking their expiry dates
• –Chasing renewal after expiry rather than before
• –No check on whether cover is appropriate to the work actually being done
• –Allowing a contractor on site while documents are pending
• –Keeping the register somewhere the person booking contractors does not look