Discover the importance of Annaizu Compliance Management in today's business landscape and how a Home Office compliance management platform can help your business streamline its compliance efforts, reduce risks, and stay ahead of regulations.
SOC 3319 is the UK's catch-all occupation code for protective service associate professional roles that do not fit a more specific code in the Standard Occupational Classification 2020 — it covers jobs such as import/export control officers, non-police investigation officers, immigration officers working outside the Home Office, and crime scene examiners. A sponsor hiring into any of these roles must sponsor against this exact code on the Certificate of Sponsorship.
What actually falls under this code
Because 3319 is an 'not elsewhere classified' bucket, the roles inside it are more varied than most occupation codes. In practice, employers most commonly use it for investigation and enforcement-adjacent associate professional roles that sit below the fully qualified professional level — for example a compliance investigation officer at a logistics or trading company, a forensic or crime scene support role outside a police force, or an import control specialist handling customs and licensing checks. Other roles sponsors sometimes place here include senior transport or aviation security officers who supervise checks rather than personally screen passengers, non-warranted trading standards or environmental health enforcement officers, and private investigation associates working under a licensed lead investigator. None of these titles appear by name in the SOC index, which is precisely why the duties test matters more than the job title on the offer letter. Before assigning a Certificate of Sponsorship, check the actual duties against the official occupation description rather than the job title, since a mismatched SOC code is one of the most common reasons Certificates of Sponsorship get queried at audit.
How this code differs from neighbouring protective service codes
SOC 3319 is easy to confuse with adjacent codes that look similar on paper but sit at a different skill level or fall outside the eligible occupations list entirely. Frontline, uniformed protective roles — security guarding, door supervision, static site patrol — normally sit in a lower-skilled protective services category that is not included on the Skilled Worker eligible occupations list, so a sponsor cannot simply reclassify a security guard vacancy as 3319 because the duties sound protective in nature. It's also worth being precise about what 'immigration officers working outside the Home Office' actually means here: warranted immigration enforcement officers employed directly by the Home Office are civil servants, recruited through Civil Service channels rather than private sponsorship. The 3319 category instead covers people performing an analogous compliance or control function for a private employer — for instance a freight forwarder's import compliance officer checking licensing and customs documentation, not a government enforcement role. Getting this distinction right in the job description avoids a caseworker reading the role as something it isn't.
Skill level and salary requirements
SOC 3319 sits at RQF level 3 (broadly A-level equivalent), which does meet the minimum skill threshold for the Skilled Worker route, but associate professional roles like this are frequently paid closer to the salary floor than graduate-level jobs. Sponsors need to check both the general salary floor threshold and the specific going rate for this SOC code, since the higher of the two figures applies. Because 3319 sits toward the lower end of the eligible skill range, it's also worth double-checking that the role as actually performed doesn't drift below RQF level 3 in practice — a job that turns out, on inspection, to be routine data entry or basic monitoring rather than genuine investigative or control work risks failing the skill test regardless of what the certificate says. The authoritative rate and eligibility status for SOC 3319 is published on the Skilled Worker eligible occupations and codes list, and should be checked at the time each Certificate of Sponsorship is assigned, not just when the licence was first granted.
Vetting timelines and the genuine vacancy test
Many roles under this code involve security clearance or sector-specific vetting — anything from basic DBS checks to industry vetting schemes for transport or logistics security roles — that can take considerably longer than a standard right to work check. Sponsors should factor realistic vetting timelines into the assumed start date on the Certificate of Sponsorship rather than assigning it against an optimistic date and hoping clearance lands in time; a gap between the CoS start date and the date the worker can actually begin their real duties is the kind of drift that draws questions at a compliance visit. The genuine vacancy test applies here as it does everywhere else in the Skilled Worker route: a caseworker can and does ask whether the sponsoring organisation genuinely needs someone performing associate-professional-level protective or investigative duties, particularly for a smaller or newly licensed business, so the job description and business rationale need to hold up on their own merits, not just on paper.
Evidence sponsors should keep on file
Roles under this code often involve security clearance, vetting, or handling of sensitive material, so sponsors should retain evidence that the job genuinely required the duties claimed — job descriptions, org charts showing reporting lines, and interview notes explaining why the role was pitched at associate professional level. Where vetting or clearance was part of the recruitment process, keep the clearance certificate or outcome letter and any correspondence with the vetting body alongside the rest of the file, since a caseworker reviewing an unusual or catch-all SOC code will often ask for this evidence first, not last. This sits alongside standard sponsor duties under Part 3: sponsor duties and compliance, and the same secure document storage that holds right to work checks should hold this job-matching evidence too.
Common mistakes to avoid
The most frequent error is reaching for 3319 as a default whenever a role has a vaguely protective or investigative flavour, rather than working through the actual duties against the SOC index first — this includes wrongly placing routine security guarding, door supervision or basic surveillance monitoring under 3319 when those roles typically aren't eligible occupations at all. A second common mistake is copying forward a SOC assignment from a previous hire or a previous year's Certificate of Sponsorship without re-checking it, on the assumption that if it worked before it will work again; occupation eligibility and going rates are reviewed periodically, and a code or figure that was correct twelve months ago may not be current now. A third is under-documenting why a role was pitched at associate professional level rather than a lower, ineligible tier — without contemporaneous evidence, that judgement call is difficult to defend retrospectively.
FAQs
Can I use SOC 3319 if the role doesn't fit any other protective service code?
Yes — that's its purpose — but you should be able to explain in writing why none of the more specific protective service codes fit, since an unusually broad code invites closer scrutiny during a compliance visit.
Does this occupation require a DBS check?
Not automatically — DBS requirements depend on the specific duties and sector, not the SOC code itself, so check separately whether the role involves regulated activity before assuming a check is or isn't needed.
Is a security guard or door supervisor role eligible under SOC 3319?
Generally no. Routine frontline security guarding and door supervision normally sit in a different, lower-skilled protective services category that isn't on the Skilled Worker eligible occupations list, so check the exact duties against GOV.UK's current list rather than assuming a protective-sounding job title clears the bar.
What if security vetting takes longer than expected after the Certificate of Sponsorship is assigned?
Build realistic vetting time into your planning before you assign the certificate, and track the clearance timeline actively rather than assuming it will resolve itself — a system of smart alerts and reminders can flag when a clearance is overdue so you can address the gap before it becomes a compliance issue rather than after.
.svg)