Who Has to Agree
How to work out whose agreement a rota change actually needs, the four parties usually involved, and why asking the wrong one first is the commonest way a change fails.
Most attempted rota changes fail at the agreement stage, not the analysis stage. The arithmetic was fine; somebody who had to say yes was asked late, asked wrongly, or not asked at all.
The constraint in “Who Has to Agree” becomes useful only when its source, cost and effect on coverage are visible. A team considering consult the official platform details for ways to track work hours can add timely work and attendance context, with transparent settings, limited access and a clear correction route.
Working out who has to agree takes fifteen minutes and is the part of the work most often skipped, because it is the least interesting.
Additional context for “Who Has to Agree” is available from WHO occupational-health resources. Use external guidance to prompt a specific validation check rather than replace local review.
The four parties
The people affected. Whoever owns the constraint — the author of the rule or the holder of the document. Whoever owns the money if the change costs anything. And whoever is accountable for the risk the constraint was managing.
- The people affected.
- Whoever owns the constraint: the author of the rule or the holder of the document.
- Whoever owns the money, if the change costs anything.
- Whoever is accountable for the risk the constraint was managing.
Different changes involve different subsets, and a change can be blocked by any one of them.
Finding the constraint's owner
The author column on the register, which is why it exists. Where the author has gone, the owner is whoever currently holds that role or that document.
An internal standard has an owner even if nobody has thought about it for years, and the owner will usually engage readily, because nobody has asked them about it in all that time.
The risk holder, who is often forgotten
Where a constraint manages a risk — safety, clinical, financial, regulatory — somebody is accountable for it, and they are frequently not in the scheduling conversation at all.
Asking them early converts a potential veto into a contribution. Asking them after the change is announced produces the veto, correctly, and also damages the credibility of the whole exercise.
The order of asking
Constraint owner first, to establish whether the rule can move at all. Risk holder second, to establish on what conditions. Money third, if needed. People affected last, with a concrete proposal rather than a consultation about possibilities.
Reversing the last two is the classic error: consulting people on an option that is later blocked for a reason nobody checked.
What to ask for
A decision on a specific proposal, with the price, the trial period and the measurement attached. Not permission to explore.
"Can we try this for one cycle and look at these three numbers" is answerable in a meeting. "Can we look at the weekend rules" is not, and it will be deferred indefinitely while appearing to be supported.
The people affected
Where a change touches contracted terms, patterns or notice, what process is required differs by jurisdiction and by agreement, and is a question for somebody qualified in the place concerned.
What is universal: people respond better to a proposal with a reason, a trial length and a commitment to review than to a change presented as settled. That is true even where no consultation is required.
Representatives
Where there is a union or staff forum, involving them early is practically useful whatever the formal position, because they know which arrangements people actually rely on.
They also know which of the unsourced constraints were agreed in some forgotten forum, and that information exists almost nowhere else.
The agreement nobody records
Having got a yes, write down who gave it, when and to what exactly. This sounds bureaucratic and it prevents the most common unwinding: a change agreed in a meeting, implemented three months later, and challenged by somebody who understood it differently.
Three lines in the register, at the time, and the change survives its first difficult week.
When somebody says no
Record that too, with the reason. A refusal with a reason is information: it tells you what would have to be different for the answer to change, and sometimes that is achievable.
A refusal with no reason recorded is simply the end of the matter, and the same proposal will be reinvented in two years by somebody who does not know it was tried.
The party who only appears later
Payroll, almost always. A change to shift times, breaks or premium boundaries has a payroll consequence, and payroll finds out when the first wrong payslip is queried.
Ten minutes with whoever runs the pay cycle, before the change, prevents the single most reliable source of damage to a rota change: people being paid incorrectly in the first month of something they were already uncertain about.
What this is really about
Not process for its own sake. Rota changes touch people's lives, money and risk at the same time, and the four parties exist because each of those has somebody responsible for it.
Identifying them is fifteen minutes of work that determines whether the afternoon spent pricing the constraint produces anything at all.