Running SIA-compliant door rotas without the headache

For a security company, a rota is not just a schedule. It is a compliance document in disguise. Every door-supervision shift has to be covered by someone who holds a valid, in-date SIA licence for the role they are working, and if that is not true, you are exposed: to a failed client audit, to a regulator's questions, and to the real possibility of an uninsured, non-compliant officer standing on a door in your company's name.

Most security firms know this perfectly well. The problem is rarely a lack of awareness. It is that the tools used to build rotas, usually a spreadsheet or a generic shift app built for cafes and shops, have no concept of an SIA licence. So the compliance check happens separately, in someone's head or in a second document, and over time the two drift apart. This guide walks through how to build a door rota that stays compliant by design, with less manual chasing, fewer last-minute panics, and a clear audit trail when a client asks for one.

Why the rota is where compliance quietly breaks down

Think about how a typical rota comes together. A manager knows roughly who is available, drops names into shifts, and sends it out. The licence check, if it happens at all, relies on the manager remembering who is licensed and whose badge is about to expire. That works until it does not: a busy week, a last-minute swap, a new starter, and suddenly someone is on a door without a current licence and nobody noticed.

The reason this keeps happening is that the two pieces of information, who is scheduled and whether they are compliant, live in different systems. The schedule is in one place and the licence details are in another, or in nobody's hands at all. Bringing them together is the single most important thing you can do to make your rotas reliable.

Treat the licence as part of the shift, not a side note

The mental shift that fixes most of this is simple: a shift is not filled until the person assigned to it has a licence that is valid for the role and in date on the day they are working. Not valid last month. Not valid in general. Valid on that date, for that role.

To make that possible, three pieces of information need to live permanently against each member of staff:

• The licence number. This is what lets you verify the licence against the official register rather than taking a photo of a card on trust.
• The licence type. A Security Guarding licence does not authorise door supervision. Matching the licence to the role is part of being compliant, not an optional extra.
• The expiry date. This is the piece that most often goes stale, and the one that causes the most damage when it does.

When those three things sit next to the person in whatever you use to build rotas, compliance stops being a separate task. The rota itself can tell you, at the moment you assign someone, whether that assignment is valid.

Check against the official register, not your own records

A licence that was genuine and valid when you onboarded someone can be suspended or revoked later, for reasons that have nothing to do with their work for you. Your internal spreadsheet will happily keep showing it as valid, because a spreadsheet only knows what someone last typed into it. The only way to know the real status is to check the licence number against the official SIA Register, and to do it more than once.

A good rhythm looks like this:

1. Verify at onboarding. Before a new starter reaches a single shift, confirm the licence number is valid, in date, and the right type for the work.
2. Re-check on a schedule. Because status can change at any time, re-check periodically so a suspension or revocation surfaces quickly rather than at an inspection.
3. Record the date you checked. Being able to show when you last verified a licence is what turns a claim of compliance into evidence of it.

This is covered in more depth in our guide on how to verify an SIA licence, but the headline for rota-building is this: trust the register, not the card, and not your own memory.

Make expiry a warning, not a surprise

There is a world of difference between an expiry you see coming and one that lands on you. An officer whose licence quietly expires on a Friday, who is then scheduled for a Saturday door, is a problem you discover at the worst possible moment. The same expiry, flagged four weeks earlier, is a two-minute conversation about renewal.

The practical answer is to build early warnings into the way you work. You want to know about an upcoming expiry while there is still time to do something about it, which in practice means at least four to six weeks out, because renewals are not instant. If your current process only tells you a licence has expired after it has expired, it is working against you.

A simple test of any rota system: does it tell you about problems before they happen, or only report them afterwards? Compliance that only ever looks backwards is just a record of things that already went wrong.

Default shift times and special hours

Compliance is the part that must not fail, but rota admin is the part that eats your time. A lot of that time goes on re-entering the same information: the same venues, opening the same hours, the same standard shift patterns, week after week.

Two things save a surprising amount of effort here. The first is default shift times per venue. If a venue's doors are covered from 20:00 to 03:00 on a Friday, the rota should start from that assumption rather than making someone type it in every week. You are only ever adjusting the exceptions.

The second is special hours for the dates that break the pattern: bank holidays, Christmas, a one-off event, a venue closing early. These are exactly the dates where mistakes creep in, because they are not the norm. Handling them explicitly, with their own hours and their own rates if they differ, stops the predictable December scramble.

Filling gaps without cutting corners

Every security manager knows the sinking feeling of a gap on the rota a few hours before a shift. The temptation in that moment is to put a body on the door and worry about the paperwork later. That is precisely how non-compliant shifts happen.

The way to avoid the choice between an uncovered door and a non-compliant one is to keep a small, vetted bench: a pool of staff whose licences and right-to-work are already verified, so filling a gap is a phone call rather than a compliance decision. When the checks are already done, speed and compliance stop being in tension. Reducing how often you reach that point in the first place is covered in our guide on cutting no-shows and last-minute gaps.

Keep an audit trail you can actually produce

Sooner or later a client, an insurer or a regulator will ask a version of the same question: who worked this door, on this date, and were they licensed? The quality of your answer in that moment depends entirely on the records you kept beforehand.

A strong audit trail ties together three things for every shift: who was scheduled, that their licence was valid and the right type on that date, and ideally proof that they actually attended. If those live together, you can answer in seconds. If they live in a spreadsheet, a chat thread and someone's memory, you are in for an uncomfortable afternoon of reconstruction, and your answer will never be as convincing.

Common mistakes to avoid

• Relying on memory for expiry dates. Human memory is not an alerting system. If the only thing standing between you and a lapsed licence is someone remembering, it will eventually fail.
• Checking once and never again. A single check at hiring tells you nothing about status six months later.
• Ignoring licence type. A valid licence for the wrong role is still a non-compliant shift.
• Treating last-minute swaps as outside the process. The swap is exactly where compliance is most likely to slip, so it needs the same check as a planned shift.
• Keeping compliance data separate from the rota. Two sources of truth guarantee they will disagree eventually.

Key takeaways

• A door rota is a compliance document. Build it so that an invalid shift is hard to create, not easy.
• Keep the licence number, type and expiry against each person, so the rota can check compliance as you build it.
• Verify against the official register and re-check over time, not just at hiring.
• Turn expiries into early warnings, four to six weeks out, so renewals are routine.
• Use default times and special hours to cut the repetitive admin, and keep a vetted bench so gaps never force a compliance compromise.
• Keep an audit trail that links schedule, licence and attendance, so you can answer the hard question in seconds.

Get these habits in place and SIA-compliant rotas stop being a weekly source of stress. The compliance becomes a property of the system rather than a test of your memory, and your time goes back into running the operation instead of chasing licence numbers.