Signing off a rota you didn't build

A rota that arrives finished from an agency, head office or a scheduling tool looks right. That is the problem. Before you sign it off, write down what you checked, what failed and who fixes it, and keep the version you looked at.

Below is an eight-check sheet for a shift or production manager, and a worked example of the check that catches most: a short turnaround. It runs on a spreadsheet. It also runs on workforce scheduling software.

Get the records before you read the grid

Ask the planner for the dated rota, how many people each line needs, current leave and availability, training records, and the hours rules they used. Ask for the last shift before the period and the first one after it too. Without them, a Sunday late followed by a Monday early can slip between two weeks that each look fine.

If something is missing, mark that check unknown and name who can supply it. A blank training record is not permission to work. Ask whoever owns training to confirm the qualification, that it is valid on the shift date, and whether supervision is needed.

Then pin down the working-time rules that apply to your site: the country's law and any agreement you work under. Note where each came from. If you can't establish a rule, ask HR before approving that part.

Use all eight checks

Copy this sheet into a spreadsheet. For each check, write pass, fail or unknown, point to your evidence, and note any correction. It is a review aid, not a legal certification.

In check 7, keep contracts apart from preferences. An agreed restriction has to be resolved before release. A declined preference may only need an explanation.

Check 5 has a trap: a weekly total can't settle an average-hours rule that runs over a longer period. Get the earlier hours, or record the check as incomplete. And a break drawn into the rota doesn't say who covers a role that must stay staffed.

If your tool reports on every assignment, use that to find the exceptions, and still check what went into it. By hand, sort each person's shifts by start time; rest gaps and overlaps show up fast. Scanning the three or five shortest gaps is a good first pass. It isn't the whole review.

Work the turnaround through to a decision

Article 3 of the EU Working Time Directive gives at least 11 consecutive hours of daily rest in each 24-hour period (directive text). Exceptions and national rules apply. For Great Britain, Acas describes an 11-hour entitlement between working days and the cases where rest is handled differently. Treat these as a way to find your own rule, not a figure for every worker or sector.

For the example, assume your rule is 11 hours, there is no clock change, all times are local, and the person does no other work in the gap. The shifts are illustrative.

Work the gap out from the full dates, not just two clock times. If a shift crosses a clock change, count the real elapsed time.

The figure uses an 11-hour rule as an assumption. Worker A finishes at 10pm and starts again at 6am: 8 hours. Worker B finishes at 3pm and starts at 6am: 15 hours.

Take the first row. 10pm plus 11 hours is 9am on Monday. Moving that person's start to 9am fixes their rest and leaves 6am to 9am with nobody on it.

Now suppose a second worker is free, signed off for the role, and finished at 3pm on Sunday. Their gap to 6am is 15 hours, so they are a candidate for cover, once you've checked their remaining hours, breaks and the staffing level. Make that change and recheck the whole rota before release. If nobody suitable is free, send the rota back and name the uncovered hours. A shift is not covered just because its last hours are.

Publish, hold or return: the decision in one picture

flowchart TD
  A[Rota arrives] --> B{Any check failed?}
  B -->|yes, and the fix is known| R[Return with check number, people and day]
  B -->|no| C{Any input unknown?}
  C -->|yes| H[Hold until the input arrives]
  C -->|no| P[Publish the version you reviewed]
  R --> A
  H --> A

Keep a decision someone else can follow

Use a short cover record with the sheet:

For the turnaround above, the entry reads: return for correction; check 4; Monday 6am start follows Sunday 10pm finish; needs an 11-hour gap and qualified cover for 6am to 9am; planner to send a revised version before publication. Add the real owner and due date.

Publish when the required checks pass, any known gaps have a plan someone with authority has agreed, and the version you release is the version you reviewed. Hold when an input that could change the decision is unknown. Return it when a known failure needs fixing. After a correction, recheck that person's surrounding shifts and the cover, and keep the original issue and its fix together.

Writing “accepted” next to a rest, qualification or cover failure doesn't clear it. Take it to whoever can change the staffing or confirm the rule.

Where a tool helps, and where the review stops

Fivexer's rest-break checker takes a week of shifts and the shift before it, compares them with the working-time figures you pick, and lets you copy or print the report. It checks the schedule you enter. It can't tell you whether training records are current or whether someone can safely cover a line.

It works in days and clock times, without calendar dates, so it doesn't model clock changes. Check those dates yourself.

A spreadsheet and one accountable reviewer can be enough for a small rota. As rotas get harder to read, a tool takes over the arithmetic, but the reviewer still needs the records and the authority to release it. None of this is legal advice, and a passing check isn't a finding that the rota is lawful.

Next step: take one person's full week, including their last shift before it, to the rest-break checker. Pick your own figures, replace the sample shifts, and save the report with your sign-off sheet. Then do the same for the others. One passing example doesn't approve the rota.