Right to work checks as an operational system

Right to work checks in the UK are an operational process. An employer needs a clear record of what was checked, when it was checked, and when the file needs to be looked at again. That is a systems problem as much as a people problem.

This article is not legal advice. It does not tell an organisation how to decide a person’s status. It describes why right to work work breaks down when the only “system” is an inbox and a shared drive. Roy & Associates Limited is a technology group looking at this as software. Related products under the group are still in development and are not a public service yet.

What the process actually needs

A usable record answers four questions. Who is the person. What evidence was seen. When was it seen. What happens next, including a date for review if the file is time-limited. If any of those are missing, the organisation is reconstructing history from memory.

Why spreadsheets fail

Spreadsheets do not keep a trustworthy audit trail. They do not control who can edit a row. They do not remind anyone when a date arrives. Right to work files that live in email attachments have the same weakness: the document exists, the process does not.

Software, not a verdict

Software in this space should store the operational record. It should not pretend to be a government decision. The useful product is the one that keeps the file complete, dated, and restricted to the people who need it. That is the same discipline as any other UK HR system: records first, then workflow.

How this group talks about the work

StaffDock is the group’s product in this area, and it is live at staffdock.co.uk. It keeps the record of right to work checks; the business still carries out the checks itself, in the way the Home Office allows.