How to track sponsored-worker visa expiry dates

Keep the different dates separate

A passport expiry, Certificate of Sponsorship end date, immigration permission expiry and Right to Work follow-up date describe different things. A single spreadsheet column labelled “visa date” hides those differences. Give each date its own field and record the source from which it was taken.

Choose an internal review date early enough for your team to assess the situation and obtain advice where needed. That date is an operational reminder, not a legal extension deadline. Do not assume that a reminder or a pending task extends somebody’s permission to work.

• Worker identifier and current work location
• Immigration route and permitted work restrictions
• Permission expiry and source evidence
• Last Right to Work check and next required follow-up
• Internal review date, action owner and escalation contact
• Action taken, evidence link and date of review

Use a queue that ends with evidence

Review upcoming dates in a shared action queue. For each item, identify whether the current evidence is sufficient, whether a new check is due and who needs to act. Keep the resulting document or online check output against the worker record so another authorised colleague can understand what happened.

An email sent is not the same as an action completed. Close a task only when the relevant check or administrative action is recorded. If a worker changes role, hours or location while an expiry task is open, review both issues together rather than allowing separate spreadsheets to contradict each other.

Handle exceptions by the actual check route

Follow-up requirements depend on the person’s status and the prescribed checking route. The Home Office no longer requires repeat checks for holders of EUSS pre-settled status after a correctly completed initial check. An outstanding application is a different situation; use the official guidance to determine when the Employer Checking Service is needed.

Where a Positive Verification Notice is used, record the date and period stated on the notice and schedule the next action accordingly. Escalate uncertainty before a deadline instead of changing the date in the tracker without supporting evidence.

Review the process using a worked example

Illustrative workflow: a compliance administrator reviews an upcoming permission expiry, confirms the stored check result and allocates the next action to the responsible manager. The manager obtains the relevant information and the administrator records the new evidence and any required follow-up. A second authorised colleague can then see both the original alert and its resolution.

In LuwaSuite, employee records, document expiry tracking, Right to Work evidence and compliance views support this connected workflow. During a demo, ask to follow one test worker from an expiry reminder through to the recorded evidence. This is more informative than counting the number of alert emails a product can send.

A weekly review your team can sustain

Filter for due and overdue actions, inspect items without an owner, and sample recently closed tasks. Check whether cover arrangements work when the usual administrator is absent. A small, repeatable review is easier to maintain than a large clean-up just before an inspection.

Keep access limited to the colleagues who need the records. Review retained information against your retention policy and applicable sponsor and employment requirements; a tracker should not become an unrestricted archive of identity documents.