← Insights

Compliance

Right-to-work records that do not quietly lapse

July 2026 · 6 min read

Before we go a word further, one thing needs saying clearly, because it is the whole frame for what follows. The tool described here is a record-keeping and reminder register. It is not the right-to-work check itself, it is not legal verification of anyone's right to work, and it is not immigration or employment-law advice. What it does is much narrower and genuinely useful: it makes sure the records you keep stay organised and that the follow-up dates you need to watch do not slip past you.

With that established, here is the problem it actually solves.

The check is only half the job

Most attention goes to the moment of hiring - carrying out the check correctly on day one and keeping dated evidence of it. That part matters enormously, and nothing here replaces it. But for a large share of the workforce the check is not a one-off. Where someone's right to work is time-limited - tied to a visa, a status document or a share code with an expiry - the record has a shelf life, and the second half of the job is re-checking before that shelf life runs out.

This is precisely where organisations get caught out. The original check was done properly, filed, and then forgotten, because nothing was watching the expiry date. Months later a document has quietly lapsed and nobody noticed until it was already a problem. The failure is not carelessness at the point of hiring; it is the absence of a diary that looks ahead.

The check is a moment. The record is a lifecycle. Time-limited documents need re-checking, and that only happens if something is watching the date.

A register that watches the dates for you

The fix is a register that turns each record into a live countdown rather than a filed-and-forgotten line. Record an employee's document check once - the document type, the date of the check, and either an expiry date or a re-check interval for a time-limited status - and the follow-up date works itself out. Days-to-due then count down on their own, so the next action is always visible instead of buried in a folder.

Status decides itself from those dates. A British or Irish passport, or another continuous statutory excuse, sits as Permanent and needs no clock. A current time-limited document reads Valid. As the window narrows it turns amber for Due soon, and once the date has passed it turns red for Expired. You are no longer interpreting a column of dates; the register has already told you where to look.

The single most useful output is a due-soonest list, with anything expired surfaced at the top. That is the working list - it tells you exactly whose re-check to repeat next, in the right order, so the follow-ups get worked before the window closes rather than after.

What the tool does, and firmly does not, do

It is worth restating the boundary in concrete terms, because a register like this is easy to over-trust. It organises your records and diaries your re-checks. It does not verify anyone's right to work, it does not establish or maintain your statutory excuse on its own, and a green cell in a spreadsheet is not evidence of anything - the evidence is the correctly conducted check and the dated proof you keep of it.

So the responsibilities stay exactly where they belong. You still carry out each check correctly, following current Home Office guidance, and you still keep proper dated evidence. Document types, rules and timescales change, and they vary by circumstance, so nothing here is a fixed standard to lean on. What the register adds is a reliable memory: it makes sure the checks you are responsible for are not undermined by a re-check date that nobody was watching. Where any of this raises a real question, that is a matter for professional HR or legal advice, not for a template.

And it is personal data

One more thing follows from all of this. The information in a right-to-work register - names, nationalities, document details, status - is personal data, and some of it is sensitive. It has to be handled in line with UK GDPR and your own data protection obligations: kept securely, seen only by those who need it, and retained no longer than you have a proper basis for. A register that keeps this data tidy makes that easier, but the obligation is yours, not the file's.

Used within those limits, the value is simple and real. You keep doing the checks properly; the register makes sure none of the records you rely on lapses quietly in the background - which is the one failure that good hiring practice, on its own, does not prevent.