How to Run a Right to Work Compliance Process
A missing Right to Work record can become an operational problem long before it becomes a legal one. A worker may be booked for a night shift, trained for a production line and relied upon to protect output, only for a document gap to surface during an audit. A disciplined Right to Work compliance process prevents that disruption by making eligibility checks a controlled part of deployment, rather than an administrative task completed after the worker has started.
For labour-intensive operations, the objective is straightforward: every person on site must be cleared to work, correctly recorded, assigned only where their eligibility and training allow, and visible to the managers responsible for the shift. That requires more than collecting documents. It requires ownership, timing, evidence and a reliable way to manage expiry dates at scale.
Why Right to Work failures disrupt operations
Employers have a legal duty to prevent illegal working. Completing prescribed checks correctly before employment begins can establish a statutory excuse against a civil penalty if an individual is later found not to have the right to work. The financial and reputational consequences of getting this wrong are serious, but the operational consequences are often more immediate.
A failed audit can trigger urgent reviews of agency labour, access permissions and shift plans. Supervisors may need to remove workers from a line at short notice. HR and compliance teams can be left searching across inboxes, shared drives and paper files to establish what was checked, by whom and when. In a warehouse, food production or manufacturing environment, that uncertainty quickly becomes lost productivity, overtime pressure and missed service levels.
Temporary labour adds complexity because worker volumes change rapidly. A site may bring in dozens of people across multiple shifts, with different assignment lengths and document expiry dates. The risk is not simply that a check is missed. It is that the process works on a quiet week but breaks down when demand rises.
The core Right to Work compliance process
A compliant process should be designed around the worker journey, from registration through to the end of an assignment. The detail of acceptable evidence and checking methods is set by current Home Office guidance, so internal procedures must be reviewed whenever that guidance changes. However, the operational control framework remains consistent.
1. Check eligibility before work starts
The check must be completed before the worker begins employment or an assignment. Not on their first break, not at the end of an induction and not once a supervisor confirms they are needed on the line.
Depending on the worker’s status, this may involve checking original documents, conducting an online Right to Work check using a share code, or using an identity service provider for an eligible British or Irish citizen. The correct route matters. A photocopy of a document, an image sent by message or an expired form of evidence will not necessarily provide the required protection.
For online checks, the employer or authorised checker must review the result while the individual is present, either in person or by live video link, and confirm that the photograph and biographical details reasonably match the person presenting themselves. The point is verification, not merely downloading a result.
2. Record the evidence and the date of the check
A sound record should show exactly what was checked and when. Retain a clear copy of the relevant document or online check output, record the date the check took place and ensure the record can be retrieved quickly. These records must normally be retained securely for the duration of employment and for two years after it ends.
This is where fragmented processes create avoidable risk. If the evidence sits in one system, assignment records in another and training data in a third, a site can struggle to prove that its workforce controls are operating as intended. A central worker record gives compliance teams a single source of truth and gives operations a clearer answer to a basic question: is this person approved to work this shift?
3. Set follow-up dates for time-limited permission
Not every worker has an indefinite right to work. Where permission is time-limited, the initial check is only the first control. The business must diarise a follow-up check before the permission expires, using the appropriate method at that time.
This should not rely on an individual recruiter’s calendar or a spreadsheet that only one person understands. Use automated alerts with clear ownership and escalation points. For example, a 90-day alert gives the compliance team time to contact the worker, a 30-day alert prompts a firm decision on future bookings, and an overdue status should prevent further deployment until the matter is resolved.
The right lead time depends on workforce size, assignment patterns and how quickly workers can provide updated evidence. High-volume sites should build in more time, particularly where a replacement may need site induction or role-specific training.
4. Link compliance status to booking and site access
The strongest control is prevention. If a worker’s Right to Work check is incomplete, expired or awaiting review, they should not be bookable onto a shift. This sounds obvious, yet many organisations still manage compliance separately from booking, attendance and access processes.
A practical workforce system should make status visible before a booking is confirmed. It should also distinguish between a worker who has a valid Right to Work record, one whose permission is approaching expiry and one who is not cleared for deployment. Managers do not need to see sensitive immigration details to make an effective decision. They need a clear, reliable deployment status.
This is particularly valuable when a site faces a late absence. A fast replacement process must not bypass compliance. The replacement may be available, trained and close to site, but they are only a viable option if their eligibility record is complete.
Clarify responsibility between agency and client
Where temporary workers are supplied by an agency, the agency will commonly be the employer and therefore responsible for carrying out Right to Work checks on its workers. The client should not assume that this removes all operational responsibility.
The client still needs confidence that the supply chain is controlled. Contractual expectations should define who completes checks, what evidence is retained, how expiry risks are managed, what reporting is available and what happens when a worker’s status changes. Site teams should know who can authorise a worker onto site and how exceptions are handled.
The most effective arrangements avoid unnecessary duplication while maintaining visibility. If an agency has completed the legal check, the client can focus on assurance: confirmation of cleared status, audit-ready reporting, worker identity at site entry and the connection between eligibility, training and assignment suitability.
Build an audit trail that works under pressure
An audit trail should be easy to follow without relying on institutional memory. For each worker, a reviewer should be able to see the check type, the date completed, the evidence retained, the checker, the expiry or follow-up date and the worker’s current deployment status.
Test this before an audit forces the issue. Select a sample of workers from live shifts, including new starters and time-limited permissions. Can the team retrieve the required evidence quickly? Does the booking system match the compliance record? Has every required follow-up date been set? Are workers with unresolved records blocked from deployment?
This exercise often exposes process gaps that are not visible in day-to-day activity. It may show that night-shift bookings are being approved outside standard workflows, that site access lists are not refreshed promptly, or that workers are being reactivated after a break without a review of their records.
Use workforce visibility to prevent last-minute risk
Compliance performs best when it is part of workforce planning, not a separate back-office function. Operations leaders need live visibility of booked headcount, attendance, capability, training and compliance status together. That enables informed decisions before a gap affects output.
Recruit Mint’s Deploy Mint platform is designed around this operational reality. It brings worker onboarding, Right to Work, training, attendance and live workforce reporting into one view, helping employers identify risks before a worker reaches the gate. For a busy distribution or production operation, that means fewer manual checks, faster escalation and greater confidence that the people booked are genuinely ready to work.
The right process will vary by workforce model, site complexity and the proportion of time-limited permissions in the labour pool. What should not vary is the standard of control: complete checks before deployment, clear evidence, active expiry management and a booking process that cannot override compliance. When those controls are visible in daily operations, Right to Work becomes part of business continuity rather than a last-minute compliance scramble.
