The planning–operations handoff: who owns the plan once it’s live?

Leadership · ~6 minute read

The plan is finished — now the hard part

A planner can build a flawless forecast and a beautifully shaped roster, hand it over, and still watch it fail — not because the maths was wrong, but because nobody agreed what happens once the plan meets the operation. The handoff between planning and operations is where good plans quietly go to die: ops decides it knows better and reshuffles the schedule, or sticks rigidly to a roster that reality has overtaken, and a week later planning and operations are each pointing at the other’s decisions to explain a missed target. The technical work is only half the job; the governance around it is the half that decides whether any of it gets used.

The ownership question nobody answers out loud

The root problem is unclear decision rights. Planning owns the forecast and the schedule; operations owns the day and the outcome — and in the gap between those two ownerships sit a hundred small decisions that no one has been told who makes. Can a team leader move an agent off the planned activity to clear a queue? Can a site swap two shifts without telling planning? When the forecast and the floor disagree at 10am, whose call wins? Left undefined, these resolve themselves the unhealthy way: the operation overrides the plan silently because it’s closer to the action, planning loses visibility of what’s actually being run, and the “plan versus actual” analysis becomes meaningless because the plan stopped being the thing in force hours ago. The deviations aren’t the problem; the absence of an agreed way to make and record them is.

A governed handoff, not a silent override Planning forecast + schedule Change control who can move what Operations runs the day feedback loop: deviations logged and learned from The plan stays the plan — changes go through a gate and come back as learning.
A healthy handoff has a change-control gate and a feedback loop. Without them, the operation silently becomes the planner, and nobody can tell plan from actual.

Governing the handoff

Make the decision rights explicit and the changes visible. Agree a simple change-control protocol for the live roster — what kinds of changes operations can make freely, which need planning’s sign-off, and the notice each requires — so deviations are deliberate and recorded rather than silent. Write down a light RACI for the recurring decisions (who’s responsible for the intraday call, who’s consulted on a re-forecast, who’s accountable for the number) so the 10am disagreement has a pre-agreed answer. Build the feedback loop that closes it: log deviations and review them together, not to assign blame but to feed the next forecast and the next schedule — today’s override is often tomorrow’s legitimate planning assumption. And cultivate shared ownership of the outcome, because the moment it becomes “planning’s number” versus “ops’s reality,” the handoff is already broken. The plan only works if the two functions agree, in advance, how they’ll disagree.

Pair this with working with your planning team, the planning operating rhythm, and building planning credibility.