The Contractor Pack Is Not a Compliance File: Rethinking Site Access for 2026

Most UK facilities teams can produce a contractor compliance pack. Fewer can prove, at 08:00 on a wet Tuesday, that the electrician waiting at reception is insured, competent and cleared for the area they are about to enter. That gap is the contractor pre-qualification trap. The pack looks like assurance. Too often it is a filing convention.

The argument here is simple: annual pre-qualification questionnaires (PQQs) and generic accreditation schemes have a place, but they are snapshots. Site access is a continuous decision. A living compliance file, kept current with the systems already on site, is a better control than a thick pack renewed once a year.

The annual pack problem

A typical pack contains insurance certificates, a health and safety policy, method statements, competency cards and a signed declaration. It is uploaded to a portal, checked by someone in procurement or facilities, and approved. Twelve months later, the cycle repeats. In between, people change, insurance expires, subcontractors appear and the scope of work moves.

The trap is not that the documents are false. It is that they are treated as current when they are only recent. An insurance certificate can be valid on the date it was uploaded and expired on the date of the visit. A competency card can belong to a named individual who is not the person on site. A security clearance check can be relevant to one site and not another. The pack does not answer the question the gate needs answered: is this person, from this employer, cleared for this work, today?

Why real-time verification matters

Operations managers own the risk at the gate. If an incident occurs, the first questions will be about induction, supervision, insurance and competence. Insurers may ask whether the contractor was approved for the work. Clients may ask whether subcontractors were visible. The answer cannot be a folder dated eleven months ago.

This is not about creating a parallel bureaucracy. It is about using the access control, induction booking, email and shared-drive tools already in place to keep the file alive. The compliance file should follow the person and the visit, not the annual renewal cycle.

Five questions before the next contractor induction

1. Who checked the insurance today, and does it match the entity and the work package?

Ask for the certificate, not a summary. Check the legal entity, the policy period, the limits and the work covered. A group certificate may not cover the subsidiary sending the crew. Record the checker’s name and the date. If the certificate expires during the works, set a diary reminder before the visit.

2. Which named person will be on site, and where is their competency evidence?

A company-level certificate is not a person-level check. Ask for the names, the role and the evidence for the task. For some work this will be a card scheme or a qualification; for others it will be a supervisor’s sign-off. Keep the evidence against the name, not against the contract. If the name changes, the check restarts.

3. What security clearance or right-to-work status applies, and when was it last verified?

Not every contractor needs the same level of clearance, but the site should know what it requires. Record the check, the date and the person who verified it. If a DBS check or right-to-work evidence is part of the requirement, make sure it is current and filed where the gate can see it. Do not rely on a contractor’s assurance that checks are done.

4. Who approves subcontractor substitutions, and what triggers re-induction?

Subcontractor changes are where packs fail. The principal contractor may be approved, but the crew on site may be from another business. Ask who approves substitutions, what evidence is required and who informs reception. A substitution should trigger a fresh induction and a fresh check, not a note in an email.

5. What will an auditor see at 08:00 if something goes wrong?

Imagine the visit, the incident or the insurer’s request. Can you produce the induction record, the insurance check, the named person’s competency evidence and the approval for the work? If the answer depends on someone’s inbox, the file is not living. The evidence should be in one place, dated and owned.

Making the file living

A living compliance file needs four things: a named owner, an expiry calendar, a gatekeeping rule and a monthly audit. The owner does not need a new system. They need the authority to stop a visit when evidence is missing. The expiry calendar can sit in the existing email or calendar tool. The gatekeeping rule should be written into the induction booking process. The monthly audit should sample three contractor files and record the result.

It also needs an exception log. When a contractor arrives without the right evidence, record what was missing, who approved the exception and what was done to close it. Exceptions are not failures if they are visible and managed. They are failures when they are absorbed into the day and forgotten.

The bottom line

The contractor pack is not useless. It is a starting point. The trap is treating it as a substitute for verification. In 2026, with scrutiny of premises readiness higher than ever, the question is not whether your pack is thick. It is whether it is current. A living file, built on the systems you already have, is the difference between a paper trail and a site that knows who is on it.