The Departure Pack: Planning a Clean Exit from UK Public Service Contracts

An exit file is a mobilisation document

Most contract discussions concentrate on the first ninety days. Mobilisation plans, service transition and staff arrangements take up the early meetings. Exit planning often waits until renewal. That is backwards. The best time to define how a contract will end is when the parties are still defining how it will begin. An exit file is not a sign of distrust. It is a sign that the contracting authority intends to remain in control of the service.

In CLI Ltd's public sector procurement work, the exit file is treated as a mobilisation document, not an end-of-contract chore. It should sit beside the contract schedule, the data protection schedule and the asset register. It should be owned by a named contract manager and reviewed at least annually. In 2026, with multi-supplier frameworks and tighter budgets, an untested exit position is a commercial risk.

What belongs in the exit file

The file need not be long. It must be complete enough for a new supplier, an insourced team or an interim provider to take over without relying on the outgoing supplier's goodwill.

Data return

Define what data the supplier holds, in what format, and how it will be returned or destroyed. Include service records, case notes, asset data, performance reports and any personal data. State the return window, the accepted formats and the deletion evidence. For public sector contracts, check the data protection schedule and retention duties before agreeing a destruction date.

Asset register

List the assets used to deliver the service: equipment, vehicles, software licences, keys, access cards, stock and records. Record ownership, location and condition. If the supplier owns an asset that the service depends on, the exit plan should say how the authority will obtain continuity or a replacement.

Knowledge transfer

Identify the roles, processes and local knowledge that must pass to the incoming provider. A knowledge transfer plan should name the people, the subjects, the format and the dates. It should include site-specific arrangements, escalation routes and any informal practices that keep the service running.

Notice sequencing

Set out the order of events after a notice of termination or non-renewal. Which notices must be served, by whom and to whom? When does the supplier stop taking new work? When does the incoming provider start shadowing? When are final reports due? A simple sequence prevents the last three months from becoming a dispute about dates.

Sign-off responsibilities

Name the people who will sign off data return, asset handover, knowledge transfer and final accounts. Include deputies. The exit plan should state what happens if a signatory is unavailable. Without named responsibilities, exit tasks drift.

The one-page exit template

A one-page template is enough to start. Use five headings and a named owner for each:

1. Data: records, format, return date, deletion evidence, owner.
2. Assets: register, condition, handover date, owner.
3. Knowledge: roles, subjects, sessions, acceptance method, owner.
4. Notices: trigger, sequence, dates, authority, owner.
5. Sign-off: names, deputies, acceptance criteria, escalation route.

Attach the template to the contract as a schedule. Add a review date. Require the supplier to update it every twelve months and at each contract change. A one-page plan that is reviewed is more useful than a fifty-page plan that is filed.

Questions to ask before signing in 2026

Ask the supplier to explain its last exit. What went well, what slipped and who signed off? Ask how it will return data in a usable format, not just a report. Ask which assets are essential to continuity and what happens if they are leased or subcontracted. Ask how knowledge transfer will be evidenced. Ask who in the supplier's organisation can serve a notice and who can accept a handover.

The contracting authority should also ask itself a harder question: could we run this service for six months without the incumbent? If the answer is no, the exit plan is not complete. The aim is not to make exit painless. It is to make exit possible without a panic renewal.

Avoiding lock-in and panic renewals

Lock-in rarely appears suddenly. It builds through unreturned data, undocumented processes and assets that the buyer cannot replace. By the time the renewal date arrives, the incumbent is the only realistic option. The exit file is the antidote because it makes the dependencies visible early.

Public sector buyers should treat exit readiness as part of value for money. A supplier that resists a reasonable exit plan is giving useful information about how it will behave at the end of the contract. A supplier that accepts one is not weakening its position; it is showing that it expects to be judged on delivery rather than on capture.

The exit file should be signed before the service starts. It should be reviewed when the service changes. It should be tested before the renewal decision, not after. That is the practical discipline for 2026.