Closing Slides Are Not Capability: Putting Handover Back Into the Consultancy Contract

There is a peculiar asymmetry in the way UK firms buy consultancy. The entry is negotiated with care: scope, milestones, fees, payment terms, intellectual property, liability. The exit is often left to a closing slide and a general offer of support.

That imbalance is worth challenging. If an engagement is intended to leave the firm stronger, then the handover is not an administrative afterthought. It is part of the deliverable. Yet in many contracts it is the least specified element of all.

The contract is built for delivery, not transfer

Most statements of work describe what the consultancy will produce. They are less clear about what the client will be able to do afterwards. The assumption is that proximity will do the work: the internal team will sit in meetings, read the decks and absorb the method by osmosis.

In practice, absorption is uneven. The people who attend are not always the people who must operate the new process. The model is handed over as a spreadsheet with opaque assumptions. The decision log is incomplete. The external team leaves, and the firm discovers that it has acquired a set of recommendations rather than a repeatable capability.

This is not usually a failure of goodwill. It is a failure of design. Contracts shape behaviour, and most consultancy contracts are designed around delivery milestones rather than knowledge transfer.

What a handover clause should contain

A useful handover clause does not need to be lengthy, but it does need to be specific. Four elements matter most.

First, a named recipient. Not a role, not a department, not 'the project team'. A named individual, with a named deputy, who is accountable for receiving the knowledge and can demonstrate it afterwards. If the recipient changes, the clause should require the change to be recorded and the handover plan updated.

Second, defined artefacts. These should include the working model, not just the final report; the data dictionary; the assumptions register; the decision log; the risk register; the stakeholder map; and any proprietary tools or templates the firm is licensed to use. The test is simple: could a competent internal person use these artefacts without calling the consultancy?

Third, shadowing. A closing workshop is not shadowing. Shadowing means the internal recipient performs the task while the consultant observes and corrects. Reverse shadowing, where the consultant performs and the recipient challenges, is also useful. For substantive engagements, the clause should specify hours, timing and who attends.

Fourth, a 30-day support window. This is not an indefinite retainer. It is a defined period after final delivery during which the named consultant answers reasonable questions, reviews the first internal application and helps resolve defects in the handover materials. The clause should state the expected response time and the boundary between support and new work.

A simple test of whether handover happened

Closing slides are not capability. A more honest test is to remove the external team for a defined period and ask the recipient to operate the new process, model or governance routine without assistance. Can they explain the assumptions to a sceptical colleague? Can they update the model when a variable changes? Can they answer a board question about the recommendation without referring to the consultancy's deck? Can they identify the risks that would cause the approach to fail?

If the answer is no, the handover has not happened. It has been performed.

This test is uncomfortable because it exposes the difference between attendance and transfer. But it is also fair. It gives the consultancy a clear standard to meet and the client a clear basis for acceptance.

Why firms leave it out

There are understandable reasons. Procurement teams focus on price and risk. Operational leaders assume their people will pick things up. Consultancies may resist detailed handover obligations because they add cost and constrain how delivery is resourced. And no client wants to appear distrustful at the point of signature.

But a handover clause is not an accusation. It is a design choice. It says that the firm is buying capability, not just activity, and that both parties will be judged on whether the capability is present at the end. That clarity usually helps the consultancy as much as the client, because it prevents the familiar post-engagement drift in which the external team is blamed for dependencies it was never asked to resolve.

Keep it proportionate

Not every engagement needs a bespoke knowledge-transfer regime. A short advisory assignment may need only a named recipient, a defined set of artefacts and a two-week question window. A large transformation programme may need staged shadowing, formal acceptance criteria and a longer support period.

The principle is proportionality, not bureaucracy. The clause should sit in the statement of work as a one-page annex, agreed before signature and reviewed at each major milestone. It should be owned by the internal sponsor and tested by the recipient, not merely signed off by procurement.

Exit is part of entry

UK firms are rightly careful about how they enter a consultancy relationship. They should be equally careful about how they leave it. The handover clause is the mechanism that converts external advice into internal capability, and it costs far less to agree at the outset than to discover its absence at the end.

Before signing the entry, contract for the exit. Name the recipient, define the artefacts, schedule the shadowing and set the support window. Then, when the closing slides are shown, ask the only question that matters: can we do this without you?