Security rotas breach working time rules more often than most sectors, and the industry's special-case exemptions are widely misunderstood. A practical guide to what applies, what does not, and what you have to record.
The Working Time Regulations 1998 apply to security operations like any other employer, but the way security work is structured means breaches happen more easily and are noticed less often. Long shifts, night work, permanent-presence requirements and officers working across multiple sites all push against limits that were written with more conventional patterns in mind.
This guide covers what applies in practice, where the security-specific exemptions genuinely help, and where operations tend to assume an exemption that does not exist.
As always with regulation, this is general guidance rather than legal advice, and it is worth confirming anything borderline with an employment law adviser who knows your contracts.
The 48-Hour Average and What It Actually Means
Workers should not work more than 48 hours a week on average. The word doing the work is average, the limit is calculated across a reference period, normally 17 weeks, not week by week.
This matters for security because it means a 60-hour week is not automatically a breach. It becomes one if the average across the reference period exceeds 48. Equally, an operation that keeps every individual week under 48 but does so by never tracking the average is not managing the limit, it is avoiding it by accident.
The practical failure is officers working across more than one branch, contract or employer. Each side sees a compliant total. Nobody sees the combined figure. If you operate multiple branches from one back office, this is worth checking specifically, because it is invisible until someone looks for it.
Opting Out Is Not a Blanket Permission
Workers can agree to opt out of the 48-hour limit. The opt-out must be individual, voluntary and in writing, and the worker can cancel it by giving notice.
Three things go wrong with opt-outs in this industry. They are presented as a condition of employment, which undermines the voluntariness the opt-out depends on. They are signed once at induction and never revisited. And they are assumed to cover everything, when in fact the opt-out applies only to the 48-hour weekly limit, not to rest breaks, not to daily or weekly rest, and not to the separate limits on night work.
An officer who has opted out is still entitled to their rest periods. That is the misunderstanding that appears most often.
Daily and Weekly Rest
Workers are entitled to eleven consecutive hours of rest in each 24-hour period, and to an uninterrupted period of 24 hours of rest each week, or 48 hours in each fortnight.
Eleven hours between shifts is the check that catches most security rotas. A 6pm to 6am night shift followed by a 4pm start the next day leaves ten hours. It is an easy thing to build accidentally when covering a gap, and an easy thing to miss when the rota is built in a spreadsheet with no automatic checking.
Rest Breaks During a Shift
Where a shift exceeds six hours, the worker is entitled to an uninterrupted rest break of at least twenty minutes, taken during the shift rather than at the start or end.
Uninterrupted is the operative word, and it is where single-officer sites create genuine difficulty. An officer who is the only person on site and remains responsible throughout has not taken an uninterrupted break, even if they sat down for twenty minutes.
Night Work Has Its Own Limits
Night workers should not work more than an average of eight hours in each 24-hour period, again calculated over a reference period. Note that this is a separate limit from the 48-hour week and is not covered by the opt-out.
Night workers are also entitled to a free health assessment before starting night work and at regular intervals afterwards. This is a requirement a lot of security operations have simply never implemented, and it is straightforward to put right.
Where Security Gets a Genuine Exemption
The Regulations recognise certain activities as special cases, and security and surveillance activities requiring a permanent presence are explicitly among them. Where the exemption applies, the requirements for daily rest, weekly rest and in-shift rest breaks can be modified.
Two things are widely misunderstood about this.
First, the exemption does not remove the entitlement. It defers it. Where a worker cannot take the rest they would normally be entitled to, they should receive an equivalent period of compensatory rest. The obligation shifts rather than disappears.
Second, it does not touch the 48-hour average weekly limit or the night work limits. Those still apply in full.
An operation relying on the special-case provision to justify short rest between shifts, without providing compensatory rest and without any record of doing so, is not in the position it thinks it is.
Why Security Rotas Breach These Rules More Than Most
Cover changes are the main cause. A rota built carefully on Monday is compliant. By Thursday, two sickness absences have been covered by whoever answered the phone, and nobody re-ran the checks on the replacement.
Long shifts compound it. Twelve-hour shifts leave much less headroom for an unexpected extra shift than eight-hour ones, so a single piece of last-minute cover can push someone over a limit that a shorter pattern would have absorbed.
And multi-site working hides it. The manager assigning the cover shift often has no visibility of what the officer worked for a different site earlier in the week.
Keeping Records That Prove Compliance
Employers are required to keep adequate records showing the 48-hour limit is being complied with, and to retain them. Records relating to night workers' health assessments should also be kept.
Adequate is doing some work in that sentence. A rota showing planned shifts is not the same as a record of hours actually worked, and in an industry where actual hours routinely differ from planned hours, the distinction matters. Verified clock-in and clock-out data is a considerably stronger record than a published rota.
What Good Looks Like Operationally
The checks that matter, cumulative hours across the reference period, eleven hours between shifts, weekly rest, night work averages, are all mechanical. They are also all easy to skip under time pressure, which is exactly when they are most needed.
ProRota runs them as the rota is built rather than afterwards. Assigning a shift that would breach the weekly hours limit, leave insufficient rest, or push a night worker over the average surfaces immediately, at the point where fixing it is cheap. Actual worked hours come from GPS-verified clock-in and clock-out rather than from the plan, so the record reflects what happened. And because hours are tracked against the person rather than the site, cross-site totals are visible.
If you are not confident you could currently evidence compliance across your whole workforce, that is a good reason to look at how the data is being captured. Get in touch and we will walk through it with your own rota.
