A missing share code, an unreadable passport copy or a visa follow-up date buried in a spreadsheet can turn a routine new-starter task into a serious employment risk. Right to work check software gives HR teams a controlled way to collect evidence, record the check and make sure temporary permission to work is reviewed at the right time.

The distinction matters. Software can organise the process and create an auditable record, but it does not remove an employer’s responsibility to carry out the prescribed right to work check correctly. For organisations hiring at volume, across several sites or into deskless roles, that control is often the difference between a repeatable onboarding process and a collection of inboxes, paper copies and individual manager habits.

What is right to work check software?

Right to work check software is a system that supports employers in verifying, recording and managing an individual’s right to work in the UK. It typically forms part of recruitment, onboarding or core HR software rather than operating as an isolated compliance spreadsheet.

Its job is practical: request the right information from the candidate, route documents to the person responsible for checking them, store a dated record and trigger follow-up actions where a worker has time-limited permission. A well-configured system also keeps the evidence against the employee record, rather than leaving it in a recruiter’s email folder or a shared drive with uncertain access controls.

In the UK, employers must carry out checks before employment begins to establish a statutory excuse against a civil penalty. GOV.UK sets out the acceptable routes, which can include a manual document check, an online right to work check using a share code, or an Identity Document Validation Technology check for eligible British and Irish citizens through an appropriately certified identity service provider. The correct route depends on the worker’s circumstances and documents.

That is why the best software is not simply a document upload tool. It should guide a defined workflow while leaving HR able to apply judgement when documents, eligibility or timing need closer review.

What the software should record

A defensible process needs more than a tick box saying that a check took place. HR should be able to show what was checked, how it was checked, who completed the task and when.

For an online check, the employer must use the Home Office online service with the individual’s share code and date of birth, then retain a clear copy of the profile confirming the right to work and the date the check was made. For a manual check, the employer needs to obtain original acceptable documents, check their validity in the holder’s presence and retain a clear copy marked with the date of the check. Requirements can change, so teams should use current GOV.UK guidance when setting their process.

Right to work check software should therefore be capable of attaching evidence to the employee record, recording completion dates and allocating responsibility. It should also distinguish between a candidate providing a document and an authorised employee completing the employer’s check. Those are different actions, and treating them as one creates avoidable gaps.

For time-limited workers, the system should capture the follow-up date and create an action before that date arrives. An expiry date is not a reminder strategy. The useful outcome is a named task, visible ownership and an escalation path if evidence is not supplied.

Where manual processes fail

A spreadsheet can hold names and expiry dates. It rarely controls the process around them. The problem becomes sharper when recruitment, HR, payroll and site management all hold parts of the record.

Consider a facilities business onboarding cleaners across multiple client locations. A recruiter may receive a share code, a people administrator may save the result, and an operations manager may schedule the worker. If the check is incomplete or the evidence is stored inconsistently, the worker could be assigned before HR has finished the required action.

The same issue affects care providers, construction firms, logistics operators and hospitality groups. High turnover and decentralised hiring create more handovers. More handovers create more opportunities for a task to be assumed complete when it is not.

A structured system reduces this risk by making right to work a condition within onboarding. The employee cannot be progressed to the next agreed stage until the required task is completed, or an authorised person records an exception. It also gives HR a single view of outstanding checks, upcoming follow-ups and missing information by site, manager or employing entity.

Choosing right to work check software for UK employers

Start with the workflow, not a feature checklist. Map how a candidate moves from offer to payroll and first shift. Then identify who requests evidence, who is permitted to verify it, what happens when information is incomplete and how a temporary right to work is monitored.

A suitable system should support four connected outcomes:

Beyond those basics, assess whether the system fits the rest of your people operation. If payroll data is prepared in a separate platform, for example, the workflow should make clear when a worker is approved to move forward. If recruitment is managed through an applicant tracking system, the right to work task should transfer into onboarding without rekeying candidate details.

For larger organisations, configuration matters. Different entities may have different approvers, locations or hiring pathways. A central policy can still be applied consistently, but the route to completion may need to reflect local operations. An office-based employee joining next month is not processed in the same way as a field engineer needed on a client site next week.

Automation helps, but it is not the decision-maker

Automation is valuable when it removes predictable administration: sending a request, chasing an overdue item, creating an employee record, filing evidence and notifying HR of a follow-up date. It creates consistency without asking HR to monitor every open task manually.

It should not be positioned as an automatic legal decision. A system cannot make an uncertain document acceptable, interpret a complex immigration status without the appropriate information, or substitute for the employer completing the required check. Where there is doubt, HR should pause the workflow and follow current Home Office guidance or seek specialist advice.

This is also where specialist AI can be useful when used carefully. An AI document agent can perform defined administrative work such as extracting information from supplied files, classifying documents and routing incomplete records for review. It is not a replacement for the person accountable for the right to work check. The value lies in reducing repetitive handling while preserving an explicit human approval point.

Data protection and access need equal attention

Right to work evidence contains personal data, and often identity information that should not be available to every manager. The ICO’s data protection principles are relevant here: collect only what is necessary, keep it secure, restrict access and retain it only for an appropriate period.

Ask potential suppliers how role-based permissions work, whether audit histories show changes to records and how documents are separated by entity or team. Also consider deletion and retention workflows. A process that stores every document indefinitely because nobody owns the review is not good information governance.

For organisations with mobile and deskless teams, it is worth separating right to work compliance from attendance evidence. Verified time or location data may help resolve operational questions about presence at a site, but it does not prove an employee’s immigration status. Each record has a different purpose and should be handled accordingly.

Making the process work in practice

The strongest implementation is usually simple. Define one policy, configure the available checking routes, nominate authorised checkers and test the workflow using real hiring scenarios. Include a British citizen, an Irish citizen, an individual using a share code and a worker with a time-limited right to work. Testing these paths exposes unclear ownership before a live vacancy does.

Sense HR can support this wider workflow by bringing recruitment, onboarding, employee documents, automation and reporting into one UK-focused HR platform. Rather than treating a right to work record as a static file, HR can assign the action, store its evidence against the employee record and manage follow-up work alongside the wider onboarding journey.

FAQs

Can right to work check software carry out the check for us?

No. Software can collect documents, guide the approved process, record actions and send reminders. The employer must still complete the relevant prescribed check and retain the required evidence. Where an external identity service provider is used for an eligible IDVT route, confirm that its service and certification meet the applicable requirements.

Do we need to repeat every right to work check?

No. Follow-up requirements depend on the individual’s right to work and the evidence used. Workers with time-limited permission generally require a further check before their permission expires. Build this into the employee record rather than relying on a manager’s calendar reminder.

Can managers see right to work documents?

Only if they need access for a defined role in the process. Restricting permissions protects sensitive personal information and helps maintain a clear audit trail of who handled the evidence.

Is right to work checking the same as a DBS check?

No. They serve different purposes. A right to work check confirms eligibility to work in the UK. A DBS check relates to criminal record information and may be required for particular roles. Both can sit in an onboarding workflow, but they need separate policies, evidence and retention controls.

A good process gives HR more than a completed task. It gives the organisation a clear answer to a simple operational question: can this person start work, and can we prove the checks were handled correctly?