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 3132 covers IT user support technicians — first- and second-line troubleshooting, hardware and software fixes, system installs and access provisioning for end users — a technician-level (RQF3) role with its own, lower salary going rate than the professional IT codes.
Helpdesk work is often skilled enough, but not always
Not every support desk role meets the bar for sponsorship. What typically qualifies is diagnosing and resolving technical faults, configuring systems and access, and escalating complex issues with informed judgement — as opposed to purely scripted, first-response call logging with no technical troubleshooting involved. If the role is genuinely closer to a call-handling function than technical support, it's worth checking eligibility carefully before committing a CoS to it. In practice this often comes down to who owns the fix: a technician who resets a password, rebuilds a laptop image, or reconfigures a mailbox permission is exercising judgement that sits above scripted call logging, whereas a role that only records a fault and passes it upward is not.
SOC 3132 sits between several similar-sounding IT codes
User support technicians are frequently confused with adjacent IT occupations that carry different skill levels and different going rates. SOC 3131 (IT operations technicians) covers infrastructure monitoring and operational tasks rather than direct end-user support; SOC 2137 (IT and telecommunications professionals not elsewhere classified) and other 21xx codes sit at graduate professional level and typically involve designing, building, or architecting systems rather than fixing them for end users. Choosing the SOC code is not a matter of picking whichever one is administratively convenient — it has to reflect what the person actually does day to day, because the Home Office checks the CoS job description, the advertised job title, and the actual duties against each other. A mismatch between a grand-sounding job title and genuinely technician-level duties is one of the more common triggers for follow-up questions during a visit, so it is worth writing the CoS duties in plain, specific language rather than reusing generic marketing copy from a job advert.
Salary floor is the tightest part of this one
Because SOC 3132 sits at the lower end of the IT going-rate scale, sponsored user support hires often sit closer to the salary threshold than staff in other IT roles — which means a routine pay freeze elsewhere, or a threshold uprating, can put an existing sponsored technician below the required rate without anyone noticing until a check is run. Compare current pay against the salary floor guidance and the SOC-specific going rates at least annually, not just at the point of hire.
Support technicians are also a common route into sponsorship for younger or newly qualified staff, which is exactly where the new entrant salary discount tends to get used and then mismanaged. If someone was sponsored under the new entrant rate — for example because they were under 26, recently graduated, or in the early stages of a recognised professional training path — that discount only applies for a limited period, and it does not renew indefinitely just because the person is still junior. Track the date the discount expires against each affected worker and confirm the salary steps up to the standard going rate in good time, rather than discovering the gap when a threshold uprating or an audit forces the comparison.
Right to work checks matter just as much here
Support technicians are frequently onboarded in batches alongside other new starters, which is exactly where right to work checks get rushed. Follow the standard process for verifying share codes for every new hire regardless of role, and keep the check evidence with the rest of the sponsorship file.
Watch out for third-party site placements
IT user support is one of the roles most likely to involve working somewhere other than the sponsor's own premises, because a lot of first- and second-line support is delivered by managed service providers and IT outsourcers who place staff on-site at client offices, or support client systems remotely under a service contract. Sponsoring a worker to sit primarily at a third party's site, doing work directed day to day by that third party rather than the sponsor, raises a genuine compliance question — sponsors are expected to be the entity that actually employs, supervises, and directs the sponsored worker, not a staffing conduit for someone else's IT function. This is exactly the kind of arrangement that draws attention during a Home Office enforcement visit, so if your support technicians work on client sites or under a managed services contract, be able to show clearly who supervises them, who sets their duties, and how that fits your sponsor licence obligations before you assign a CoS to the role.
Evidence to keep on file for each support technician
Because this role sits close to the salary and skill thresholds, the paper trail matters more than usual. Alongside the standard right to work check, keep a specific, duties-based job description that matches what the CoS actually says; any qualification certificates, training records, or prior employer references that support the RQF3 skill level if it's ever questioned; and a clear record of who the person reports to and where they are actually based day to day. Payslip and bank statement evidence showing the salary paid matches the CoS figure — not just at the start date but as pay changes over time — is worth keeping in the same place. Storing all of this centrally, rather than scattered across HR, payroll, and line managers' inboxes, is what secure document management is for, and it is far easier to pull together before an audit than during one.
Reporting duties don't stop once the CoS is issued
Any material change to a sponsored support technician's circumstances needs reporting through the sponsor management system within the usual reporting window, not just noted internally. That includes a change of duties or job title, a change of work location (including a move onto or off a client site), a reduction in salary, or — as below — a promotion into a different role entirely. Missing these reporting deadlines is treated as a compliance failure in its own right, separate from whatever the underlying change was, so it's worth building a routine reminder into your onboarding and line-management process rather than relying on someone remembering. A reminder system that flags reportable changes as they come up removes the risk of a change simply being missed.
Preparing for a compliance check
Technician-level roles are a common focus in Home Office visits precisely because the skill threshold is lower and easier to misjudge. Running a mock audit on your support team's files, and tracking everything through sponsorship compliance software, catches gaps before an inspector does. Sponsor obligations around reporting and evidencing the role are set out in the official sponsor duties guidance.
FAQs
Is a 'service desk analyst' the same as SOC 3132?
Often, yes, but check the actual duties — a role that's purely ticket triage with no technical resolution work may not meet the threshold, regardless of the job title used.
What if a support technician is later promoted into a network or systems role?
Report the change and reassess the SOC code and salary requirement — a promotion into a professional-level IT role (such as SOC 2137) carries a different, higher going rate.
Does an IT apprenticeship count toward the skill level for SOC 3132?
A recognised IT support apprenticeship, together with the practical duties being performed, can support the case that a role sits at the required RQF3 level — but the apprenticeship itself doesn't substitute for the duties test. Keep the training record on file alongside evidence of the actual day-to-day work.
Can a sponsored user support technician be based at a client's premises?
It's possible, but it needs careful handling. Be clear about who directs the worker's day-to-day tasks, keep evidence that the sponsor remains the genuine employer, and review this arrangement against your reporting duties whenever the work location or line management changes.
.svg)