UK SOC Codes for Sponsors 2026: Finding the Right Code and Going Rate

A UKVI caseworker does not care what you called the role on the job advert. They care what the person does all day, and whether that matches the four digit code you put on the Certificate of Sponsorship. Get the match wrong and you are looking at a refusal, a wasted CoS fee, and possibly a compliance visit that puts your sponsor licence rating at risk.

Most SOC code guides hand you a list of 400 plus codes and tell you to search your job title. That is not the hard part. The hard part is choosing between two or three plausible codes when a role does not sit neatly in one box, and building a defensible reason for the one you pick. This is a framework for making that call.

What the SOC Code Actually Locks In

Once you assign a code to a Certificate of Sponsorship, it decides four things at once, not one.

• Eligibility. The role must sit in a table in Appendix Skilled Occupations at RQF Level 6 or above for new entry clearance, unless it qualifies under the Temporary Shortage List or Immigration Salary List.
• Salary floor. Each code carries its own going rate. Your sponsored worker must clear the higher of that going rate and the general threshold.
• Discount eligibility. Some codes unlock a reduced salary option for new entrants or shortage roles. Others do not.
• Audit exposure. UKVI compares the code against the actual job description during compliance visits. A mismatch here is one of the most common triggers for licence action.

In practice, the code is not paperwork. It is the load bearing wall of the whole application.

The Five Step Framework for Choosing the Right Code

Skip the job title. Start with what the person will actually spend their week doing.

• Write the role from duties, not title.
  
  • List the five or six tasks that take up most of the working week. "Manager" alone maps to dozens of codes; a restaurant manager and a construction site manager are not interchangeable.
• Search duties, not job title, in the coding tools.
  
  • Run the description through the ONS SOC 2020 index or the CASCOT coding tool. Both return two or three candidate codes for most roles, not one.
• Cross check every candidate against Appendix Skilled Occupations.
  
  • A code that CASCOT returns is not automatically eligible for sponsorship. Confirm it sits in an eligible table and check the current going rate for that code.
• Pick the code that reflects the majority of the role, not the most senior sounding one.
  
  • Rounding up to a higher skilled code to hit a salary you have already offered is the fastest way to invite a compliance review.
• Keep the evidence.
  
  • Save the job description, the candidate codes you considered, and the reason you rejected the others. If UKVI asks later, this file is your answer.

Which salary figure actually applies to your employee's role

For the full breakdown of how these thresholds interact, see our 2026 salary threshold guide. This piece focuses on getting the code right first, since the wrong code makes the salary calculation meaningless anyway.

When a Role Sits Between Two Codes

This is where most SOC code guides stop being useful, because most roles are not textbook cases. A senior developer who also manages two juniors. A marketing lead who spends a third of their time on data analysis. Here is how to break the tie.

• Count time, not titles. Whichever set of duties takes up more than half the working week wins.
• Check seniority language in the job description against the unit group description for each candidate code, not against the job advert you already published.
• If duties are genuinely split close to even, choose the lower risk option: the code with the more conservative going rate and a stronger eligibility position under Appendix Skilled Occupations.
• Document why you rejected the other code, in one or two sentences, at the time you make the decision. Reconstructing this six months later during an audit is much harder.

Three Mistakes That Trigger Refusals or Audits

These account for the bulk of SOC related refusals we see across sponsor accounts.

• Matching the job title instead of the duties. A title that sounds senior does not make the code correct. Caseworkers read the job description, not the letterhead.
• Using a SOC 2010 code. Every application must use SOC 2020. Old codes carried over from a previous CoS template are an automatic problem.
• Rounding up to justify a salary you have already agreed. If the going rate for the accurate code is lower than what you are paying, that is fine. Choosing a higher code purely to match the salary is the pattern UKVI compliance visits are designed to catch.

Honestly, rounding up does the most damage, because it rarely happens once. It tends to become the default for every similar role after that, and that pattern is exactly what a licence audit catches.

Make the Decision Repeatable Across Your HR Team

A framework only holds up if every hiring manager applies it the same way. If your team is switching an employee onto the Skilled Worker route or sponsoring for the first time, inconsistent SOC code decisions across departments are what turn one refusal into a pattern an auditor flags.

Disclaimer: Immigration rules change quite frequently; please verify with official sources or contact us for the latest info before making any decisions.