DEV Community: ImmigrationGPT

UK Immigration Health Surcharge 2026: Modelling IHS Costs in HR Systems — The Calculation Gaps That Break Workforce Budget Tools

ImmigrationGPT — Wed, 16 Sep 2026 08:07:19 +0000

£1,035 per person per year. That's the headline rate for the UK Immigration Health Surcharge (IHS) in 2026, and it's the number most HR systems and workforce budget models start with. It's also where most of them stop — which is why IHS calculations are consistently wrong in ways that compound across multi-year workforce plans.

This is a reference post for HR teams, finance functions, and anyone building compliance tooling around UK sponsored worker costs. The calculation model you're probably using has at least three structural gaps.

Gap 1: The Grant Date vs Entry Date Problem

The IHS is calculated from the date of visa grant, not the date of UK entry. For applicants applying from overseas — which is the majority of Skilled Worker cases — there's typically a gap between when the visa is issued and when the worker actually arrives.

That gap is paid for. There's no partial-period refund for days outside the UK between grant and entry. In a budget model, if you're estimating IHS costs based on employment start dates rather than visa grant dates, you're systematically undercosting applications where the worker arrives after the grant.

For a five-year Skilled Worker visa with a three-month entry gap, the miscalculation is £776 per person at current rates. Multiply that across a hiring cohort, and it's material.

Gap 2: Extension Applications Reset the Clock

IHS calculations don't carry over between applications. When a sponsored worker extends their Skilled Worker visa, the extension application triggers a fresh IHS calculation for the extension period. There is no credit for unused time on the expiring visa.

This matters for budget modelling in two scenarios:

Early extensions. If an employer applies to extend a worker's visa before it expires — which is common to maintain continuity of right to work — the worker pays IHS for any overlap period twice.
Route switches. A worker switching from a Graduate visa to a Skilled Worker visa before their Graduate visa expires loses whatever IHS they've already paid for the remaining Graduate period. The Skilled Worker application starts from zero, at the full adult rate of £1,035/year rather than the student rate of £776/year.

Most compliance systems model this as a single cost event per visa category. The multi-event, no-carryover reality costs more.

Gap 3: The Children's Rate Changed in January 2024

Before January 2024, children under 18 paid a reduced IHS rate of £776/year. From that date, the rate was harmonised to £1,035/year — matching the adult rate.

HR systems and budget templates built before 2024 often still carry the old rate for dependants. For a worker with two children on a five-year visa, that's a discrepancy of £2,590 against current actual costs.

The rate at application time locks in for the full visa period. So existing visa holders aren't retrospectively charged for rate increases — but new applications, including extensions and switches, use the current rate.

The Refund Mechanic Most Employers Miss

Three scenarios trigger an IHS refund:

The application is refused
The visa granted is shorter than the period paid for
The worker leaves the UK permanently before their visa expires

Refunds are claimed through the UKVI refund portal, separately from the visa application system. The paying party claims — which is the employer if they covered the IHS on the worker's behalf.

This creates an operational issue: if the employment relationship ends before the worker leaves the UK, the employer (as paying party) has no automatic trigger to claim the refund. The worker, as visa holder, has no direct claim route on payments made by the employer. Neither party has a clear contractual obligation to initiate the process, and the refund window isn't formally defined.

In practice, this means unclaimed IHS refunds are common in workforce transitions. Building a process to track departure dates and initiate refund claims is worth the overhead — at £1,035/year per head, a six-month early departure represents £517.50 per worker.

What This Looks Like in a Compliance System

If you're building or maintaining an HR system that models sponsored worker costs, the IHS component needs to account for:

Grant date, not employment start date, as the calculation baseline
Per-application calculation with no carryover between extensions or route switches
Current rate tables, updated as of the application date (not a static rate)
Dependant count and ages at application, using the current children's rate
A refund-tracking workflow triggered by departure confirmation

The default spreadsheet model — headcount × rate × years — will produce a number. That number will be systematically low for overseas applicants, families with children, and workers who extend or switch routes.

For checking whether a UK employer actually holds an active sponsor licence before you model any of this, the sponsor register search at immigrationgpt.co.uk covers 125,000+ licensed companies with real-time register data.

General information only. Not legal or immigration advice. Verify current IHS rates and refund rules with a regulated immigration adviser before submitting applications.

UK Global Talent Visa in 2026: What Engineers, Data Scientists, and Their HR Teams Need to Know

ImmigrationGPT — Tue, 15 Sep 2026 08:08:28 +0000

Most visa conversations in UK tech circles start with the Skilled Worker route — salary thresholds, sponsor licences, certificate of sponsorship. But for a specific class of senior technical professionals, there's a route that completely sidesteps the employer sponsorship model: the Global Talent visa.

This post covers what it is, who it actually fits, and the operational details HR teams and individual applicants consistently get wrong.

What makes it different from Skilled Worker

The Skilled Worker visa is an employer-led route. A company holds a sponsor licence, issues a Certificate of Sponsorship, and ties the worker's immigration status to that employment relationship. Change jobs without notifying the Home Office correctly and you're in violation.

Global Talent inverts this. There is no employer sponsor. The visa is granted to the individual on the basis of their personal standing in their field. They can freelance, found a startup, take a research role, or work for multiple employers simultaneously without any additional immigration paperwork. From an HR perspective, if you're hiring someone on Global Talent, you have no compliance obligations — no sponsor duties, no right-to-work checks beyond confirming their visa status.

The catch: they have to qualify, and the qualifying bar is real.

The endorsement stage (where most applications fail)

The visa is two-stage: endorsement, then visa. You don't apply to the Home Office for the endorsement — you apply to a designated endorsing body, specific to your sector.

Relevant bodies for the tech and engineering space:

UKRI (UK Research and Innovation) — for researchers, academics, and those working at the intersection of applied research and industry
Royal Academy of Engineering — engineering professionals with demonstrated leadership impact
Innovate UK's endorsed body for digital technology — for software engineers, data scientists, security professionals, and tech founders (this pathway changed after Tech Nation closed in April 2023; confirm the current body and criteria before applying)

Each body publishes its own criteria document. The criteria are not interchangeable. A strong application to RAEng may be entirely unsuitable for UKRI, because the evidence types they weight are different.

Exceptional Talent vs. Exceptional Promise

Both tiers grant the same visa. The difference is:

Exceptional Talent: requires demonstrated, established impact (published work, major projects delivered, peer recognition)
Exceptional Promise: for earlier-career professionals showing strong trajectory (this is still a high bar — it's not "promising grad," it's "senior IC or manager with notable early-career achievement")

ILR timelines differ: Talent qualifies in 3 years, Promise in 5.

What the endorsing bodies actually look for

The criteria documents are worth reading in full, but some patterns hold across most bodies:

High signal:

Being invited to speak or judge (not applying to do so)
Open-source projects with substantial adoption (measured in contributors or deployments, not stars)
Press coverage or analyst mentions that originated from someone else citing you
Leading a team or product that demonstrably scaled — numbers matter here, not job titles
Patents, published research, or technical standards contributions
Board or advisory roles at credible organisations

Lower signal than applicants expect:

Senior job titles without accompanying evidence of impact
Conference talks at events where entry is by speaker application
Personal blog posts, however technically detailed
Awards that are paid for or require application fees

The underlying logic: the endorsing body is trying to establish that your field already recognises you. Evidence that you sought out recognition is weaker than evidence that recognition found you.

Cost and processing time

Endorsement application: £716 (non-refundable if rejected)
Visa application fee: additional, varies by duration
Immigration Health Surcharge: currently £1,035/year
Total cost for a 5-year application: typically £4,000–£5,500

Processing is generally 8 weeks for endorsement, then a further 3–8 weeks for the visa itself once endorsed. Priority processing exists but costs more.

Switching from within the UK: Applicants already in the UK on Skilled Worker, Student, or most other routes can switch to Global Talent without leaving. This is underused and saves significant cost compared to reapplying from abroad.

When to recommend this route to candidates

For HR teams assessing immigration options for senior hires:

If the candidate is a recognised name in their technical domain — publications, open-source leadership, former CTO/VP-level at a known company — explore this route before defaulting to Skilled Worker
If the candidate wants flexibility to consult or advise alongside their role, Global Talent enables this without visa complications
If your company doesn't hold a sponsor licence and acquiring one is logistically complex, this route means you can hire the person without needing one

The qualification bar is high enough that this won't be the right route for most hires. But for the ones who do qualify, it's a meaningfully better position than a Skilled Worker visa tied to a single employer.

For a full overview of UK immigration routes — including sponsor search, salary thresholds, and the right-to-work obligations for employers — visit immigrationgpt.co.uk.

General information only. Not legal advice. UK immigration rules change — verify current requirements with a qualified solicitor.

ILR Eligibility in 2026: Modelling Route-Specific Qualifying Periods Across UK Visa Categories

ImmigrationGPT — Mon, 14 Sep 2026 08:08:48 +0000

Building a system that tracks ILR eligibility correctly is harder than it looks. The qualifying period isn't a single countdown — it's route-specific, it resets on a visa switch, and there's a parallel track (the Long Residence route) that follows completely different rules. Most compliance tools get at least one of these wrong.

The qualifying period by route

The table below captures the primary routes and their qualifying periods for ILR as of 2026:

Route	Qualifying Period	Notes
Skilled Worker	5 years	Clock starts at leave grant date
Global Talent	3 years	Requires active endorsement
Innovator Founder	3 years	Subject to business conditions
Scale-Up	5 years	First 2 years require sponsor
Spouse/Civil Partner	5 years	Combined route with FLR(M)
Long Residence	10 years	Multiple route types count

For most HR compliance use cases, the Skilled Worker route is the dominant one. Five years from the date of first leave grant in the Skilled Worker category — not from the applicant's date of arrival in the UK, not from their first Skilled Worker application.

The route-switch reset problem

When someone switches routes — most commonly from Student to Skilled Worker — their qualifying period for the new route starts at zero on the date the new leave is granted. Their prior UK residence doesn't carry over for route-specific ILR eligibility.

This creates a modelling problem. If you're building an eligibility tracker and using the applicant's total UK residence time as a proxy for qualifying period, you'll produce incorrect results for anyone who switched routes. The correct model requires tracking leave history, not UK presence history.

The code implication: you need a leave history array, not just a start date. Each leave entry has a route, a grant date, an expiry date, and accompanying flags. The qualifying period calculation should iterate over that history and compute contiguous qualifying time within the target route.

def compute_qualifying_period(leave_history: list[dict], target_route: str) -> int:
    """
    Returns qualifying days for ILR under target_route.
    leave_history: sorted by grant_date ascending.
    Each entry: {route, grant_date, expiry_date}
    """
    qualifying_days = 0
    last_contiguous_end = None

    for leave in leave_history:
        if leave['route'] != target_route:
            last_contiguous_end = None
            continue

        start = leave['grant_date']
        end = leave['expiry_date']

        if last_contiguous_end and start <= last_contiguous_end:
            qualifying_days += (end - last_contiguous_end).days
        else:
            qualifying_days += (end - start).days

        last_contiguous_end = end

    return qualifying_days

This is simplified — real implementation needs to handle FLR extensions that aren't technically new leave grants, 3C leave (overstay protection during pending applications), and cases where the Home Office grant date differs from the BRP issue date.

The Long Residence parallel track

Long Residence is a fundamentally different model. Rather than requiring continuous time on one specific route, it requires ten years of continuous lawful residence across any combination of valid leave grants. Student, Skilled Worker, spouse — all count toward Long Residence, which they don't for route-specific ILR.

The qualifying conditions are stricter on absences (more than 540 days total, or 180 in the final year, breaks the Long Residence clock), and the route carries additional conditions around good character.

For compliance tools, Long Residence eligibility should be computed as a separate track running in parallel with route-specific ILR eligibility. Both should surface in a complete eligibility model — an applicant might become eligible for Skilled Worker ILR in year five while also running down a Long Residence clock that started on their first Student visa.

KOLL validation layer

Beyond the qualifying period, ILR requires satisfying the Knowledge of Language and Life check. Two-part requirement:

Life in the UK test — 24 questions drawn from the official handbook, £50 per attempt in 2026
English language — approved qualification at B1 CEFR level or above, OR national of a majority English-speaking country, OR exempt (age 65+, certain disabilities)

KOLL exemptions need to be stored against the applicant profile and checked before flagging KOLL as a blocking condition. English language proofs have expiry considerations — some qualifications are accepted indefinitely, others are time-limited.

Application state machine

The ILR application (SET(O) for most work routes) is submitted via the UKVI online service. Key validation states to track:

Qualifying period met? (route-specific calculation)
Absences pass 180-day-per-rolling-year test?
KOLL satisfied or exempt?
Current leave still valid? (cannot apply with expired leave unless 3C protection is active)
Biometric information enrolled?

A successful grant issues a BRP with no expiry date on the leave. For HR right-to-work verification: an ILR BRP still requires a valid share code check — employers must not rely on the physical card under the current RTW regime.

Processing times in 2026 are typically 8–12 weeks for standard applications. Priority services exist (five working days for super priority, ten working days for priority), at additional cost.

What breaks in practice

The five most common modelling errors I see in HR compliance tools:

Using UK entry date instead of leave grant date as the qualifying period start
Not resetting the clock on route switches (especially Student → Skilled Worker)
Computing absence limits as a rolling total across the entire qualifying period rather than per rolling year
Not tracking Long Residence as a parallel eligibility path
Treating ILR grant as end-state rather than modelling the post-ILR naturalisation window

If you're building or auditing a compliance tool, those five are worth testing against explicitly with edge-case data.

ImmigrationGPT provides AI-powered guidance on UK immigration based on official GOV.UK sources.

Not legal advice. Immigration rules change frequently — consult a qualified adviser for individual cases.

UK Sponsor Licence Register: A Technical Reference for HR Systems and Compliance Tools

ImmigrationGPT — Fri, 11 Sep 2026 08:06:57 +0000

If you've ever tried to verify whether a UK employer is actually authorised to sponsor overseas workers, you've probably hit the same wall: a government-published CSV file that's updated daily, has inconsistent capitalisation, and contains ~100,000 rows with no API.

This is the definitive technical reference for working with the UK Register of Licensed Sponsors — parsing it, querying it efficiently, and integrating it into HR compliance pipelines.

What the Register Is (and Isn't)

The UK Home Office publishes a list of every employer currently licensed to sponsor overseas workers across various routes (Skilled Worker, Intra-Company Transfer, Global Business Mobility, etc.). Updated every working day. No API. No pagination. Just a downloadable .xlsx file with roughly 100,000 rows.

The columns you actually care about:

Column	Values	Notes
Organisation Name	string	Inconsistent casing, Ltd/Limited variants
Town/City	string	Sometimes blank
Type & Rating	"A-Rated", "B-Rated"	A = active; B = under action plan
Route	Skilled Worker, etc.	A licence covers specific routes

What's NOT in the register: company registration number, Companies House ID, contact information, or number of sponsored workers. That's the first pain point for compliance teams — you can't reliably deduplicate on name alone.

Parsing Strategy

Download and normalise

The file URL changes with each update (embedded in a GOV.UK attachment link), so you need to scrape the publication page to get the latest URL each run.

import requests
from bs4 import BeautifulSoup
import pandas as pd
from io import BytesIO

def get_latest_register_url():
    page = requests.get(
        "https://www.gov.uk/government/publications/register-of-licensed-sponsors-workers",
        headers={"User-Agent": "Mozilla/5.0"}
    )
    soup = BeautifulSoup(page.content, "html.parser")
    for link in soup.select("a.gem-c-attachment__link"):
        href = link.get("href", "")
        if href.endswith(".xlsx"):
            return href
    raise ValueError("No .xlsx found on register page")

def load_register(url: str) -> pd.DataFrame:
    r = requests.get(url, headers={"User-Agent": "Mozilla/5.0"})
    df = pd.read_excel(BytesIO(r.content))
    df.columns = [c.strip().lower().replace(" ", "_").replace("/", "_") for c in df.columns]
    df["name_norm"] = (
        df["organisation_name"]
        .str.upper()
        .str.replace(r"\b(LIMITED|LTD|PLC|LLP|LLC)\b\.?", "", regex=True)
        .str.replace(r"[^A-Z0-9 ]", "", regex=True)
        .str.strip()
    )
    return df

Fuzzy matching for employer lookups

Exact name matching fails on roughly 30% of real queries because of abbreviations, trading names, and punctuation. Use rapidfuzz for threshold-based matching:

from rapidfuzz import process, fuzz

def find_employer(query: str, df: pd.DataFrame, threshold: int = 85):
    query_norm = query.upper().strip()
    results = process.extract(
        query_norm,
        df["name_norm"].tolist(),
        scorer=fuzz.token_sort_ratio,
        limit=5,
        score_cutoff=threshold
    )
    if not results:
        return []
    indices = [r[2] for r in results]
    return df.iloc[indices][["organisation_name", "town_city", "type___rating", "route"]].to_dict("records")

A threshold of 85 catches "Acme Ltd" vs "ACME LIMITED" while avoiding false positives. Drop to 75 for broader recall on candidate-facing tools.

Rating Logic: A-Rated vs B-Rated

A-Rated: Active licence. The employer can issue Certificates of Sponsorship (CoS) and hire overseas workers on the relevant routes.

B-Rated: The employer is under a Home Office action plan. They cannot issue new CoS until restored to A-rated. Workers already sponsored on a B-rated licence are not automatically affected, but renewals and extensions become more complex.

For a compliance tool:

Filter type___rating == "A-Rated" for new hire eligibility checks
Flag B-Rated entries with a warning rather than a hard block
No entry = not licensed (or licence recently surrendered/revoked)

Revoked and surrendered licences are removed from the register without trace. If you need historical data, snapshot the file daily — GOV.UK doesn't maintain an archive.

Integration Patterns

Daily sync to your own database: Fetch and upsert every working day at 9AM GMT. Key on normalised name + route + town to detect additions and removals.

Real-time lookup via cached in-memory index: A 100k-row DataFrame is roughly 20MB — fine for a single-instance service. Load on startup, refresh every 24 hours. Sub-millisecond lookups.

Candidate pre-check webhook:

POST /api/check-sponsor
{ "company_name": "...", "route": "Skilled Worker" }

Response:
{ "found": true, "rating": "A-Rated", "town": "London", "matches": [...] }

This is the pattern used by tools like ImmigrationGPT — letting candidates verify a prospective employer's sponsor status before investing time in an application.

Edge Cases to Handle

Multiple routes per company: A large employer might hold licences for Skilled Worker, Intra-Company Transfer, and Global Business Mobility simultaneously. Return all rows for a matched employer.

Charities and public sector: NHS trusts, councils, and universities often appear under their official legal name. "Guy's and St Thomas' NHS Foundation Trust" won't match "Guys Hospital" without tuning.

Subsidiaries: Parent companies and subsidiaries hold separate licences. "Amazon UK Services Ltd" and "Amazon Data Services UK Limited" are different licence holders — a candidate cannot be sponsored by the wrong entity's licence.

Newly licensed employers: There's typically a 24-48 hour lag between a licence decision and appearing on the register.

The Bigger Picture

The register is critical UK immigration infrastructure running on a daily-updated spreadsheet. For serious compliance work: daily snapshots (removals leave no trace), fuzzy matching (names are not standardised), route-specific filtering, and a human review layer for edge cases.

If you're building in this space or want to check a specific employer, ImmigrationGPT indexes the full register and supports plain-language sponsor lookups.

This post is for informational purposes only. Immigration law changes frequently — verify current rules at gov.uk or consult a regulated immigration adviser.

UK Right to Work Checks in 2026: What Your HR System Needs to Handle (And What Manual Processes Get Wrong)

ImmigrationGPT — Wed, 09 Sep 2026 08:08:32 +0000

If you're building or configuring an HRIS that operates in the UK, right to work compliance is not optional and not trivial. Since February 2024, civil penalties for employing someone without right to work have been capped at £60,000 per worker — a three-times increase from the previous maximum. And since the shift from Biometric Residence Permits (BRPs) to eVisa-only status for non-UK nationals, the technical requirements for compliant checking have changed significantly.

Here's what you need to know if you're on the HR tech or compliance side.

Two check types with different data requirements

UK right to work checks split into two categories with fundamentally different data flows:

Manual checks apply to British/Irish citizens presenting physical passports or specific documents (e.g., birth certificates + National Insurance letters for UK nationals without a passport). These are document-in-hand reviews.

Online checks are required for anyone whose immigration status is held digitally — which, post-BRP phase-out, is the majority of non-UK nationals. These use either:

The Home Office online checking service (share code + date of birth)
An Identity Document Validation Technology (IDVT) provider for British/Irish citizens (commercial services like Yoti, Onfido, etc.)

The system implication: you cannot treat all non-UK workers as "do manual check." You need logic in your onboarding workflow to route workers to the correct check type based on their nationality and immigration status.

Share codes: the technical flow

A worker with eVisa status generates a share code through their UKVI account. The employer inputs that code plus date of birth at gov.uk/view-right-to-work to get a result.

Key technical points:

Share codes are valid for 90 days from generation
The result must be stored as a dated record — typically a screenshot or PDF — tied to the worker's employment record
For time-limited right to work (visa expiry), your system needs to flag the expiry date and trigger a follow-up check before it lapses
The check result page shows name, DOB, right to work type, and any time limit — your record must capture all of these

If you're automating any part of this via API: the Home Office does not currently offer a public API for bulk employer right to work queries. Share code validation happens through the employer-facing web interface. Any vendor claiming to automate this via a backend API without user authentication is worth scrutinising carefully.

Statutory excuse and what breaks it

Statutory excuse is the legal shield that protects employers from civil penalties if a worker turns out not to have the right to work. Checks that fail to create this shield offer false confidence.

Statutory excuse is lost if:

A manual check was done on someone whose right to work is digital-only (eVisa, no physical BRP)
The check was done on a copy rather than an original (manual checks)
The check was done after the employment start date
The share code was entered but no dated record was stored

For HR systems: the date stamp on the check record should be auto-generated at the time of check, not editable by users post-hoc.

Follow-up checks for time-limited right to work

Workers on time-limited visas (Skilled Worker, Graduate, Health and Care, etc.) must have their right to work rechecked before their visa expires. If the check isn't done and they're still employed after expiry, the employer loses statutory excuse from that date.

Your system needs:

A field for the worker's visa expiry date, populated at initial check
Automated reminders at 90 and 30 days before expiry
A workflow that triggers a new share code check and updates the dated record

This is where many HR systems rely on manual tracking — and where compliance gaps compound. An employer who was meticulous at onboarding can find themselves in breach 18 months later because no one tracked the expiry.

Discrimination avoidance in system design

One legal requirement that often gets missed in technical implementation: all workers must be checked using the same process. You cannot build a workflow that routes British nationals through a lighter check compared to non-UK nationals.

Practical implementation: check type differs based on document type, not nationality. Your HR system should present the same initial prompt to all new starters and branch based on what documents they can provide — not based on where they're from. Filtering by nationality at the workflow-routing stage is an Equality Act problem.

Sponsor licence cross-referencing

If your organisation holds a UK sponsor licence and sponsors Skilled Worker or other visa holders, right to work checks are the floor, not the ceiling. Sponsors must also maintain sponsorship records, report changes in circumstances, and keep visa documents tied to CoS (Certificate of Sponsorship) records within defined timescales.

Tools like immigrationgpt.co.uk can help HR and compliance teams search the sponsor register and understand obligations — but the underlying compliance infrastructure needs to live in your HRIS and be maintained there.

The compliance architecture for right to work in 2026 is more complex than it was pre-eVisa. Systems built before 2024 that haven't been updated to handle digital-only immigration status are carrying silent risk.

This post is for technical and informational purposes. For legal compliance advice, consult a UK immigration solicitor or registered adviser.

UK Skilled Worker Visa 2026: The Going Rate Stack — Why Checking the General Threshold Isn't Enough

ImmigrationGPT — Tue, 08 Sep 2026 08:07:48 +0000

UK Skilled Worker Visa 2026: The Going Rate Stack — Why Checking the General Threshold Isn't Enough

Most eligibility logic for UK Skilled Worker visa compliance starts with a single salary check: is the offered salary >= £38,700? That check is necessary. It is not sufficient.

The Home Office applies a two-constraint model, and failing either constraint produces a refusal. Building your compliance system around only one of them means your eligibility screen has a systematic blind spot.

The Two-Constraint Model

Every Skilled Worker visa application is assessed against both:

General minimum salary — currently £38,700/year or £10.75/hour, whichever is higher (post-April 2024 thresholds)
SOC-code going rate — the 25th percentile salary for the specific occupation, as defined in the Home Office Skilled Worker Appendix

The operative threshold is max(general_minimum, going_rate). An application that clears £38,700 but falls below the going rate for its SOC code fails on constraint 2.

For common SOC codes where going rates exceed the general minimum:

SOC 2136 (Software developers): ~£49,400
SOC 2121 (Civil engineers): ~£45,900
SOC 2139 (IT professionals NEC): ~£43,800
SOC 1132 (Marketing managers): ~£47,100
SOC 2112 (Biological scientists): ~£40,200

If your eligibility check returns PASS at £39,000 for a software developer, it's wrong.

Modifier Stack: New Entrant and ISL Discounts

The system applies two potential discount multipliers. Neither is simply subtracted from the general minimum. Both apply to the going rate.

New Entrant Rate

Conditions for new entrant classification:

Switching from Student or Graduate visa at time of application
Within first 3 years of career post-graduation (PhD holders get additional flexibility)
Under 26 at the date of application (removed as a standalone criterion in 2024 — now must meet one of the above)

Threshold calculation:

new_entrant_going_rate = max(going_rate * 0.70, 30_960)
operative_threshold = max(new_entrant_going_rate, 30_960)

Wait — those two lines collapse to:

operative_threshold = max(going_rate * 0.70, 30_960)

The common implementation error: treating £30,960 as a flat new entrant threshold regardless of the going rate. If the going rate is £50,000, the new entrant threshold is £35,000 — not £30,960. Setting the salary to £30,960 fails constraint 2.

Immigration Salary List (ISL) Discount

The ISL replaced the Shortage Occupation List in April 2024. For ISL-listed occupations, the going rate threshold is discounted by 20%. The general minimum is unaffected.

isl_going_rate_threshold = going_rate * 0.80
operative_threshold = max(isl_going_rate_threshold, 38_700)

The trap: When going_rate * 0.80 < 38_700, the ISL discount doesn't reduce the minimum at all. The general threshold becomes binding again.

Example: ISL role with going rate £45,000

Discounted going rate: £36,000
General minimum: £38,700
Operative threshold: £38,700 (general minimum wins)

Example: ISL role with going rate £55,000

Discounted going rate: £44,000
General minimum: £38,700
Operative threshold: £44,000 (discounted going rate wins)

The ISL discount only provides meaningful relief where going_rate > £48,375 (since 80% of that = £38,700, above which ISL starts beating the general floor).

Combined: New Entrant on ISL Role

operative_threshold = max(going_rate * 0.70, 30_960)

Note: new entrant on an ISL role does NOT stack the two discounts to get 50% of going rate. The new entrant rate applies, which already incorporates the more generous discount.

SOC Code Validation Is a Pre-Condition

Salary logic is only correct if the SOC code is correctly assigned. SOC codes are not self-evident from job titles:

"Data analyst" → could be 2137 (IT business analysts), 2154 (data scientists), or 3539 (business associate professionals NEC)
"Product manager" → 2137 or 1134 depending on scope
"UX designer" → 2139 or 3111 (laboratory technicians) — a mistake that's been made

Home Office case workers cross-reference the SOC code against the job description in the Certificate of Sponsorship. Mismatches trigger requests for further information and can result in refusal.

Your compliance system should flag applications where:

The job title doesn't clearly map to the assigned SOC code
The assigned SOC code's going rate is significantly different from what the sponsor expected
The salary is close to (within 5% of) the going rate threshold — these cases have no margin for SOC reclassification

Pseudocode for a Correct Eligibility Function

def skilled_worker_eligible(salary, soc_code, is_new_entrant, is_isl):
    going_rate = get_going_rate(soc_code)  # from current HO appendix

    if is_new_entrant:
        going_rate_threshold = max(going_rate * 0.70, 30_960)
        general_floor = 30_960
    elif is_isl:
        going_rate_threshold = going_rate * 0.80
        general_floor = 38_700
    else:
        going_rate_threshold = going_rate
        general_floor = 38_700

    operative_threshold = max(going_rate_threshold, general_floor)

    return {
        "eligible": salary >= operative_threshold,
        "operative_threshold": operative_threshold,
        "binding_constraint": "going_rate" if going_rate_threshold >= general_floor else "general_floor",
        "margin": salary - operative_threshold
    }

The binding_constraint field matters for error messages. If general_floor is binding, telling the user their SOC code's going rate is wrong won't help them.

Data Currency Problem

Going rates are updated periodically based on ASHE data. The going rate for SOC 2136 in 2023 was different from 2024. Any system that hardcodes going rates rather than pulling from a regularly updated source will drift out of compliance within 12 months.

For the current going rate table and a working eligibility check against real applicant parameters, ImmigrationGPT maintains an up-to-date implementation.

This post covers the technical structure of UK Skilled Worker salary thresholds as of September 2026. Immigration rules change. Verify against the current Home Office Skilled Worker Appendix before making compliance decisions.

UK Spouse Visa 2026: Calculating the Minimum Income Requirement — Where Compliance Logic Breaks Down

ImmigrationGPT — Mon, 07 Sep 2026 08:09:43 +0000

The problem isn't the threshold

The £29,000 Minimum Income Requirement for UK spouse visas sounds like a simple field to validate: sponsor_income >= 29000 → eligible. Most HR and compliance systems treat it that way. That's wrong.

The UKVI assessment logic is more granular, and several edge cases that are common in real workforces produce incorrect pass/fail outputs when you model them as a single threshold check.

Income categorisation matters before the comparison

UKVI doesn't aggregate across income types. The categories are mutually exclusive for assessment purposes:

Category A: Salaried and non-salaried employment (6+ months at current employer)
Category B: Salaried/non-salaried with <6 months at current employer, or recent employment gap
Category C: Self-employment, sole trader, limited company director
Category D: Non-employment income (rental, pension, investments)
Category E/F: Cash savings top-up

If the sponsor has both self-employment income and salaried income, they can't add them. They pick the category that applies to their primary income source, and only that income counts.

This breaks the naive "total income >= threshold" validation.

Category B edge cases

Category B is where most HR integration errors occur. It applies when the sponsor:

Has been with their current employer less than 6 months
Had a gap in employment in the past 12 months
Changed from self-employment to employment (or vice versa) within the last 12 months

For Category B, UKVI looks at both current employment income and income from any previous employer in the past 12 months — but only employment income, and the two employers must be distinct entities.

If your system is pulling the sponsor's income from their current payroll record only, it will misclassify Category B sponsors who have 12-month income that satisfies the threshold across two employers.

The savings top-up formula

If income is insufficient, savings bridge the gap:

required_savings = ((threshold - annual_income) * 2.5) + 16000

Example:

Threshold: £29,000
Annual income: £22,000
Gap: £7,000
Required savings: (7000 × 2.5) + 16000 = £33,500

Savings must be:

Held in a regulated financial institution
Continuously held for at least 6 months before application date
In the name of the sponsor, the applicant, or jointly (fully counted in all cases)

The 6-month rule is applied strictly. A transfer from a foreign account to a UK account 5 months and 28 days before application will fail the continuous holding test, even if the foreign account held the funds for years prior.

What income categories don't contribute

Building the exclusion list is as important as the inclusion logic:

Child benefit: not counted
Working Tax Credit / Universal Credit: not counted
Maintenance payments received: not counted
Income from the applicant (overseas partner): not counted at entry clearance stage
Casual work / informal economy income not evidenced by payslips: not counted

Child benefit in particular causes errors in financial aggregation pipelines — many APIs include it in "household income" figures, producing false positives if passed to an MIR check without filtering.

The threshold drift problem

£29,000 is the current MIR as of early 2026. It was £18,600 before April 2024, raised in stages. A further increase was planned but has not been confirmed. Any system that hardcodes the threshold needs a configuration point — not a constant — for this value.

The same logic applies to the savings floor (currently £16,000). Both figures have changed in the last two years and may change again.

Summary of failure modes in eligibility modelling

Error	Common cause
False positive for mixed income	Aggregating across UKVI categories
False negative for Category B	Only checking current employer payslips
False positive savings top-up	Not checking 6-month holding period
False positive benefit income	Including child benefit in income total
Stale threshold	Hardcoded £18,600 from pre-2024 rules

The MIR seems like a simple eligibility check. The edge cases are dense enough that they warrant a separate decision tree, not a single comparison operator.

For up-to-date information on current thresholds and acceptable evidence, ImmigrationGPT provides answers based on live Home Office guidance.

For general information only. Not legal advice. UK immigration rules change frequently.

UK Visa Appeal Routes 2026: Modelling the Decision-Challenge State Machine in HR and Compliance Systems

ImmigrationGPT — Fri, 04 Sep 2026 08:08:09 +0000

When a sponsored worker's visa application is refused, most HR platforms flag it as a terminal state and hand it to the employee's solicitor. That's the right escalation, but it creates a blind spot: the compliance system loses visibility during the appeal period, which can be 6–18 months, and the worker's right to remain — and right to work — may continue or lapse depending on which appeal route was taken and when.

Modelling the appeal period correctly matters because the states aren't equivalent and the downstream effects on right-to-work checks, payroll, and sponsor duties are different for each.

Two routes, two different data models

There are two distinct challenge mechanisms in UK immigration:

Administrative review is an internal Home Office check. The applicant argues that a caseworking error occurred — a document was overlooked, a calculation was wrong, an evidential requirement was misapplied. No judge is involved. The Home Office reviews its own decision. Administrative review does not extend section 3C leave (the statutory right to remain while an in-country application is being decided). Once it fails, the applicant's leave — if any — ends on the original date.

First-tier Tribunal appeal goes to the Immigration and Asylum Chamber. A judge hears it. The applicant can present new evidence, argue legal grounds including human rights (Article 8), and challenge the proportionality of the decision, not just its procedural correctness. Crucially for HR systems: lodging a tribunal appeal from inside the UK does extend section 3C leave. The worker's leave continues until the appeal is determined or withdrawn.

These two paths produce different leave states for the sponsored worker, different right-to-work check obligations for the employer, and different sponsor reporting duties under SMS.

Deadline logic

The deadline model is the first place compliance systems tend to break:

Administrative review (in-country): 14 days from service of the refusal decision
Tribunal appeal (in-country): 14 days from service (28 days if in detention)
Administrative review (out-of-country): 28 days from service
Tribunal appeal (out-of-country): 28 days from service

Service date is not receipt date. If the decision was served to a UK address while the applicant is overseas, the 28-day clock still runs from the service date on the document, not from when the applicant physically reads it.

Any compliance system that calculates challenge windows from the date the employee notified HR has the wrong anchor. The anchor is the decision service date on the refusal letter.

Which route applies to which visa type

This is where the logic tree gets complicated:

Skilled Worker refusal (non-human rights grounds): administrative review only in most cases
Skilled Worker refusal (human rights grounds raised): tribunal appeal may be available
Spouse / family visa refusal: tribunal appeal, often on Article 8 grounds
Student visa refusal: administrative review for most PBS routes
Refusals where no appeal or review right exists: increasingly common for PBS applications refused for non-compliance with the Rules rather than caseworker error

The presence or absence of an appeal right is determined by the Immigration (Leave to Enter and Remain) Order 2000 and the Nationality, Immigration and Asylum Act 2002 as amended. A compliance system that assumes every refusal generates an appeal right will misclassify a meaningful proportion of cases.

Right-to-work implications during appeal

Section 3C leave applies only to in-country applications and only when the appeal is lodged before the original leave expires. If the worker's leave expires before the appeal is lodged — even by one day — section 3C does not apply and the worker no longer has leave to remain.

For right-to-work purposes, a worker in the appeal period with active section 3C leave can still work. The employer must hold a Positive Verification Notice from the Home Office Employer Checking Service — a share code check alone is not sufficient during this period.

HR systems that rely solely on share code verification will miss the ECS step and may generate a false positive on right-to-work compliance.

Success rate context

Roughly 40% of First-tier Tribunal immigration appeals are allowed. The breakdown by route matters: human rights appeals (Article 8 family life) run materially higher than Points-Based System appeals, where the binary rules leave less room for proportionality arguments.

Administrative review outcomes are not published systematically, but the Home Office's own transparency data has historically shown review success rates well below 20% for Points-Based System cases.

What to build into case tracking

A minimal appeal-period data model needs:

Challenge type (admin review / tribunal / none available)
Submission date (to validate deadline compliance)
Decision service date from refusal letter (the deadline anchor)
Section 3C leave flag (boolean, with expiry logic tied to submission timing)
ECS verification requirement flag (triggered when section 3C is active)
Appeal outcome and date (to trigger downstream leave recalculation)

Without these fields, a compliance system cannot correctly determine the worker's leave status, the employer's right-to-work obligations, or whether the sponsor has a reporting duty under the sponsor guidance.

For a plain-language breakdown of how appeal routes apply to specific visa categories, immigrationgpt.co.uk covers the current rules and route logic based on official Home Office guidance.

For compliance-critical decisions, always confirm against the current Immigration Rules and Sponsor Guidance, which are updated without notice.

UK Visa Refusal Patterns 2026: Pre-Submission Validation Rules That Catch the Five Most Common Failure Modes

ImmigrationGPT — Thu, 03 Sep 2026 08:07:40 +0000

UK visa refusal rates have held at around 1-in-7 for general entry clearance applications over the past three years. The pattern in Home Office decision letters is consistent enough that it's worth formalising as structured validation logic — particularly for HR platforms, compliance tools, and recruiting systems that guide applicants through submission.

This post maps the five highest-frequency refusal reasons to concrete pre-submission checks, with specific field references where they apply.

1. Financial Evidence: Period Coverage Failure

Refusal pattern: Financial evidence submitted but doesn't cover the required period, or meets the threshold in amount but not in format.

For Skilled Worker routes: The financial requirement falls on the sponsor (via the certificate of sponsorship). The applicant doesn't submit personal finances — but if a compliance tool is pre-screening candidate eligibility, the salary offered must clear the going rate threshold and the general threshold (£38,700 or role-specific minimum, whichever is higher).

For family routes (spouse/partner): The UK sponsor must demonstrate income at or above £29,000. Required format:

6 months of payslips (or equivalent evidence if self-employed)
6 months of personal bank statements showing those deposits
Employer letter confirming current salary

A bank statement alone is insufficient. Payslips alone are insufficient. The combination is required. Systems that only check for "financial evidence present" without validating document type and period coverage will pass invalid applications.

2. English Language Requirement: Exemption Logic Errors

The English language requirement applies across multiple routes (Skilled Worker, spouse/partner, student). The exemption list — nationalities from "majority English-speaking countries" — is defined by the Home Office, not by intuitive geography.

Key validation rules:

Exemption check: Nationality against GOV.UK exempt country list (updated periodically — parse from source, don't hardcode)
Academic qualification exemption: Degree-level qualification, taught in English, from a non-exempt country → requires UK ENIC assessment, not just a certificate
Test expiry: Most approved tests (IELTS, TOEFL, etc.) valid for 2 years from test date. An expired result fails even if the score meets the threshold

3. Sponsor Licence Status at Decision Time

The Skilled Worker route CoS is only valid if the sponsoring employer holds an active licence when the Home Office processes the application — not just when the CoS was issued.

Licence status can change:

Suspension (compliance investigation) — CoS becomes frozen
Revocation — CoS becomes invalid

The public register at GOV.UK is updated when licences are suspended or revoked. Any compliance system managing Skilled Worker cases should:

Verify sponsor licence status at CoS issuance
Re-verify within 48-72 hours of planned submission
Alert if status has changed to Suspended or Not on register

The Home Office ran compliance sweeps resulting in around 450 suspensions in a recent six-month period. Refusals from sponsor licence status change after CoS issue are non-appealable on the merits — they require a new CoS from a licensed sponsor.

4. Immigration History: Disclosure Field Validation

Applications contain mandatory disclosure fields for prior refusals, overstays, removals, and bans. Common system failures:

Lookback period not enforced: Many HR intake forms ask "Have you ever been refused a UK visa?" without surfacing whether a "no" from 10 years ago is still accurate
Resolved overstays: An overstay that ended via voluntary departure still requires disclosure — "resolved" does not mean "exempt from disclosure"
Previous refusals on non-UK visas: Some routes require disclosing refusals from other countries. Validation logic often only captures UK refusal history

The Home Office has access to border records that extend back further than most applicants expect. Inconsistency between disclosed history and UKVI records is a standalone refusal reason independent of whether the underlying issue is disqualifying.

5. Document Consistency Validation

High-frequency failure mode even in well-prepared applications: name mismatches, reference number discrepancies, and uncertified translations.

Specific checks to automate:

Name normalisation: Compare passport name against all supporting documents — flag exact mismatches
Translation certification: Non-English documents require certified translation from an accredited translator. Self-certification by the applicant is not accepted
Business registration number match: If self-employment evidence is submitted, cross-reference registration numbers across all documents
Date consistency: Marriage certificate date should not post-date the claimed relationship start date in the covering letter

The Home Office does not request clarification on document inconsistencies — the standard process is to refuse and require reapplication.

Summary Table

Refusal Category	Validation Type	Automatable?
Financial period coverage	Rule-based: document type + date range	Yes
Language test expiry	Rule-based: test date + 2-year window	Yes
Sponsor licence status	API check: GOV.UK register	Yes
Immigration history disclosure	Completeness check + cross-reference	Partial
Document consistency	Name/number matching	Partial

If you're building compliance tooling for UK immigration or need to query current rules against a specific application scenario, ImmigrationGPT provides structured answers based on live GOV.UK guidance.

For legal compliance matters, consult a regulated immigration adviser.

UK Points-Based Immigration 2026: How the Route Architecture Actually Works, and Where Eligibility Logic Breaks Down

ImmigrationGPT — Wed, 02 Sep 2026 08:08:00 +0000

UK Points-Based Immigration 2026: How the Route Architecture Actually Works, and Where Eligibility Logic Breaks Down

The UK's points-based immigration system turned five years old this year, and the compliance tooling built around it is still making the same foundational mistakes. Not because the system is particularly complex — it isn't — but because the "points" framing creates a mental model that doesn't match how decisions are actually made.

Here's what's actually happening under the hood, and where automated eligibility checks tend to go wrong.

The Name Is Misleading

"Points-based" implies a scoring system where you accumulate points until you hit a threshold. That's not how most routes work. For the Skilled Worker visa — the main employment route — you need 70 points. But 50 of those points are mandatory and non-tradeable: sponsorship (20 points), skill level at RQF3 or above (20 points), and English language (10 points). The remaining 20 come from salary meeting the going rate for the SOC code.

In practice, that means the system is closer to a checklist with one variable criterion than a flexible points accumulation model. An applicant either has a sponsor or they don't. Either the role meets RQF3 or it doesn't. The salary either meets the going rate threshold or it doesn't. There's no partial credit, no compensating factors across those mandatory elements.

Compliance systems that model this as a flexible point trade-off will produce wrong results whenever they try to compensate a salary shortfall with other "points."

The Tradeable Points Are Narrower Than They Appear

The 20 tradeable points exist for situations where a role's salary falls below the going rate. Three scenarios allow a lower salary to still meet the threshold:

The applicant is a new entrant (typically under 26, in a graduate programme, or switching from a student visa): going rate reduced by 30%, minimum floor at £30,960
The role is on the shortage occupation list: going rate reduced by 20%
The role comes with a PhD relevant to the role: going rate reduced by 10% (or 20% for a STEM PhD in a shortage occupation)

These reductions can stack — but only in specific combinations. A new entrant in a shortage occupation role gets the larger of the two discounts, not both added together. Systems that add percentage reductions without checking for stacking rules will calculate incorrect floors.

The minimum salary threshold — currently £38,700 for most applicants — also operates as a hard floor beneath the going rate calculation. Even if the going rate for a role is lower than £38,700, the applicant must earn at least £38,700 unless an exception applies. Those exceptions (healthcare workers, new entrants, some education roles) each have their own floors that must be applied instead.

Route Switching Changes the Points Calculation

When an applicant switches from one route to another in-country, the points requirements don't change — but the evidence accepted to meet them can. Someone switching from a Student visa to a Skilled Worker visa is treated as a new entrant if they're within two years of their course end date, which shifts the applicable salary floor down by 30%.

HR systems that check right-to-work post-switch without updating the salary eligibility logic can end up validating roles that would actually fail a fresh application assessment. This becomes relevant when a company sponsors a switch applicant at a salary that's valid under new entrant rules, then the employee later seeks an extension or ILR — at which point new entrant status no longer applies and the salary may no longer meet the standard going rate.

Dependent Applications Add a Separate Layer

Points thresholds don't change with dependants, but the minimum salary requirement does — for some routes. Skilled Worker applicants must now meet an additional financial requirement when bringing dependants, tied to minimum income thresholds separate from the going rate logic. This threshold is entirely separate from the 70-point calculation and doesn't interact with it.

Eligibility checks that only run the points calculation and ignore the dependent financial requirement will return false positives for applicants trying to bring family members.

The Global Talent Route Has No Points at All

The Global Talent visa is consistently categorised as part of the points-based system, but it doesn't use a points threshold. It's endorsement-based: an approved body (Tech Nation successor, British Academy, Royal Society, etc.) assesses an application against their own criteria and issues or refuses endorsement. The Home Office then grants or refuses based on endorsement status.

Grouping this route with Skilled Worker in compliance logic is a category error. The data requirements, evidence types, and decision pathways are entirely different.

What Actually Matters for Compliance Systems

The reliable approach is to treat each route as a separate decision tree rather than a unified points model. For Skilled Worker specifically, the sequence is:

Is there a valid sponsor licence (and is it not suspended or revoked)?
Does the role meet RQF3?
Does the applicant meet English language requirements?
What is the SOC code going rate?
Which salary floor applies (standard, new entrant, or shortage occupation)?
Does the offered salary meet the applicable floor?
Are there dependants? If yes, does the salary meet the separate dependant income threshold?

Steps 4 and 5 require current data — the going rate tables were revised in April 2024 and reflect updated ONS salary data, so any system using pre-2024 going rates is working from wrong numbers.

ImmigrationGPT covers the sponsor licence register, salary threshold lookups, and route eligibility checks with data sourced from GOV.UK. If you're building compliance tooling or just need to verify a specific scenario, it's worth cross-referencing against the live register rather than relying on cached snapshots.

This article is for informational purposes only. Immigration rules change and individual circumstances vary. Always consult a qualified immigration adviser for decisions affecting visa applications.

UK Family Visa Routes 2026: What Compliance Systems Need to Model for Dependent and Partner Applications

ImmigrationGPT — Tue, 01 Sep 2026 08:07:49 +0000

HR and compliance platforms that handle UK visa tracking often lump family visas into a single "dependent visa" bucket. That's a category error. The Home Office has six distinct family routes with materially different eligibility logic, leave conditions, and ILR timelines — and getting the categorisation wrong in your system leads to incorrect right-to-work expiry flags, missed renewal windows, and miscommunication with employees about their settlement timeline.

Here's the reference architecture.

The Six Routes and Their Key Distinguishing Parameters

Spouse / Civil Partner Visa (entry clearance + FLR(M))

Financial threshold: £29,000 gross annual income from the UK sponsor. Not household income — the sponsor's income alone. Savings top-up: £16,000 baseline plus £2.50 saved for every £1 of annual income shortfall, held continuously for at least six months. English language: B1 speaking and listening from a Home Office-approved provider. Leave structure: 33 months initial, 30-month extension, ILR eligibility at five years. Right to work: unrestricted once leave is granted.

Unmarried Partner Visa

Financially identical to the spouse route. The distinguishing requirement: two years of continuous cohabitation, documented with overlapping official correspondence from the same address. Most systems treat this as equivalent to the spouse route — the ILR path is the same — but the cohabitation evidence requirement is a separate application failure point worth flagging in any pre-application screening workflow.

Fiancé(e) Visa

Six months, no right to work, no extension. Purpose is entry to marry in the UK, then switch to FLR(M). The ILR clock does not start from fiancé(e) entry — it starts from the first FLR(M) grant. This is a critical modelling error in many HR systems: an employee on a fiancé visa has no right to work until the FLR(M) application is approved. Any right-to-work check run against a fiancé(e) vignette should flag a work restriction, not a clean pass.

Child Visa

Applies to children under 18. At least one parent must be settled in the UK or applying simultaneously, unless the sponsor can demonstrate sole responsibility. Children under 18 do not generate their own right-to-work codes — right to work is not applicable at that age. HR systems tracking dependants should hold the parent's settlement status as the relevant variable, not the child's leave directly.

Parent Visa

The eligibility gate is strict: the parent must not be leading an independent life, and must require long-term personal care that cannot reasonably be provided in the home country even if the family could fund it privately. The financial requirement falls on the UK sponsor.

The ILR path is ten years, not five. This is the most common modelling error in compliance systems that handle family visas: any tool that calculates ILR eligibility as grant date plus five years will produce wrong output for parent visa holders. The correct value is ten years of continuous lawful leave.

Adult Dependent Relative Visa

Scope: siblings, adult children over 18, grandparents, other extended family. Same personal care threshold as the parent route, with a higher evidentiary bar — the applicant must show the required care is unavailable in their home country even with the financial means to purchase it. Refusal rates on this route are consistently high. ILR conditions mirror the parent visa.

What HR Systems Should Track Per Employee

For any employee with family visa holders as dependants, the minimum compliant data model needs:

Visa category by route — not just "family visa". Spouse, partner, fiancé, child, parent, and ADR have materially different work permissions and ILR timelines.
Leave expiry from BRP or eVisa — not from application date or grant date. These frequently diverge.
Right-to-work status of the visa holder — spouse/partner grants full right to work; fiancé(e) visa does not; child visa not applicable.
ILR eligibility date — 5 years for spouse/partner, 10 years for parent. Hard-coding 5 years for all family routes is wrong.
Renewal window — FLR(M) can be submitted up to 28 days before expiry. Flag to HR at 90 days to give employees realistic preparation time.
Share code validity — Home Office share codes expire after 90 days. Right-to-work verifications run more than 90 days ago need to be rerun.

The Income Threshold and Where Calculations Break

The £29,000 threshold is gross annual income from the UK sponsor. Several common scenarios break a straightforward salary check:

Recent employer change: income evidence must typically come from the same employer over a continuous period. Payslips from two employers in the six-month window require careful handling in the application.
Self-employment: the calculation uses the average of the last two years' self-assessment profit, not current invoiced income. A record year followed by a lower year produces a lower qualifying figure than applicants expect.
Variable hours: only guaranteed contract hours count unless payslips show a consistent pattern over the reference period. Zero-hours contracts with variable income are a known point of failure.

HR platforms pre-screening employees' ability to sponsor family members should model these conditions rather than using gross salary as a binary threshold check. The savings top-up route (£16,000 + 2.5× the income shortfall) is worth surfacing as an alternative calculation path where income falls short.

For a tool that parses the current Immigration Rules directly and gives route-specific answers, immigrationgpt.co.uk is useful for HR teams handling ad-hoc employee queries without re-reading the Rules after each policy update.

For guidance on a specific case, consult a regulated immigration adviser or solicitor. Immigration Rules change; verify against current Home Office published guidance.

UK Graduate Route 2026: What HR and Hiring Managers Actually Need to Know

ImmigrationGPT — Mon, 31 Aug 2026 08:07:41 +0000

The UK Graduate visa sits between the Student visa and any long-term employment-based route. For HR teams and hiring managers, it creates a specific operational context that's genuinely worth understanding — because it removes the sponsor licence burden entirely, which changes the hiring calculus significantly.

Here's a technical breakdown of what this route means for employers and talent pipelines.

No sponsor licence required — what this means operationally

A candidate on a Graduate visa has unrestricted permission to work in the UK. They do not require an employer to hold a Skilled Worker sponsor licence. No Certificate of Sponsorship (CoS) is needed. There is no obligation to notify UKVI of a job change.

For right to work purposes, the employer's obligation is:

Verify the individual's status via the UKVI online service (or check the BRP)
Note the expiry date
Retain evidence of the check

That's it. Graduate visa holders are operationally equivalent to EU Settlement Scheme holders from a hiring process perspective: simpler than sponsoring, no ongoing reporting obligations, no per-visa costs.

The expiry problem — and why it requires succession planning

The Graduate visa expires. Two years is not long. For roles where you want long-term retention, the HR implication is that you need a Skilled Worker sponsorship pathway lined up before expiry.

The timeline matters here. Assume:

8-12 weeks for sponsor licence application (if you don't already hold one)
4-8 weeks from licence grant to Certificate of Sponsorship issuance
3 weeks for UKVI to process the Skilled Worker application (standard service; priority is faster but carries a fee)

If you start the process 6 months before the Graduate visa expires, you're generally safe. If you start 3 months out, you're cutting it close. If you start 6 weeks out, you have a problem.

For HR systems: flag Graduate visa expiry dates at point of hire. Build a 6-month pre-expiry review trigger into your HRIS workflow.

Salary threshold compatibility check

When transitioning someone from Graduate route to Skilled Worker, the current minimum salary threshold is £38,700 for most Standard Occupational Classification (SOC) codes — or the going rate for that specific code, whichever is higher.

The going rate for some technical roles (software engineers, certain healthcare roles) is higher than £38,700. Check the Skilled Worker Appendix published by the Home Office — last updated April 2024, with ongoing adjustments possible. Build your salary bands for graduate hires with Skilled Worker compatibility in mind from the start.

A £2,000 salary gap discovered at the sponsorship stage is an avoidable problem. Discovering it at month 22 of a 24-month Graduate visa is not.

What to build into your hiring pipeline

Right to work check at hire — use the UKVI online service, not just a document review. Retain the evidence.
Record the Graduate visa expiry date in your HRIS at point of hire.
6-month pre-expiry trigger — decide whether to sponsor on Skilled Worker. If yes, begin the CoS process immediately. If your organisation doesn't hold a sponsor licence, start that application now.
Salary verification against SOC going rate — confirm the role's salary meets both the £38,700 floor and the occupation-specific going rate before committing to sponsorship.

One thing most HR teams get wrong

The Graduate visa cannot be extended. If the Skilled Worker application is not filed before the Graduate visa expires — or is refused — the individual loses their right to work in the UK. This has employment law implications: you'd be required to end employment. Avoiding this requires planning, not firefighting.

If your organisation doesn't currently hold a sponsor licence, the ImmigrationGPT sponsor search lets candidates verify whether a specific employer is a registered UK sponsor — useful both for candidates checking before accepting offers and for HR teams researching what peer organisations are licensed.

UK immigration rules change. This post is informational only — consult a qualified immigration adviser for case-specific guidance.