The Notice Is Not the Starting Gun: Exit Readiness as a Standing Control

A termination notice is a poor moment to discover that the exit provisions were never designed to be used. Whether the trigger is expiry, convenience, poor performance or supplier failure, the contracting authority’s ability to preserve services, recover data and transfer know-how depends on preparations made long before the notice is drafted. Exit readiness is therefore not a procurement afterthought; it is a governance control that should be visible to contract managers, legal teams and the board.

Exit risk is a standing risk

Public contracts rarely end neatly. They expire while services are still running, terminate in disputed circumstances or end because a supplier’s financial position has changed. The current procurement regime has sharpened attention on contract management, but no statutory framework can substitute for contractual exit mechanics that actually work. A contract can be lawful, well-drafted for award and still unexitable in practice.

The practical question for a contracting authority is not whether an exit clause exists. It is whether the clause can be operated at pace, at a known cost and without unacceptable disruption. That question should be asked during mobilisation, at each contract review and before any major variation, not only when a notice is being considered.

Four questions that expose weak exit provisions

Can we require assistance after termination?

Termination assistance is often expressed in general terms: the supplier will provide reasonable assistance to facilitate transition. That formulation gives little comfort when a replacement provider needs access to systems, records, personnel and operational know-how within a short window. Authorities should test whether the contract identifies the services to be provided, the recipient of the assistance, the duration, the standard of performance, the payment mechanism and the consequences of failure.

A workable exit schedule will usually address named roles, response times, reporting, access to premises and systems, cooperation with incoming providers and the treatment of subcontractors. It should also settle whether assistance is provided at agreed rates, at cost or as part of the contract price. Leaving cost to later negotiation invites delay and dispute.

Can we recover and control data?

Data return is not simply a matter of asking for a download. Authorities need to know what data is held, in what format it can be extracted, how it will be transferred securely, what will be deleted and what must be retained. The contract should distinguish between operational data, personal data, records subject to information requests and material that the authority needs for continuity or audit.

References to UK GDPR and the Data Protection Act 2018 are necessary but not sufficient. The exit schedule should include a data map, transfer formats, deletion certification, retention periods and arrangements for handling information requests during and after transition. Where public records are involved, retention obligations should be considered alongside the authority’s records management policies.

Do we know what assets we rely on?

Asset registers are frequently incomplete, out of date or held by the supplier rather than the authority. That is a material exit risk. The authority should be able to identify land, equipment, software licences, interfaces, shared platforms, records, intellectual property and anything else on which service continuity depends. It should also know which assets are owned, leased, licensed or shared with third parties.

A static register is not enough. Exit planning should test whether shared assets can be decoupled, whether access rights survive termination, whether third-party consents are required and whether the authority can step in or procure replacements at short notice. Where the supplier controls a critical interface, the contract should provide for continued access during transition.

Can we capture knowledge before it walks?

Knowledge transfer is often the weakest part of an exit plan because it depends on people rather than clauses. The authority should identify critical roles, undocumented processes, configuration details, runbooks, supplier contacts and operational history. The exit schedule should require named individuals to support handover, produce documentation, deliver training and participate in shadowing or exit interviews.

Knowledge transfer should begin before the final weeks of a contract. If the authority waits until a notice is served, key staff may already be redeploying or leaving. Contract managers should test whether the supplier can demonstrate a handover plan, whether the plan has been rehearsed and whether the authority has the internal capacity to receive the knowledge.

Continuity sits across every exit workstream

Exit readiness is not only about recovering from a supplier. It is about maintaining services while the authority changes provider, insources, disaggregates a contract or brings a disputed arrangement to an end. Continuity planning should therefore cover fallback arrangements, service stabilisation, direct agreements with critical subcontractors, step-in rights and communication with service users.

The authority should also consider its own dependencies. If a small internal team has relied on the supplier for specialist capability, the exit plan needs to address recruitment, training or interim support. A transition that preserves the contract but loses the capability to manage it is not a successful exit.

A legal checklist before the notice lands

Contract managers and legal teams should use a structured review to test exit readiness. The following checklist is a starting point:

• Confirm the trigger map. Identify every route to termination or expiry, including convenience, default, insolvency, change of control and end of term. Check notice periods, content requirements and who may issue a notice.
• Appoint an exit lead. Give one person visible responsibility for exit planning, with legal, finance, data protection, ICT and service leads contributing.
• Test termination assistance. Walk through the clause with the service team. Identify gaps in scope, duration, cost, access, cooperation and remedies.
• Validate the data schedule. Confirm data sets, formats, transfer methods, deletion certification, retention requirements and records management responsibilities.
• Reconcile the asset register. Verify ownership, access rights, shared dependencies, third-party consents and decoupling costs.
• Build a knowledge transfer plan. Name critical roles, documents, training needs and handover milestones. Test whether the supplier can deliver them.
• Stress-test continuity. Model a short-notice exit and identify the authority’s fallback arrangements, interim resources and communication needs.
• Map the supply chain. Identify critical subcontractors, direct agreements, consents and any dependencies that could delay transition.
• Record the assurance. Report exit readiness to the appropriate governance forum and keep the evidence with the contract file.

Making exit readiness auditable

Exit readiness should be reviewed periodically and treated as part of contract performance management. A simple assurance question can be put to each contract review: if notice were served tomorrow, what would we be able to require, recover and transfer, and what would we have to negotiate? The answer should be recorded, with actions assigned and deadlines set.

Legal teams can support this by maintaining standard exit schedules, reviewing departures from them and advising on remedies where cooperation is withheld. Contract managers can support it by keeping asset registers, data maps and key-person lists current. Boards and audit committees can support it by asking for assurance that critical contracts are not merely performing, but exitable.

The notice is not the starting gun. By the time it is issued, the authority should already know how services will continue, how data will return and how knowledge will transfer. Exit readiness is a governance discipline, and it is strongest when it is practised before it is needed.