Temp Worker Document Verification Before the First Shift

A temp worker's file needs three things confirmed before an agency lets them start a client assignment: every required document is present, each one is still valid — in date, not expired, matched against the right official register — and the details on one document match the details on every other document in the same file. Missing any of the three turns a routine placement into a compliance problem weeks later, when the client, the umbrella company, or the Employment Agency Standards Inspectorate asks to see the file.

This is a file-completeness and consistency question, not a forgery question. Most first-assignment holdups in UK staffing are administrative rather than criminal: a share code nobody generated, a National Insurance number that doesn't match the name on the passport, a certificate for a role that changed between the interview and the start date. Fixing that requires a checklist and a cross-check, not a fraud investigation.

What a complete temp worker file contains

A complete file has seven components an agency should be able to point to before booking a first shift: photo ID, proof of address, right-to-work evidence, a National Insurance number, role-specific qualifications where relevant, bank details for payroll, and a signed assignment contract or Key Information Document. Staffing businesses are the legal employer for right-to-work purposes even when a client hosts the worker day to day, so the paperwork obligation sits with the agency, not the site manager who signs off the timesheet.

Under the Conduct of Employment Agencies and Employment Businesses Regulations 2003, the employment business — not the hirer — carries the statutory duties around worker information, contracts, and record-keeping for temporary placements, a structure the Employment Agency Standards Inspectorate enforces on behalf of the Department for Business and Trade. A hirer can refuse a candidate whose file is incomplete, but the retention duty itself does not transfer.

Why the check has to happen before the shift starts, not after

A right-to-work check only creates a statutory excuse against a civil penalty if it is completed before the individual begins work, not retrospectively once a problem surfaces. Generating a share code or copying a passport after someone has already worked their first shift does not protect the agency, even if the worker turns out to have full permission to work.

Since 13 February 2024, the Home Office civil penalty for employing someone without the right to work has stood at up to £45,000 per worker for a first breach and up to £60,000 per worker for a repeat breach, a threefold increase on the previous £15,000/£20,000 scale, set out in the employer's guide to right to work checks. For an agency running dozens of first assignments a week, the exposure scales with volume, not with any single worker's history.

Right-to-work evidence: share codes, List A, List B

A right-to-work share code has to be generated by the worker and checked online by the agency before the assignment starts; it is not a document that can be requested and reconciled later. List A documents (typically a British or Irish passport, or settled status) establish a permanent right to work and need no further check once verified correctly the first time.

List B document holders — those with time-limited permission — need a follow-up check at whichever comes first: the date their current permission expires, or twelve months after the last check, per the same gov.uk employer's guide. Missing that second date is a common way an otherwise-compliant file quietly falls out of compliance months into a placement, well past the point anyone was still looking at it.

Consistency across the file, not just presence of documents

A document being present and in date is not the same as a file being internally consistent. The spelling of a legal name on a passport, the address on a utility bill, and the name printed on a bank account are frequently close but not identical — a married name still on one document, a maiden name on another, a hyphenated surname split across two systems.

Cross-document validation checks the same field — full legal name, date of birth, current address — against every document in the file at once, which is the mechanical core of a consistency check that a manual reviewer otherwise has to do line by line. That approach matters most in staffing specifically, because a single worker's file is assembled from several independent sources (the worker, the umbrella company, a training provider, a bank) rather than issued by one employer's HR system.

Where files stall in practice

On recruitment and payroll compliance forums, staffing coordinators and umbrella-company compliance teams describe two recurring bottlenecks that rarely make it into formal guidance. The first is chasing a candidate for one missing document after a placement has already been agreed with the client, which puts the agency in the position of either delaying a start date it has promised or booking someone with an incomplete file. The second is tracking List B expiry and twelve-month recheck dates in a spreadsheet, where a date quietly passes because nobody was assigned to watch it.

A related, less-discussed gap involves umbrella companies. Workers paid through an umbrella rather than directly by the agency still need their identity, right-to-work, and bank details verified against the agency's own file — an FCSA or Professional Passport accreditation for the umbrella does not substitute for checking the individual worker's documents. Agencies that treat "the umbrella handles it" as sufficient are the ones most likely to discover a gap during a client audit rather than before the first shift.

The REC Code of Professional Practice and audit readiness

Agency membership in the Recruitment and Employment Confederation is not itself a legal requirement, but it sets the practical bar most UK clients now expect before awarding a preferred-supplier contract. REC corporate members must pass a compliance assessment — at least 26 to 48 multiple-choice questions covering the Code of Professional Practice and current legislation — scoring a minimum of 80% and answering every "red flag" question correctly, repeated at least once every two years.

That test format is a reasonable proxy for what a client audit will actually check: not whether an agency has heard of right-to-work rules, but whether its process reliably produces a complete, valid, and internally consistent file for every worker, every time, before day one. Building that process once — a fixed checklist, a recheck calendar for time-limited documents, and a cross-field comparison step — removes the need to re-solve it manually for each new starter.

For a broader look at how document verification requirements differ across regulated sectors beyond staffing, see our guide to document verification by industry. Agencies handling HR-adjacent checks such as diploma verification alongside right-to-work evidence may also find our walkthrough of diploma and right-to-work checks for HR teams useful, and our deeper breakdown of share codes and List A/List B evidence covers the right-to-work mechanics in more depth than fits here.

CheckFile's security page describes how document data is handled and retained once a file is verified, and the pricing page sets out how verification volume maps to plan tiers for agencies running high first-assignment throughput. For staffing and recruitment specifically, our staffing solution is built around this exact sequence — completeness, validity, and cross-document consistency — applied before a worker's first day rather than discovered after it.

Frequently Asked Questions

What is temp worker document verification?

It is the process of confirming that every document required for a temp placement is present, still valid, and consistent with the other documents in the same file, before the worker's first assignment begins. It covers identity, right-to-work evidence, address, National Insurance number, qualifications where relevant, bank details, and the signed assignment contract.

How does temp worker document verification work in a staffing agency?

An agency collects the required documents against a fixed checklist, checks each one against the relevant official source (the Home Office online service for right-to-work share codes, a training or professional body for certifications), and compares shared fields such as name, date of birth, and address across the full set. Time-limited documents get a recheck date logged against the twelve-month or expiry-date rule, whichever comes first.

Why does this matter before the first assignment specifically?

A right-to-work check only establishes a statutory excuse against a Home Office civil penalty if it is completed before the individual starts work; doing it afterward does not protect the agency even if the worker was always entitled to work. The same logic applies commercially — a client who discovers a missing document mid-assignment will question the agency's whole vetting process, not just that one file.

Who is legally responsible for right-to-work checks when a worker is supplied by an agency?

Under the Conduct of Employment Agencies and Employment Businesses Regulations 2003, the employment business supplying the worker carries the right-to-work and record-keeping duties, not the client site where the worker is placed. Some contracts restructure this responsibility, but by default it stays with the agency.

Does using an umbrella company remove the agency's verification responsibility?

No. An umbrella company's own accreditation, such as FCSA membership, relates to its payroll and tax compliance, not to whether the individual worker's identity, right-to-work status, and bank details have been checked against the agency's file. Agencies still need their own verification step for each worker regardless of how that worker is paid.