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 3119 covers technicians who set up equipment, run tests, and support scientists or engineers in labs, workshops and production environments, where the specific specialism doesn't map to a more precise technician code. It sits at RQF3, so sponsorship is generally viable provided salary and going-rate thresholds are met.
What sits under this code
Typical roles include laboratory technicians preparing samples and running standard tests, engineering technicians assisting with builds, calibration or fault-finding, and production technicians overseeing a manufacturing line under a senior engineer's direction. Quality control technicians carrying out routine testing against a specification, and research support technicians maintaining equipment and reagents for a wider scientific team, also commonly sit here. The common thread is hands-on technical work carried out under supervision rather than independent design or research responsibility, which would usually sit at a different, higher-skilled code.
Where the boundary sits with more senior — or more junior — roles
3119 sits in the middle of a spectrum, and getting the boundary wrong can go either way. On one side, a technician who independently designs experiments, signs off on validation results, or takes ownership of R&D decisions is arguably doing an engineer's or scientist's job and may need a different, higher SOC code with its own going rate. On the other side, a role that's largely cleaning equipment, basic stock-keeping or unskilled assistance to technicians doesn't meet the RQF3 skill level 3119 requires and shouldn't be sponsored under it at all. The safest approach is the same one that applies to any borderline SOC decision: describe what the person actually does day to day, compare it against the index entries either side of 3119, and keep that comparison on file rather than defaulting to the closest-sounding job title.
Evidencing the qualification and skill level
Because this is a technical, RQF3-level role, keep evidence of the relevant qualification or equivalent experience — an HNC/HND, a completed apprenticeship, or a documented track record where formal qualifications weren't obtained. This is separate from, but sits alongside, the right to work check every sponsor must complete before employment starts.
Health, safety and site-specific certifications
Beyond the technical qualification itself, lab and production environments often require role-specific certifications that are worth keeping alongside the immigration file even though they're not immigration documents in themselves — COSHH training for handling hazardous substances, manual handling or IOSH certificates for production floor work, radiation or biological safety training where relevant, and equipment-specific competency sign-offs. These records serve two purposes: they support the case that the role is genuinely skilled and carried out to a professional, supervised standard, and they're often the first thing a health and safety inspection or an internal audit asks for, so it's efficient to hold them alongside your sponsorship evidence rather than in a separate HR system nobody checks together. A mock audit that pulls together both sets of records at once is a good way to find gaps before a real visit does.
Salary and going rate
Confirm the role clears both the general Skilled Worker salary floor and the specific going rate for SOC 3119. Our salary floor guide explains how these two thresholds combine, which matters here because technician roles can sit close to the boundary depending on sector and region.
Shift pay, overtime and the salary calculation
Production and lab technicians are more likely than office-based roles to work shift patterns that include night, weekend or overtime pay. As with variable pay in other occupations, it's generally the guaranteed basic salary for guaranteed contracted hours that counts toward the salary floor and going rate, not overtime premiums, shift allowances, or on-call payments that depend on the hours actually worked. If a technician's base salary only clears the threshold once shift or overtime pay is added in, the role may not in fact meet the requirement — this is worth checking carefully before an offer is made, particularly where a production role has irregular contracted hours.
Site and safety-specific record keeping
Where the technician works across multiple lab or production sites, keep a clear record of each work location, since a change of site can be a reportable event under sponsor duties. The Home Office's Appendix D record-keeping guidance sets out exactly what must be retained, and a centralised document system makes multi-site evidence far easier to produce on request.
FAQs
Does the technician need a formal qualification to be sponsored?
Not necessarily — equivalent experience can satisfy the RQF3 skill requirement, but you should keep clear evidence of that experience on file in case it's queried.
What if the technician rotates between our lab and a client's site?
Document the arrangement and report any change of normal work location per your sponsor duties, since undisclosed site changes are a recurring issue in compliance checks.
Does overtime or a shift allowance count toward the salary threshold?
Generally no — guaranteed basic pay for guaranteed contracted hours is what's assessed, so build your salary check around the base salary rather than total expected earnings including overtime or shift premiums.
What if a technician's role genuinely evolves into more senior engineering work over time?
Treat that the same way as any other material change to a sponsored role — reassess the SOC code and going rate against the new duties, and update the certificate of sponsorship or take advice if the change is significant enough to amount to a different job.
.svg)