SIA Refresher Training Turned Licence Dates Into a Resourcing Problem

Published: 12 August 2026

The introduction of refresher qualifications into the SIA licence renewal route was, on the face of it, a training change. In practice it was a resourcing change, and a lot of security contractors are still managing it with the tools they used before.

Here is the difference. When a licence renewal was primarily an administrative process, an expiry date was a deadline for paperwork. Once renewal depends on holding a qualification, that same date becomes the end point of a chain that starts with booking a course — and the booking has to happen weeks earlier, against a training provider's availability, around a rota you are already struggling to fill.

What changed, and why it lands on operations

Refresher requirements attach to the licence types that make up most of the deployed workforce in manned guarding and door supervision, with relevant first aid sitting alongside for the applicable types. Two consequences follow immediately.

First, the training obligation is now on a cycle you do not control. It is driven by each officer's individual licence date, which is set by when they first applied, not by your training calendar. An annual training plan that runs January to December will always be misaligned with a workforce whose licence dates are spread across all twelve months.

Second, the failure mode is more expensive than it used to be. A missed compliance module is a record gap. A missed refresher is an officer who cannot lawfully be deployed, on a contract you are contractually obliged to staff, at a point where the alternative is overtime or a subcontractor at a worse margin.

"92% of courses completed" is not an operations metric

Most training reporting in the sector answers a question nobody in operations is asking. Completion rate is a training department measure. It aggregates across the whole workforce, it is backward-looking, and it treats every outstanding item as equivalent.

The operations question is different in three ways:

• It is forward-looking — not who is out of date now, but who will be, and when.
• It is segmented by contract — eight per cent outstanding spread evenly is a nuisance; eight per cent concentrated on one large site is a crisis.
• It is actionable — the number should come with the reason and the fix, not just the shortfall.

The version of the number that changes behaviour looks more like this: 38 officers cannot be deployed after the next 90 days unless action is taken — 14 with licences expiring and no renewal started, 19 with refreshers not yet booked, 5 with first aid lapsing. That sentence gets an operations director's attention in a way a percentage never will, because every element of it is something someone can act on this week.

Three clocks per officer, none of them aligned

The tracking problem is that a single officer carries several independent expiry dates, and the binding constraint moves between them.

Tracking three or four dates each across several hundred officers is not a spreadsheet job for long, and the spreadsheet fails in a specific way: it tells you the dates but not the interaction. Knowing an officer's licence expires in 60 days is useful only if you also know their refresher is not booked and the next available course is in 10 weeks.

Work backwards from the lead time, not forwards from today

The most useful change most contractors can make costs nothing. Stop calculating renewal warnings from a fixed number of days before expiry, and start calculating them from the total lead time required.

That total is roughly: course booking lead time, plus course duration, plus awarding body processing, plus SIA application processing, plus a contingency for a failed first attempt or a missed course due to shift patterns. In many cases that adds up to considerably more than the 30-day warning most systems default to.

Site clearance sits on top of the licence

A licensed officer is not automatically a deployable officer. Assignments carry their own inductions and client-mandated training — retail, events, corporate, public realm and critical infrastructure all differ, and some clients require site-specific content that has its own renewal cycle.

This matters more now that preparedness obligations for qualifying premises and events are working their way into contracts through the Terrorism (Protection of Premises) Act 2025. Where those obligations create staff training requirements for a client's site, they behave like any other assignment requirement: they attach to the contract rather than to the officer, and an officer cleared for one venue is not cleared for another. Worth confirming the current commencement position before planning firm dates around it.

The practical implication is that deployability has two layers. The licence layer determines whether someone can work at all. The assignment layer determines where. A resourcing view that only models the first will still put the wrong officer on the wrong site.

Operations checklist

• Hold licence, refresher, first aid and client training on one record per officer, not in four places.
• Report deployability at 30, 60 and 90 days rather than completion percentage.
• Segment the forecast by contract, because that is the unit of commercial risk.
• Set alert thresholds from total lead time, not from a fixed number of days.
• Attach a reason and a fix to every officer in the forecast, so the report is actionable.
• Model site and client requirements as a separate layer above the licence.
• Include subcontracted officers you are responsible for supplying.
• Keep renewal history — a client audit may ask how you managed a previous cycle.

The underlying point

Security contractors have always managed licence expiry. What changed is that the consequence of getting it wrong now sits in operations rather than in compliance, and the lead time is long enough that discovering a problem at 30 days is often discovering it too late. The reporting needs to move accordingly — from a record of what has been completed to a forecast of who you will and will not be able to deploy.