The Long Goodbye: Drafting Post-Termination Services That Withstand the Break-Up

Termination is usually drafted as an event: a notice, a breach, an insolvency, a change of control. In practice, it is a process. The commercial relationship does not stop cleanly on the day the notice expires. Staff still need access, data still needs to move, invoices still need to be settled and confidential information still needs to be protected. When those wind-down obligations are left to a short survival clause, the parties discover after the break-up that they disagree about what "reasonable assistance" means, how quickly data must be deleted and who bears the cost of keeping the lights on.

The disputes that follow are rarely about the termination itself. They are about the long goodbye. A well-drafted exit regime should therefore be negotiated with the same care as the commencement terms, not treated as boilerplate to be tidied up at the end of a negotiation.

Transition assistance: from aspiration to service catalogue

Most contracts contain an obligation to provide "reasonable assistance" on termination. That phrase is a recipe for disagreement. It does not identify what assistance is required, over what period, at what cost or to what standard. A supplier may regard a single handover meeting as sufficient; a customer may expect months of parallel running, knowledge transfer and technical support.

The drafting fix is to turn assistance into a defined service. Specify the deliverables—for example, export of configuration data, transfer of administrative credentials, attendance at handover meetings, provision of interface documentation and support for a defined parallel-running period. Set a standard, such as reasonable skill and care, and link it to a timetable. Address cost expressly: whether assistance is included in the fees, charged at agreed day rates or capped. If the customer's cooperation is a precondition, say so, so that delay cannot later be attributed solely to the supplier. Finally, provide an escalation route for disputed assistance requests, rather than leaving the parties to argue after the final invoice has been issued.

Data return and deletion: making the obligation verifiable

Data is often the most valuable asset affected by termination. UK GDPR and the Data Protection Act 2018 impose obligations on controllers and processors, but contractual drafting must translate those obligations into an operational sequence. A clause that simply requires the supplier to "return or delete all data" is unlikely to be sufficient where data is held across production systems, archives, backups and third-party sub-processors.

The exit schedule should identify the data, the format and the method of return. Machine-readable formats and agreed transfer mechanisms reduce the scope for delay. Deletion should be addressed separately from return, with a defined period, a certificate of destruction and a clear position on backups and disaster-recovery copies. Where retention is required by law or for a live dispute, the contract should carve out that retention and impose conditions on continued processing. Verification rights—such as a short audit or written attestation—are useful where the customer needs assurance but does not want an open-ended inspection right. The aim is to avoid a post-termination argument in which the supplier says it has deleted the data and the customer has no way to test the claim.

Records retention: statutory duties and contractual limits

Termination does not suspend statutory record-keeping. Companies Act 2006 requirements, tax rules and limitation periods may require both parties to retain records for defined periods. The contract should acknowledge those obligations rather than purport to require immediate destruction of everything. A sensible clause distinguishes between operational data, which can be returned or deleted, and records that must be retained for legal, regulatory or accounting purposes.

For retained records, specify the categories, the permitted purposes, the security measures and the persons who may access them. If the supplier will hold records on the customer's behalf after termination, the contract should say for how long and at what cost. It should also address what happens if litigation or a regulatory enquiry begins during the retention period. A retention clause that is too broad may be unenforceable or commercially unacceptable; one that is too narrow may put the customer in breach of its own statutory duties.

Final invoicing and reconciliation: closing the account

The final invoice is a common flashpoint. Disputes arise over unused prepayments, service credits, accrued expenses, early-termination charges and the treatment of sums already paid. If the contract does not provide a reconciliation mechanism, the parties may find themselves arguing about the final account long after the services have ceased.

A final-account clause should set out how credits and debits are calculated, the period within which the supplier must issue its final invoice and the customer must raise queries, and the consequences of failing to do so. Deemed approval of undisputed amounts can bring certainty, provided it is coupled with a genuine opportunity to dispute. Set-off rights should be addressed expressly, particularly where the customer alleges a separate breach. Where transition assistance is chargeable, the final account should distinguish between included services and additional work. The objective is not to favour either party but to ensure that the last payment is not the first point at which the commercial consequences of termination are examined.

Confidentiality and continuing obligations: duration and scope

Survival clauses often lump confidentiality, intellectual property, liability and governing law into a single sentence. That is rarely satisfactory. Confidentiality obligations may need to continue for different periods depending on the information. Trade secrets may require indefinite protection; commercial terms may need a shorter period. The contract should also address the return or destruction of confidential information, permitted disclosures to regulators and professional advisers, and the parties' public announcements.

Restrictive covenants should be reviewed at the same time. A non-solicitation or non-compete clause that is too broad may be unenforceable; one that is too narrow may fail to protect legitimate interests. The point is not to add more restrictions but to align duration, scope and geography with the legitimate interest being protected.

Designing the exit before it is needed

The most effective post-termination clauses are those negotiated while the parties still intend the relationship to succeed. They read as an operating manual for an orderly separation: who does what, by when, at what cost and with what evidence. That approach reduces the likelihood of a dispute and, where a dispute is unavoidable, gives the parties a framework for resolving it without derailing the exit itself. In UK commercial practice, the long goodbye deserves as much drafting attention as the first hello.