The Last Page First: Reviewing Exit Terms Before a UK Consultancy Engagement

Most clients read a consultancy agreement from the front: scope, deliverables, timetable, fees. That is understandable. The opening pages describe the work the client wants and the adviser has promised. Yet the last few pages often determine what happens when the work stops early, changes shape or reaches an uncertain end. For UK businesses commissioning advisers in 2026, a short review of the exit terms before the first meeting can be more valuable than another round of scope refinement.

At Harman Dean, the practical view is simple: an engagement should be understood from both ends. The client should know not only what success looks like, but also what an orderly departure looks like. This is not a counsel of suspicion. It is a discipline of preparation. The aim is to avoid discovering awkward terms at the very point when time, money and goodwill are under pressure.

Why the ending deserves an early reading

An exit clause is not merely a legal safety net. It is a working instruction about how the relationship will be wound down if circumstances change. Those circumstances are rarely dramatic. A budget may be revised. A project sponsor may leave. A regulatory deadline may move. A smaller piece of work may prove more useful than the original brief. In each case, the client needs to know how to stop, pause or reshape the engagement without confusion.

Reading the exit terms early also improves the commissioning conversation. If the adviser knows that the client has considered notice periods and handover, the discussion tends to become more concrete. Vague assurances about flexibility are replaced by practical questions: how much notice is fair, what work will be completed by then, and what records will change hands.

Notice: length, triggers and practical effect

Notice periods deserve more attention than they usually receive. A thirty-day period may sound generous until it is measured against a monthly reporting cycle, a board meeting or a regulatory filing. A shorter period may appear decisive but leave insufficient time for a proper handover. The right question is not whether the notice period is long or short in the abstract, but whether it fits the rhythm of the work.

Clients should also check what triggers notice. Is termination possible for convenience, or only for cause? If cause is required, what counts as cause, and who decides? Are there escalation steps before termination? Does a dispute about fees suspend the client’s ability to give notice? These points are not merely legal. They affect the client’s room to manoeuvre when a project loses its sponsor or changes priority.

It is equally important to understand what notice does not do. Notice may end future work without cancelling fees already incurred. It may stop new tasks while leaving a final report outstanding. A calm review will separate the end of the instruction from the end of the financial relationship.

Money at the point of exit

Final fees are a common source of friction because the agreement may not distinguish clearly between work done, work committed and work merely planned. Before signing, the client should identify how outstanding fees will be calculated on termination. Are fees payable for time spent up to the notice date, for a fixed proportion of the project, or for costs already committed to subcontractors? Are expenses recoverable, and on what evidence? Are any mobilisation or early-termination charges payable?

A useful habit is to trace a hypothetical exit through the fee schedule. If the client gave notice at the end of month two, what would be due? Which invoices would already have been issued? Which costs would be unavoidable? The exercise need not be adversarial. It simply turns an abstract clause into a practical number. Where the answer is unclear, the client should ask for the position in writing before the engagement begins.

Data, documents and the return of working assets

The end of a consultancy project is also a data event. Client information may sit with the adviser, in shared folders, on laptops or in third-party systems. The agreement should say what happens to that material when the engagement ends. Will it be returned, deleted or retained? If retained, for how long and for what purpose? Does the adviser need to keep copies for professional records, insurance or regulatory reasons?

UK clients should consider these questions alongside their data protection duties. A short schedule can help: what information was provided, where it is held, who can access it, and how its return or deletion will be confirmed. The point is not to create bureaucracy but to prevent the quiet persistence of project files after the project has closed. The same discipline applies to working assets such as models, trackers, drafts and meeting notes. The client should know which of these will be handed over and in what format.

Handover: a deliverable, not a courtesy

Handover is often treated as a closing courtesy. In practice, it should be a defined obligation. If the engagement ends, who will explain the adviser’s work to the client team or a successor? What will be included in a handover pack? Will there be a final meeting, a written summary, a walkthrough of the model, or a list of open risks? The answer matters most when the adviser leaves earlier than planned.

A clear handover clause does not need to be elaborate. It should identify the minimum content of the handover, the person responsible for providing it, and the period within which it will be delivered. It should also say whether handover is conditional on payment. Clients may accept that final delivery follows settlement of undisputed invoices, but they should understand the sequence before they sign.

Transition support and the run-off period

Some engagements need more than a handover. They need a short period of transition support while the client team takes over. This might involve answering questions, attending a final board meeting or reviewing a first draft produced by someone else. The agreement should say whether such support is included, chargeable or excluded.

A run-off period is especially useful where the adviser holds specialist knowledge that is not easily documented. Even a modest arrangement, such as two hours of availability in the month after termination, can prevent a small exit from becoming a large disruption. The client should check whether any support is capped, how it is requested, and whether it survives the end of the main engagement.

A short pre-signature review

Before signing, a client can conduct a compact exit review by asking five questions. First, how would we give notice, and how much notice must we give? Second, what would we owe if we stopped at short notice? Third, what data and documents would come back to us, and in what form? Fourth, what handover would we receive, and when? Fifth, what transition support, if any, is included after the work ends?

These questions are best asked calmly, before the pressure of delivery. They signal that the client is serious about governance without suggesting distrust. A well-run adviser should welcome them. Clear answers make the engagement easier to manage and the ending easier to explain to colleagues, auditors or successors.

The calm advantage

The purpose of reading the last page first is not to plan an escape. It is to remove uncertainty from the relationship. A client who understands how an engagement ends is better placed to commit to it, to monitor it and, if necessary, to close it without recrimination. In UK consultancy work, where reputations and repeat relationships matter, that calm preparation is part of good commissioning. The beginning is the right time to understand the way out.