Getting a sponsor licence is the easy part. Keeping it depends on record keeping, reporting and monitoring duties that most security operations are not set up to evidence. Here is what compliance actually requires day to day.
Security companies employing workers from outside the UK and Ireland generally need a sponsor licence from the Home Office. Most of the attention goes into the application. Far less goes into what happens afterwards, which is where licences are actually lost.
A sponsor licence is not a permission you obtain once. It is an ongoing set of duties, and the Home Office can visit to check you are meeting them, sometimes announced, sometimes not. If you cannot evidence compliance at that visit, the licence can be downgraded or revoked. Revocation means your sponsored workers lose their right to work for you, which in a manned guarding operation can mean losing contracts overnight.
This guide covers the operational side: what you need to be able to show, and how to be set up so you can show it.
A note before going further: immigration rules change frequently, and specific thresholds, fees and reporting timescales are updated regularly. Everything here is about process and systems rather than figures. Check the current sponsor guidance on gov.uk for anything numeric before acting on it.
Who Needs a Sponsor Licence
If you employ someone who does not already have the right to work in the UK through settled status, a family visa, or another route that permits unrestricted work, you will generally need to sponsor them.
Whether specific security roles qualify under the available work routes depends on skill and salary requirements that have changed more than once in recent years. This is the part most worth taking current professional advice on rather than relying on what was true last year.
The Three Duties That Actually Get Licences Revoked
Home Office sponsor duties fall into three practical categories, and licences are lost far more often through administrative failure than deliberate wrongdoing.
Record keeping means holding specified documents for each sponsored worker and being able to produce them on request. Reporting means notifying the Home Office of certain changes within short deadlines. Monitoring means having systems that track your sponsored workers' immigration status, attendance and duties on an ongoing basis.
The third one is where security companies are most exposed, and it is worth understanding why.
Record Keeping in Practice
For each sponsored worker you are expected to hold their immigration documentation, evidence of the recruitment decision, contact details including current address, and records of absence.
The failure mode is almost never that the documents do not exist. It is that they are scattered, one document in a personnel file, another in an email, a third on a manager's phone, and cannot be assembled quickly when someone asks. A compliance officer who has to wait two days for you to gather records has already formed a view about whether your monitoring is real.
Everything for a given worker should be retrievable from one place, in seconds, by more than one person in the business.
Reporting Duties Are Time Sensitive
Certain changes must be reported to the Home Office through the Sponsorship Management System, and the deadlines are measured in working days rather than weeks.
Reportable events typically include a sponsored worker failing to turn up for their first day, being absent without permission for an extended period, leaving the employment, having a significant change to their role or pay, or a change in your own organisation such as a new address or a change of ownership.
The practical requirement is that whoever runs your rota needs a route to whoever holds your sponsor licence duties, and it needs to be a reliable one. In a lot of security operations, a sponsored officer failing to attend a shift is handled entirely at branch level as a staffing problem. Nobody tells the person responsible for reporting, and a reporting deadline passes silently.
Monitoring Attendance Is a Rota Problem
The monitoring duty is the one that maps directly onto workforce management, and it is the reason this matters operationally rather than just administratively.
You are expected to know whether your sponsored workers are actually working, in the role they were sponsored for, at the hours they were sponsored for. In an office that is straightforward. Across twelve sites with rotating shift patterns and last-minute cover changes, it is not, unless attendance is captured systematically.
Paper sign-in sheets and WhatsApp confirmations do not constitute a monitoring system. Time-stamped, location-verified attendance records do.
What a Compliance Visit Looks Like
A visit will typically test whether your stated processes are real. Expect requests to see documentation for named workers, questions to managers about how right to work checks are carried out, and comparisons between what your records say a worker was doing and what other evidence suggests.
The distinguishing feature of operations that pass comfortably is not that they have better paperwork. It is that the same system produces the rota, the attendance record and the compliance file, so the three cannot contradict each other. Where those live in separate places, they drift, and drift is what a visit surfaces.
Where Security Companies Get Caught Out
Right to Work checks done once at onboarding and never repeated, when the worker holds a time-limited visa that expires eighteen months later.
Follow-up check dates tracked in a personal calendar belonging to a manager who has since left.
Sponsored workers moved between sites or roles without anyone assessing whether the change is reportable.
Attendance recorded well enough for payroll but not well enough to evidence that a specific person was at a specific place at a specific time.
Building a System That Survives an Audit
The common thread is that compliance fails at the seams between systems. Anything that requires a person to remember to move information from one place to another will eventually fail, usually at the worst moment.
What works is a single record per employee that holds immigration documents alongside licence and qualification data, with expiry dates that generate alerts well before the deadline rather than on the day. Scheduling controls that prevent a worker being assigned a shift when their documentation has lapsed. Attendance capture that produces a defensible record without anyone having to file anything. And an audit trail showing when documents were uploaded, when alerts fired, and what happened next.
ProRota's compliance module was built around this. Right to Work checks, visa expiry and passport validity are tracked in the same place as SIA licences and training records, with configurable alerting. Compliance status is linked to scheduling, so lapsed documentation blocks deployment rather than generating a warning someone can click past. Every compliance action is logged, which is what turns a claim that you monitor your workers into evidence that you do.
If you sponsor workers and are not confident you could evidence all of this at short notice, get in touch and we will show you what an audit-ready record looks like.
