What actually happens when an SIA licence expires mid-contract
Under the Private Security Industry Act 2001, licensable activity carried out without a valid licence is a criminal offence — and the exposure is not only the individual's. A contractor who rosters an unlicensed officer onto a licensable post has a problem with their client, their insurer and potentially the regulator, all at once.
The uncomfortable part is that this almost never happens because someone decided to cut a corner. It happens because a date moved past without anyone noticing.
Why expiry dates get missed
Licences do not all expire together. Officers join from other contractors mid-cycle, licences are renewed at different times, and a three-year term is long enough that whoever recorded the date has often moved on before it matters.
- The date lives in a spreadsheet that is only opened when someone remembers to open it
- The officer knows their own renewal date but assumes the office is tracking it
- A renewal application is in progress, and nobody is clear whether the officer can work while it is
- Someone is rostered as cover at short notice, and their licence status is never checked at all
That last one is the common case. Cover decisions get made in minutes, by whoever is available, and a spreadsheet in someone else's inbox does not participate in that decision.
What the SIA expects you to know
The SIA maintains a public register, and the expectation is that you check it. Licence status can change between the date you recorded and the date the officer works — a licence can be suspended or revoked, not only expire. Checking once at onboarding and treating that as permanent is the mistake.
Sector matters too. A licence is granted for specific licensable activities, and an officer licensed for one sector is not automatically licensed for another. Rostering someone onto a post outside their sector is the same problem wearing a different hat.
Making the date do the work
The practical fix is not better discipline. It is making the expiry date visible at the moment a rostering decision is made, rather than in a document someone has to go and consult.
- Hold the licence number, sector and expiry against the officer record, not in a separate file
- Surface an alert weeks ahead, so a renewal has time to complete
- Make licence status visible on the roster itself, where cover decisions actually happen
- Keep a record of when status was last verified, so you can evidence the check
None of this is sophisticated. It is simply putting the fact next to the decision. See also tracking licence expiry without a spreadsheet.
The cost lands on the contract, not the officer
When a licence lapses, the immediate consequence falls on the individual — but the commercial consequence falls on the contractor. A site that has to be covered at short notice, a client who notices the change, and a conversation about how it was allowed to happen. That conversation is rarely about the one officer; it is about whether the contractor knows the status of everyone else on the account.
Which is why a single lapse tends to trigger a client asking for the full licence position across the contract. A contractor who can produce that same day is in a very different position from one who needs a week to compile it.
Common mistakes
- Treating a lapse as an individual's problem rather than a contract risk
- No ability to produce the licence position across an account quickly
- Discovering the lapse from the officer rather than from your own records
- No plan for covering a post at short notice when someone is stood down
- Telling the client after they have noticed rather than before
- Fixing the individual case without checking who else is close to expiry
One practical test: produce the account's position today
Pick your largest contract and try to produce, this morning, the licence status and expiry date of every officer working it. Time it.
Under ten minutes means the information exists somewhere real and a client asking after a lapse gets a confident answer the same day. An afternoon means that after any lapse you will be compiling the position under pressure, while the client is already wondering how it happened — which is the conversation that costs contracts rather than the lapse itself.
- Hold the position per contract, not only per officer
- Be able to produce it same-day rather than assembling it
- Tell the client before they notice rather than after
- Audit the rest of the account after any single lapse
- Plan cover for a stood-down post in advance
- Unlicensed licensable activity is a criminal offence under the Private Security Industry Act 2001
- Licences can be suspended or revoked, not only expire — a one-off check at onboarding is not enough
- Sector matters: a licence covers specific licensable activities, not all of them
- Short-notice cover is where the check is most often skipped
- Check the SIA register and current SIA guidance for the rules that apply to your operation
About this article
The SecureOptix team
Written by people who work daily with security contractors on SIA licensing, screening and the records that hold up under an inspection.
- Published
- 24 August 2026
- Last revised
- 27 September 2026
- Topic
- SIA Licensing
How this is researched, dated and corrected is set out in our editorial standards. If something here is wrong or out of date, email hello@secureoptix.co.uk — corrections to a regulated detail are made as soon as we can confirm them, and the revision date above moves when they are.