Subcontractor Compliance Is Not Admin

A main contractor holds a folder of subcontractor documents. Insurance certificates, qualifications, method statements, tax status. Collected at the start of the relationship and rarely looked at again.

Then something happens on site, and somebody checks, and a certificate expired in March.

The exposure is not administrative

When a subcontractor’s insurance has lapsed and an incident occurs, the claim does not simply fail for them. The main contractor is frequently the party left carrying it, because the obligation to verify sat with you.

The same applies to qualifications. Somebody working without the certification the task required is a problem for whoever allowed them on site, and the defence that a document was collected two years ago is not a defence.

This is why treating it as filing is the wrong frame. It is a control, and controls have to be current rather than collected.

The failure is silent by design

Nothing happens on the day a certificate expires. No alert, no notification, no visible change. The subcontractor may not have noticed either.

It surfaces at the worst possible moments: an inspection, an incident, a claim, or a client audit. In each case the question is not whether you had the document once, it is whether it was valid when the work was done.

Which means a folder of correct looking documents provides very little protection. What matters is whether anything was checking the dates.

Why chasing does not scale

Somebody in the office chases renewals. It works at five subcontractors and does not at thirty.

The chasing itself is a poor use of a person: repeated emails, follow up calls, and a spreadsheet that is only as current as the last time somebody updated it. It also stops entirely during busy periods, which are exactly the periods when most subcontractors are on site.

And it fails quietly rather than loudly. Nobody reports that they did not get round to chasing.

Documents arrive in every possible form

The practical obstacle to automating this used to be the material itself.

Certificates arrive as photographs taken at an angle, scans of varying quality, attachments in a dozen formats, screenshots from a phone. The layout differs by insurer, by trade body, by year. The expiry date is somewhere different on each one.

Rules based systems could never read those reliably, which is why this stayed manual long after most administration had been automated.

Where AI does the work

It reads them. Whatever the format, whatever the layout, however the photograph was taken.

It identifies what the document is, whose it is, what it covers, and when it expires. It checks that the cover matches the trade and the value of the work. It writes the expiry date into your system and tracks it forward rather than waiting for somebody to discover it backward.

Then it chases. Reminders to the subcontractor starting before expiry rather than after, continuing until the replacement arrives, without anybody sending an email.

And it flags what it cannot judge confidently to a person, with the reason attached, rather than passing something that should have been questioned. On a compliance document a confident wrong answer is worse than no check at all.

What good looks like

• Nobody works on site without current documents, verified rather than assumed.

• Expiry dates tracked forward, with renewal chasing starting before the date.

• An audit trail: what was requested, what arrived, what was checked, and what was valid on the date the work happened.

• One place to answer the question, so a client audit takes an hour rather than a week.

The four documents that actually matter

Most contractors collect more than they need and check less than they should. The short list:

• Public and employer liability insurance. Check the limit against the value of the work, not just that a policy exists. A policy covering a fraction of the contract value is close to no cover at all in the situation where it matters.

• Trade qualifications and cards for the specific tasks being carried out, held by the individuals actually on site rather than by the company in principle.

• Tax and employment status, because a subcontractor who turns out to have been an employee is a separate and expensive problem.

• Method statements and risk assessments for the work as scoped, refreshed when the scope changes rather than filed once at the start.

Each of these has an expiry, a scope and a named holder. All three have to be current at once for the check to mean anything, which is precisely the sort of cross referencing people do badly and software does perfectly.

The renewal window is the whole game

Insurance renews annually and qualifications on their own cycles, so at any moment a portion of your register is about to lapse. With thirty subcontractors carrying four documents each, that is a hundred and twenty expiry dates moving independently.

Nobody tracks a hundred and twenty dates. They track the ones they happen to remember, which is why the failures cluster around the subcontractors who work with you least often and are therefore least visible.

Those are also, as a rule, the ones you know least about.

Your clients are starting to ask

The other reason this matters commercially: larger clients and public sector work increasingly require evidence of subcontractor verification as part of prequalification.

A contractor who can produce a current register wins work from one who has to assemble it from a folder. That is a straightforward competitive advantage, and it arrives from doing something you should be doing anyway.

What to check this week

Take your active subcontractors and find out how many have a document expiring in the next sixty days. Then how many have already expired.

Most contractors running this for the first time find at least one that has lapsed and somebody currently on site. That is the argument for changing something, and it takes an afternoon to produce.

AI Optimize reads the certificates whatever form they arrive in, tracks every expiry forward, and chases renewals without anybody sending an email. That work sits under Document Intake & Validation.