The departure drill: proving you can leave a critical IT supplier

UK organisations tend to invest heavily in the beginning of an IT relationship. Contracts are negotiated, service levels are defined and transition plans are signed off with care. The end of that relationship receives far less attention. Exit clauses sit unread in schedules, data extraction is assumed to be straightforward, and the practical question of how the organisation would actually leave a critical supplier is rarely tested until a dispute, a merger or a change of strategy forces the issue.

That is a governance gap. An exit route that has never been walked is not a plan; it is a hope. A short, structured rehearsal — a departure drill — can convert that hope into evidence. It does not require a live dispute or a full procurement exercise. It requires ninety minutes, the right people in a room, and a willingness to ask uncomfortable questions before they become urgent.

Why a rehearsal beats a clause

Contracts describe rights and obligations. They do not demonstrate capability. A clause may entitle an organisation to extract its data within thirty days, but that entitlement says nothing about whether the data will arrive in a usable format, whether historical records will be complete, or whether the supplier’s own subcontractors will cooperate. Similarly, a service continuity schedule may promise transition assistance, but it cannot guarantee that the departing supplier’s staff will document what they know before they leave.

Rehearsing the exit tests the difference between what is written and what is workable. It also produces a record. For boards and audit committees, a documented rehearsal is stronger assurance than a statement that exit arrangements are “in hand”. It shows that finance, legal and IT have collectively examined the commercial, operational and evidential consequences of leaving — and that gaps have been identified while there is still time to close them.

Setting the room for ninety minutes

The drill works best as a tabletop exercise. Invite a small group: a senior IT service owner, a finance lead who understands the cost base, a legal or contracts specialist, and a business representative who depends on the service. A chair who is not the supplier relationship owner should run the session, so that defensiveness does not shape the conclusions.

Before the meeting, choose one critical supplier. Not the most difficult relationship, but one whose failure or departure would matter. Gather the contract, the service descriptions, the data map, the current spend and any transition or exit plan that already exists. The purpose is not to review the documents page by page, but to use them as prompts for a structured conversation.

Set the scenario plainly: the organisation has decided to leave, or the supplier has given notice. The clock starts now. What happens next?

Four tests that expose the truth

Data extraction

Ask the group to describe exactly how the organisation’s data would be identified, extracted and transferred. Who holds the authoritative copy? What formats are available? Are there historical records, attachments or audit trails that sit outside the main system? If the supplier hosts data across multiple platforms or uses subcontractors, can the organisation obtain a complete extract without relying on the supplier’s goodwill?

The test is not whether the contract permits extraction. It is whether the organisation could reconstruct its own records if the supplier became uncooperative or insolvent. If the answer depends on a single contact or an undocumented process, that is a finding.

Service continuity

Next, examine the operational bridge. Which services would stop, and on what day? What interim arrangements exist, and who would invoke them? If the supplier provides a managed service, are there shared dependencies — identity management, network connectivity, security monitoring — that would also be affected?

A useful discipline is to map the first thirty days hour by hour. The exercise usually reveals that continuity depends on knowledge held by individuals rather than on documented procedures. That is a risk in any exit, and it is one that can be mitigated long before a departure occurs.

Knowledge transfer

Knowledge transfer is the most frequently promised and least frequently evidenced part of an exit. Ask what documentation exists today, not what the supplier has committed to produce later. Which processes are documented, which are tacit, and who would be available to explain them during a transition? If key staff have already left the supplier, what has been lost?

The rehearsal should produce a short list of knowledge assets that the organisation would need to receive, in what format and by when. That list becomes a practical checklist for the relationship owner, whether or not an exit is imminent.

Exit costs

The finance lead should test the cost of leaving, not just the cost of staying. Are there termination charges, transition fees, duplicate running costs during parallel operation, or recruitment costs for replacement skills? If the organisation would need to rebuild a capability in-house, what would that cost in the first year?

Exit costs are often underestimated because they are scattered across budgets. The drill should produce a single, indicative view — even a rough order of magnitude — so that the board can compare the cost of leaving with the cost of continuing. That comparison is central to any credible supplier strategy.

Turning the rehearsal into board evidence

A drill is only useful if it leaves a trace. The chair should record three things: the assumptions made, the gaps identified and the actions agreed. Assumptions matter because they show where the organisation is relying on supplier cooperation. Gaps matter because they become the agenda for contract negotiation or internal remediation. Actions matter because they turn discussion into accountability.

A concise exit readiness note — two pages at most — can then go to the board or audit committee. It should state which supplier was tested, what was found, what has been fixed and what remains exposed. It should not claim that the organisation is fully prepared; it should demonstrate that the organisation knows where it is not. That is the kind of evidence directors can interrogate, and it is more valuable than a generic assurance that exit arrangements are satisfactory.

The failure modes to watch

The most common failure is to treat the exercise as a contract review. The contract is an input, not the subject. Another is to invite only IT. Finance and legal see risks that IT may normalise, and the business representative tests whether the service matters as much as the organisation claims. A third is to let the supplier relationship owner dominate the conversation. The drill should be conducted as if the supplier were absent, because that is the condition it is designed to test.

Finally, avoid the temptation to rehearse only when a problem is already visible. The value of the drill lies in doing it early, when findings can be addressed quietly and when the organisation still has leverage. A departure drill conducted in calm conditions is a sign of mature governance, not disloyalty.

After the drill

The output of a ninety-minute session is rarely a complete exit plan. It is a map of where the plan would fail. That map should feed into the next contract renewal, the next service review and the next board assurance cycle. It should also prompt a simple question for every critical supplier: if we had to leave tomorrow, what would we wish we had done last year?

For UK organisations operating in an environment of continuous change, the ability to leave a supplier is part of the ability to manage one. Rehearsing the departure is not an admission that the relationship will fail. It is evidence that the organisation would survive if it did.