Rota planning, read from the constraints
A rota is what is left
after everything
that could not move
Fifty notes on shift scheduling, written from the constraints rather than the calendar. Not a guide to rota software — a working account of what actually holds a rota in place: which constraints bind, which only look as though they do, what each one costs to keep, and what changes when a single one is relaxed.
Where one fortnightly rota actually had room
Both people are on fixed part-time patterns nobody may change.
Movable to another twilight only; no transport after 21:00.
Movable at premium rates the budget does not hold.
No room in either direction.
Last contacted in April; nobody knows who still answers.
The rota has six spare shifts in it and two of them can actually be used. Spare capacity that cannot be moved is not spare capacity, and the difference is never in the staffing report. This is one employer's own fortnight, not a benchmark.
No jurisdiction is told what its law requires. Every figure here is an illustration of what one employer recorded for itself, labelled as such. Nothing in this collection is legal advice: rest requirements, notice of change, contractual hours and what may be asked of whom differ by jurisdiction, by sector and by agreement, they change, and they are a question for somebody qualified in the place concerned.
The two tables nobody writes down
Nine constraints on one ward rota, and what actually holds each
Three of the nine bind outright, three bend at a price somebody could state, two are assumptions nobody has tested and one is left over from a structure that no longer exists. The rota was built as though all nine were the first kind. This is one employer's own list, not a statement of what any rule requires.
What changed when one site stopped treating the shift start as fixed
Four lines improved, one got worse and one nobody is measuring — which is the line to watch. One employer's own before-and-after over four months, not a benchmark and not a recommendation about handover.
The rule discussed in “A rota is what is leftafter everythingthat could not move” is easier to test when the published schedule can be compared with a consistent record of actual hours. A team reviewing employee monitoring software for employee monitoring software can add current attendance and project context while keeping contractual rules and manager decisions explicit.
The assumptions behind “A rota is what is leftafter everythingthat could not move” can also be checked against US Wage and Hour Division FLSA resources. Record what applies locally and what requires qualified advice.
Why this starts at the constraints
Most writing about rota planning starts with the calendar: here is how to build a pattern, here is a system that will build it for you. This collection starts one step earlier, because the pattern is not the decision. The decision is the list of things that were treated as fixed before anybody opened the calendar at all.
That list is real, and in most organisations it has never been written down. Some of it genuinely binds: rest between shifts, a qualification somebody either holds or does not, a staffing standard that exists in a document. Some of it bends at a price that could be stated on one line, if anybody asked — a room, a van, two days of training. And a surprising share of it is neither: a number inherited from a structure that no longer exists, a promise made by a manager who has left, a start time chosen because a room was free in 2019.
A rota built as though all three kinds were the first kind is the normal case. It is also why so much scheduling effort produces so little change: the work goes into rearranging people inside a box whose walls were never measured.
So the sections run by where a constraint comes from: what holds a rota at all, the ones that truly bind, what people were promised, who can do what, the place and the kit, the ones nobody imposed — and last, what it takes to relax a single one and find out whether anything moved.
01 / 07
What holds a rota
Every rota is the output of constraints. The four kinds, who imposed each, and the one nobody can name.
02 / 07
The ones that bind
Rest, qualifications, licences and safe staffing — and how to tell a real requirement from a retold one.
03 / 07
What people were promised
Contracted hours, fixed days, what was said at interview, and arrangements that hardened without anybody deciding.
04 / 07
Who can do what
Skill mix as the constraint it really is, the single qualified person, and training as a way of relaxing it.
05 / 07
The place and the kit
One van, one key, one handover room, one terminal — the constraints made of physical things.
06 / 07
The ones nobody imposed
Inherited numbers, shift patterns built for demand that has gone, and rules whose author has left.
Scheduling software
Tools for shifts, time records and workforce operations
Three comparison formats based on structured product review and realistic rota exceptions.
07 / 07
Relaxing one
How to test a constraint, price it, choose which to move first, and measure whether anything actually changed.
The short version
Sort the constraints before improving the rota
Every rota is the arrangement left over after everything that could not move has been subtracted. Most schedules are rebuilt again and again inside a constraint set nobody has examined, and in almost every one of them a third of the constraints turn out to be habit, assumption or a rule whose author has left. Write the list down, mark what actually holds each line, and price the two or three that bend. That is cheaper than any system, and it is the only step that changes what a rota can be.