A consultant handover checklist for live client projects

A consultant is leaving a project on Friday. The successor joins on Monday. The shared folder contains the proposal, workshop slides, a delivery plan and several versions of the same spreadsheet.

Before calling the handover complete, ask one question: can the successor prepare for the next client conversation without having to reconstruct the project?

Use this checklist to build a handover around that first week of work. It suits a change of project lead, a consultant rotating to another assignment, or a colleague covering an absence. Start while the outgoing consultant is still available to answer questions.

1. Define what the successor is taking over

Write a short project brief with the client objective, current phase, agreed scope and next meaningful milestone. Include the date of the handover and the person responsible after it.

Be precise about boundaries. “Own the workstream” leaves room for confusion. “Prepare the weekly progress update, coordinate the two outstanding interviews and escalate scope changes to the engagement manager” gives the successor a starting point.

Record any responsibilities that stay with someone else. Name the manager who can resolve an unclear ownership question.

2. Explain the current position

Describe what has been delivered, what has been accepted and what still needs a decision. Separate these states rather than treating “sent to the client” as “approved.”

For each active deliverable, include:

• Its current status and the date that status was checked
• The authoritative file or location
• The next action, owner and due date
• Any dependency that could prevent progress

If two versions disagree, identify the current one and explain the difference. Avoid making the successor guess from filenames.

3. Preserve the reasons behind important decisions

Choose the decisions that will shape the successor’s next actions: the scope boundary, the selected approach, the sequencing of work or a commitment to the client.

For each, record what was decided, who approved it, why that option was chosen and which constraint mattered. Link the supporting email, meeting record or other evidence where access is permitted.

Add a condition for revisiting it. A phased rollout might have been agreed because a client team lacked capacity. If that capacity changes, the successor should know the earlier decision may need review.

4. Make client relationships actionable

List the people the successor will actually work with. Include their role, the decisions they own, agreed communication arrangements and any introduction still needed.

Keep relationship notes factual and respectful. “Requests the draft agenda before steering meetings” is actionable. A personal judgment about someone’s character is harder to verify and may be inappropriate to share.

Distinguish the person who provides input from the person who approves the work. If authority is unclear, flag it as a question for the manager rather than filling the gap with an assumption.

5. Surface risks and open loops

An open loop is an unfinished commitment or unresolved question that still needs an owner. Examples include a promised analysis, a client clarification, an unanswered request or a pending approval.

Give each open loop an owner, a next step and a date. For risks, add the signal that would tell the successor to act and the person to involve.

Avoid entries such as “Watch stakeholder alignment.” Write something observable: “The regional lead has not reviewed the revised scope. Confirm their feedback before the steering meeting.” Label hypothetical examples and uncertain information clearly in your own pack.

6. Check access and handling requirements

Have the successor check that essential links open using their own account. List access requests separately, with an owner to resolve each one.

Use your firm’s approved process for permissions and client material. Keep passwords and access tokens out of the handover. Include only the information the successor needs and is allowed to receive.

For teams working across Morocco and France, agree the working language and write meeting times with the relevant time zone. Confirm any client-specific handling restrictions with the appropriate person before moving material into a new tool.

7. Review the handover with the manager

Ask the outgoing consultant to distinguish confirmed facts, interpretation and unanswered questions. The manager should check client commitments, responsibilities, sensitive relationship notes and the most consequential decisions.

Record corrections and make unresolved issues visible. A polished paragraph can still contain an unsupported assumption. Approval should mean the manager has reviewed the substance and understands the remaining gaps.

8. Test it against three real tasks

Choose tasks the successor is genuinely about to perform. For example:

1. Prepare the next client meeting agenda using current priorities and commitments.
2. Explain an important project decision, including its rationale and when it should be revisited.
3. Move an outstanding action forward by identifying its owner, deadline and escalation route.

Let the successor attempt these tasks using the handover and the normal project materials. Note where they need help, which details are missing and what needs correction. Fix those gaps before the outgoing consultant becomes unavailable where possible.

Keep the handover usable after day one

Put the immediate next actions at the top. Give the pack a clear owner and review date. Agree how material changes will be recorded after responsibility transfers.

Handov’s guided workflow brings together employee capture, optional AI-assisted rewriting and gap prompts, manager feedback and approval, and a successor pack. Human review remains essential for checking accuracy and client commitments. For the reasoning behind important decisions, see the decision-context guide.

If your consulting firm has a real transition coming up, discuss a focused Handov pilot around two handovers. Start with the work the successors need to do and agree how you will judge whether the packs help.