The Departure Window: Governing a Notice Period as a Delivery Workstream
Photo by Photo by Amina Atar on Unsplash on Unsplash
Resignations are rarely a surprise in the aggregate and almost always a surprise in the specific. A delivery lead, a programme manager or a specialist with deep operational knowledge gives notice, and the organisation moves quickly into a familiar pattern: a farewell email, a handover document assembled in the final week and a quiet hope that the successor will absorb what matters. In practice, the notice period is a delivery window with a fixed end date. It deserves the same discipline as any other workstream on the plan.
For UK teams, the risk is not usually a dramatic collapse. It is a gradual loss of control at the points where judgement, relationships and decision rights sit with one person. The purpose of a notice-period protocol is to make those points visible while there is still time to transfer them.
Begin with a live dependency map, not a goodbye email
The first task is not to ask the departing person to write everything down. It is to establish what the delivery actually depends on them for. That means a short, evidence-based map of live dependencies: approvals they are expected to give, meetings they chair or steer, supplier relationships they hold, risks they are watching, informal escalations they absorb and decisions that have been deferred to their judgement.
A useful test is to ask what would stop if the person were unavailable tomorrow. The answers should be specific. A dependency described as “oversight of workstream three” is too vague to transfer. A dependency described as “approval of change requests above £25,000 before the steering committee” can be assigned, shadowed and tested.
This map should be owned by the line manager or delivery owner, not left to the departing individual to define alone. The person leaving may not see the full shape of their own influence, and they may reasonably wish to present a tidy picture. The organisation needs the operational picture.
Move decision rights explicitly
The most common handover failure is the transfer of knowledge without the transfer of authority. A successor may be briefed on a supplier dispute, understand the history and still be unable to resolve it because the formal right to approve, escalate or sign off has not moved. In UK governance structures, those rights are often embedded in terms of reference, delegated limits, board protocols or programme mandates. They do not transfer by osmosis.
A decision-rights log should accompany the dependency map. For each live decision, record who currently decides, who recommends, who must be consulted and who is informed. Then record the intended post-departure position. Where a formal change is required, it should be made during the notice period, not after the final day. Where a temporary delegation is needed, it should be documented and communicated to the suppliers, delivery teams and governance bodies that will encounter it.
This is not bureaucracy for its own sake. It prevents the successor from being nominally in post but practically unable to act. It also protects the departing person from being drawn back into decisions after they have left, which is unfair to them and unreliable for the delivery.
Rehearse the successor at the next governance gate
Shadowing is useful but insufficient. The real test is whether the successor can run the next governance gate without the departing person carrying the room. Identify a live gate that falls within the notice period: a steering committee, a stage review, a change board, a supplier performance meeting or a budget approval. Then arrange for the successor to prepare the papers, present the position, answer questions and make recommendations, with the departing person present only as an observer.
This rehearsal exposes gaps that a handover document cannot. It shows whether the successor understands the sensitivities, whether the data is genuinely accessible, whether the relationships are transferable and whether the governance body has confidence in the new arrangement. It also gives the departing person a dignified role: not rescuing the meeting, but confirming what has and has not been transferred.
The findings should be recorded as actions, not impressions. If the successor cannot answer a question about supplier commitments, that is a gap with an owner and a date. If the governance body still expects the departing person to sign off, that is a decision-rights issue to resolve before the final day.
Convert memory into plan entries
Handover notes have a place, but they are not a control. The delivery plan, risk register, dependency log and decision log are the records that survive. During the notice period, every material item that the departing person holds should be moved into one of those records with an owner, a date and a clear next action.
This is where many teams discover that the plan was less complete than it appeared. Items that were managed conversationally, held in a personal inbox or resolved through informal escalation may never have entered the formal record. The notice period is the last realistic opportunity to bring them in. The test is simple: if the item is not in a shared record with an owner who is staying, it has not been handed over.
The line manager should review this conversion weekly. The question is not whether the departing person has been helpful. It is whether the delivery has genuinely changed state: what was once dependent on one person is now dependent on a documented arrangement that others can operate.
Keep a weekly cadence and close with evidence
A notice period can be short, particularly for senior roles where gardening leave may apply. A weekly cadence keeps the work moving: week one for the dependency map and decision-rights log, week two for shadowing and record conversion, week three for the governance-gate rehearsal, and the final week for verification and communication. For longer notice periods, the same rhythm applies with more testing time.
At the end, the closure should be evidenced rather than assured. A signed handover checklist, a confirmed decision-rights position, a tested governance gate and a verified set of plan entries give the organisation something firmer than a farewell meeting. The departing person leaves with a clear boundary, the successor starts with a workable mandate and the delivery avoids the slow discovery of gaps that only becomes apparent weeks later.
A resignation is a disruption, but it need not be an uncontrolled one. Treated as a governed workstream, the notice period becomes what it should be: a managed transfer of authority, knowledge and live dependencies, completed while there is still time to test it.
