Shift work and rotating schedules

A fixed nine-to-five is easy to track and easy to check. A rotating rota is neither, which is why shift workers both need a personal record most and are least likely to keep one.

Templates first

The single change that makes rota tracking sustainable is to stop entering times and start applying templates. Define your shifts once — early, late, night, whatever your workplace calls them — with their start, end and break already set. Entering a week then becomes seven selections rather than twenty-eight fields.

In Working Hours 4b these are called working profiles. The specific tool matters less than the principle: if entering a week of shifts takes more than a minute, the record will not survive a busy month.

A useful discipline is to name templates after what your workplace calls them, not after their times. "Early" is what appears on the rota you are copying from; "06:00–14:00" requires a translation step every single time, and translation steps are where errors enter.

Night shifts and the date problem

A shift running 22:00 to 06:00 spans two calendar days. Which day does it belong to?

There is no universally correct answer, but there is a correct approach: pick one convention and never vary it. The two workable options are to attribute the shift to the day it started, or to the day on which most of its hours fell. The first is more common, simpler to apply, and usually matches how rotas are published.

What breaks a record is inconsistency — attributing some night shifts to the start date and others to the end date. Monthly totals then depend on which nights happened to fall at the month boundary, and reconciling against a payslip becomes impossible. Decide once, write the decision down somewhere, and apply it even when it feels wrong for a particular week.

Cycles and how far ahead to enter

Most rotas repeat on a cycle: 4 on 4 off, a three-week rotation through early/late/night, a two-week pattern with alternating weekends. Once you know the cycle, you can enter the scheduled version of it several weeks ahead in a few minutes.

This is worth doing, with one caution. A rota entered in advance is a plan, and plans change. Shifts get swapped, extra shifts get picked up, sickness reshuffles a week. If you enter ahead, you must also review each week as it passes and correct what actually happened. A record full of planned shifts that never occurred is worse than no record, because it looks authoritative and is not.

The practical compromise most shift workers land on: enter the cycle ahead so nothing is forgotten, and spend two minutes at the end of each week correcting the reality. That is a far smaller job than entering from scratch, and it keeps the record accurate.

Swapped and covered shifts

Shift swaps are the most under-recorded event in rota work. You cover someone's Saturday, they cover your Wednesday, and both of you assume it nets out. Sometimes it does. Sometimes the Saturday attracted a weekend premium and the Wednesday did not, and the swap quietly cost you money.

Record swaps explicitly: the date, who it was with, and what was given in return. It takes ten seconds in a note field and it is the only way to answer the question later.

Averaging periods make monthly totals misleading

Many working-time frameworks do not cap hours per week directly. Instead they cap an average over a reference period — commonly several months, with the exact length set by law, collective agreement or contract. The EU Working Time Directive works this way, and so do a number of national regimes outside the EU.

Two consequences for anyone keeping a record:

• A heavy month is not necessarily a breach, and a light month does not necessarily fix one. What matters is the rolling average over whatever period applies to you.
• You need continuous data to compute it. An average over seventeen weeks cannot be reconstructed from three weeks of records. This is a genuine argument for keeping the log going during quiet periods, when the motivation to bother is lowest.

Look up the reference period that applies to your contract rather than assuming a figure — they differ substantially, and some sectors have their own rules. The point here is structural: if your working time is assessed as an average, your tracking has to be continuous or it cannot answer the question.

Night work has its own rules

Beyond pay, night work is usually regulated separately: limits on the length of a night shift, restrictions on consecutive nights, and in many jurisdictions a right to health assessments for regular night workers. The definitions — what counts as "night", how many night hours make you a "night worker" — vary by country.

You do not need to know the regulations to track the data. Record the shifts accurately and the underlying facts (how many nights, how long, how much rest between them) are there if you ever need them. That is the general case for tracking: the record is cheap to keep and impossible to reconstruct.

A workable routine

1. Define a template per shift type, named as your workplace names them.
2. Enter the published rota as far ahead as it is published.
3. At the end of each week, correct what actually happened — swaps, extra shifts, early finishes, interrupted breaks.
4. At the end of each month, check the total and the month boundary before comparing against the payslip.

Steps 3 and 4 take about five minutes a month between them. That is the whole cost of having a record you can rely on.