Writing the Constraint Down as a Sentence
Why a constraint has to be written as a sentence somebody could disagree with before anything can be done about it, and the four tests a good one passes.
Nothing can be done with a constraint until it is written as a sentence somebody could disagree with. "Weekend cover" is not a constraint. "No individual works more than one weekend in three" is, and the difference is the whole of what makes the rest possible.
The constraint in “Writing the Constraint Down as a Sentence” becomes useful only when its source, cost and effect on coverage are visible. A team considering employee monitoring at tech companies for planning teams for employee monitoring at tech companies can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
This sounds like a formatting point. It is the step at which most constraint work either succeeds or quietly stops.
As a separate benchmark for “Writing the Constraint Down as a Sentence”, see Eurofound working-time research. Keep the source rule, operational interpretation and scheduling decision distinct.
The four tests
A usable constraint sentence states what, for whom, when, and with what exception. Miss any of the four and the sentence will be interpreted differently by two people in the same room.
- What is required, precisely enough to check.
- For whom: everybody, one role, one person, a defined group.
- When: always, during an activity, at certain hours, in certain conditions.
- What happens if it cannot be met, and who decides.
Most informal constraints fail three of the four, which is why discussions about them circle.
What: the thing being required
Precisely. Not "enough staff" but a number or a composition. Not "supervision" but presence, proximity or availability. Not "cover" but which task has to be coverable.
Vagueness in this field is usually deliberate, in the sense that it preserves everyone's own version. Removing it is uncomfortable and productive.
For whom: the population
Everybody, one role, one person, or a defined group. Constraints routinely get applied more widely than they were meant to, and the widening happens in exactly this field.
Writing "for the two staff holding the authorisation" rather than "for the team" has, on its own, released several hundred shifts in organisations that have done this exercise.
When: the condition
Always, during an activity, at certain hours, in certain conditions. This is the field that documents contain and practice loses, as a requirement tied to a process becomes a requirement tied to a shift.
A constraint with no condition stated is an always, and almost nothing is really an always.
The exception: what happens if it cannot be met
A constraint with no stated exception is one that will be breached silently at some point, because a service under pressure does not stop.
Writing the exception down — who decides, what is recorded, what happens afterwards — is both more honest and considerably safer than the alternative, which is an undocumented decision at six in the morning.
A worked example
Before: "There always has to be someone trained on the machine."
After: "At least one person authorised on the autoclave must be on site whenever it is running. If none is available, the machine does not run that shift and the duty manager records the decision."
Same constraint. The second can be checked, priced, trained against and argued with. The first cannot.
Who should write it
The person who enforces it, checked by the person it constrains. Two drafts, five minutes each, and the differences between them are the substance.
Where the two versions disagree, that disagreement has been live for years and has been resolved weekly by whoever was in the room. Seeing it written is often the first time anybody realises it existed.
The length rule
One sentence, two at most, no sub-clauses that start with "unless, in cases where". If it cannot be written that short, it is probably two constraints.
Splitting them is almost always right. Compound constraints hide the cheap half behind the expensive one and ensure neither gets examined.
What this makes possible
Everything else in this section. A sentence can be sourced, priced, tested on one shift and measured afterwards. A vague understanding can only be defended or resented.
The conversion costs ten minutes per constraint and it is the step that turns a register from a list of grievances into a working document.
The sentence that cannot be written
Occasionally nobody can produce one, because the constraint is a feeling about risk rather than a rule: something that has always been avoided without anybody being able to say what would happen.
That is a finding, not a failure. Record it as an unwritten caution with whoever holds it named, and treat it as a prompt to ask somebody qualified rather than as a line to be deleted by whoever is building the rota this week.
Where to keep the sentences
In the register, in the order the shifts occur rather than by category. People read a rota chronologically and will look for the constraint on the shift they are building.
A register sorted by type is tidier and gets consulted less, which is the only measure that matters for a document whose entire purpose is to be looked at while somebody is working.
What to do with the old wording
Keep it, briefly, in brackets. People recognise the old phrasing and will look for it, and a register that silently replaces familiar language reads as somebody else's document.
"No lone working in the plaster room" alongside the precise version costs one line and buys the register its legitimacy with the people who have to live by it.