The Constraint Nobody Can Name
What to do with a rule everybody follows and nobody can source, why it is the most common kind, and the single question that usually resolves it.
Every rota has at least one rule that everybody follows and nobody can source. Ask why the late shift starts at 13:45 and you get four different answers, none of them documentary, all of them delivered with complete confidence.
The constraint in “The Constraint Nobody Can Name” becomes useful only when its source, cost and effect on coverage are visible. A team considering Monitask for task completion rate for task completion rate can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
That is not carelessness. It is what happens to a reasonable decision after three managers, two reorganisations and a system migration: the decision survives, the reason does not, and the rule hardens because following it is cheaper than asking about it.
The assumptions behind “The Constraint Nobody Can Name” can also be checked against Ontario hours-of-work guidance. Record what applies locally and what requires qualified advice.
How to recognise one
The signature is the confident vague answer. "That's the agreement." "It's always been like that." "The union wouldn't wear it." "Health and safety." Each of those may point at something real, and none of them is the thing itself.
The second signature is that different people give different reasons for the same rule, and nobody notices the disagreement because the rule itself is not in dispute.
The question that resolves most of them
One sentence, asked of the longest-serving person in the department: what would happen if we did it the other way next Tuesday?
The answers divide cleanly. Either somebody can describe a specific consequence — a document breached, a person affected, a service that would not be covered — or the answer is a shrug, and the constraint has just been downgraded in front of you.
Where to look before asking anybody
Four places, in order of how often they hold the answer:
- The contract and any variation letters for the people concerned.
- Risk assessments and method statements for the area.
- The minutes of whatever committee changed the pattern last.
- The configuration of the scheduling system, which frequently encodes a rule nobody remembers setting.
The fourth is the one people forget. A system can hold a constraint as firmly as a document, and it will apply it silently, which is worse.
When nobody can name it and it is still right
Unsourced does not mean wrong. Plenty of unwritten constraints encode real operational learning: a handover that needs twenty minutes, a round that cannot start before the pharmacy opens, a machine that needs a second person while it warms up.
The work is not to delete them. It is to write them down, with whatever reason can be reconstructed and a date, so the next manager inherits a constraint with a reason attached rather than an instruction with none.
When it turns out to be a person
A common ending: the rule exists because one person arranged their life around it years ago, and the arrangement quietly became policy for everybody.
That needs handling carefully and honestly. The individual arrangement may be perfectly legitimate and worth keeping; applying it to a whole team because nobody separated the two is a different thing, and the separation is usually welcomed by the person themselves.
The cost of leaving them alone
An unnamed constraint cannot be weighed against anything, so it wins every argument by default. It also cannot be explained to a new starter, which means it gets transmitted as folklore and acquires reasons that were never true.
Over a few years an organisation accumulates enough of these to make its own rota look impossible, and the impossibility is real in the sense that nobody can see past it.
Writing one down properly
Three lines are enough: what the rule is, the best available account of where it came from, and the name and date of whoever last confirmed it. Uncertainty gets recorded as uncertainty.
"Reason not established; confirmed as current practice by the department manager in March" is a perfectly good entry. It is honest, it is checkable, and it stops the rule being quoted as though it had a source.
What changes once they are named
The rota stops being a fixed object and becomes a set of decisions with owners. That sounds abstract; in practice it means a manager can say which three things would have to change for the pattern to improve, and name who would have to agree to each.
That is the whole difference between a rota that cannot be improved and one that nobody has tried to improve, and it is reached by writing down the rules nobody can source.
The one that survives every review
There is usually one rule that stays unnamed after all of this: everyone believes it, nobody owns it, and no document anywhere mentions it.
Record it as exactly that and give it a review date. A constraint that has survived an honest attempt to source it is worth keeping on probation rather than deleting, and the record stops the next review starting from nothing.