The Person Everyone Routes Around
Every team has someone the rota quietly works around, why that arrangement is a constraint nobody has recorded, and the three honest ways to resolve it.
Every team has at least one person the rota works around. They are never put on that shift, never paired with that colleague, never given that task, and nobody has ever written down why.
The constraint in “The Person Everyone Routes Around” becomes useful only when its source, cost and effect on coverage are visible. A team considering a structured route to 7 minute rule payroll for 7 minute rule payroll can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
It is a real constraint with real costs, it is carried in the head of whoever builds the rota, and it is the single hardest entry to put on a constraint register.
As a separate benchmark for “The Person Everyone Routes Around”, see HR Open Standards resources. Keep the source rule, operational interpretation and scheduling decision distinct.
The three reasons underneath
A capability gap nobody has addressed. A health or personal matter somebody once mentioned informally. Or a working relationship that went wrong years ago and has been managed by separation ever since.
- A capability gap nobody has addressed, and the rota has been compensating for it.
- A health or personal matter mentioned informally and never recorded.
- A working relationship that went wrong and has been managed by separation since.
The three need completely different handling, and the first step is knowing which one is in front of you — which the person building the rota usually does.
What it costs
More than its size suggests, because every workaround removes options from the pattern and the workarounds compound.
It also costs the person. Being routed around is noticed, it is demoralising, and it is frequently misread by the individual as something worse than whatever the actual reason is.
The capability version
The easiest of the three and the most commonly misfiled as one of the others. Somebody cannot do a task, nobody has said so, and the rota has been quietly compensating for two years.
This is a training conversation that should have happened long ago. It is uncomfortable for about ten minutes and it resolves a constraint permanently, which the workaround never will.
The health or personal version
Where the reason relates to somebody's health or circumstances, the informal arrangement is doing real good and the informality is the problem: it depends on one manager's memory and it is invisible to everybody else.
Converting it into a recorded arrangement — the restriction, not the reason, with a review date — protects the person better than the informal version does. What may be recorded, and where, is a question for somebody qualified in the place concerned.
The relationship version
The hardest, and the one most likely to be managed by separation indefinitely. Two people cannot work together, the rota keeps them apart, and nobody has addressed it since.
Separation is a legitimate short-term measure and a poor permanent one: it constrains the rota every week, it is visible to the whole team, and it tends to be read as the organisation taking a side.
Why nobody raises any of it
Because raising it looks like a complaint about a colleague, and the person who could raise it most precisely is the one who has been quietly managing it. Their reward for raising it is a difficult conversation they did not have to have.
That is an organisational design problem rather than a personal failing, and the fix is a routine occasion for the conversation rather than courage.
The occasion that works
A constraint register review where every unexplained workaround in the pattern is listed as a line: "shift X never assigned to person Y, reason not recorded".
Written like that, neutrally, alongside twenty other lines about rooms and training, it becomes a scheduling question rather than an accusation, and it gets handled.
The three honest endings
Address it, with training, a recorded arrangement or a conversation between the people involved. Record it, as a constraint with a review date, if it genuinely needs to persist. Or end it, where it turns out the reason expired years ago and nobody noticed.
The fourth ending — continuing to route around it silently — is the current state nearly everywhere, and it is the only one that gets worse with time.
The one line that survives you
The restriction in operational terms, its status, who knows about it, and a review date. Nothing about health, nothing about the relationship, nothing that belongs in a file.
One line on the register, and the line survives the manager who has been carrying it, which is the entire point of writing anything down.
The signal in the rota itself
These arrangements are visible in the pattern without anybody saying anything: one name never appears against one shift type over a year, or two names never appear on the same day.
Running that check across a published year takes a few minutes with a spreadsheet and produces a short list. The list is not an accusation; it is simply where the undocumented constraints are, and it is the easiest way to find them without asking anybody to volunteer an awkward subject.
What usually happens when it is raised
Less than anybody fears. Most of these resolve into either a training need nobody had named or an arrangement everybody is content to record properly.
The relationship version is the exception and it is also the one where silence is costing the most, both to the rota and to the two people involved.