BookKeptevidence chain
Documentation

Right-to-work records

A right-to-work check establishes a statutory excuse only if it was done properly and can be shown. The record therefore holds the method, the evidence, the date it was checked and the date it needs checking again.

The three methods

Evidence uploaded against a check is stored with a retention category and a retention date, because the Home Office employer's guide expects it kept for the duration of employment plus two years and no longer.

Recheck dates

A check on time-limited permission carries a recheck date. The compliance screen surfaces what is due, and the change radar counts anyone whose recheck falls after a statutory change as exposed to it.

1 October 2026

SI 2026/700 renames IDSPs to right-to-work DVSPs, requires the facial-image record to be held for a digital check, and adds a supply-chain statement.

Both fields exist on the record already and both are nullable, because a check recorded before the duty existed did not fail to answer it: it was never asked. From the effective date, a digital check without a facial-image record is refused rather than stored as complete, since filing it as done would tell an agency it is covered when it is not.

None of that is a release. The duties arrive because a rule pack dated 1 October 2026 becomes the answer on that day. The guide sets out the change itself.

What the change radar does with it

The radar pairs each dated change with your own exposure: for right to work, the workers with no check on file at all, plus those whose recheck falls due on or after the effective date. It names them, rather than telling you a change is coming and leaving you to work out who it touches.

See it working

Who this change actually touches

The demo agency is exposed to the October change through two named workers. Open compliance and look at what is changing.

Have it set up for you