A three-shift rota, without rebuilding it five times

Echipa HR 365 · reviewed 2026-09-04 · 5 min read

The rota gets rebuilt five times because it starts with the people. The order that works is the reverse: first what has to be covered, then who cannot work when, and only at the end who goes where. Every step skipped comes back as a rebuild.

The six steps, in order

From requirement to published rota

1. 1. The requirement — how many people on each shift and each day — including the weekend, which has a different requirement from the one assumed
2. 2. Competencies — which posts need a specific qualification; they constrain the most, so they are placed first
3. 3. Unavailability — approved leave, requests submitted by the announced deadline, known restrictions
4. 4. Rotation — who worked nights and weekends in the preceding period — it gets balanced, not started from zero
5. 5. Allocation — filled in only now, with the constraints above already fixed
6. 6. Publication — at least a week ahead, in one place that stays valid through changes

The deadline for requests: fixed, not discretionary

Unavailability requests are collected up to an announced time — for instance Thursday noon for the following week. Anything arriving after the deadline falls into the category of changes, which are handled differently and with more difficulty.

The effect of the deadline is not disciplinary, it is practical: it turns twenty scattered messages into one list the planner goes through once. Without it, planning never ends, because a new request always appears while you are working on the rota.

Rotation: what actually gets balanced

The last row is a practical observation many planners discover on their own: it is easier to move from mornings to afternoons to nights than the other way round. The direction of rotation is a choice that costs nothing and is felt.

Changes after publication

They cannot be eliminated, but they can be channelled. Three rules, announced along with the rota:

• Whoever requests a change also proposes the solution: who they are swapping with. A request without a solution is a problem passed to the planner.
• The change is recorded in the same place as the rota, not in a message. Otherwise it surfaces at month-end reconciliation as an unexplained deviation.
• Under 24 hours before a shift, the change goes through the manager rather than being settled between colleagues. At that point, an unannounced swap means an uncovered post.

How far ahead you publish

The planning horizon is the decision with the greatest effect on people’s lives and on the number of changes you will handle. A week is the functional minimum; two weeks changes the quality of life of a night-shift team more than almost any other benefit.

The usual argument against a long horizon is that volume cannot be predicted. That is usually untrue for the skeleton of the rota: who is on mornings and who is on nights can be fixed two weeks out even if the exact number of people is adjusted a few days ahead. Publish the skeleton early and the adjustments late, rather than publishing everything late.

Repeating patterns and when they get in the way

A fixed pattern — for instance four days on, two off, rotating the shifts — saves hours of planning and is easy for everyone to understand. Its limit shows at the exceptions: somebody with a permanent restriction on nights breaks the pattern and forces manual adjustment of everything else.

The practical solution is not abandoning the pattern but taking the exceptions out of it: people with permanent restrictions are placed first, by hand, and the pattern is applied over the rest of the team. The reverse order — pattern first, exceptions after — requires rebuilding half the rota at every adjustment.

Where to start

If you rebuild the rota several times a month, first check which step you get stuck at: usually it is unavailability, received after you started allocating. A fixed deadline for requests solves that on its own, with no other change.

If the rota is stable but people complain about fairness, the problem is at the rotation step: nobody keeps a record of night and weekend shifts, so the distribution looks arbitrary even when it is not. One column with the number of nights in the last eight weeks makes the argument disappear.

If you are just starting, build in the order in this article and publish the first rota two weeks ahead, even if it is imperfect. A mediocre rota published early is more useful than a good one published on Friday evening.