A hiring manager forwards a CV at 4pm on a Thursday. The candidate looks ideal — strong background, willing to relocate, available in six weeks. By Friday morning, the question on the HR director's desk is no longer "can we hire them?" but "can we still sponsor this role at this salary under the current rules?" That question, increasingly, does not have a quick answer.
The Skilled Worker route has been through one of its most substantial recalibrations since its introduction. Salary thresholds have moved upward, occupation codes have been re-mapped, and the relationship between job title, going rate and sponsorship eligibility has tightened. For sponsor-licensed employers, the practical consequence is that workflows built in 2021 or 2022 no longer reliably produce compliant outcomes.
What actually changed, in plain terms
Three shifts matter most for day-to-day hiring decisions.
First, the general salary floor for the Skilled Worker visa has risen sharply compared with the figures most HR teams memorised during the post-Brexit transition. The headline minimum is now meaningfully higher, and the "going rate" for each occupation — the role-specific benchmark that sits alongside the general floor — has been recalculated against more recent ONS earnings data. Sponsors must satisfy both the general threshold and the going rate, whichever is higher.
Second, the Standard Occupational Classification system has moved from SOC 2010 to SOC 2020. This is not a cosmetic relabelling. Some roles that previously sat comfortably inside a sponsorable code now map to a different code with a different going rate, or in some cases to a code that no longer appears on the eligible occupation list. Roles around the borderline — junior analyst positions, certain operations and administrative hybrids, some care-adjacent roles — are where the reclassification bites hardest.
Third, the discount structures have been tightened. The "new entrant" rate, PhD-relevant discounts and shortage-related reductions still exist in various forms, but the arithmetic has changed and the eligibility gates are stricter. The Immigration Salary List has replaced the older Shortage Occupation List with a narrower scope and, importantly, without the same level of salary discount the SOL once offered.
The cumulative effect: a role you sponsored at £30,000 eighteen months ago may now require materially more, may need a different SOC code, or may no longer be sponsorable in its current shape at all.
Where sponsors are getting caught
In our work with UK employers across technology, professional services, hospitality groups and care providers, the same operational failure points keep surfacing:
- Stale SOC mappings in the ATS. Job templates still reference SOC 2010 codes. When the Certificate of Sponsorship is assigned, the code looks fine on paper but no longer matches the worker's actual duties under the new classification.
- Salary set at the old going rate. Offers are extended at the previous benchmark, then withdrawn or renegotiated when compliance reviews the CoS — a poor candidate experience and a risk to the sponsor's reputation.
- Inflated job titles to fit a higher code. A common shortcut, and a significant compliance risk. The Home Office assesses the genuineness of the role and the substantive match between duties and the chosen SOC code, not the wording on the letterhead.
- Assuming the old "new entrant" route still applies. Eligibility windows and conditions have changed; not every graduate hire qualifies for the reduced rate now.
- Forgetting that the going rate is pro-rated for part-time work in only specific circumstances. Hybrid four-day arrangements have caused more than one CoS to be issued at an unintentionally non-compliant salary.
- CoS allocation timing. With Defined CoS still routinely processed within the Home Office's standard window, the bottleneck for many sponsors has shifted to Undefined CoS capacity — particularly for in-country switches and extensions during busy quarters.
A practical reset for HR and compliance
If you sponsor more than a handful of Skilled Workers a year, the following sequence is worth running this quarter rather than next.
- Re-baseline every active sponsored role. Pull the current SOC 2020 code, the current going rate and the current general threshold. Document which figure governs each role and why.
- Audit your job description library. For each sponsored job family, confirm the duties listed substantively match the SOC 2020 code you intend to assign. If a role has drifted, rewrite the JD or re-map the code — do not split the difference.
- Rebuild offer letter templates. Salary clauses, hours clauses and any allowance breakdowns should reflect what counts toward the threshold under current rules. Allowances that used to count may no longer do so.
- Brief hiring managers, not just recruiters. The people writing the JD and interviewing the candidate need to understand that "we'll just bump the title" is not a workable response to a threshold problem.
- Map your CoS pipeline against the calendar. If you anticipate a hiring surge — graduate intakes, seasonal expansion, a funding round — model your Defined and Undefined CoS needs now. Undefined CoS slots in particular can become a constraint at speed, and recovering from a missed allocation window is painful.
- Refresh your sponsor licence compliance file. Right-to-work checks, salary records, role descriptions and reporting obligations all need to align with the post-reset rules. An audit visit assesses your current practice, not your historic intent.
The strategic question underneath the rules
Beyond the mechanics, the recent changes pose a more uncomfortable question for HR strategy: which roles in your organisation are still economically sensible to sponsor? For some employers, the answer will involve genuine restructuring — consolidating responsibilities to push roles cleanly above the threshold, investing more in domestic pipeline development for borderline positions, or relocating certain functions outside the UK altogether.
This is not a counsel of despair. The Skilled Worker route remains workable for most professional and technical hires, and the UK immigration rules continue to support genuine skills shortages. But the era of treating sponsorship as a light-touch HR add-on is over. Sponsors who treat the licence as an operational discipline — with the same rigour as payroll or data protection — will continue to hire well. Those who treat it as paperwork will encounter increasingly expensive surprises.
For sponsors managing tight CoS allocation windows, Serene Jade's CoS Priority Service captures Undefined Certificate of Sponsorship slots at millisecond precision — useful when the calendar, not the candidate, becomes the constraint.
FAQ
Q: We assigned a CoS under SOC 2010 before the transition. Do we need to reissue it under SOC 2020? A: Existing valid CoS assignments generally remain valid on the terms under which they were issued, but any new CoS — including extensions and changes of employment — must use the current SOC 2020 framework. Treat the next sponsored action for that worker as the trigger to re-map.
Q: Can we use allowances or guaranteed bonuses to bridge the gap to the new salary threshold? A: Only specific types of guaranteed, contractual payments count toward the salary calculation, and discretionary bonuses generally do not. Review each component of the package against the current rules before relying on it to clear the threshold.
Q: One of our existing sponsored employees is now paid below the new going rate for their role. Are they suddenly non-compliant? A: Not automatically — workers already on the route are typically assessed against the rules in force when their permission was granted, until their next application. The risk window opens at extension or change-of-employment, which is when the salary needs to meet current requirements.