The Unofficial Timetable: Reconciling the Plan Teams Actually Work To
Photo: Foreign, Commonwealth & Development Office, CC BY 2.0, via Wikimedia Commons
The official schedule is approved, baselined and circulated. It is also, on many UK delivery programmes, no longer the plan that the team uses to decide what happens on a Tuesday morning. Somewhere between the programme office and the delivery floor, a second schedule has taken root: a spreadsheet maintained by a workstream lead, a whiteboard in a project room, or a pinned message thread that lists the real sequence of approvals and hand-offs. It is rarely presented as rebellion. More often it is a coping mechanism developed by people who need a plan they can trust.
As 2026 draws to a close, many organisations are entering a period of budget scrutiny and delivery reset. That makes the shadow plan more than an untidy curiosity. It is operational evidence about where the main plan has stopped describing reality.
The second schedule is usually a symptom
Shadow plans are often treated as a discipline problem. The assumption is that the team has failed to use the official plan properly, or that a workstream lead has gone rogue with a private spreadsheet. That reading is usually wrong, and it is rarely useful.
A second schedule tends to emerge when the main plan can no longer absorb the changes that delivery has already absorbed. A dependency disappears from the plan because it sits outside the programme boundary. An approval step takes three weeks rather than three days, but the baseline still assumes the original duration. A specialist resource is promised to two workstreams at once, and the clash is managed informally because the formal capacity model does not show it. None of these issues necessarily reflects bad intent. They reflect a plan that has become presentable rather than usable.
Once the official schedule loses credibility, people do what operational teams always do: they create a local control that works. The shadow plan is the result.
What the shadow plan reveals
A well-constructed shadow plan is a diagnostic instrument. It usually contains information that the main plan should hold but does not. Four patterns are common.
First, it shows the real dependency map. Teams know which approval, technical decision or third-party input actually gates their work, even when the formal plan records only a milestone date.
Second, it exposes approval latency. If the shadow plan includes waiting time for change boards, legal review or client sign-off, it is likely more honest than a baseline that treats those steps as instantaneous.
Third, it reveals capacity conflict. The informal schedule often marks the same person as unavailable on two workstreams in the same week. That is not a diary problem. It is a resourcing decision that has not been made.
Fourth, it captures informal commitments. A supplier agrees to turn something around in five days, a manager promises a review by Friday, or a client-side team accepts a hand-over date in a meeting. These commitments shape delivery even when they never reach the change log.
Read in that light, the shadow plan is not a rival to governance. It is a report from the operational edge.
The temptation to confiscate
The instinct in many programme offices is to tidy up. The private spreadsheet is banned, the whiteboard is photographed and erased, and the team is instructed to use the official plan. This usually achieves the opposite of what is intended. The shadow plan does not disappear. It moves somewhere less visible, and the programme office loses the last reliable signal of what is actually happening.
A better response is reconciliation. The aim is not to defend the unofficial plan or to elevate it above the baseline. It is to bring its operational knowledge back into the main plan without punishing the people who kept it.
A reconciliation protocol
A practical reconciliation can be run over two weeks, with a light touch and a clear rule: no blame for maintaining a local plan. The purpose is to improve the main plan, not to conduct an audit of individual behaviour.
-
Declare a reconciliation window. State that the programme wants to understand where the official plan and operational reality have diverged. Make clear that the exercise is about schedule quality, not personal performance.
-
Collect the artefacts. Ask workstream leads to share whatever they use to manage their own commitments: spreadsheets, extracts, whiteboard photographs or lists of known dependencies. Do not require a standard format. The variation is part of the evidence.
-
Compare at the level that matters. Do not begin with a line-by-line comparison of tasks. Compare milestones, dependencies, approval steps, resource commitments and assumed durations. These are the points where plans usually fail.
-
Triage the variances. Group differences into four categories: missing dependencies, unrealistic durations, unrecorded decisions or approvals, and capacity conflicts. Each category points to a different governance fix.
-
Assign owners and dates. Every variance should have an owner in the main plan. If a dependency is real but sits outside the programme, it should still be recorded with an owner and an escalation route.
-
Update the baseline with a change log. Reconcile the main plan, record what changed and why, and publish the revised version. The change log matters because it shows that the plan is capable of learning.
-
Set a review rhythm. A monthly dependency and assumption review is usually enough to keep the main plan from drifting away from operational reality again.
Making the main plan worth using
Reconciliation only works if the main plan becomes more useful than the shadow plan. That means the official schedule must show the things teams actually manage: decision dates, approval waiting time, named dependencies and honest capacity. It must also respond quickly enough to be worth updating. A plan that takes three weeks to change will be bypassed within three days.
Status reporting should be rebuilt around decisions rather than colour. The question is not whether a workstream is green, but which decisions are outstanding, which dependencies are at risk and what the programme is doing about them.
A shadow plan is not a sign that a team has stopped cooperating. It is a sign that the team still cares enough about delivery to keep a workable schedule. The governance task is to make the official plan worthy of that effort, and to bring the operational knowledge back into the light before it becomes a risk that nobody recorded.