Practical operating guidance

Make sponsor administration easier to follow.

Map the records, review tasks and handoffs behind your sponsor administration process. Software should support the responsible people with clear information and ownership.

This page preserves the administrative software topic of the former Sponsor Licence product page. A current standalone product, feature set or subscription is not confirmed. This is a software-scoping guide, not immigration advice or a promise of compliance, a licence or a visa outcome.

Discuss an administration workflow

Start with the current official requirements.

The government's employer guidance describes responsibilities around immigration-status monitoring, relevant documents, attendance, contact details and reporting to UKVI. The responsible organisation should use the current guidance that applies to its route and circumstances.

A software discussion should begin with the process your responsible team has established. It should not decide a person's immigration eligibility or substitute for advice from an appropriately authorised adviser where that is needed.

Define the record and its owner.

Identify which system holds the authoritative worker information and who is permitted to review or update it. Avoid creating a second record that silently drifts away from the one your team uses.

For each administrative task, specify what triggers review, which evidence is needed and what completion means. Dates and reporting requirements must come from the current applicable guidance and your approved process, not a hard-coded assumption in a generic template.

Record ownership: the person accountable for accuracy and follow-up.
Access: who can view, edit, approve or export the relevant information.
Evidence: where an authorised reviewer finds the supporting record.
Review tasks: the trigger, due date, escalation and completion evidence.
Handoffs: how the next responsible person acknowledges the action.

An illustrative review workflow.

A member of the HR team identifies an information change that needs review. A proposed workflow gathers the relevant reference, assigns a named reviewer and records the next action.

The authorised person checks the applicable requirement and carries out any necessary action through the appropriate official route. The internal record can then note who completed the task and where the evidence sits. This does not imply a direct UKVI or Sponsorship Management System integration.

Evaluate the workflow before relying on it.

Walk through one routine review and one overdue or incomplete task using synthetic information. Check whether the right person can find the record, recognise a missing item and escalate it.

Agree how corrections, account changes, retention and exports will be handled. The design should make uncertainty visible; a green status should not be presented as a legal determination.

Can each action be traced to a person and a source record?
Can restricted information be kept from people who do not need it?
Does an incomplete task remain visible to its owner?
Can the team correct a mistake without losing the history needed for review?
Does the process still work if a notification or integration fails?

Discuss the administration need.

Bring a high-level process description and the systems involved. Do not send worker passports, immigration documents or other sensitive records through the general website enquiry form.

We can assess a bounded software workflow separately from your legal and sponsorship decisions. Current delivery capability, integration feasibility, access controls and support arrangements are agreed for the specific project.

Start with your
actual requirement.

Tell us the work, people and outcome you have in mind. We’ll confirm current scope and availability before agreeing the next step.