Skip to content

Overtime and the Working Time Directive

Whenever someone is put on a shift, ShiftTracker checks the Working Time Regulations 1998: the 48-hour limit as an average over a 17-week reference period, eleven hours' rest, and whether they are already booked. A clash is refused; a Working Time breach can be overridden with a reason, which is kept as a Working Time record. The roster shows each person's average. Overtime is a separate thing, and is not calculated as pay.

What is checked, and when?

Every time someone is assigned to a shift — from the roster, the month grid, copying a week, approving an application, or confirming an agency officer — and whenever a shift's times change.

Check Outcome What you see
Already on an overlapping shift Refused Employee is already scheduled for an overlapping shift
Approved leave over the date Refused Employee is on approved … leave from … to ….
Average over 48 hours, no opt-out Warning, needs a reason Exceeds the 48-hour average (Working Time Regulations 1998 reg 4(1)): …h averaged over the 17-week reference period (this week …h). Employee must sign a reg 5 opt-out before proceeding.
Average over 48 hours, opt-out on file Warning, needs a reason The same, ending Employee has a signed reg 5 opt-out on file — override permitted.
This week over 48, average under Advisory only …h scheduled this week, above 48h. Lawful — reg 4(1) sets an average … but worth watching before the average follows.
Less than 11 hours' rest before or after Warning, needs a reason Less than 11 hours rest …, naming the other shift
The employee marked themselves unavailable Warning Employee marked themselves as unavailable on this day of the week.

Overlaps and rest are measured on the real start and end of each shift, so an overnight shift and a same-day turnaround at another site are both caught.

How is the 48-hour average worked out?

As the regulations do: hours worked in the reference period divided by its weeks, across every site in your organisation.

  • The reference period is 17 weeks, rolling, and every 17-week window the shift falls in is tested — the worst one counts. For someone who started less than 17 weeks ago, it is the weeks since they started.
  • Leave is left out. Days on approved leave come out of the period, and the same number of days worked after it are added in, so a fortnight's holiday does not make a heavy rota look lighter.
  • Weeks run Monday to Sunday.

Two settings exist but have no screen: the organisation's reference period, which can be up to 52 weeks under a workforce agreement, and a per-employee flag for reg 21 — security work needing a permanent presence — which lengthens their period to 26 weeks and turns the rest rule into compensatory rest. Both stay at the default, 17 weeks and off, unless they are set for you.

Where do I see it before I assign?

On the roster's Employees view — switch Patterns to Employees. The last column, Avg / week, shows each person's average over the reference period, with this week's hours beneath. Hover for the working. The same two figures sit on each shift on the Patterns view.

Colour Means
Grey Average 40 hours or less, and this week 48 or less
Amber Average over 40, or this week over 48 — lawful, but heading that way
Red Average over 48, with no opt-out — a breach
Blue Average over 48, with an opt-out on file

The Meadowhall Distribution Centre roster for Sep 7 – Sep 13, 2026, with the row toggle on Employees. Five rows — Marcus Ademola, Ifeoma Adeyemi, Callum Boyd, Gareth Pritchard and Priya Raghunathan, each with their number and job title — carry their Gatehouse Day and Gatehouse Night shifts across the week, plus an S sickness mark for Ifeoma on Wednesday, an AL annual leave mark for Gareth on Thursday and Gareth's ad-hoc 14:00 – 22:00 shift on Saturday. The Avg / week column reads Marcus 2.8h avg, 48h wk; Ifeoma 1.4h avg, 24h wk; Callum, in amber, 3.5h avg, 60h wk; Gareth 2.6h avg, 44h wk; and Priya 2.8h avg, 48h wk.

The averages in the demo are low because it holds only a few weeks of shifts. Callum is amber: 60 hours this week is over 48, but lawful, because his average is far under.

How does the opt-out work?

A reg 5 opt-out is recorded on the employee.

  1. Open People → Employees, the person, and the HR tab.
  2. Under Working Time Directive, tick WTD 48-hour opt-out signed. Signed date fills in with today; change it to the date on the signed form.
  3. Save changes.

Unticking it later records a cancellation date rather than erasing it. The opt-out is judged as of each shift's date, so it covers shifts while it was in force.

An opt-out changes the colour, the wording and your paperwork. It does not skip the check: a breach is still a warning to override, with a reason.

How do I override a warning?

When an assignment raises warnings, Shift Conflicts Detected lists each with Blocked, Override allowed or Warning — Same-time overlaps are blocked. UK Working Time warnings can be overridden.

  1. Read what it collides with.
  2. Where a Working Time finding is listed, fill Reason for overriding the Working Time warning *.
  3. Press Override and assign.

The note under the box reads Kept as a Working Time record (reg 10(1)) against this decision, attributed to you. The brackets name the regulation actually breached — reg 4 for the 48-hour average, reg 10(1) for rest between shifts, reg 11 for weekly rest — and list more than one when the assignment breaches more than one. On a confirm from the requests screens the note reads Recorded against this allocation with your name. Working Time warnings are kept as a Working Time record. A clash on its own needs no reason, because there is nothing to record — and cannot be overridden anyway. The same applies when you confirm an agency officer; see Review proposals and confirm officers. Copy week to… does not override a week with warnings for you: it marks that week with a Review button, which opens this dialog for that week alone. Changing the employee on a shift from its panel, and restoring a cancelled shift, open it the same way.

What about agency officers?

They are checked in the same way, against everything they are committed to: shifts on their agency's roster, and work confirmed or proposed at every organisation they cover, not just yours.

  • Confirming an officer onto a shift that overlaps another confirmed one is refused. Proposing one, or confirming over a proposal, is a warning.
  • The 48-hour average applies to them as to employees.
  • An officer can also set a maximum hours per week in their own portal, tested against the single week — a personal limit, separate from the regulations.

What counts as overtime?

Something else, unconnected to the 48 hours.

On the reporting dashboard's Payroll tab, OT Hrs splits each employee's hours week by week: up to 40 hours is regular, anything above is overtime. It is a count of hours, nothing more.

Overtime is not paid at a different rate. No screen sets an overtime rate, arbitration records every shift's overtime pay as zero, and so the Overtime element in the payroll export is always zero hours. If your staff are paid more for overtime, apply it in your payroll.

If it goes wrong

What you see What it means
Refused, with no override button An overlap or approved leave. Move one first.
Override and assign is greyed out Write the reason.
Someone is amber though under 48 this week Their average is over 40 — heading for the limit.
A warning names hours at another site The average and rest checks count every site in your organisation.
You need a 26-week or longer reference period It can be stored for your organisation or a worker, but no screen sets it.
Night-work limits, young workers Not checked. They need your own procedures.

Last updated 2026-11-17