Most HR platforms that handle UK immigration compliance are good at tracking visa expiry dates. Almost none of them model ILR eligibility correctly — and that gap has real consequences: employees lose track of their qualifying window, employers make decisions based on inaccurate residence status, and ILR applications get submitted with avoidable errors.
This post covers the actual logic of ILR eligibility as it applies in 2026, with the precision you need to implement it correctly in a compliance or HR tool.
The Qualifying Period: Not as Simple as a Date Diff
The core rule sounds simple: 5 years continuous lawful residence in the UK on a qualifying route. But application_date - visa_start_date >= 5_years is not the right calculation.
Three things complicate it.
Route-specific qualifying periods. Skilled Worker is 5 years. Global Talent is 3 or 5 years depending on endorsement type (Exceptional Promise vs Exceptional Talent). Innovator Founder is 3 years. UK Ancestry is 5 years. Any system modelling ILR eligibility needs a qualifying_years field per route, not a hardcoded value.
Route changes reset the clock. Time on a Student or Graduate visa does not count toward ILR. The transition Student → Graduate → Skilled Worker trips people up constantly. A person who has lived in the UK for 7 years might have only 3 years of ILR-qualifying residence. A correct data model needs a qualifying_start_date that reflects the beginning of the most recent unbroken qualifying route chain — not the applicant's first UK entry date.
The Skilled Worker re-entry edge case. If someone leaves the UK and re-enters on a new Skilled Worker visa rather than an extension, the qualifying period continues rather than resetting — provided the gap does not constitute a break in lawful residence. Absence tracking and visa continuity tracking are separate concerns that interact.
Absence Tracking: Rolling Windows, Not Calendar Years
The 180-day absence limit is calculated on a rolling 12-month basis, not per calendar year or visa year. This is the most commonly misimplemented rule.
The correct calculation: for any date D in the qualifying period, absences in the 365-day window [D-365, D] must not exceed 180 days. This must hold for every single day in the qualifying period — not just a snapshot at application time.
A person could pass a per-year check but fail a rolling-window check if absences cluster at the boundary between two years. UKVI runs the rolling check.
For a compliance system this means: a complete absence log for the full qualifying period, a function calculating the maximum rolling-window violation rather than total absences, and alerting logic that flags risk during the qualifying period — not six months before the application deadline.
Salary Continuity for Skilled Workers
Skilled Worker ILR does not require a specific salary floor, but it requires the applicant was paid at least the going rate for their SOC code throughout the qualifying period. A role change without a new Certificate of Sponsorship, a salary reduction, or a gap in employment all need to be evidenced.
For HR systems: store historical salary records against the CoS they were paid under, not just current compensation. An employee who changed job titles internally may have needed a new CoS — if the role change involved a different SOC code or a salary drop below the going rate, the ILR application is exposed.
Good Character: The Fields Most Systems Ignore
The good character requirement catches things that do not look like immigration issues: criminal convictions including overseas ones, civil penalties under immigration law, short periods of overstay (even 1-2 days), and working in breach of visa conditions such as exceeding the student 20-hour work limit.
Most HR compliance systems do not capture overstay history because it predates the employer relationship. But it is something employees should self-audit before submitting.
English Language and Life in the UK Test
These are binary gates. Systems tracking ILR readiness should flag whether a valid Life in the UK test pass certificate exists and whether an accepted English language qualification has been taken within the allowable window.
The list of accepted English tests changes. Build in a data refresh mechanism rather than hardcoding accepted test types. Some applicants are exempt — citizens of majority English-speaking countries, or those with degrees taught in English. Exemption logic needs to be explicit.
What This Means for Compliance Tooling
The tools that actually help employees reach ILR are the ones that start tracking from day one of the qualifying period. Absence alerts, salary continuity monitoring, and route-eligibility checks need to be in the normal workflow, not bolted on at the end.
The Home Office guidance on SET(O) applications and the Immigration Rules Appendix Continuous Residence are the authoritative sources. They update periodically — point-in-time snapshots of eligibility logic will drift.
If you are working on immigration status verification or sponsor licence checking for UK employers, ImmigrationGPT covers the UK sponsor register — useful context for ILR-adjacent compliance workflows.
Nothing in this post constitutes legal advice. Verify against current Home Office guidance before implementing.
Top comments (0)