Handover, Not Handover Ceremony: Making Consultancy Work Survive the Monday After

The final workshop is usually a good day. The slides land, the room nods, and there is a genuine sense of progress in the air. Then Monday arrives, the consultant's diary fills with someone else's problems, and a quieter question takes hold: what still works now that they have gone?

Consultancy is unusual among professional services in that its most important moment is invisible. Nothing is signed off at departure, no goods change hands, and no warranty card is stamped. Value either persists in the client organisation or evaporates with the leaving card. That distinction is decided almost entirely by preparation — and preparation is a matter of operations, not sentiment.

The exit plan belongs in the kick-off pack

The most common structural error in consultancy procurement is treating the handover as an end-of-project activity. It is agreed late, described loosely, and performed under time pressure by people already thinking about the next engagement. The remedy is simple in principle: the departure terms should be negotiated at the same moment as the scope, when both parties still have leverage and appetite.

In practice this means the statement of work should name the artefacts that will exist on the final day, identify who inside the business will own each of them, and specify when the 30/60/90-day review will occur. A handover that is not written into the contract is a courtesy. A handover written into a milestone is an obligation.

Six items that decide whether value survives

The following checklist is not exhaustive, but it covers the areas where capability most often leaks away in the weeks following a consultancy engagement.

1. The decision log

Every engagement involves judgement calls: options dismissed, assumptions adopted, trade-offs accepted. These are rarely captured, because to the people in the room they feel obvious. Six months later they are archaeology. A decision log — one page per significant call, with the rationale and the dissenting view recorded — is the single most valuable document a client can insist upon. It also protects the consultant, who is otherwise blamed for choices that were jointly made.

2. Named owners, not job titles

"The finance team will own this" is not an owner. A named individual, with a defined responsibility and the authority to match, is. Where ownership sits with a role rather than a person, confirm the current post-holder in writing and diarise a check after any internal move. In UK SMEs undergoing growth or restructure, role churn is the quiet destroyer of newly installed processes.

3. Documentation to house standard

Consultancy documentation frequently arrives in a format the client would never produce: bespoke templates, unfamiliar taxonomies, a folder structure that reflects the consultant's mind rather than the business's. Ask for the handover pack to be written in the organisation's own conventions, stored in the organisation's own systems, and usable by someone who was not in the room. If it cannot be read by a competent newcomer, it is not documentation — it is a memoir.

4. Training that transfers judgement, not just clicks

A two-hour walkthrough of a new operating model transfers familiarity, not competence. The test is whether a colleague can run the process unaided, including the exceptions, while the consultant is still reachable. Build in at least one observed run-through where the client leads and the consultant watches, and record the gaps that emerge.

5. Access, credentials and continuity

A mundane but consequential point. Licences, model access, dashboards, repository permissions and third-party subscriptions should be transferred to client-owned accounts, not left running under the consultant's tenancy. Agree in advance what happens to tooling costs at exit, and confirm the position on any data the consultant retains for their own records under UK GDPR.

6. The 30/60/90-day capability review

This is the mechanism that converts a handover into an outcome. At thirty days, check that the process is running at all. At sixty, check that it is running without prompts. At ninety, check whether it has been adapted sensibly or quietly abandoned. A short, scheduled conversation at each point costs very little and catches decay early. Where the engagement was substantial, consider agreeing a modest aftercare provision in the original fee rather than paying day rates for what amounts to reassurance.

What the consultant owes, and what the client owes

Handovers fail from both directions. Consultants guard their methods as commercial assets and describe them too thinly; clients accept vague assurances because the work is nearly over and everyone wants to be agreeable. The balanced position is that methods may remain the consultant's intellectual property while the client's ability to operate the resulting process must be unambiguously transferred. Those two things are compatible, but only if they are written down.

Clients also carry a duty of candour. If the organisation cannot resource the new process, or if a key sponsor is about to leave, that should be raised while something can still be done about it. A handover performed into a vacuum is not a failure of consultancy; it is a failure of joint planning.

A test you can apply this week

If an engagement is currently live, ask one question of the person best placed to answer it: on the Monday after the consultant leaves, who will open which document, and what will they do first? If the answer is immediate and specific, the exit plan is working. If it produces a pause, there is still time — but not much.

Departures are the part of consultancy that nobody enjoys discussing. They are also the part that determines whether the fee bought a change or a very well-rehearsed series of meetings.