Consultant Knowledge Transfer Plan for a Client Handover
When a consultant rolls off, the client should notice nothing. A knowledge transfer plan for handing a client to a colleague, in 10 days or 48 hours.

A consultant knowledge transfer plan lists what a consultant hands to the colleague who takes over a client. It covers the people, the open work, the agreements nobody wrote down, the access and the reason behind each of them. It works for an interim role and for a project. This post gives you the plan, two timelines and a template to copy.
Every assignment ends
Consulting work comes in assignments. An interim manager fills a role for six or twelve months. A project team runs a project until it is delivered. Then the consultant moves on. Often the next client starts the same week.
The client stays. So does the work. A colleague from the same firm takes over and the client expects the work to continue as before.
So the handover is a normal part of every assignment. Most firms still plan the start of an assignment in detail and leave the end to the last week.
The client is the first to notice a handover that went wrong. The new consultant asks questions the client already answered. A promise made in a meeting gets lost. Nobody knows that the finance director wants to see a proposal before the board does.
Panopto and YouGov found in 2018 that 42 percent of institutional knowledge is unique to the employee in their role. In an assignment run by one consultant, that person may be the only one at the firm who knows how the client works.
What is a KT plan?
A KT plan is a knowledge transfer plan. "KT" is the common shorthand in IT and SAP consulting. The plan names what must be handed over, who hands it over, who receives it and by which date.
Knowledge transfer is the wider process. It is how what one person knows about a job reaches the next person.
Who is involved in a client handover
Four people take part. Each needs something different.
Who | What they need | What they do |
|---|---|---|
The leaving consultant | Time in the last weeks to hand over | Writes the first draft of the plan and answers questions |
The successor | The context behind the open work | Reads the plan, asks questions and explains the work back |
The client contact | Proof that nothing will drop | Meets the successor and confirms the open promises |
The engagement lead | A handover that fits the budget | Names the successor, sets the dates and signs off |
What goes in the plan
Six parts cover most handovers.
The client map. Who works on the assignment at the client. Who decides what. Who must hear about a decision before it is taken. Who is sensitive about which topic.
Open work and promises. Deliverables in progress, deadlines and anything the consultant promised in a meeting or an email.
Agreements nobody wrote down. For example: changes to the planning go to the operations manager first, although the project charter names the director. Rules like this live in one head.
Systems, documents and access. Where the files are. Which accounts the consultant holds. Which of them must be moved and which must be closed.
Recurring work and the reason for each step. The weekly report, the monthly steering meeting, the quarterly review. For each one: what it is for and what goes wrong if it is skipped.
Risks and sensitive topics. Open issues, tensions in the client team and subjects to avoid in the first weeks.
An interim role or a project
The weight of each part depends on the assignment.
An interim role hands over a role. The successor needs to know what to know, who to call and where things break. Parts 1, 3 and 5 carry most of the weight.
A project hands over a project. The successor needs the status, the decisions taken and why, the stakeholders and the open risks. Parts 2, 4 and 6 carry most of the weight. In many firms this part is called the project handover document.
Two timelines
Sometimes there are ten working days for a handover. Sometimes there are two. Plan for both.
The 10-day plan
Day 10. The engagement lead names the successor. The leaving consultant drafts the plan with the six parts.
Day 8. A capture interview with the leaving consultant. Ask about real cases. Our 42 knowledge transfer interview questions are a starting point.
Days 7 to 4. Knowledge transfer sessions on live work. The successor sits in on client meetings and does one task while the leaving consultant watches.
Day 3. A joint meeting with the client. The leaving consultant introduces the successor and goes through the open promises.
Last day. The successor explains the assignment back. Gaps show quickly when the receiver has to tell the story.
Two weeks later. A check-in call. The leaving consultant stays reachable for questions until then.
The 48-hour plan
Sometimes the next assignment starts on Monday. Then do three things.
A capture interview first. One to two hours on the client map, the open promises and the agreements nobody wrote down.
One joint call with the client. Thirty minutes. Introduce the successor and confirm the open promises out loud.
A written handover the successor can question. The successor reads it and sends questions while the leaving consultant can still answer them.
The first 72 hours after a resignation follow the same order.
The part every template skips
Templates list tasks. They rarely hold the reason behind a task.
An example. The project plan says decisions are taken in the monthly steering committee. The leaving consultant knows that the committee only confirms. The real decisions happen in the client lead's stand-up on Thursday morning, so proposals go there first. A successor who works from the project plan prepares for the wrong meeting and loses a month.
That reason is tacit knowledge. The consultant knows it and never wrote it down, because nobody asked. Questions about real situations bring it out. Ask: "What happened the last time a proposal went to the steering committee?"
Put the handover in the statement of work
The usual objection is time. A handover costs hours and nobody wants to pay for them.
Settle that when the assignment starts. Four lines in the statement of work do it.
A handover budget in hours, included in the fee.
A named successor, or a rule for naming one.
A minimum overlap between the leaving consultant and the successor.
Client sign-off on the handover plan.
The client gets continuity. The firm keeps the client. The leaving consultant starts the next assignment without calls about the last one.
KT plan template to copy
Copy this table into your own document. Fill one row per item. Give every row an owner and a date.
Part | What to hand over | Owner | Due | Status |
|---|---|---|---|---|
Client map | People, roles, who decides what | Leaving consultant | Day 8 | |
Open work and promises | Deliverables, deadlines, promises made | Leaving consultant | Day 8 | |
Unwritten agreements | Rules that live in one head | Leaving consultant | Day 8 | |
Systems and access | Files, accounts and logins to move or close | Leaving consultant | Last day | |
Recurring work | Each routine and why it exists | Successor | Day 4 | |
Risks and sensitive topics | Open issues and tensions in the client team | Leaving consultant | Day 3 | |
Client meeting | Successor introduced, promises confirmed | Engagement lead | Day 3 | |
Explain-back | Successor tells the assignment back | Successor | Last day |
The Handover Kit has a booking email and a template for the written handover.
Frequently asked questions
What is a KT plan?
A KT plan is a knowledge transfer plan. It lists what a person who leaves a job or an assignment hands over, to whom and by when. "KT" is common shorthand in IT consulting.
How long should a consultant handover take?
Ten working days is a good target for an assignment that ran several months. When there is less time, a capture interview, one joint client call and a written handover fit in 48 hours.
What if the engagement ends and the client takes over the work?
Then the client's own staff receive the handover. The same six parts apply. Agree in the contract which documents and access the client keeps when the engagement ends.
Who owns the knowledge after an assignment?
The contract decides who owns documents and work products. What sits in the consultant's head leaves with them unless it is written down. A handover plan makes sure the firm and the client keep what they need.
What goes in a client handover email?
Introduce the successor by name and role. Give the date the handover takes effect. List the open promises and who now owns each one. Say how long the leaving consultant stays reachable.
Handing over an interim role or a project soon? Rinto interviews the leaving consultant in about 1.5 to 2 hours and writes the handover in their own words. It scopes the interview to one interim role or one project. Get access
Sources
Build a Company That Keeps Getting Smarter
Your people carry tomorrow's answers. Rinto makes them timeless.
Excellence shouldn't leave with people. Capture their wisdom, their methods and their brilliance. So every goodbye becomes a gift.
Build a Company That Keeps Getting Smarter
Your people carry tomorrow's answers. Rinto makes them timeless.
Excellence shouldn't leave with people. Capture their wisdom, their methods and their brilliance. So every goodbye becomes a gift.
Build a Company That Keeps Getting Smarter
Your people carry tomorrow's answers. Rinto makes them timeless.
Excellence shouldn't leave with people. Capture their wisdom, their methods and their brilliance. So every goodbye becomes a gift.