The problem of knowledge loss at departure is more severe than most organisations acknowledge. A significant proportion of what experienced employees know is tacit knowledge - it exists in their heads, not in any document. How to manage a particular client relationship, which shortcuts work in a specific system, which unofficial processes have evolved around the documented ones, which stakeholders need to be approached in which order to get things done - none of this is in the procedures manual. The departure of even a single experienced employee can take months to recover from if their tacit knowledge was not captured before they left.
Knowledge transfer planning should begin as soon as a departure is confirmed, ideally in the first week of the notice period rather than the last. The first step is an inventory: what does this employee know that others do not? Which processes and relationships are they the sole owner of? What decisions have they been the institutional memory for? This inventory forms the basis for a structured transfer plan - a list of knowledge elements, the intended recipient(s) for each, and the transfer method (documentation, shadowing, handover meeting, recorded walkthrough, introduction to relationship holders). The plan should be reviewed and tracked by HR throughout the notice period rather than left entirely to the departing employee and their manager.
Knowledge capture methods vary in depth and scalability. Documentation - writing up processes, decision frameworks and contact lists - is scalable but captures only explicit knowledge. Shadowing - the successor or peer working alongside the departing employee to observe and ask questions in context - is more effective for tacit knowledge but requires both parties to be present and available. Video walkthroughs - recorded screenshares or demonstrations of processes - sit between these two extremes: richer than documentation alone, scalable because they can be reviewed later by multiple people. For critical roles, all three methods should be used in combination.
Knowledge transfer risk is highest in organisations with long-tenured specialists, small teams where individual expertise is concentrated, and roles with significant external relationship capital (account managers, business development leads, lobbyists, senior technical architects). These roles should have ongoing knowledge sharing as a standard practice - not just a departing activity. Documentation, cross-training, pair working and relationship introductions to ensure no key relationship is held by a single individual should be part of the regular talent management approach, making departure planning a formalisation of practices already in place rather than a crisis response.
Key Points: Knowledge Transfer
- Tacit knowledge risk: The most valuable knowledge is often informal and undocumented; it exists only in the departing employee's head.
- Timing: Begin knowledge transfer planning in week one of the notice period, not the final week.
- Inventory first: Identify which knowledge is unique to this employee before choosing transfer methods.
- Methods: Documentation (explicit), shadowing (tacit), video walkthroughs (hybrid) - use in combination for critical roles.
- Proactive approach: High-risk roles should practise continuous knowledge sharing, making departure preparation a formalisation not a crisis.
How Knowledge Transfer Works in Treegarden
Knowledge Transfer in Treegarden
Treegarden's offboarding module includes a knowledge transfer task framework. When an employee's departure is logged, HR generates a knowledge transfer checklist based on the role. Departing employees complete documentation templates directly in the platform, upload recordings, and log introductions made to key contacts. Managers track completion against the checklist. All transfer artefacts are stored in the HR system, accessible to successors and the team after the employee leaves.
Related HR Glossary Terms
Frequently Asked Questions About Knowledge Transfer
Knowledge management is the broader organisational discipline of capturing, organising, storing and enabling access to collective organisational knowledge on an ongoing basis - through intranets, wikis, document management systems and communities of practice. Knowledge transfer is a specific, time-bounded activity that occurs at a transition point - typically when an employee is departing, changing roles, or going on extended leave. Knowledge transfer feeds into knowledge management when the artefacts it produces (documented processes, recorded walkthroughs) are stored in the organisation's knowledge management systems for future reference.
The appropriate length depends on the role's knowledge complexity and the amount of time available within the notice period. For most individual contributor roles, two to four weeks is sufficient for structured knowledge transfer if planning begins promptly. For senior or highly specialised roles, especially those with significant client relationships or institutional knowledge built over many years, three to six months of overlap - through an extended handover or a specific transition period - may be warranted. Roles where the departing employee has built a large portion of the business case for renewal of a major client contract or funding relationship may require even longer, or the knowledge transfer may need to span multiple people rather than a single successor.
This is more common when the departure is acrimonious or where the employee perceives their knowledge as a source of leverage. In most employment jurisdictions, there is no legal obligation to transfer knowledge beyond the reasonable performance of duties during the notice period. The practical approach is to make knowledge transfer expectations explicit in the employment contract (as a duty to assist with handover) and in the resignation acceptance process, to involve the manager in tracking completion, and to make the experience as positive as possible for the departing employee - including a genuine thank-you for their contribution and a helpful reference. Adversarial approaches to knowledge transfer requests typically produce poor quality outputs.