Skip to content

SIA licence verification

ShiftTracker records SIA licences; it does not check them. Nothing in the platform contacts the Security Industry Authority — the compliance report links out to the public register for you to cross-reference by hand. Two separate stores matter: the licence typed onto the officer record, and a verified licence document. Only the second one blocks every deployment and raises expiry alerts.

Does ShiftTracker check a licence against the SIA?

No. There is no call to any SIA service anywhere in the platform. What you can do is record, by hand, what the public register told you.

What the platform gives you is a link. The SIA Compliance Report carries a panel headed Verify SIA Licenses, reading Cross-reference officer license numbers with the official SIA public register to verify validity and status, with an Open SIA Public Register button that opens services.sia.homeoffice.gov.uk/rolh/ in a new tab. Checking is yours to do, in that tab, by eye.

Under it, Record what the register said lets an Agency Admin or Agency Coordinator pick the Officer and the Result (valid, not found, suspended, revoked or expired) and press Record check. The officer's row then shows the result and date, and your audit trail records Checked the SIA public register: …. It is your reading of the register, not a check by the platform. It is shown and audited only: it does not change the officer's licence dates or block anything, and if the licence number changes the shown result is dropped.

The top of the SIA Compliance Report, subtitled Officer license details for SIA verification, with an Export menu on the right. Four counters run across it — Total Officers 5, Valid Licenses 5 in green, Expiring Soon (30d) 0 in amber, Expired 0 in red. Under them a Filters card offers a search box for officer, licence number or agency, an All Organizations menu and an All Statuses licence-status menu. Below that sits a blue panel headed Verify SIA Licenses, reading Cross-reference officer license numbers with the official SIA public register to verify validity and status, with an Open SIA Public Register button carrying an external-link icon. Under it a Record what the register said strip offers greyed-out Officer and Result menus and a Record check button. The frame stops above the officer table.

So "valid" on any ShiftTracker screen means one thing only: the expiry date somebody typed in has not yet passed. It does not mean the licence exists, that it belongs to that officer, or that the SIA has not suspended or revoked it.

Where does a licence actually live?

In two places, kept by two different actions, feeding two different screens. This is the part that catches people out.

Officer record Verified document
How it gets there Typed into Add Officer, or into the Role & licence card on the Officer Details tab after pressing Edit on it A file uploaded on the officer's Compliance tab, then marked Verify
Who can do it Agency Admin, Agency Coordinator Upload: either. Verify: Agency Admin only
Feeds Officers list, officer profile badge, SIA Compliance Report Officer Compliance rollup, expiry alerts, the deploy-block
Checked when you propose the officer for a request Yes — the officer must hold every licence the request needs, each with an expiry on or after the shift date Yes — the expiry must not fall before the shift, when the request needs a licence
Checked when you put the officer on your own roster No Yes
Raises expiry alerts No Yes

The two never sync in that direction. Typing a licence number onto the officer record leaves the compliance summary reading No data for that officer, and no alert will ever fire for it. Verifying a document goes the other way: it copies the number, type and expiry onto the officer's roster record and rebuilds the compliance summary.

You can see the split on any officer added through Add Officer with no document behind them: they count towards Valid Licenses on the SIA Compliance Report, and read No data on the Compliance tab of the officers list at the same moment.

Before you start

  • An Agency Admin login. A Coordinator can add officers and upload right to work documents, but cannot upload or Verify a licence, which is the step that counts.
  • The officer's email address. It is required on Add Officer, and the officer must accept the invitation before they can be put on any shift.
  • For the document route, a scan or photo of the licence as JPEG, PNG, WebP or PDF, 25 MB or smaller.

How do I record a licence on the officer record?

  1. Go to People → Officers.
  2. Press Add Officer, or open an existing officer and press Edit on the Role & licence card. The ⋯ menu on a row has Edit licence to go straight there.
  3. On a new officer, fill Full name and Email address, then press Continue. Phone number is optional.
  4. On Role and licence, pick a Role type. The licence fields appear unless the role needs no licence.
  5. Set SIA licence type — one of Door Supervisor, Security Guard, CCTV PSS, NASDU Level 2.
  6. Type the SIA licence number. It must be exactly 16 digits, and spaces are fine.
  7. Set SIA licence expiry. It cannot be in the past.
  8. Press Continue, skip anything else you do not have, and press Create Officer.

You can also skip the licence and add it later. The officer then shows Not ready until it is in. Nothing stops them being put on your own roster in the meantime, so check it first.

That is the whole of it. Nothing is checked against anything external. From then on the officer's licences are checked whenever you propose the officer for an organisation's request — but not when you put them on your own roster, and no expiry alert is ever sent for a licence that exists only here.

How do I record a verified licence document?

This is the route that arms the deploy-block and the expiry alerts. The compliance documents page covers the Compliance tab in full.

  1. Open the officer and choose the Compliance tab.
  2. Under Upload document, pick SIA Licence from Document type.
  3. Set Expiry date to the date on the licence. This is the date everything downstream reads — the compliance rollup, the alerts and the deploy-block all use it, not the one on the officer record.
  4. Put the licence number in Reference / number, which relabels itself (SIA number) once the type is chosen, and the licence type in SIA licence type.
  5. Choose the File and press Upload. The row appears with a Pending status.
  6. Check the file against the SIA public register yourself, then press Verify. The row turns Verified.

Verifying does three things at once: it stamps the document with who verified it and when, copies the number, type and expiry onto the officer's roster record, and rebuilds that officer's compliance summary. Unverify and the archive button both reverse the copy, clearing the mirrored fields back to empty.

What does an expired licence stop?

Putting the officer on a shift dated after it ran out — on your own roster, or against an organisation's request.

The check compares the verified SIA expiry against the shift's date, not against today, so an officer whose licence is valid now but lapses before the shift is refused. There is no override for it: unlike a working-time warning, this one cannot be reasoned past. The wording depends on where you are:

Where What you see
Your own roster — assigning or reassigning a shift SIA licence expired (YYYY-MM-DD) before the shift date — officer cannot be deployed.
An organisation's request — proposing, being confirmed, or changing the officer Verified SIA licence expired on YYYY-MM-DD, before the shift on YYYY-MM-DD

On a request, the licences held on the officer record are checked as well, against the licences the request needs. Both refusals name them:

Where the officer falls short What you see
Does not hold a required licence Officer does not hold the required licence: Door Supervisor — several are listed with commas
Holds it, but it ends before the shift Officer licence expired before the shift on YYYY-MM-DD: Security Guard expired YYYY-MM-DD

A licence is valid through its expiry date, so one that ends on the day of the shift still counts. If a request lists no licence, only its role is looked at: a role that needs an SIA licence checks it, and a role that needs none takes any officer.

It fails open. An officer with no compliance summary at all — nobody has verified a document for them — is allowed through on the verified-document check. A hard block on unknown data would make every new officer unschedulable until their paperwork landed.

Right to Work is checked in exactly the same way, with the same message shape and the same fail-open rule. Separately, an officer who has not yet accepted their login invite cannot be put on any shift at all.

Can an officer hold more than one licence?

Yes. The licence on Role & licence is the officer's main one. Any others go under Additional licences on the same card — see Add and manage officers. Up to 10 can be added.

An organisation's request, or a shift pattern, can ask for one or several licences, and an officer must hold all of them, each valid on the shift date. Extra licences an officer holds never count against them. Propose, bulk propose, confirm, and changing the officer on a proposal all use the same rule, and refuse an officer who falls short. The refusal links to Add licence, or Update licence where one has expired, on the officer's page, in a new tab so your dialog is kept.

Additional licences are recorded only. They have no verified document, no check against the SIA register, no expiry alert and no place on the SIA Compliance Report.

What warns me before it lapses?

A daily sweep reads the compliance summaries and notifies each agency's Agency Admin and Agency Coordinator users about the officer's soonest-expiring credential, in three bands:

Band Notification title
Already expired Officer credential expired
Within 7 days Officer credential expires in ≤ 7 days
Within 30 days Officer credential expires in ≤ 30 days

The message names the credential and the officer, and says the officer cannot be deployed once expired. The officer is e-mailed at the same points, unless they have been deactivated.

Because the sweep reads the compliance summary, it only ever fires for licences recorded as verified documents. A licence that exists only on the officer record produces no alert at all — however close to expiry it gets.

The SIA Compliance Report is the other early-warning surface, and it reads the officer record instead. It counts Total Officers, Valid Licenses, Expiring Soon (30d) and Expired, filters by search text, organisation and License Status, and labels each row Valid (n d), Expiring Soon (n d), Expired or N/A for an officer with no licence at all. Its Export menu offers Excel (.xlsx) and CSV, both named sia-compliance-report- plus today's date.

If it goes wrong

The Document type menu is empty. The agency upload dropdown is fed from the platform's system document types, which are installed with the database rather than created by the app. If they are missing on your instance the list comes back empty and there is nothing to pick — the licence document cannot be uploaded at all. Contact support.

"Licence number must be exactly 16 digits." The field strips anything that is not a digit and caps the result at 16, so a shorter number is what a partial paste leaves behind. Check for a missing group of four.

"An officer with this licence number already exists." That number is already on another active officer in your agency. The check ignores deactivated officers, so set the officers list's status filter to Deactivated or All statuses and search again before assuming a typo.

"Licence expiry date cannot be in the past." Both the form and the server refuse a past date outright. There is no way to record a lapsed licence on the officer record — record it as a document instead, where a past expiry is accepted and correctly reported as expired.

Officer shows Valid on the report but No data on the Compliance tab. Working as designed, and the point of this page: they have a licence typed onto their record and no verified document. Upload and verify one.

"File exceeds 25MB limit", "Unsupported MIME type …", or "File content doesn't match declared type". The last of those is a content check, not an extension check — a PDF renamed to .jpg is caught by it. Re-export the file in a genuine JPEG, PNG, WebP or PDF.

A Coordinator presses Verify and gets Agency Admin role required. Verifying, unverifying and archiving are Agency Admin actions; the buttons are shown to Coordinators too, but the action is refused. Uploading is open to both.

Last updated 2026-11-17