Prepare a useful handover
Knowledge transfer: keep client context when an expert leaves or goes on holiday
Knowledge transfer helps another person use the information and judgement needed to take over a job. For client work, a useful handover explains the current agreement, recent decisions, open issues and the recipient’s authority. Test it through a real task before the person who holds the context is unavailable.
A handover is ready when the recipient can complete the chosen job, identify its unresolved questions and know who can make the next decision.
Define the job the other person is taking over
Covering a meeting, maintaining a report and taking over an account permanently need different amounts of context. Agree the job, dates, useful result and decisions the recipient can make.
Write down what needs attention during the cover period. Include promised work, deadlines, unresolved questions and the people who can approve changes. A chronological archive can contain all this information while still making it hard to find.
Keep the handover focused enough to use. Link to authoritative records rather than copying every document into a new folder. The recipient should be able to inspect the source when a decision matters.
Preserve current context and unresolved decisions
| Part | What the recipient needs |
|---|---|
| Agreement | Current scope, requirement and source. |
| Goals | What the client is trying to achieve now. |
| Recent decisions | What changed, who approved it and when it became valid. |
| Open issues | Question, consequence, owner and next decision date. |
| Work | Upcoming tasks, dependencies and promised outputs. |
| Authority | Decisions the recipient may make and where to escalate. |
Record source origin separately from validity and collection dates. A handover prepared today can still cite an old agreement. Mark missing evidence so the colleague can raise it rather than accidentally treating an assumption as an approved decision.
Use a short discussion to capture judgement the records leave out. Ask the current owner about an awkward recent example and a similar case handled differently. The tacit-knowledge interview provides prompts for that conversation.
One reported example from our current build
Said reported that someone unfamiliar with a client account used the current build to obtain enough context to cover a colleague’s meeting, in as little as 30 minutes. The build connects internal information so relevant account context can be used.
This is one reported event. There is no previous-time baseline, independently inspected brief or established meeting outcome. The colleague’s reason for being absent is not recorded, so the holiday scenario in this guide is illustrative.
The practical lesson is to make the necessary context available before a handover becomes urgent. A connected knowledge system can support that, while the recipient still needs clear authority and a way to resolve missing information.
Ask the recipient to practise the job
Have the recipient prepare the meeting brief, plan the report or explain the next account decision using the handover. Ask what they would do if the current owner were unavailable. Check the sources they selected and the questions they still need answered.
Include one known gap or contradiction. A good handover helps the colleague recognise it and find the right decision owner. The aim is not to make them confident about every possible question.
Confirm access before the cover period. Grant only what the job needs through the organisation’s approved process. Keep credentials out of the handover record. After the job, reviewed decisions and corrections should update the shared context.
Prepare a handover the recipient can use
Worked example
An invented account-meeting handover
Invented teaching example. No client outcome is claimed.
JOB
A colleague prepares and attends one account meeting.
CONTEXT
Current agreement, approved goals, recent decision log and two open issues.
AUTHORITY
The colleague may explain current work; a scope change goes to the account owner.
PRACTICE
The colleague prepares a brief and identifies an open issue with no confirmed decision.
UPDATE
Approved meeting decisions update the decision log with their source and validity date.
Further reading
Written by Said Lopez, founder of LeverageAI and author of Lean AI. Our guides draw on the method in the book and our work with clients.