How to build a 24/48 rota that survives the first month

Twenty-four hours on, forty-eight off looks simple on paper. Three shifts, each one comes in every third day, done. The trouble starts with the first holiday request, the first swap, and the first month when somebody adds up the hours.

Why three shifts

The 24/48 rhythm follows straight from arithmetic: one day on and two days off is a three-day cycle, and covering every day of that cycle takes three crews. With four you get 24/72 — one day on, three off — a calmer rhythm that needs more people.

So the first decision is not about the rota at all. Count how many people must be on duty at once, multiply by the number of crews, and compare that with the staff you actually have. If the number does not fit, no pattern will fix it.

The shift is the unit, not the person

The most common mistake when building this kind of rota is planning by individuals. You put Smith on Monday, Jones on Tuesday, and it works until somebody takes a week off. Then the queue slides, crews get mixed, and two weeks later nobody knows who they are working with.

In shift work the unit is the crew. It comes on for the day, it goes off, and it returns two days later. One person's absence makes their own shift smaller, but it does not shift the whole queue — the rest of the rota stays untouched.

The difference sounds small until you compare three months of a rota run each way.

What to do about time off

Time off in a shift system has two effects: somebody drops out of specific days, and somebody else needs to know early enough. That is why it pays to separate two things that often blur together:

• the request — the worker says they cannot make those days;
• the approval — the coordinator accepts it, and only then does the rota stop counting on them.

Without that split everyone excuses themselves and the coordinator finds out about the gap the day before. With it, the request waits for a decision and the rota changes only after one.

Swaps without a hole in the roster

When somebody cannot take an assigned day, the tempting fix is simple: take them off and look for a replacement. The problem is that in between, the rota shows a gap although nothing has actually been cancelled.

Turn the order around. The person stays on duty and flags that they are looking for cover. Only when somebody takes it does the exchange happen: the successor goes on first, then the predecessor comes off. The roster is never briefly short, and the coordinator has no gap to watch.

Count hours, not duties

At the end of the month it is easy to decide that ten days each means everything is fair. Except days differ — holidays, nights, ones stretched by a swap. The number of duties says nothing about the load.

Count hours and look at the gap between the busiest and the quietest person. If that gap grows month after month, the queue has jammed somewhere — usually through swaps that were never returned.

Where to start

If you are building such a rota for the first time, work in this order: split people into crews, set the start day of the first one, and only then deal with exceptions. There will always be more exceptions than you expect, but they only make sense once the rhythm works.

In DutyShifts the whole pattern is one form: pick 24/48, a start day and your crews, and the app creates the series and the queue where each shift takes its own day. Time off, swaps and hour counting run on that same rota, so none of them needs watching separately.