The UK Register of Licensed Sponsors is public, free, and updated daily. If you're building anything in the HR or compliance space that touches right-to-work or visa sponsorship — or if your team makes decisions based on it manually — you should understand what the data actually looks like and where it fails.
Most implementations I've seen treat the register as a ground truth. It isn't, and the edge cases where it isn't are exactly the ones that create compliance risk.
What the data structure looks like
The register ships as two CSV files — not one:
Worker route CSV — covers Skilled Worker, Senior or Specialist Worker, Scale-up Worker, International Sportsperson, Minister of Religion, International Agreement (worker)
Temporary Worker route CSV — covers Creative Worker, Charity Worker, Religious Worker, Seasonal Worker, Government Authorised Exchange, International Agreement (temporary)
Each row contains five fields: Organisation Name, Town/City, County, Type & Rating, Route.
That's it. No Companies House number. No VAT registration. No date of licence issue. No record of how many Certificates of Sponsorship the employer has issued or how many remain in their annual allocation. No contact details.
The absence of any unique persistent identifier — something that maps to a canonical company record — is the most significant structural problem for any system that tries to do automated matching rather than manual lookup.
What "Type & Rating" actually means
An employer can hold multiple routes simultaneously, and they'll appear as multiple rows with the same organisation name. An entry for "Acme Technologies UK Limited" might appear twice: once with Skilled Worker / A and once with Temporary Worker / A.
Rating A is the standard status. Rating B means the employer has active compliance concerns and is on an improvement plan — but they can still issue CoS certificates. A B-rating doesn't block sponsorship. Only suspension or revocation does.
The revoked-sponsors file is a separate download from the Home Office, not included in the main register CSVs. A system that only processes the active register returns a clean result for an employer whose licence was revoked yesterday, if the revoked list hasn't been synced. That's not a theoretical edge case — the daily update cycle creates a real window.
Update timing and what "daily" means in practice
The Home Office updates on working days, typically before 10am UK time. The exact update time isn't published. A revocation processed on a Friday afternoon won't appear in the register until Monday morning — roughly 65 hours.
During that window, querying the active register gives a positive result for a suspended employer. If your system makes automated onboarding decisions based on register status, you need to account for this lag explicitly: a clean result isn't evidence of current status, it's evidence of status as of the last update.
For compliance audit purposes, recording the timestamp of every register check — and flagging results more than 24 hours old as potentially stale — is the bare minimum.
The name-matching problem
The register uses the name as recorded with the Home Office, which may differ from the Companies House name, the trading name, and the name the employer uses in job adverts. All three can diverge.
"Acme UK Technology Limited" and "Acme Technologies UK Ltd" could be the same legal entity with a different registered name, or two different entities. The register gives you no way to distinguish without external data.
Building reliable automated matching against the register requires:
- Normalising capitalisation, punctuation, and whitespace
- Stripping legal suffixes (Ltd, Limited, PLC, LLP, LTD, plc) before matching, then re-checking with them included
- Fuzzy matching with a confidence threshold — typically 0.85+ on a string similarity metric
- Cross-referencing
Town/Citywhen multiple entries match the normalised name - Flagging anything below the confidence threshold for manual review rather than assuming clean
The proper fix is a Companies House API integration that resolves a legal entity number, which you can then use to look up the registered name precisely and match against the register without fuzzy logic. Most teams don't build this, and the fuzzy match fails loudly on hyphenated names, Welsh entities, and group subsidiaries.
What's missing from the data that matters operationally
Two things practitioners ask about most often that aren't in the register:
CoS allocation remaining. The Home Office assigns each sponsor an annual quota of unrestricted CoS. The register doesn't show allocation used or remaining. An A-rated employer with zero CoS left looks identical to one with 200 remaining. The only way to know is to ask the employer directly, or check with a solicitor who has access to their SMS (Sponsor Management System) records.
Licence age. No issue date is published. A two-week-old licence holder appears the same as a six-year licence holder. Licence age is a reasonable proxy for compliance maturity — the Home Office's compliance visit programme targets newer sponsors disproportionately.
Practical implementation notes
If you're consuming the register programmatically — for example, to verify employers in a job board, HR platform, or compliance dashboard — two things most implementations skip:
Dual-list checking. Every query should check both the active register and the revoked list. Positive on active + positive on revoked simultaneously can happen during a revocation in progress (the active list update lags the revoked list). This is the edge case that creates actual liability.
Time-bounded result caching. Cache register lookups, but expire them within 24 hours. A stale Active result from three days ago is not a compliance-grade check.
A search interface over both the active register and the revoked-sponsors list is available at immigrationgpt.co.uk for manual lookups. For automated or bulk use, processing the raw CSVs with the considerations above is the right approach.
UK immigration rules and UKVI policies change regularly. Verify current requirements directly with the Home Office or a qualified immigration adviser before making compliance decisions.
Top comments (0)