ILR Absence Compliance in 2026: How to Build an Absence-Tracking System for UK Settlement Applications

HR teams and immigration compliance developers rarely spend time thinking about absence tracking — until someone's ILR application gets refused and the question becomes urgent. This post outlines the technical requirements behind the UK's continuous residence rule, and how to build tooling (or configure existing HRIS data) to surface compliance issues before they become problems.

The Rule in Plain Technical Terms

For Indefinite Leave to Remain (ILR) via most sponsored work routes (including Skilled Worker), an applicant must not have exceeded 180 days of absence from the UK in any rolling 12-month window during their qualifying period (typically five years).

Key variables:

• Rolling window: Not calendar year. Any consecutive 365-day period.
• Absence definition: Days physically outside the UK border. The departure day counts; arrival day typically does not.
• Qualifying period start date: Usually the date the first visa was granted, not the date of entry.

The Home Office assesses this retrospectively at the point of application. There is no real-time tracking — the burden is entirely on the applicant.

Why This Is a Data Problem

In an HRIS, you have several data sources that approximate absence:

• Annual leave / approved absence records
• Travel booking integrations (Egencia, Concur, etc.)
• Expense claims with foreign currency transactions
• Project management systems with location-tagged working patterns

None of these are built for immigration compliance. Leave systems often don't distinguish "worked abroad" from "on holiday abroad" and may miss personal travel entirely. Business travel tools capture flights but not total days outside the UK.

What you actually need is a user-maintained log with employer-sourced corroboration — but if your team is proactive, you can surface signals automatically.

Minimum Viable Tracking Schema

CREATE TABLE employee_uk_absences (
  employee_id     UUID REFERENCES employees(id),
  departure_date  DATE NOT NULL,
  return_date     DATE NULL,   -- NULL if not yet returned
  trip_type       TEXT,        -- BUSINESS | PERSONAL | COMPASSIONATE
  destination     TEXT,
  days_absent     INT GENERATED ALWAYS AS 
                    (CASE WHEN return_date IS NOT NULL 
                     THEN (return_date - departure_date) 
                     ELSE NULL END) STORED,
  notes           TEXT,
  created_at      TIMESTAMPTZ DEFAULT now()
);

With this, a rolling-window query is straightforward:

-- Find any 12-month window with >180 absence days for a given employee
SELECT 
  window_start,
  window_start + INTERVAL '365 days' AS window_end,
  SUM(days_absent) AS total_absent_days
FROM (
  SELECT 
    d.departure_date AS window_start,
    a.days_absent
  FROM employee_uk_absences a
  CROSS JOIN (SELECT DISTINCT departure_date FROM employee_uk_absences) d
  WHERE a.departure_date >= d.departure_date
    AND a.departure_date < d.departure_date + INTERVAL '365 days'
    AND a.employee_id = :employee_id
) windowed
GROUP BY window_start
HAVING SUM(days_absent) > 180
ORDER BY total_absent_days DESC;

This surfaces every window where compliance is breached. Run it as a scheduled job and alert employees when they're approaching 150 days in any rolling window (giving a 30-day buffer).

Integration Points to Consider

1. HRIS sync: If you use Workday, BambooHR, or similar, their API typically exposes absence records with date ranges. Map leave types to an is_uk_absent boolean and sync nightly.

2. Travel booking feeds: Most corporate travel tools support webhook events on booking confirmation. Capture flight departures from UK airports automatically.

3. Employee self-service: For personal travel (which HR cannot see), build a simple self-reporting form with email reminders. Staff underreport precisely when they're nearing visa milestones and most anxious about the outcome — a counterintuitive but real pattern.

4. ILR eligibility alerts: Track each sponsored employee's visa grant date + 5 years. At the 4-year mark, trigger a rolling absence review. Flag anyone above 140 days in any 12-month window for a conversation with your immigration solicitor.

What You Should Not Rely On

• Passport stamps alone (stamps aren't always reliable, especially with eGates)
• Calendar invites (too easy to miss or miscategorise)
• "I was working, so it's probably fine" — there is no business travel exemption in standard ILR calculations

Resources

The Home Office publishes detailed guidance on continuous residence and absence calculations in the Indefinite Leave to Remain policy guidance document. For a plain-English interface to current UK immigration rules — including ILR eligibility checks — ImmigrationGPT is worth bookmarking for your compliance team.

---

This is technical guidance for compliance and HR purposes only. It is not legal advice. Always verify current rules with a regulated UK immigration adviser before making applications on behalf of employees.