Exit Without Friction: Preparing a Supplier Departure Dossier While Relations Are Calm

A supplier exit is a project, not a cancellation

Most supplier exits are planned in the wrong order. Notice is served, access is withdrawn, and only then does someone ask where the data lives or who owns the integration. The result is avoidable friction: delayed migration, duplicated work, unexpected invoices and a team that cannot prove what was handed over.

The remedy is a one-page supplier departure dossier, completed while the relationship is still calm. It is not a sign of distrust. It is a continuity document that allows a UK team to leave cleanly, or to be ready if the supplier exits first. Complete it at renewal, review it annually and update it when the service changes.

The one-page exit file

Keep the dossier to a single page plus attachments. A page that is read is more useful than a manual that is filed. Use six fields.

1. Commercial baseline

Record the contracting entity, contract reference, start and end dates, renewal mechanism, notice period and notice method. Note any termination triggers, minimum terms, early termination fees and service credits. Identify who inside the organisation can authorise notice. If the contract is held by a parent company or procured through a framework, say so.

2. Data and records

List the data the supplier holds or processes, including client records, operational data, backups, logs and derived reports. State the required export format, the retrieval route and the deadline for receiving it. Record whether deletion is required after exit and what evidence the supplier will provide. For personal data, note the processing role and any UK GDPR obligations that need advice. The dossier is not a legal opinion; it is a prompt to obtain one.

3. Access and credentials

Inventory every route into your systems and every route the supplier uses. Include admin accounts, single sign-on connections, API keys, integrations, domains, DNS records, security certificates, shared mailboxes and payment mandates. Record who removes each item, when and how confirmation will be obtained. Access removal should follow handover, not precede it, unless security requires otherwise.

4. Handover responsibilities

Name the responsible person on both sides. Define the artefacts to be handed over: documentation, configuration, open tickets, client handover notes, outstanding deliverables and knowledge-transfer sessions. Set acceptance criteria. Handover complete should mean something specific, such as a successful test export, a signed checklist or a working parallel run.

5. Exit costs

Estimate the full cost of leaving, not just the notice fee. Include early termination charges, data extraction, migration support, parallel running, hardware return, professional services, internal time and contingency. Record which costs are fixed, which are negotiable and which depend on timing. An exit that is affordable only in theory is not a plan.

6. Communication and escalation

Identify the internal approver, the supplier contact, procurement or legal support, and the communication route for staff and clients. Note any service continuity risks during transition. If the supplier provides a critical service, set a fallback arrangement before notice is served.

Notice periods reward preparation

Notice periods are usually missed for mundane reasons: the renewal date sits in a shared inbox, the contract is held by someone who has left, or the notice method requires a recorded delivery letter rather than an email. The dossier should state the date by which notice must be served, the person responsible and the evidence that will be retained. Put a diary reminder before the deadline, not on it.

Keep the file alive

Assign an owner. Review the dossier at each renewal and after any material change in scope, price or service. Store it with the contract and the supplier contact record. When a new supplier is onboarded, start the next dossier at the same time. The calm moment to prepare an exit is the day the service begins.

Common failure modes

The recurring failures are predictable. Data is available only in a proprietary format. Access is removed before the final export is tested. The supplier's handover obligation is described in vague terms. Exit costs are discovered after the budget is set. Notice is served late because nobody owned the renewal date. A one-page dossier will not eliminate every risk, but it makes each one visible early enough to manage.

For UK organisations, a clean supplier exit is mostly a matter of records. The dossier gives the team a shared view of what must be recovered, removed, handed over and paid. That is a more dependable position than relying on goodwill when the relationship has already changed.