DEV Community: ImmigrationGPT

ILR 2026: A Technical Reference for HR Systems Handling Settled Status Applications

ImmigrationGPT — Fri, 17 Jul 2026 08:11:23 +0000

HR teams and immigration compliance tools face a specific challenge with ILR: the eligibility criteria are deterministic in theory, but the inputs — travel records, visa dates, absence windows — are often held in fragmented or self-reported systems. This post breaks down the ILR rules from a data and compliance implementation perspective.

Core Eligibility Conditions

For standard ILR under the Skilled Worker or equivalent qualifying routes, the logic looks like this:

ELIGIBLE = (
  qualifying_leave_years >= 5 AND
  max_absences_in_any_12_month_window <= 180 AND
  english_language_requirement_met == TRUE AND
  life_in_uk_test_passed == TRUE AND
  no_disqualifying_criminal_record == TRUE AND
  continuous_lawful_residence == TRUE
)

Each input requires its own validation logic. The most complex is the absence calculation.

Absence Calculation: Rolling 12-Month Window

The 180-day rule applies to any 12-month period within the qualifying residence — not the calendar year. Computing the maximum across all possible rolling windows:

from datetime import date, timedelta

def max_absences_in_any_window(
    absences: list[tuple[date, date]],
    qualifying_start: date,
    qualifying_end: date
) -> int:
    max_days = 0
    current = qualifying_start
    while current <= qualifying_end:
        window_end = current + timedelta(days=365)
        days_absent = 0
        for departure, return_date in absences:
            overlap_start = max(departure, current)
            overlap_end = min(return_date, window_end)
            if overlap_end > overlap_start:
                days_absent += (overlap_end - overlap_start).days
        max_days = max(max_days, days_absent)
        current += timedelta(days=1)
    return max_days

The data source for this calculation is typically passport stamps (manual, error-prone) or self-reported logs from the employee. UKVI has access to e-Gates records, which are more complete. If an employee underreports absences, any HR statement that contradicts UKVI's records creates additional complications.

Continuous Residence: Handling Visa Gap Periods

A common edge case: what happens when a visa expiry date and the grant date of the subsequent visa have a gap?

UKVI guidance (updated March 2024) allows gaps of under 28 days to be disregarded if the gap resulted from administrative delay — not from the applicant's failure to apply in time. This condition is discretionary, not automatic.

For any compliance tracking system, flag any gap > 0 days between qualifying leave periods for manual review. Do not auto-approve continuous residence calculations where gaps exist.

Leave Category Validation

Not all UK leave counts toward the ILR qualifying period. Qualifying: Skilled Worker, Intra-Company Transfer, Global Talent, Tier 1, Tier 2, certain Tier 5, family visas.

Non-qualifying leave that trips people up: Visitor leave, Student leave on non-qualifying courses, Leave Outside the Rules, and any period on an expired visa where Section 3C extension is not in force.

If your system tracks leave by visa label rather than underlying route, you may be miscategorising historic Tier 5 and pre-2021 EU cases.

English Language Evidence: Key Validation Fields

Field	Requirement
Test provider	On UKVI's SELT approved list at time of testing
Test centre	UKVI-approved at time of testing
Test date	Within validity window at submission
Score	CEFR B1 or above, all four components

One error to watch for: certificates from centres that have since lost UKVI approval. A test taken when the centre was approved remains valid — but cross-reference historical approval records, not the current list.

Degrees taught in English satisfy the requirement only if from a majority English-speaking country on the UKVI list — which does not include India, Pakistan, Nigeria, or South Africa.

Life in the UK Test: Integration Points

The test certificate is linked to the identity document used at time of sitting. Key constraints:

The reference number must be used within its validity period
The identity document used at the test must match the one on the ILR application
If the applicant has renewed their passport since sitting the test, a matching declaration may be required

UKVI verifies reference numbers directly against the test provider's records.

Criminal Record: Compliance Logic

Disqualifying record = any custodial sentence of 12 months or more (regardless of time actually served). Shorter sentences fall under discretionary bad character grounds.

For compliance workflows:

Any conviction declared in a prior visa application must be consistently reported in ILR
Inconsistency between prior declarations and current application = potential deception finding
Non-UK convictions carry equal weight; international criminal record certificates may be required

Common Errors in HR Immigration Tracking

Calendar-year absence totals instead of rolling 12-month windows — systematically underestimates breach risk
Treating all leave as qualifying — visitor and student leave don't count
Not tracking biometric enrolment status — unenrolled biometrics stall identity verification
Treating English test certificates as permanent — they have validity windows relative to application date
Relying on employee self-declaration for absences without cross-checking HR travel records

Reference Tools

For quick checks on whether an employer holds a current sponsor licence, and for plain-English breakdowns of ILR and Skilled Worker rules, ImmigrationGPT provides a searchable interface over the 125,000+ employer sponsor register and structured summaries of UKVI guidance.

Disclaimer: This post is for informational purposes only and does not constitute legal advice. UK immigration rules change frequently. Consult a qualified immigration solicitor or OISC-regulated adviser for case-specific guidance.

UK Spouse Visa 2026: What Happens Between Submission and Decision, and Where Applications Actually Fall Apart

ImmigrationGPT — Fri, 17 Jul 2026 08:10:31 +0000

Most spouse visa content covers the financial requirement and stops there. That's the wrong place to focus if you're an HR team, a caseworker, or an applicant trying to figure out why an otherwise-strong application got refused. The £29,000 threshold (rising in staged increases toward £38,700, with the Home Office having paused the final jump pending review) is easy to check against a payslip. The part that actually trips people up is everything that happens after the biometrics appointment — and the evidence bundle decisions made weeks before submission.

The timeline nobody tells you about

UKVI's published service standard for spouse visa applications made outside the UK is 12 weeks, and for in-country switching applications it's 8 weeks. Those numbers are almost never what happens. Priority and super-priority services (24-hour and 5-day, for an extra £573 and £1,000 respectively) exist precisely because standard processing routinely runs past the headline figure, especially for applications from certain visa post regions where document verification takes longer.

Here's what the 12 weeks actually contains: roughly 1-2 weeks for the application to be picked up and biometrics scheduled, 2-4 weeks for the case to reach a caseworker's desk, and then the rest is verification — of the relationship, of the financial evidence, sometimes a request for further information (an RFI) that resets part of the clock. An RFI isn't a red flag by default. It's routine when bank statements don't cover the full specified period or when a document is in a format the caseworker can't fully verify.

For HR teams managing relocations, the practical implication is: don't build offer letters or start dates around the 12-week figure. Build them around 16-20 weeks and treat anything faster as a bonus. Compliance systems tracking employee dependants should flag spouse visa applications at week 10 for a status check rather than waiting for week 12 to discover an RFI is sitting unanswered.

Where the evidence bundle actually breaks

The financial requirement gets simplified into "£29,000 salary" in almost every explainer, which erases the actual complexity. If the sponsoring partner is employed, salaried income needs 6 months of payslips plus a letter from the employer confirming the role, salary, and length of employment — and the letter has to match the payslips exactly, including job title. Mismatches between what the letter says and what the payslips show are one of the most common reasons for refusal, and they're entirely avoidable with a five-minute cross-check before submission.

If the couple is relying on savings instead of income (Category D or E, depending on combination), the money has to have been held for 6 months and the source needs to be traceable. Recent large deposits without a paper trail — an inheritance, a property sale, a gift from family — get flagged almost automatically, because the rules assume savings should show a stable balance, not a spike.

Self-employment income (Category F/G) is the messiest category by volume of refusals. UKVI wants the most recent full financial year's accounts, but if the business is under 12 months old, or the accounting year doesn't align neatly with the 6-month evidence window, applicants end up submitting a mix of tax returns, SA302s, and accountant's letters that don't tell a consistent story. If you're advising on this, the fix isn't more documents — it's fewer documents that tell one coherent number.

The relationship evidence trap

Financial refusals get the attention, but genuine-relationship refusals are just as common and harder to fix after the fact. Couples who've been together for years sometimes submit thin evidence because they assume a marriage certificate and a joint bank account cover it. UKVI wants to see the relationship's history: how it started, how it's been maintained across any periods of separation, and how it continues day to day. A cohabitation history spanning two years but with only three months of joint utility bills invites scrutiny that a fuller paper trail would have avoided.

The part that matters most for HR: the route to ILR

A spouse visa is granted for 2 years and 9 months initially, then extended for another 2 years and 6 months, with Indefinite Leave to Remain available after a total of 5 years — assuming continuous residence and no gaps. Each extension is a fresh application with its own evidence requirements, which means the financial and relationship evidence checks aren't a one-time hurdle. HR systems tracking dependant visas need renewal reminders built in at year 2, not year 5, because a lapsed extension application creates the same compliance exposure as a lapsed sponsor licence check.

There's also a 5-year continuous residence rule for ILR that resets if the applicant spends more than 180 days outside the UK in any 12-month rolling period. That's a detail that gets missed constantly by people who assume the clock only matters at the very end.

Full guidance and current thresholds are at immigrationgpt.co.uk, where you can also check sponsor status and get a plain-English read on specific evidence scenarios.

This article is for general information only and doesn't constitute legal or immigration advice. Rules change — always verify current requirements against official GOV.UK guidance or a qualified immigration adviser before making decisions.

UK Spouse Visa 2026: What Happens Between Submission and Decision, and Where Applications Actually Fall Apart

ImmigrationGPT — Thu, 16 Jul 2026 08:14:57 +0000

The timeline nobody tells you about

Where the evidence bundle actually breaks

The relationship evidence trap

The part that matters most for HR: the route to ILR

Full guidance and current thresholds are at immigrationgpt.co.uk, where you can also check sponsor status and get a plain-English read on specific evidence scenarios.

UK Global Talent Visa 2026: A Technical Breakdown of Endorsement Routes, Eligibility Criteria, and Compliance Implications

ImmigrationGPT — Wed, 15 Jul 2026 08:09:11 +0000

If you're building HR tooling, immigration compliance software, or advising international talent on UK visa options, the Global Talent visa is one of the more nuanced routes to model correctly.

Unlike the Skilled Worker visa — which has clear salary thresholds, SOC codes, and sponsor licence lookups you can query — the Global Talent route is fundamentally qualitative. But there's useful structure underneath it, and understanding that structure makes the difference between useful tooling and misleading advice.

Here's a technical breakdown of the route as it stands in 2026.

The Route Architecture

The Global Talent visa sits outside the standard Points-Based System in one important way: it doesn't require a sponsor. There's no sponsor licence check, no Certificate of Sponsorship, no salary threshold calculation. The Home Office is not the first gatekeeper — the endorsing body is.

The official endorsing bodies in 2026 are:

Sector	Endorsing Body
Digital Technology	DCMS / designated endorsing partners
Science & Engineering	Royal Society, Royal Academy of Engineering
Humanities & Social Sciences	The British Academy
Arts & Culture	Arts Council England
Research & Innovation	UK Research and Innovation (UKRI)

Each body has its own application portal, its own evidence schema, and its own SLA. There is no unified interface or shared API across these bodies.

Two Assessment Tracks

Every endorsing body uses a dual-track assessment:

Exceptional Talent — applicant is already a recognised leader in their field
Exceptional Promise — applicant shows credible potential to become one

The criteria differ not just in stringency but in the type of evidence weighted. For Exceptional Talent, the focus is on demonstrated outcomes: awards, senior positions, publications with measurable impact, industry recognition. For Exceptional Promise, trajectory and quality of recent projects carries more weight.

This distinction matters if you're building tooling that helps users self-assess eligibility. Mapping "years of experience" to track is a mistake — the tracks are about career stage relative to field norms, not arbitrary time thresholds.

The Two-Stage Application Flow

The process involves two distinct applications with different target bodies:

Stage 1 — Endorsement

Submitted to the relevant endorsing body (not UKVI)
Includes: personal statement, CV, supporting evidence, mandatory recommendation letter
Processing SLAs: UKRI averages ~8 weeks; arts/culture similar; tech route has shown more variability historically
Outcome: endorsed or rejected (re-application possible with new evidence)

Stage 2 — Visa Application

Submitted to UKVI after receiving endorsement
Must be submitted within 3 months of endorsement
Standard processing: ~3 weeks
Biometrics required

For timeline modelling, the endorsement stage is the variable constraint. Stage 2 is fairly predictable.

Evidence Schema

While each body has specific requirements, the common evidence categories across the route are:

Mandatory:
  - Minimum 2x recommendation letters from independent senior practitioners
    (NOT colleagues, NOT direct employers)

Supporting (select most relevant):
  - Published works / patents / open-source contributions
    → With: citations, download metrics, adoption data, fork counts
  - Awards and fellowships
    → With: evidence of selection criteria, not just the award
  - Senior positions at recognised organisations
    → With: role scope, team size, org recognition
  - Income evidence
    → At a level consistent with recognised practitioners in the field
  - Media coverage
    → Substantive editorial coverage, not just name mentions or press releases

Volume of evidence is not correlated with success rate. Applications with 3–5 strong, well-evidenced items consistently outperform those with 15+ weak items.

Post-Grant Entitlements — HR Compliance Implications

Once the visa is granted, the Global Talent holder has significantly more flexibility than a Skilled Worker:

Parameter	Global Talent	Skilled Worker
Employer restriction	None	Must work for sponsoring employer
Self-employment	Permitted	Restricted
Multiple employers	Permitted	Not permitted without separate permission
Job-change notification	Not required	Requires sponsor action / CoS
ILR eligibility	3 years (ET) / 5 years (EP)	5 years

For HR/compliance systems: Global Talent visa holders cannot have their right-to-work status affected by changes in employment. Their visa is entirely decoupled from any employer. Right-to-work verification procedures are identical (Share Code check), but employment change events do not trigger any compliance obligations.

ILR Timeline Calculation

# Simplified ILR eligibility calculation
def ilr_eligible_date(visa_grant_date, track):
    from datetime import timedelta

    years = 3 if track == "exceptional_talent" else 5
    days = years * 365  # approximate; continuous residence rules apply
    return visa_grant_date + timedelta(days=days)

Note: continuous residence rules apply. Absences exceeding 180 days in any 12-month period can break the continuous residence requirement. This is the same rule that applies to all settlement routes.

The Digital Technology Route — Current State (2026)

Tech Nation's endorsement functions were transferred in 2023 to a DCMS-led arrangement with designated endorsing partners. If you're referencing documentation written before 2024 — including many dev blog posts and immigration firm guides — the process described may no longer be accurate.

In 2026, the tech endorsement route operates under the new partnership model. Key criteria remain: demonstrated leadership in digital technology, evidence of innovation or technical contribution, or a track record of growing and leading teams in the sector.

What You Can Reliably Automate

✅ Routing users to the correct endorsing body based on sector input
✅ Surfacing the relevant evidence criteria for their selected track
✅ Calculating ILR eligibility dates post-grant
✅ Flagging Share Code requirement for right-to-work verification
✅ Alerting on the 3-month window between endorsement and visa application

❌ Predicting endorsement outcome from CV data alone
❌ Assessing which track (ET vs EP) an individual should apply for without expert review

For structured access to current GOV.UK immigration data, eligibility logic, and plain-English policy explanations across all UK routes, ImmigrationGPT provides an AI-powered interface to official guidance.

This article is for informational purposes only and does not constitute legal advice. Always verify against current GOV.UK guidance before building compliance tooling or advising applicants.

UK Sponsor Licence Register 2026: Status Codes, Data Fields, and Building a Verification Workflow

ImmigrationGPT — Tue, 14 Jul 2026 08:06:27 +0000

UK Sponsor Licence Register 2026: Status Codes, Data Fields, and Building a Verification Workflow

When a candidate asks your HR team "are you actually licensed to sponsor me?", the right answer isn't "we'll check with legal." It should be something your compliance systems can answer in seconds. Here's a complete reference for reading the UK Register of Licensed Sponsors and building verification into your hiring workflow.

What the Register Contains

The Home Office publishes the Register of Licensed Sponsors as a downloadable CSV at gov.uk. The file is updated on every working day and contains every organisation currently holding an active licence. There's no pagination to navigate — it's a flat file you can pull, parse, and index.

Key fields in the CSV:

Field	What It Means
Organisation Name	Legal entity name, not necessarily trading name
Town/City	Registered office location
County	County of registered address
Type of Sponsor	`Worker`, `Student`, or both
Route	Specific routes the licence covers (Skilled Worker, Intra-Company, etc.)
Rating	`A-rated` or `B-rated` (see below)

Licence Ratings: A vs B

This is the field most compliance tools overlook.

A-rated sponsors are fully compliant. They can issue Certificates of Sponsorship (CoS) freely for any role that meets the standard eligibility criteria.

B-rated sponsors have had compliance concerns identified. They're still licensed, but they're operating under a specific action plan agreed with the Home Office. Critically, B-rated sponsors cannot sponsor new workers until they return to A-rating or receive specific permission. If your hiring system only checks for presence in the register without checking rating, you may generate a CoS you cannot legally issue.

A licence can move between A and B rating — and ratings are reflected in the daily CSV update, so a polling-based sync will catch these changes.

When Absence Means Denial

A company not appearing in the register holds no active licence. The Home Office doesn't publish a list of revoked or expired licences, so absence is definitive: the company cannot currently sponsor visas.

Common reasons a previously-listed company disappears:

Licence voluntarily surrendered
Licence revoked by the Home Office following non-compliance
Licence expired (rare — licences are typically indefinite once granted, but can lapse if renewal requirements aren't met)
Corporate restructuring — the legal entity changed

If you're building a system that tracks sponsoring employers over time, capturing licence presence by date lets you detect when an employer leaves the register and trigger compliance alerts.

Building a Verification Workflow

A production-grade sponsor verification check should include:

1. Entity name normalisation
The register uses exact legal entity names. "NHS Foundation Trust" and "NHS Trust" can refer to different entities. Fuzzy matching on company names against Companies House data is the most reliable approach. Match on company registration number where possible.

2. Presence check
Is the organisation in the register at all? Boolean. Log with timestamp.

3. Route validation
Does the licence cover the specific route needed? A company licensed only for Intra-Company Transfers cannot issue a standard Skilled Worker CoS. Validate the requested route against the Route field.

4. Rating check
Is the sponsor A-rated or B-rated? If B-rated, your workflow should pause and escalate rather than auto-proceed.

5. Freshness
How old is your local copy? The Home Office updates the register daily. If your cached data is more than 24 hours old at the time of check, re-fetch before making a decision.

6. Periodic re-checks
For active sponsored employees, re-check their employer's licence status at a cadence matching your compliance obligations (typically monthly). If a licence is revoked, the 60-day countdown for the sponsored worker begins immediately — your HR system should fire an alert the same day.

Where This Fits in the Hiring Pipeline

Sponsor verification should fire at two points:

At offer stage: Confirm the hiring entity holds the correct licence type and rating before extending a conditional offer to a candidate who will need sponsorship. This avoids offers that can't legally be fulfilled.

At CoS generation: Re-validate immediately before generating a Certificate of Sponsorship. Don't rely on the offer-stage check being recent enough.

Tools like ImmigrationGPT surface sponsor register data in plain English, which is useful for candidates doing their own verification — but for internal HR systems, direct register integration gives you the auditability and freshness control you need.

Edge Cases Worth Handling

Large employer groups: Umbrella organisations with multiple sub-entities may have licences across several legal entities. A candidate's offer letter may reference a trading name that differs from the licensed entity. Build in an entity lookup step.
Healthcare and education: Many NHS trusts, universities, and schools hold Worker licences. These sectors also have higher-than-average incidence of B-rating due to compliance complexity at scale.
Sponsor licence pending: Some employers will say they're "in the process of applying." Licence applications take a minimum of eight weeks. Your system should not assume a pending application will be granted, and should not generate any CoS on its basis.

This post is for informational and technical reference purposes only. UK immigration rules are subject to change. For compliance decisions, consult a qualified immigration adviser or solicitor registered with the OISC.

UK Skilled Worker Visa Salary Thresholds 2026: Building Compliant Eligibility Logic Into HR Systems

ImmigrationGPT — Mon, 13 Jul 2026 08:09:35 +0000

For HR platforms, payroll tools, and compliance systems dealing with UK immigration, salary threshold logic is one of the trickiest areas to implement correctly. The rules have layers, exceptions, and a dependency on occupation classification data — making naive implementations a common source of compliance failures.

This post is a technical walkthrough of how the threshold system works and what your systems need to account for.

The Two-Test Model

Every Skilled Worker visa salary eligibility check reduces to a max of two independent tests:

salary_floor = max(general_threshold, going_rate_for_soc_code)
eligible = candidate_salary >= salary_floor

That's the core logic. The complexity is in how general_threshold and going_rate_for_soc_code are correctly determined.

General Threshold Values

There are two tiers, effective from April 2024:

Category	Annual Threshold
Standard	£38,700
New entrant	£30,960

A worker qualifies as "new entrant" if they meet any of:

Under 26 at time of application
Currently on a Student or Graduate visa switching to Skilled Worker
In a role that is a recognised training or apprenticeship position
Within four years of their first Skilled Worker visa grant in this category

The new entrant status expires after four years — at which point the full going rate for the occupation must be met. If your system tracks visa holders over time, this transition needs to be surfaced proactively.

Going Rate Data Source

Going rates are tied to Standard Occupational Classification (SOC) codes, published under the SOC 2020 taxonomy. Your system needs to:

Store or fetch the assigned SOC 2020 code for each sponsored role
Map that code to the published going rate (from the Home Office immigration salary list appendix)
Apply any applicable Immigration Salary List (ISL) discount — 20% reduction on going rate only, not on the general threshold

The going rate table is published in the immigration salary list appendix to the immigration rules. This data changes when the Home Office updates the rules — worth building a refresh mechanism that doesn't require a code deploy.

The Immigration Salary List Discount

If the occupation is listed on the Immigration Salary List (ISL — introduced in April 2024, replacing the Shortage Occupation List):

if occupation_on_isl:
    effective_going_rate = going_rate * 0.80  # 20% discount
else:
    effective_going_rate = going_rate

# General threshold always applies as the absolute floor
salary_floor = max(general_threshold, effective_going_rate)

A common implementation error: applying the 20% discount to the general threshold. The discount only applies to the going rate comparison. The £38,700 (or £30,960 for new entrants) floor remains unchanged.

Salary Composition Rules

Not all compensation is countable. When computing candidate_salary for threshold comparison:

Counts:

Base salary (contracted annual amount)
Guaranteed allowances — explicitly committed in the Certificate of Sponsorship and unconditional

Does not count:

Performance bonuses (not guaranteed)
Tips or gratuities
Non-guaranteed overtime
Benefits in kind (company car, healthcare, etc.)

For part-time workers, there are two separate tests that must both pass:

fte_annual = (actual_salary / contracted_hours) * standard_full_time_hours
assert fte_annual >= salary_floor  # FTE test
assert actual_annual >= salary_floor  # Actual salary test

Part-time doesn't get a proportional threshold reduction. A high hourly rate doesn't substitute for the annual total. Both tests must pass independently.

SOC Code Assignment: Where Most Errors Originate

The SOC code assigned to a role determines which going rate applies. Common failure patterns:

Title/duties mismatch: Using a SOC code that matches the job title but not the actual role responsibilities. UKVI assesses on duties, not titles.
Inflated code selection: Assigning a higher-paying SOC code to push the going rate threshold lower. This creates a compliance risk if audited.
Stale codes: Not updating SOC codes when a worker's responsibilities change materially.
Limited system options: HR systems that only expose a subset of SOC codes, forcing approximate assignments.

Building SOC code assignment into your sponsor management workflow with an audit trail — including who assigned the code and when — is good compliance hygiene.

Testing Edge Cases

Before shipping threshold logic, validate these scenarios:

1. ISL occupation: going_rate = £36,000. candidate_salary = £31,000
   effective_going_rate = £28,800 (20% discount)
   salary_floor = max(38700, 28800) = £38,700
   FAIL: £31,000 < £38,700

2. New entrant on Graduate visa switch: candidate_salary = £31,500
   general_threshold = £30,960
   going_rate = £28,000 (non-ISL)
   salary_floor = max(30960, 28000) = £30,960
   PASS: £31,500 > £30,960

3. Part-time: 25 hrs/week at £20/hr = £26,000/year, FTE = £41,600
   actual (£26,000) < £38,700: FAIL (both tests must pass)

4. High going rate occupation: going_rate = £52,000, candidate = £45,000
   salary_floor = max(38700, 52000) = £52,000
   FAIL: £45,000 < £52,000, even though above general threshold

Getting these wrong doesn't just affect the candidate's application. It can expose the sponsoring organisation to a compliance finding during a UKVI audit, with potential suspension or revocation of their sponsor licence.

Data Access and Integration Options

There is no official public API for UK immigration salary thresholds. Practical options:

Parse the Home Office immigration salary list appendix directly (published on legislation.gov.uk)
Integrate with a compliance data provider that maintains this as a structured, versioned dataset
Use tools like ImmigrationGPT to query current threshold values and eligibility rules in natural language

This post is for technical and informational purposes only. UK immigration rules change frequently. Always verify current thresholds against GOV.UK guidance and consult a regulated immigration adviser before making compliance decisions.

UK Visa Refusals and the Appeals Process in 2026: A Technical Reference for HR and Compliance Systems

ImmigrationGPT — Fri, 10 Jul 2026 08:07:21 +0000

When a UK visa application is refused, the downstream effects ripple across HR systems, onboarding pipelines, and compliance records. Understanding the appeals and review mechanisms — and how long each takes — is essential for any team managing sponsored workers or international hires.

This post maps out the four post-refusal routes available in 2026 and highlights the data points your systems need to track.

The Four Routes After a UK Visa Refusal

1. Administrative Review

Administrative review (AR) is available for most Points-Based System refusals: Skilled Worker, Student, Graduate, and most other PBS routes. It is not a full merits appeal — it asks only whether the decision-maker applied the rules correctly.

Key parameters for compliance tracking:

Deadline: 28 days (in-country) / 14 days (out-of-country) from refusal date
Processing target: 28 days (real-world timelines often 6-10 weeks)
Fee: £80
Outcome: Original decision upheld, or remitted for a fresh decision
Appeal rights after AR failure: None via this route; reapplication is the next step

If your HR system records application dates and outcomes, you should add an ar_deadline field calculated from the refusal_date field. Missing the window permanently forecloses this option.

2. First-tier Tribunal (Immigration and Asylum Chamber)

Full tribunal appeal rights apply primarily to:

Family and partner visa refusals
Decisions engaging Article 8 (right to family/private life)
Protection and asylum claims
Decisions involving EEA rights (limited, post-Brexit)

Work visas — including Skilled Worker — generally do not carry full appeal rights unless the refusal also engages human rights grounds.

Key parameters:

Deadline: Specified in the refusal notice (typically 14-28 days)
Processing: Currently 12-24 months for a listed hearing in many regions (2026 backlog)
Fee: £140 (oral hearing) or £80 (paper determination)
In-country vs. out-of-country: Determines whether the individual can remain in the UK during the appeal
Section 3C leave: Applies automatically if the person was in the UK with valid leave when the decision was made and appeals in time — they retain a form of leave pending outcome

For HR and compliance systems, the critical flag here is section 3C leave status. A worker whose visa has nominally expired but who is appealing in-time may still have the right to work. Failing to check this — and incorrectly terminating employment or access — creates both legal and reputational risk.

3. Reapplication

For most refusals on standard eligibility grounds (missing documents, salary shortfall, COS issues), immediate reapplication is permitted. There is no mandatory cooling-off period for most visa categories.

Exceptions that your systems must flag:

Refusals citing deception or misrepresentation under paragraph 9.7 of the Immigration Rules: mandatory 10-year re-entry ban
Refusals on V3.7 grounds (previous breach, overstaying): typically 1-5 year bars depending on severity
Administrative removal orders: 10-year bar

If your data model stores refusal reasons as a simple pass/fail, you're missing the structured reason codes that determine reapplication eligibility. Parse the refusal notice for the specific paragraph cited.

4. Judicial Review

Judicial review (JR) sits outside the normal appeals architecture and applies where:

There is no statutory right of appeal
The decision is alleged to be unlawful on public law grounds (illegality, irrationality, procedural unfairness)

JR is slow (12-24 months), expensive (legal costs run to thousands), and has a low success rate. It rarely features in HR compliance workflows but matters for edge cases: a Tier 1 Investor or Global Talent refusal where no other route exists, or a sponsor licence revocation where the grounds are arguably flawed.

Compliance System Design Implications

For teams building or maintaining HR compliance tools that track UK immigration status:

Fields to capture at refusal:

refusal_date
refusal_paragraph_cited[]    # array — multiple grounds common
has_appeal_right: boolean
appeal_route: enum [AR, Tribunal, None, Judicial_Review]
appeal_deadline: date
ar_deadline: date
ban_end_date: date | null
section_3c_leave_active: boolean

Alerting logic:

T-7 days before appeal deadline: escalation alert
Section 3C leave active: RTW check flag must reflect pending appeal status
Deception/misrepresentation flag: block any future sponsorship action until ban_end_date

Integration point: The Home Office Employer Checking Service (ECS) will confirm section 3C leave status and issue a Positive Verification Notice (PVN) when applicable — your right-to-work workflow should trigger an ECS check whenever a refusal or expiry event fires and an appeal is logged.

Timelines Summary (2026)

Route	Deadline to Lodge	Decision Timeline
Administrative Review (in-country)	28 days from refusal	6-10 weeks typical
Administrative Review (out-of-country)	14 days from refusal	6-10 weeks typical
First-tier Tribunal	Per refusal notice	12-24 months
Judicial Review (permission stage)	3 months from decision	3-6 months
Reapplication (standard)	No restriction	Standard processing

Wrapping Up

The UK visa appeals framework is route-specific, deadline-driven, and has meaningful consequences for right-to-work compliance. For HR and compliance systems, the key is capturing structured refusal data — not just a binary refused/approved field — so that downstream workflows (RTW checks, appeal deadlines, reapplication eligibility) can be automated correctly.

For teams that need to quickly look up which rules apply to a given refusal scenario, ImmigrationGPT provides a RAG-based Q&A interface over UK immigration policy documents that can surface the relevant rule paragraphs in seconds.

This post is for informational purposes and does not constitute legal advice. Always consult a qualified immigration solicitor for case-specific guidance.

UK Points-Based Immigration System 2026: Engineering Reference for Compliance Systems and HR Platforms

ImmigrationGPT — Thu, 09 Jul 2026 08:08:04 +0000

If your platform does anything with UK hiring — eligibility checks, right to work flows, sponsor licence validation, or immigration cost modelling — you need an accurate model of how the UK Points-Based System (PBS) actually works under the hood. The name implies a dynamic scoring model. The reality is closer to a deterministic constraint-satisfaction problem.

This post maps the actual decision logic so you can model it correctly.

System Architecture: Not a True Points Auction

Australia's GSM (General Skilled Migration) system is genuinely points-based: candidates accumulate scores across weighted categories, rankings are generated, and the top scorers receive invitations from a fixed pool. Scores in one dimension can compensate for deficits in another.

The UK PBS works differently. It's threshold-based with structured trade-offs, not a continuous scoring model. For the Skilled Worker visa — the primary work route — the decision tree looks like this:

MANDATORY (all must pass):
├── Approved sponsor exists → 20pts
├── Job at RQF3+ skill level → 20pts
└── English language requirement met → 10pts

SALARY FLOOR (must reach 70pts total via one of):
├── Salary >= general threshold (£38,700) → 20pts
├── Salary >= going rate x 0.8 AND (job on ISL OR PhD relevant) → 20pts
└── New entrant rate applies AND salary >= reduced threshold → 20pts

Key engineering insight: The mandatory block is strictly conjunctive — all three must be true. The salary block introduces conditional branches, but each branch is itself binary (not weighted). There is no partial credit; you cannot compensate for a missing sponsor with a higher salary.

This means your eligibility model should be implemented as a decision tree or rule engine, not a linear scoring function.

Salary Threshold Data Model (2026)

The salary requirement has two components that must both be satisfied:

def salary_eligible(offered_salary: float, going_rate: float,
                    on_isl: bool, has_phd: bool, is_new_entrant: bool) -> bool:

    GENERAL_THRESHOLD = 38700
    NEW_ENTRANT_THRESHOLD = 30960  # approximate — verify per SOC code

    # New entrant path
    if is_new_entrant:
        floor = min(going_rate * 0.8, NEW_ENTRANT_THRESHOLD)
        return offered_salary >= floor

    # ISL / PhD trade-off path
    if on_isl or has_phd:
        reduced_going_rate = going_rate * 0.8
        floor = max(reduced_going_rate, GENERAL_THRESHOLD * 0.8)
        return offered_salary >= floor

    # Standard path
    return offered_salary >= max(GENERAL_THRESHOLD, going_rate)

Note: The going rate is per-SOC code. The Home Office publishes a table of occupation codes with their going rates; this table is the authoritative source and gets updated periodically. Your system should treat this as a versioned dataset, not a hardcoded constant.

Sponsor Licence as a Prerequisite State

The approved_sponsor flag in the mandatory block deserves special attention. An employer either holds a valid sponsor licence or does not — but licence status can change:

Active — can assign Certificates of Sponsorship (CoS)
Suspended — cannot assign CoS; existing sponsored workers in a grey area
Revoked — cannot assign CoS; sponsored workers' leave may be curtailed

For eligibility calculations, model sponsor status as a time-indexed property, not a static boolean. A worker might be eligible today on the basis of an active sponsor and ineligible tomorrow if that licence gets revoked.

The UK Government publishes a register of licensed sponsors. If you're building a live eligibility tool, you should sync against this data — or use ImmigrationGPT which maintains a parsed copy of the full register with 125,000+ companies.

Occupation Code Classification

The RQF3+ skill level requirement is a property of the occupation code (SOC 2020), not the job title. The Home Office maintains a list of eligible occupation codes. Your system needs to map from job title/description → SOC code → RQF level → eligible/ineligible.

This mapping is non-trivial:

The same job title can map to multiple SOC codes depending on sector
Some codes are split between RQF3+ and below based on duties
TIDES (the SOC lookup tool) is the official reference, but requires interpretation

Store the occupation code alongside the eligibility decision for auditability.

Route-Specific Constraint Tables

The Skilled Worker visa is the main route, but the PBS covers multiple routes with different constraint sets:

Route	Key Distinguishing Constraint
Global Talent	Endorsement from designated body replaces salary/sponsor requirements
Graduate	No salary floor; no sponsor needed; time-limited (2 years, 3 for PhDs)
Scale-up	Salary >= £36,300; sponsor only required for first 6 months
Senior/Specialist	No salary cap upward; no ISL trade-off available

If your system needs to suggest the optimal route for a given profile, build a multi-route resolver — evaluate each route's constraint set independently against the candidate profile.

Monitoring Threshold Changes

The PBS is a live regulatory framework. Salary thresholds changed significantly in 2024 and were reviewed again in 2025. The Immigration Salary List is reviewed periodically by the MAC (Migration Advisory Committee). Occupation code classifications change with SOC revisions.

For production compliance systems, treat threshold data as configuration that changes on a known schedule — not as hardcoded constants. Implement a versioning strategy so you can answer "what were the rules on date X?" for audit purposes.

ImmigrationGPT indexes official GOV.UK policy pages and provides an interface for rule lookups, reducing the overhead of tracking upstream changes yourself.

Summary

The UK PBS is best modelled as:

A conjunctive mandatory block (all-or-nothing)
A conditional salary floor with structured trade-offs
A versioned dataset for going rates, ISL membership, and SOC eligibility
A time-indexed sponsor status lookup

Build it as a rule engine with auditable decisions and version-controlled thresholds — not a static scoring function.

This post covers the technical architecture of the UK PBS for engineering and HR platform purposes. It is not legal advice. UK immigration rules change frequently — always validate against official GOV.UK sources for production systems.

UK Graduate Route 2026: Application Timing, Work Rights, and What HR Compliance Systems Should Track

ImmigrationGPT — Thu, 09 Jul 2026 08:07:06 +0000

The Graduate Route is the mechanism UK universities and employers expect international students to use after graduation. For HR teams and developers building compliance tools, understanding its timing model, work right rules, and absence tracking is operationally important — especially when managing recent graduates approaching their Skilled Worker switch.

Route Classification

The Graduate visa is an in-country switching route: it can only be applied for from inside the UK, while the applicant holds a valid Student visa. There is no equivalent entry clearance category.

Key identifiers:

Visa type: Student → Graduate (in-country switch only)
Duration: 2 years standard, 3 years for doctoral qualifications
Sponsor requirement: None
Salary threshold: None
Occupation restriction: None

Application Timing Logic

The application window is bounded at the top by Student visa expiry. There is no post-expiry grace period for this route. HR systems should surface alerts at 60 days and 30 days before Student visa expiry for any employee who hasn't yet applied.

Student visa expiry: [DATE_EXPIRY]
Latest application date: DATE_EXPIRY - 1 day
Earliest application date: Course completion confirmed

During the application pending period, the applicant retains their existing leave (the Student visa) and may work full-time even if the Student visa's work restriction was lower. The Home Office has confirmed this interpretation in published guidance.

Work Rights by Status

Status	Work Rights
Student visa (active)	Typically 20 hrs/week during term
Graduate application pending	Full-time (per Home Office guidance)
Graduate visa active	Unrestricted — any employer, any role
Graduate visa expired	No right to work in UK

HR systems tracking work authorisation should treat the Graduate pending period as full unrestricted work rights once the application reference number is confirmed by the Home Office.

Share code availability: Share codes are not generated until the Graduate visa is actually granted. During the pending period, the right to work is evidenced by the Student visa plus the application acknowledgement from the Home Office. Build your verification logic to handle this two-document state.

The Non-Extendability Constraint

The Graduate Route cannot be extended. This is architecturally significant for HR compliance tools that manage visa renewal reminders.

A Graduate visa holder approaching expiry needs a switch to another route (typically Skilled Worker) or departure. This means:

Track Graduate expiry separately from other renewable routes
Reminder logic should trigger Skilled Worker eligibility checks at 12 months before Graduate expiry, not just 90 days
If a Skilled Worker application is in progress at the same time the Graduate visa is still active, two concurrent visa reference numbers may exist simultaneously

Settlement Clock — What Doesn't Count

Time on the Graduate Route does not accrue toward ILR directly. The qualifying residence clock for Skilled Worker ILR starts from the date of the Skilled Worker visa grant.

# Incorrect — treats Graduate time as qualifying
ilr_eligible_date = graduate_visa_grant_date + timedelta(days=5*365)

# Correct — clock starts from Skilled Worker grant
ilr_eligible_date = skilled_worker_grant_date + timedelta(days=5*365)

For employees who spent 2 years on Graduate before switching to Skilled Worker, their 5-year ILR timeline starts fresh from Skilled Worker grant date. Systems treating Graduate time as qualifying residence will produce incorrect ILR eligibility dates and misinform employees.

Absence Tracking During Graduate Period

The Graduate visa itself has no continuous residence requirement beyond what's inherited from a later ILR application. However, extended absences during the Graduate period can affect the subsequent Skilled Worker → ILR calculation.

Track all departure and entry dates throughout the Graduate period and pass them into the Skilled Worker absences model. The running total of days outside the UK matters for ILR purposes, and gaps in tracking are hard to reconstruct from passport stamps alone.

Sponsor Licence Verification for Onboarding Graduates

HR systems onboarding recent graduates should verify that their degree was completed at an institution holding a valid Student sponsor licence at the time of study. A course at an institution whose licence was revoked or suspended during the student's enrolment can invalidate the Graduate Route application.

The register of licensed student sponsors is updated regularly by the Home Office. You can cross-reference institution names and current status via ImmigrationGPT, which indexes the GOV.UK published register.

Summary Reference Table

Field	Value
Route type	In-country switch only
Application window opens	Course completion confirmed
Application window closes	Day before Student visa expiry
Duration granted	24 months (PhD/doctoral: 36 months)
Extensible	No
Salary threshold	None
Sponsor required	No
Work restriction	None (once granted)
Counts toward ILR	No

Key Engineering Takeaways

Hard expiry, no extension — model Graduate as a countdown timer with no renewal path, unlike Skilled Worker
Pending state = full work rights — don't restrict employee work authorisation between application submission and grant
ILR clock resets at Skilled Worker grant — never roll Graduate time into the settlement calculation
Absence data must persist — collect dates throughout Graduate period even though it doesn't directly affect ILR; they're needed for the subsequent Skilled Worker → ILR calculation

For plain-English explanations of these rules for end users and employees navigating the process themselves, see ImmigrationGPT.

For plain-English explanations of UK immigration rules and sponsor register lookups, see ImmigrationGPT.

UK Visa Refusal Patterns 2026: Decision Logic, Common Failure Triggers, and What HR Compliance Systems Should Flag

ImmigrationGPT — Wed, 08 Jul 2026 08:10:51 +0000

UK Visa Refusal Patterns 2026: Decision Logic, Common Failure Triggers, and What HR Compliance Systems Should Flag

Understanding why UK visas get refused maps directly to the validation logic that HR and compliance systems need when checking employee eligibility or preparing sponsored worker applications. This post breaks down the most common refusal triggers, the underlying decision logic the Home Office applies, and the specific flags a well-built immigration compliance tool should surface.

Decision framework overview

Every UK visa decision runs through roughly the same logical hierarchy:

Does the applicant meet mandatory eligibility rules? (age, nationality, prior status)
Is the specific financial threshold met with verifiable evidence?
Is the English language requirement satisfied?
Is there a compliant sponsor, or adequate ties to the home country?
Does the applicant pass immigration history checks?
Are all supporting documents valid, complete, and consistent?

A failure at any layer typically causes refusal, even if all other layers pass. Refusal letters usually cite the first failure point — so a letter citing "insufficient funds" may mask a deeper issue at the document layer.

Layer 1: Financial evidence validation

Skilled Worker / sponsored routes:

income_check(CoS_salary) >= max(
  going_rate_for_SOC_code,
  £26,200,           # general threshold (post-April 2024)
  new_entrant_rate   # if applicable
)

For system builders: the CoS salary is fixed at issue. If the applicant's circumstances change between CoS assignment and application submission, there's no update mechanism — a new CoS is required.

Spouse/family sponsor income:

Minimum: £29,000 (from 11 April 2024)
Acceptable sources: employment payslips (last 6 months) + P60, self-employment (accounts + tax returns), pension
Flagged patterns: large irregular deposits shortly before application ("funds parking"), undeclared deductions, combined income without correct averaging

Visitor visa:

No fixed threshold — caseworker discretion applies
System flag heuristic: bank_balance < (estimated_trip_costs × 1.5) → flag for additional evidence

Layer 2: English language decision logic

def passes_english_requirement(applicant, visa_type):
    if applicant.nationality in EXEMPT_NATIONALITIES:  # Home Office published list
        return True
    if applicant.degree_taught_in_english and degree_recognised_by_naric():
        return True
    return selt_valid(applicant.test_result, visa_type)

def selt_valid(test_result, visa_type):
    if test_result.provider not in APPROVED_SELT_PROVIDERS:
        return False
    if (today - test_result.date).days > 730:   # 2-year validity window
        return False
    if test_result.cefr_level < MIN_LEVEL[visa_type]:
        return False
    return True

A compliance system should track SELT expiry dates and alert well before the 2-year cutoff — this is a common gap in existing HR platforms that catches workers by surprise.

Layer 3: Sponsor status validation

Sponsor-side refusals are particularly damaging because the applicant often has no visibility into the problem until a refusal arrives.

# Public sponsor licence register (updated weekly)
curl "https://assets.publishing.service.gov.uk/media/[LATEST]/Tier_2_5_Register.csv" \
  -o sponsor_register.csv

Key fields to track per employer:

Field	Validation rule
`Organisation Name`	Exact or fuzzy match against employer claim
`Route`	Must include the relevant sub-type (Skilled Worker, etc.)
`Rating`	A-rated = can assign new CoS; B-rated = cannot
`Licence number`	Cross-reference against CoS issued

A revoked sponsor invalidates any CoS assigned after the revocation date. Build a nightly diff against the published register to detect status changes before they surface in a live application.

Layer 4: Immigration history flags

Automatic refusal triggers the system should capture at self-declaration stage:

AUTOMATIC_REFUSAL_FLAGS = [
    "prior_deception_finding",          # 10-year ban
    "deportation_order_in_force",       # indefinite ban unless revoked
    "overstay_more_than_28_days",       # 1 or 5 year re-entry ban
    "prior_refusal_within_10_years",    # context-dependent
]

Important: caseworkers cross-reference the applicant's UK immigration history automatically. Self-declaration gaps — e.g., failing to mention a prior refusal — trigger a deception finding even if the underlying application would have succeeded.

Layer 5: Document consistency validation

Cross-document checks that catch the most common failures:

def validate_document_consistency(docs):
    errors = []

    # Name consistency
    if docs['passport'].name != normalise_name(docs['bank_statements'].name):
        errors.append("Name mismatch: passport vs bank statements")

    # Date ordering
    if docs['employer_letter'].date < docs['payslips'][-1].date:
        errors.append("Employer letter predates most recent payslip")

    # CoS occupation alignment
    if docs['cos'].soc_code != lookup_soc(docs['job_offer'].title):
        errors.append("CoS SOC code may not match stated job title")

    # Translation present for non-English documents
    for doc in docs.values():
        if doc.language != 'en' and not doc.has_certified_translation:
            errors.append(f"Missing certified translation: {doc.type}")

    return errors

Refusal rates by visa category

Visa Type	Approximate Refusal Rate
Visit visa (non-EEA nationals)	15–20%
Skilled Worker	3–6%
Student visa	5–10%
Spouse / Partner visa	10–15%
Global Talent	15–25%

Rates vary by applicant nationality. Official breakdowns are in the Home Office immigration statistics quarterly releases.

Post-refusal decision tree

refusal received
│
├── Human rights grounds engaged?
│   └── YES → Appeal to First-tier Tribunal (14 working days to lodge)
│
├── Suspected caseworker error?
│   └── YES → Administrative Review (£80 fee, decision within 28 days)
│              NOTE: reviews errors of law only, not proportionality
│
└── Otherwise
    ├── Re-entry ban applies? → Wait out ban period
    └── No ban → Reapply with corrected/stronger evidence

Administrative review is not a merits appeal. It only examines whether the caseworker applied the rules correctly — not whether the refusal was fair or proportionate.

Implementation notes

Systems aggregating these checks should:

Integrate with the live UKVI sponsor register (CSV, weekly refresh)
Track SELT validity dates and fire alerts at 90-day and 30-day thresholds
Run name normalisation across all uploaded documents before submission
Log immigration history declarations as structured data, not free text
Surface CoS occupation code mismatches at the drafting stage, not after CoS assignment

For a reference implementation covering sponsor licence lookups, visa eligibility checks, and immigration status validation, visit immigrationgpt.co.uk.

Content is informational only. Immigration Rules change regularly — verify all thresholds and logic against the current Immigration Rules HC 395 and GOV.UK guidance before implementation.

UK Family Visas 2026: A Technical Guide for HR Teams and Developers Building Immigration Compliance Tools

ImmigrationGPT — Tue, 07 Jul 2026 08:10:14 +0000

UK Family Visas 2026: A Technical Guide for HR Teams and Developers Building Immigration Compliance Tools

UK family visas are one of the most misunderstood areas of UK immigration — not because the rules are especially obscure, but because there are several distinct routes, each with different financial thresholds, evidence requirements, and processing timelines. For HR teams dealing with employees who want to bring family members to the UK, and for developers building immigration compliance tooling, understanding the structure of these routes matters.

This post maps out the main family visa routes, the data points that determine eligibility, and the technical gotchas that create problems in practice.

The Route Taxonomy

UK family visas sit under Appendix FM of the Immigration Rules. The main categories are:

Route	Target applicant	Key financial threshold
Partner (Spouse/Civil/Unmarried)	Husband, wife, civil partner, unmarried partner (2+ years cohabitation)	Sponsor earns ≥ £29,000/yr
Parent	Parent or grandparent needing personal care	Sponsor provides full financial support
Child	Dependent children under 18	Sponsor meets income/accommodation threshold
Adult Dependent Relative (ADR)	Parents, grandparents, siblings, adult children — needing long-term care	Highest bar; no public funds ever

The Partner Visa: Financial Threshold Logic

The spouse/partner visa has the clearest financial requirements, but the rules around how income is counted are where systems fail.

The current minimum income threshold is £29,000 per year (raised from £18,600 in stages from April 2024).

Income sources the Home Office accepts:

Salaried employment (gross, annualised)
Self-employment (HMRC Self Assessment — last full tax year)
Non-employment income (rental, dividends, interest) with stipulations
Partner's income can only be counted if the partner is already in the UK with permission to work
Savings can supplement income if below threshold, but must be held for at least 6 months

What this means for data modelling:

If you're building an eligibility checker, the income test is not just a single integer comparison. You need to handle:

Income type (salaried vs self-employed vs mixed)
Whether the partner is currently in the UK and working
Whether savings are being used as a supplement (the formula is: shortfall x 2.5 = minimum savings required, held 6+ months)
Employment history gaps within the 12 months prior to application

A naive sponsor_income >= 29000 check will produce false positives and false negatives across a significant portion of real-world cases.

The Adult Dependent Relative Route: Why It Fails So Often

The ADR route has one of the highest refusal rates of any UK visa category. The test is:

Does the applicant need long-term personal care due to age, illness, or disability?
Can that care NOT be obtained in their home country — either because it does not exist or because it is unreasonable to expect them to use it?

The second limb is the one that fails most applications. Home caseworkers interpret unavailable care strictly. If any form of professional care exists in the country (even if expensive or low-quality), the applicant typically does not meet the test.

System implication: If you are building eligibility logic for ADR, it cannot be determined from structured data alone — it requires qualitative evidence assessment. Flag this route as requiring manual review rather than automated pass/fail.

Processing Timelines

Application type	Standard	Priority	Super Priority
Entry clearance (outside UK)	12 weeks	3-5 weeks	N/A
Leave to remain (inside UK)	8 weeks	5 working days	1 working day

These are target times — not guarantees. The Home Office does not legally commit to processing within these windows, and missing them does not trigger a right of appeal.

For HR compliance tracking: if an employee's dependent is applying from outside the UK, a 12-week window is realistic minimum planning time. Build in buffer for incomplete applications or requests for further information (RFI).

Biometric Enrolment Requirements

All family visa applicants (from most nationalities) must enrol biometrics at a Visa Application Centre (VAC). For some countries, in-country biometric capture is limited — applicants may need to travel to a VAC in a neighbouring country.

This is a real-world bottleneck that pure eligibility logic often ignores: an applicant can be fully eligible and still face a 4-6 week delay waiting for a VAC appointment.

Tools for Checking Sponsor Eligibility

When employees ask HR about bringing family to the UK, the first question is usually about their own immigration status — whether they are on a visa that allows dependants, and what the financial requirements are.

ImmigrationGPT provides plain-English explanations of UK immigration rules, lets you search the sponsor licence register for UK employers, and gives employees and HR teams a fast way to understand route eligibility before engaging an immigration solicitor.

For developers building HR or onboarding tooling, structuring your immigration status data model around the Appendix FM route taxonomy (rather than generic visa type strings) will save significant re-engineering when financial thresholds change or new routes are added.

Key Takeaways

Family visa routes are distinct — not a single family visa with variants
Income thresholds on the partner route are higher than many expect and have specific counting rules
ADR is high-risk and not suited to automated eligibility logic
Processing timelines should be treated as planning minimums, not commitments
Biometric appointment availability is a real-world constraint worth surfacing in any compliance tool

This article is for technical and informational purposes only and does not constitute immigration or legal advice. UK immigration rules change frequently. Always consult a qualified immigration solicitor or OISC-regulated adviser for case-specific guidance.

UK Right to Work Checks: How to Build an Automated Compliance Workflow for Your Hiring Pipeline

ImmigrationGPT — Mon, 06 Jul 2026 08:08:29 +0000

Right to work compliance in the UK sits at an awkward intersection of HR policy, immigration law, and document verification technology. If you're building or managing a hiring system that touches UK employees, getting this wrong isn't just an audit finding — it's a £60,000-per-worker civil penalty exposure.

This post covers the current legal framework, the three verification methods, and how to design a workflow that handles the edge cases your hiring pipeline will inevitably encounter.

The Legal Foundation

Under the Immigration, Asylum and Nationality Act 2006, every UK employer must verify that workers have the right to work before they start. The Home Office operates a strict liability system: if you employ someone without a right to work, you're liable for a civil penalty even if you didn't know — unless you followed the correct checking process and obtained a "statutory excuse."

The statutory excuse is the key concept. It's your documented proof that you did what the law requires. Without it, you have no defence.

Three Checking Methods — and When to Use Each

The Home Office currently recognises three checking mechanisms:

1. Manual Document Check

Used for British/Irish citizens with physical passports, and for some legacy immigration documents. You examine original documents in person (or via live video call in prescribed circumstances), retain copies, and record the date of check.

Gotcha: Physical EU passports and national ID cards no longer confer the right to work for EU/EEA/Swiss nationals who arrived after 31 December 2020. If your manual check process accepts these, it's misconfigured.

2. Home Office Online Checker (Share Code)

For anyone with a digital immigration status: Skilled Worker visa holders, EU/EEA/Swiss nationals with settled or pre-settled status under the EU Settlement Scheme, Graduate route holders, and more.

The employee generates a 9-character share code from their UKVI account; you enter it alongside their date of birth at gov.uk/prove-right-to-work. The result gives you their name, permission to work, and any work restriction details.

Implementation note: The check result page must be saved as a screenshot or printed record that clearly shows the employee's photo, the date of the check, and the work permission details. An audit log entry that just says "checked online" is insufficient.

3. Identity Document Validation Technology (IDSP)

Certified IDSPs can verify the identity and right to work of British and Irish citizens using their passport or driving licence — entirely digitally. The employer receives a verified record from the IDSP.

This is increasingly the default for large-volume hiring because it creates a more auditable trail than manual document checks and removes the in-person verification step.

When to use which: If the candidate is a British or Irish citizen, you can use manual check, IDSP, or (in limited cases) the online checker. If they have any other immigration status, use the online checker with a share code.

The Repeat Check Problem

Most compliance systems handle the initial check reasonably well. Where workflows break down is the follow-up check for time-limited permissions.

If an employee has a visa that expires in 18 months, your system needs to:

Record the expiry date at the time of the initial check
Schedule a follow-up check 4-6 weeks before expiry
Alert an HR owner (not just the employee) when the check is due
Block or flag the employee record if the check isn't completed by expiry

Missing a repeat check means you lose your statutory excuse from that point forward — even though you did everything right initially.

The eVisa Transition Edge Case

BRPs have been replaced by eVisas. Employees who previously had a BRP should now have a UKVI account and can generate share codes. However, the transition hasn't been seamless: some employees have accounts with mismatched names, expired BRPs they haven't converted, or technical issues generating share codes.

Practical approach: If an employee can't generate a share code, they need to contact the UKVI technical helpline before starting work. Don't accept the physical BRP card as a workaround — the Home Office no longer considers this sufficient for time-limited permissions.

Document Retention

Right to work records must be retained for the duration of employment and two years after employment ends. This means:

Clear copies of all documents checked (front and back where applicable)
Screenshot/printout of online check results with employee photo and check date
Date of check and name of the person who conducted it
Repeat check records with their own dates

Penalty Framework (2026)

Offence	Maximum Civil Penalty
First offence, unknowing	Up to £45,000 per worker
Repeat/deliberate	Up to £60,000 per worker
Criminal conviction	Unlimited fine + up to 5 years imprisonment

The Home Office publishes a public register of civil penalty recipients. The reputational consequence adds to the financial one — particularly relevant if you hold or plan to apply for a sponsor licence, since a civil penalty can affect sponsor licence eligibility.

Building a Compliant Workflow

Minimum viable compliance setup:

Pre-offer: Inform candidates which checking method applies to them based on their stated right to work status
Pre-start: Complete the check, retain records with correct metadata
HRIS integration: Store expiry dates as structured fields, not document notes
Automated reminders: Trigger follow-up check tasks 6 weeks before visa expiry
Escalation path: If follow-up check isn't completed by expiry date, escalate to HR lead and flag in payroll

For teams building on top of UK immigration data — including sponsor licence lookups, visa type classifications, and policy Q&A — ImmigrationGPT provides an AI-powered reference layer built on live government data.

This post is for informational purposes only and does not constitute legal advice. UK immigration law changes frequently — always verify against current Home Office guidance.