Every security company knows that SIA licences matter. But knowing they matter is very different from having a system that ensures every operative is licensed, every licence is current, and every renewal is managed before the deadline, not after.
As a security company grows, SIA licence management moves from a manageable mental list to an operational challenge that requires proper infrastructure. This guide covers what you need to know, where things typically go wrong, and how to build a system that keeps you compliant at any scale.
The Legal Baseline
Under the Private Security Industry Act 2001, it is a criminal offence to deploy an individual in a licensable role without a valid SIA licence. The offence lies with the business, not just the individual. Directors, managers, and the company itself can face prosecution.
The licensable roles covered by the Act include security guarding, door supervision, close protection, cash and valuables in transit, public space surveillance (CCTV), key holding, and vehicle immobilisation. Not every person who works at a security company needs a licence. Office staff, administrators, control room operators, and management personnel who do not themselves perform licensable activities are not required to hold SIA licences.
Understanding which roles are in scope is the first step to managing compliance accurately. If you are tracking licence status for people who do not need one while missing someone who does, your system is misfiring.
Why Licence Management Fails
The Spreadsheet Problem
The most common approach to SIA licence tracking among small and medium-sized security companies is a spreadsheet. It lists names, licence numbers, and expiry dates. It works, until it does not.
Spreadsheets require manual updates. An operative renews their licence and the expiry date gets updated, eventually. Someone leaves the company but their record stays in the file. An operative is added in a hurry and the licence check column gets filled in “to do” and never revisited. Nobody owns the process of checking the sheet against the SIA’s public register on a regular basis.
The result is a compliance record that looks complete but has drifted from reality. By the time the drift is discovered, it may be because an assessor has found it, or because a guard with an expired licence has already been deployed to site.
The Renewal Timing Problem
SIA licences are valid for three years. With a large workforce, multiple renewals are happening simultaneously. The renewal process itself takes time, and guides recommend starting the application at least six weeks before expiry.
Without automated alerts, it is easy for a renewal to be left too late. The operative may not flag it proactively. The manager responsible may be focused on operational demands. By the time anyone notices, the licence has expired and the operative cannot legally work until the renewal is processed.
The Scale Problem
A company with ten guards can manage licences reasonably well with a basic system. A company with fifty guards has five times the renewal volume and is much harder to manage manually. At one hundred guards, manual management is genuinely risky. The number of licences in play at any given time, each with a different expiry date, is more than human memory and intermittently updated spreadsheets can reliably handle.
Building a Reliable SIA Licence Management System
Centralise the Record
Every operative in a licensable role should have a single, canonical licence record in one system. Not spread across spreadsheets, paper files, emails, and the manager’s memory. One record, accessible to anyone who needs it, updated when something changes.
Automate Expiry Alerts
Your system should alert the relevant manager when a licence is approaching expiry. Best practice is three alert points: 60 days before expiry, 30 days before expiry, and 7 days before expiry. At 60 days, there is comfortable time to initiate the renewal. At 7 days, the situation is urgent and should be escalating.
Link Licensing to Deployability
The most important control is the connection between licence status and scheduling. An operative with an expired licence should not be schedulable to a licensable role. If your scheduling system does not know that a licence has lapsed, there is no automatic protection against an illegal deployment.
This is the principle behind a deployability gate: a system check that confirms an operative meets all compliance requirements before they appear as available for assignment. Read more about how TacDesk’s deployability gate works.
Verify Against the SIA Register
The SIA maintains a public register where any licence number can be checked against the current holder and status. Regular spot-checks against this register, particularly for operatives who handle their own renewals, provide an additional layer of assurance beyond your internal records.
Separate Roles Clearly
Maintain a clear distinction in your records between operatives in licensable roles and non-security staff who do not require a licence. Tracking everyone wastes time and creates noise. Failing to track operatives in licensable roles is a compliance failure. The distinction matters.
SIA Licence Management and ACS
Under ACS Criterion 1, assessors will review your licence records and look for evidence that your system monitors expiry dates proactively and has controls to prevent deployment of unlicensed operatives. They will check whether your records are current and whether the system you use is genuinely operationally integrated rather than a standalone spreadsheet.
A licence management system that is embedded into your daily operations, with automated alerts and scheduling controls, is far more compelling to an assessor than a spreadsheet that someone updates occasionally.
TacDesk monitors SIA licence expiry in real time, sends automated alerts at 60, 30, and 7 days, and blocks non-compliant operatives from being scheduled to site through the deployability gate. See how it works, or book a demo at tacdesk.co.uk.
Starting from £49/month, with no contracts and no setup fees.