The consulting engagement lifecycle: from first call to handover

When a consulting engagement goes wrong, the analysis in the middle is often fine. The trouble starts earlier, when nobody pinned down what the client wanted, or later, when the consultant leaves and nothing changes. A clear lifecycle gives both sides a shared map of what happens when, who does what, and what “done” looks like.

This guide walks through the eight stages of a typical engagement, from the first call to the handover. It draws on Peter Block’s phases of consulting, the engagement model published by the US government’s 18F team, and McKinsey’s description of structured problem solving. It suits independent consultants, small firms and in-house teams who run projects for other departments.

Why a lifecycle matters

Different sources slice the work differently, but they agree on its shape. Peter Block’s Flawless Consulting (now in its fourth edition) uses five phases: entry and contracting, discovery, analysis and the decision to act, engagement and implementation, and finally extension, recycle or termination. The 18F engagement handbook uses four: set up, discovery, implementation and handover. It adds that phases can overlap, repeat or run out of order.

The eight stages below expand those models so each one has a clear output. Treat them as a checklist of things that must happen, not as a rigid sequence.

Stage 1 to 3: first call, scoping and proposal

1. First call

The first conversation is for listening. Find out what prompted the call, who is involved, what has already been tried, and what a good result would look like to the person paying. Ask who else needs to be convinced. Resist the urge to diagnose on the spot.

2. Scoping

Scoping turns a worry into a question you can answer. McKinsey’s seven-step problem-solving article stresses defining the problem first: understand the forces on the decision maker, how quickly they need an answer, how precise it must be, and which areas are off limits. Its authors note that stakeholders often hold different views of why they are there, so debate the problem statement early.

The Wikipedia summary of management consulting makes a related point: clients should define the help they need so that the contract’s scope, length and content match it. Write a one-sentence question, a list of what is in and out of scope, and the decision the work will feed.

3. Proposal and agreement

The proposal confirms the objectives, scope, deliverables, assumptions, timeline and fees. Once signed, it often becomes or feeds a statement of work. Its job is to prevent surprises later, so state exclusions plainly and say how changes will be handled.

Stage 4 and 5: kick-off and discovery

4. Kick-off

The kick-off meeting gets the client team and the consultants aligned on the same plan. Cover the question, the scope, the timeline, roles, how often you will report progress, and how to reach people. Agree access to data and interviews in this meeting, because waiting for access is one of the most common causes of delay.

5. Discovery

Discovery tests whether the problem is the one the client described. 18F frames success here as research that supports the problem, an identified first slice of work, and a recommended path forward. In practice this means interviews, data requests, site visits and reading existing reports. Share early findings in short check-ins rather than saving them for the end.

Stage 6 and 7: analysis and recommendations

6. Analysis

McKinsey’s sequence moves from breaking the problem into parts, to prioritising the parts that matter most and that the client can influence, to planning the work and analysing it. Its advice is to start with simple estimates and exploratory work before reaching for advanced tools, and to check the data is sound.

7. Recommendations

Synthesis is where findings become an answer to the client’s question: what should we do? Block calls this stage the decision to act, and treats the feedback meeting as something to manage for action, not just a presentation. Be explicit about uncertainty. McKinsey quotes Hugo Sarrazin: “This is a likely answer under the following sets of conditions.” Give each recommendation an owner, a cost and a first step.

Stage 8: implementation support and close

Some engagements end with a report. Many now include support while the client puts the recommendations into practice. 18F describes implementation as delivering a first slice of work to build trust while preparing the client to carry on alone, with a transition plan as a key output.

The close, which 18F calls handover, has three tests. The client can run the work without you. The outcomes are written down. The engagement is formally closed, with final invoices, returned access and a short lessons-learned note. Block’s final phase reminds you that the end is also a decision: extend, start a new piece of work, or stop.

An example (illustration only)

A 30-person online homeware retailer asks a consultant to “fix our margins”.

Common mistakes

• Skipping scoping because the client seems sure. The stated problem is often a symptom.
• Writing a vague scope. Scope creep grows from poorly defined or poorly controlled scope, so list exclusions and a change process.
• Starting analysis before data access is agreed.
• Saving all findings for a final presentation. Surprises at the end get resisted.
• Recommending without owners or first steps, so nothing happens after you leave.
• Leaving without a handover. If the client depends on you to run the work, the engagement has not finished.

When to compress the stages

A two-day diagnostic still needs every stage, but some take minutes. Scoping can be a single email, and the handover can be a one-page summary. Long programmes may loop through discovery, analysis and implementation several times, as 18F notes. What you should not do is drop a stage entirely. A missing scope and a missing handover are the two gaps that cause the most damage.