The List Nobody Has Written
How to build a constraint register for a rota in an afternoon, what belongs on it, and why it has to live beside the rota.
The constraint register is a single page listing everything treated as fixed when the rota is built. Almost no organisation has one, including those with sophisticated scheduling systems, because the system holds the rules and nobody has ever asked it to explain itself.
The constraint in “The List Nobody Has Written” becomes useful only when its source, cost and effect on coverage are visible. A team considering open the official feature summary for task switching cost can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
Building the first version takes an afternoon. Keeping it takes about ten minutes a month, and it is the cheapest piece of workforce documentation available.
The assumptions behind “The List Nobody Has Written” can also be checked against NYC Fair Workweek information. Record what applies locally and what requires qualified advice.
What a line looks like
One constraint per line, five fields: the rule in a sentence, its source, which kind it is, what it costs to keep, and the date somebody last confirmed it.
The sentence matters more than it sounds. "Weekend cover" is not a constraint; "no more than one weekend in three for any individual" is. Vague entries cannot be tested, and the whole point of the register is that each line can be.
Where the lines come from
Four sweeps, in this order:
- Read the current rota and write down every pattern it visibly obeys.
- Open the scheduling system's rules and constraints configuration and write down what is in it.
- Ask the two or three people who build or fix the rota what they work around.
- Read the contracts and any individual agreements for the team.
The second sweep is the one that surprises people, and the fourth is the one that gets skipped. Both hold constraints nobody would otherwise name.
What does not belong on it
Preferences that have never been promised anything. Aspirations. Things the organisation would like to be true about its rota.
A register that mixes constraints with wishes becomes unusable within a year, because nobody can tell which lines are claims about the world and which are hopes. Wishes belong somewhere else.
Keeping individual arrangements on it carefully
Personal arrangements are constraints and they belong on the register, but the register is read by more people than the arrangement concerns.
The usable compromise is to record the constraint and its status without the circumstances: the days, the review date, and the fact that it is a recorded agreement. Why it exists belongs in the individual's file, and what happens to that information is a question for somebody qualified where you are.
The field everybody leaves blank
The date. A register without dates is a snapshot of beliefs at an unknown moment, and within two years it is actively misleading because the rules it records have drifted and it has not.
One date per line, updated when anybody confirms the entry. Lines that have not been touched for two years are the review list, and they generate themselves.
Where it lives
Beside the rota, in whatever the rota actually lives in, readable by everybody who builds one. Not in a project folder, not in a strategy deck, not as an appendix to a review that finished.
A register nobody opens is a register that is wrong, and it will be quoted anyway, which is worse than its not existing.
What it is not for
It is not an audit of whether managers have been following rules, and if it is used that way once it will never be honest again.
The register works because people write down the things they work around. That requires it to be safe to record "rule nobody can source, followed anyway", and the first time that entry is used against somebody the next version will contain only the rules that look good.
What the first version always contains
Between twenty and forty lines for a single department, of which four or five turn out to be duplicates of each other phrased differently, and three or four contradict each other outright.
The contradictions are the most valuable output of the first pass. They are being resolved somewhere already, usually by one person's judgement, usually unrecorded, and usually that person is the only one who can build the rota.
Who should own it
The person who builds the rota most often, with a named deputy. Not a committee, and not whoever happens to be running a transformation programme this year.
Ownership here means two obligations and no others: add a line when a new constraint appears, and update the date when somebody confirms one. A register with heavier obligations attached to it stops being maintained within about two months, which is the usual fate of these documents.
The second version
Shorter. Duplicates merged, contradictions resolved or marked as resolved by judgement, assumed lines either sourced or marked as assumptions with dates.
A register that shrinks between versions is working. One that grows is usually collecting preferences, and it is worth re-reading the second section of this page before the third version.