The Gate List: Evidence-Led Clearance for Supplier Staff at UK Client Sites

The question behind the question

A client operations manager asks on Friday afternoon which supplier staff will be on site on Monday. The immediate question is about names. The question behind it is about assurance: who is coming, and can the organisation show that each person is cleared to attend?

For UK organisations that rely on subcontractors, presence is easy to arrange and harder to evidence. A clearance register is not a badge system or a security product. It is a single record that connects each expected person to the evidence that permits them to attend a particular client site, and to the date on which that evidence expires.

Why a list of names is not enough

A list of names answers half the question. It says who is expected. It does not say whether the person has the right to work in the UK, whether their role requires a check that has been completed and is still valid, whether the employer’s insurance is current, or whether the individual has completed the site induction the client requires.

Email threads are poor evidence. Attachments duplicate, versions diverge, and expiry dates hide in filenames. When a client asks for assurance, the organisation needs to produce a dated record within minutes, not reconstruct a chain of messages.

What the register must prove

The register should be built around a simple test: for every person expected on a client site, can the organisation show, on the date of attendance, that identity and right to work have been checked, that role-appropriate checks and training are complete, and that the employer’s insurance and contractual confirmations are current?

The register records the evidence and the expiry, not merely the fact that a document was once seen. That distinction is what turns a list into a clearance record.

The fields that earn their place

A practical register can be held in a spreadsheet or a simple database. The format matters less than consistency. Each row should represent one person, not one supplier, and should include:

• Full name and employer, including any subcontractor chain.
• Role and the site or sites the person may attend.
• Right-to-work check date and method, with expiry where applicable.
• Role-appropriate checks, such as a DBS check where the role is eligible and the check is lawful, with certificate date and any update service status.
• Insurance confirmations: employer’s liability and public liability, with policy expiry.
• Training confirmations: health and safety, site induction, and any client-specific module.
• Client approval or site access reference, where required.
• Evidence location and date last verified.
• Named owner responsible for keeping the row current.
• Review date and clearance status.

The named owner field is often omitted and is the one that determines whether the register survives contact with a busy month.

One owner, one review rhythm

Registers fail when everyone owns them. A named owner — usually an operations coordinator or contract administrator — should be accountable for completeness and for chasing expiries. The owner does not need to collect every document personally, but they must be able to state, on any given day, which rows are incomplete and which expire within the next 30 days.

A monthly review is usually enough for a stable supplier population. Weekly reviews are sensible during mobilisation, peak periods, or whenever a client site has imposed a new access requirement.

Building it without a project

Start with the next fourteen days of known site attendance. That gives a real population rather than an abstract policy. For each person, record what is already held and what is missing. Do not attempt to backfill every supplier relationship at once. Once the immediate population is clean, add the next month.

The register becomes useful early and improves with use. A small, current record is more defensible than a comprehensive one that is three months out of date.

Substitutions and subcontractor chains

The highest-risk moment is a last-minute substitution. The register should carry a simple rule: no row, no attendance. That sounds rigid, but it protects both the client and the supplier. A substitution is not an administrative footnote; it is a new clearance event.

For subcontractor chains, the principal supplier should provide the evidence for its subcontractor personnel, and the register should record the chain explicitly. If the principal supplier cannot confirm insurance or training for a subcontractor, that is a clearance gap, not a detail to be resolved after attendance.

Data protection and retention

The register holds personal data, so collect only what is necessary for site clearance, restrict access to those who need it, and set a retention period. Right-to-work evidence should be handled in line with Home Office guidance. DBS information should be handled with particular care and only where the role is eligible. The register should not become a general HR file.

A short retention rule — for example, remove leavers at the end of the contract plus a defined period — keeps the register accurate and reduces risk. Access should be limited to the named owner, their deputy, and those who genuinely need to confirm attendance.

A small routine that holds

The routine is straightforward. Before any site attendance is confirmed, check the register. Before the end of each month, review expiries for the next 60 days. After any substitution, update the row before the person attends.

The client team can then answer the Friday afternoon question with a dated record rather than a search. Presence with proof is not a large system. It is a disciplined list with a named owner, a review date, and a rule that attendance follows evidence.