The Vendor You Could Leave: A 60-Day Supplier Exit Audit

Most UK organisations can list their critical suppliers. Far fewer can show how they would leave one without disrupting operations. The gap is not usually a lack of legal advice. It is a lack of operational preparation. Exit readiness sits alongside business continuity and change control: it is a control that proves the organisation could move if it had to.

The question behind the question

When a relationship is working, exit planning feels hypothetical. When it is not, it feels urgent. Risk accumulates in the space between those two states. The useful question is not whether you would leave a supplier, but whether you could. That question has a practical test: if notice were served on Monday, what would happen on Tuesday?

Why exit plans fail quietly

Exit plans fail for ordinary reasons. Contracts are negotiated for entry, not departure. Notice periods are missed because no one owns the calendar. Auto-renewal clauses roll the agreement forward while attention is elsewhere. Exit assistance is assumed to be included when it is chargeable. Data return is described in principle but not in format. Staff assigned to the service may transfer under TUPE, creating an HR workstream that was never costed. And switching cost is often underestimated because it appears as operational disruption rather than a procurement line.

None of these failures is dramatic on its own. Together they turn a manageable transition into a crisis.

Audit the clauses you would actually rely on

Start with the contract, but read it as an operator rather than a lawyer. Build a one-page clause register for each critical supplier. Capture notice periods and notice windows, termination rights, exit assistance and transition services, data and IP provisions, handover obligations, charges payable on exit, and any step-in or escrow arrangements.

Then test the clauses against reality. Does the notice window align with the budget cycle? Can exit assistance be delivered at the volume you would need? Does the data return clause specify formats, metadata and destruction certificates? Are there subprocessors or third-party dependencies that sit outside the main agreement? A clause that cannot be operated is not a control.

Data, IP and the operating model

Data recovery is rarely just a spreadsheet export. It includes master data, transaction history, attachments, metadata, integrations, configuration, documentation and credentials. It also includes the tacit knowledge held by the supplier's staff: how the service is scheduled, how exceptions are handled, which reports matter.

Check IP licences carefully. If the supplier hosts a platform you rely on, what rights do you retain on exit? If bespoke reports or automations were built for you, who owns them? If data is derived or enriched, can you take the derived outputs? UK GDPR obligations continue through transition, so retention, deletion and subject access need an owner, not an assumption.

Continuity and the real cost of switching

Every exit has a switching cost, and it is usually wider than the price difference between suppliers. Model it in ranges: migration effort, dual running, retraining, recruitment, temporary productivity loss, customer communications and management time. For each critical supplier, name an exit owner and a trigger. The trigger might be a service failure, a price event, a change of ownership or a strategic decision. Without a trigger, exit planning becomes a document that is never used.

Continuity should be tested, not asserted. A short data extraction test, a tabletop exercise or a walkthrough of the first two weeks of transition will expose more than a policy review.

A 60-day triage

Days 1 to 10: inventory critical suppliers and extract the clauses that govern exit. Days 11 to 25: map dependencies, data flows and TUPE exposure; assign an exit owner for each supplier. Days 26 to 40: test one data extraction and one continuity assumption; identify gaps in exit assistance. Days 41 to 55: build a switching cost range and a preferred exit option for each critical supplier. Days 56 to 60: sign off a one-page exit card, a live notice calendar and a review cadence.

The output should be short enough to use and specific enough to test.

What good looks like

Good exit readiness looks unremarkable. There is a current exit card for each critical supplier. Notice dates are in a calendar with an owner. Data extraction has been tested once. TUPE exposure has been flagged for HR. The board has accepted a switching cost range. The plan is reviewed annually and after any material change.

At Jenesys Associates, the test we apply is simple: can the organisation show its working? A supplier exit plan that has never been tested is a statement of intent, not a control. The aim is not to leave suppliers more often. It is to make the relationship more honest, the switching cost more visible and the operational risk more manageable.