Confirmation statement: a filing about what is already true
The confirmation statement does not update the register — it confirms it. Anything that actually changed has to be filed separately, and usually first.
A right to work check gives an employer a statutory excuse only if it was done correctly, before employment started, and recorded with a date.
A right to work check is the employer’s verification that a person is legally permitted to do the job on offer. In the UK it is what gives an employer a statutory excuse against a civil penalty if an employee later turns out not to have permission — and the excuse depends entirely on the check having been done properly, before employment began, and evidenced.
The point worth internalising is that the excuse is procedural. An employer who genuinely believed someone had the right to work, but cannot show a compliant check, is in the same position as one who never asked. Getting the record right is not administration around the decision; it is the protection itself.
The share code route causes most of the confusion. A code supplied by the candidate is not the check; it is the input. The employer enters it with the person’s date of birth, obtains the profile, confirms the photograph matches, and keeps the result. A forwarded screenshot proves nothing about who looked at what.
Checking only people who look or sound foreign is discrimination, and it is also worse compliance: the excuse depends on a consistent process. Check everyone, in the same way, and let the record show it.
Time-limited permission is where good employers still fail. The initial check is done carefully; the expiry date lands two years later, by which time the recruiter has moved on and the record sits in a folder nobody opens. A repeat check performed after expiry does not restore the excuse for the intervening period.
The fix is not vigilance, it is a diary entry attached to the record at the moment the check is made. Ettex Records keeps the check, the evidence and the expiry date as one item with a reminder against it, so the follow-up exists as a scheduled obligation rather than as something a person is supposed to remember. Fitting the check into the employee onboarding checklist keeps it before day one rather than after it.
Before the person begins work. A check performed after employment has started does not provide the statutory excuse for the period before it.
The code can be received any way, but the employer must use it on the official service themselves, view the profile, and confirm the photograph matches the person. Retaining only a candidate-supplied screenshot is not a compliant check.
For the duration of employment and for two years afterwards, in a format that cannot be altered, with the date of the check clear.
Only where their permission is time-limited — then a follow-up check is required before it expires. Employees with permanent status do not need repeat checks.
The confirmation statement does not update the register — it confirms it. Anything that actually changed has to be filed separately, and usually first.
Whether a dismissal holds up rarely turns on what the employee did. It turns on whether the employer investigated, informed and heard them before deciding.
A batch record is filled in as the work happens, not afterwards. Everything about how it is designed follows from that one requirement.