UK Visa Appeals 2026: Logic Trees, Data Constraints, and What HR Compliance Systems Miss

#immigration #uk #career #hr

Most immigration compliance tools handle visa status tracking, expiry alerts, and right-to-work verification reasonably well. Where they fall short is in modelling what happens after a refusal: specifically, whether the affected employee goes into an appeal track, an Administrative Review track, or simply reapplies. These are three different procedural pathways with different timelines, different data requirements, and different implications for current leave status. Getting this wrong creates real compliance liability.

The post-refusal decision tree

After a UK visa refusal, available remedies depend on the visa type — but the split is more nuanced than just category. The critical variable is whether a human rights claim was raised at the initial application stage:

REFUSAL
├── Points-Based System route (Skilled Worker, Student, Graduate, etc.)
│   ├── No human rights claim raised → Administrative Review only
│   │   ├── Cost: £80
│   │   ├── Deadline: 14 days (in-country), 28 days (out-of-country)
│   │   └── Scope: caseworker errors only — not a merits review
│   └── Human rights claim also raised → First-tier Tribunal appeal
│       ├── Cost: £140 (paper) / £167 (oral hearing)
│       ├── Deadline: 14 days (in-country, not detained)
│       └── Scope: full merits review including human rights grounds
├── Visitor visa
│   └── No appeal right — reapplication only
└── Asylum / protection claim
    └── First-tier Tribunal (Asylum and Immigration Chamber)

The practical implication: your system needs to store whether human rights grounds were raised at application time, not just the visa category. A Skilled Worker applicant who also raised Article 8 grounds gets a different remediation pathway than one who didn't.

Section 3C leave — the most mismodelled status in compliance systems

When an in-country applicant lodges an Administrative Review or appeal within the statutory deadline, their existing leave is automatically extended under section 3C of the Immigration Act 1971. Key properties:

Work rights: generally preserved during 3C leave (subject to original leave conditions)
Travel: prohibited — departing the UK while 3C leave is active terminates the leave and the review/appeal
Duration: extends until the review or appeal is finally determined or withdrawn, however long that takes

For HR systems, this means an employee whose BRP shows an expired date may still hold valid leave. Any system that triggers a right-to-work failure purely on BRP expiry — without checking 3C leave status — will generate false positives.

The correct workflow: use the Employer Checking Service (ECS) for any employee in this situation. A Positive Verification Notice (PVN) from ECS is valid for 6 months and provides a statutory excuse under the Immigration, Asylum and Nationality Act 2006.

Timeline expectations for SLA modelling

Current First-tier Tribunal (Immigration and Asylum Chamber) wait times run to 12–18 months for contested oral hearings. Administrative Review targets 28 days but typically runs 28–56 days for anything non-trivial.

Remedy	Target SLA	Realistic range (2026)
Administrative Review	28 days	4–8 weeks
First-tier Tribunal	No official target	12–18 months
Upper Tribunal	Varies	+12–24 months if further appeal

Any workforce planning workflow for employees with pending remedies should model the realistic range, not the official target. A 28-day SLA for Administrative Review makes headcount planning tractable; a 15-month tribunal timeline does not.

Data schema for refusal tracking

Minimum fields a compliance system should capture per refusal event:

{
  "refusal_date": "2026-07-30",
  "visa_category": "Skilled Worker",
  "human_rights_raised": false,
  "remedy_type": "Administrative Review",
  "remedy_deadline": "2026-08-13",
  "lodgement_date": null,
  "section_3c_active": false,
  "ecs_check_completed": false,
  "pvn_issued": false,
  "pvn_expiry": null,
  "expected_decision_window": "2026-09-10",
  "outcome": null,
  "outcome_date": null
}

section_3c_active should flip to true at the point lodgement is confirmed and drive the right-to-work logic away from BRP date and toward ECS-based verification.

What doesn't have an API

There's no public API for First-tier Tribunal case status. Tracking appeal progress in an HR system requires:

Manual updates from employees or their solicitors
HMCTS MyHMCTS portal (case-specific, not generally accessible to employers)
Periodic ECS re-checks (every 6 months while 3C leave is active)

For building candidate-facing tools or internal HR dashboards, ImmigrationGPT offers structured Q&A over current appeal rights, timelines, and procedural rules — useful for edge cases where the standard decision tree doesn't obviously apply and legal nuance matters.

Implementation note on appeal eligibility checks

Do not derive appeal eligibility solely from a visa category lookup table. The correct check is:

Was a human rights claim raised at application? (field required at intake)
What is the visa category?
Is the applicant in-country or out-of-country?
Are they detained? (affects the deadline window)

These four inputs determine which remedy pathway is available. Building the tree on visa category alone will misclassify a non-trivial number of cases.

This article is for informational purposes only and does not constitute legal advice. Immigration rules and tribunal procedures change — verify against official GOV.UK guidance and consult qualified legal professionals before implementing compliance workflows.

DEV Community