People leave. It is one of the few certainties in management. Yet most managers have no plan for when it happens. The resignation arrives, there is a brief scramble to figure out what the person knows that nobody else does, a hurried handover takes place in the final week, and then they are gone, along with context, relationships, and institutional knowledge that took months or years to build. A good offboarding does not prevent the loss entirely, but it captures what can be captured, communicates clearly with the team, and preserves the relationship for the future.
How someone experiences their departure shapes how they talk about your team and organisation for years. It also shapes how the remaining team views your leadership. Offboarding well is not just operational hygiene. It is a statement about the kind of manager you are.
Knowledge transfer that actually works
The most common complaint after someone leaves is "we did not realise how much they knew". For more on this, see our guide on handing over a team. This is always preventable and always the manager's responsibility. Knowledge transfer cannot happen in the last three days of someone's notice period. It needs to start immediately after the resignation is confirmed and be treated as a structured project, not an afterthought.
Start by mapping what the departing person owns or knows that others do not. The teams feature in Manager Toolkit supports this. This includes active projects, ongoing relationships with stakeholders, undocumented processes, access credentials, and context about why certain decisions were made. Create a clear handover plan with actions tracked in Manager Toolkit: who is picking up each piece of work, what documentation needs to be written, and what pairing sessions need to happen before the person leaves. A handover without written documentation is a handover that evaporates within weeks.
- Map the knowledgeSit down with the departing person and list everything they own: projects, processes, stakeholder relationships, tools they administer, decisions only they understand the context for. This inventory drives the handover plan.
- Pair, do not just documentDocumentation alone is insufficient for complex knowledge. Schedule pairing sessions where the departing person works alongside the person taking over. Doing the work together transfers context that a document cannot capture.
- Prioritise ruthlesslyNot everything can be transferred perfectly in a notice period. Identify the highest-risk knowledge gaps, the things that will cause real problems if lost, and prioritise those. Accept that some knowledge loss is inevitable and plan accordingly.
- Write it downFor processes, decisions, and context that can be documented, insist on written handover notes. These should be stored somewhere permanent and accessible, not buried in an email thread. Review them together before the person leaves to check for gaps.
- Transfer relationshipsIntroduce the replacement or interim owner to key stakeholders before the departure. A warm handover from someone they trust is far more effective than a cold introduction after the person has already gone.
Communicating the departure
How you communicate a departure matters more than most managers realise. Done badly, it creates rumours, anxiety, and a sense that something is being hidden. Our article on redundancy conversations explores this further. Done well, it demonstrates transparency and respect for both the departing person and the remaining team. The communication should be agreed with the person who is leaving, delivered promptly once they are comfortable, and honest about what is happening without oversharing.
Talk to the departing person first about how they would like the news to be shared. Some people want to tell the team themselves. Others prefer the manager to do it. Agree on timing and messaging. Then communicate with the team as quickly as possible. Delays breed speculation, and speculation is always worse than the truth. Be straightforward: the person is leaving, here is the timeline, here is the plan for their work, and here is what happens next.
- Agree the messageWork with the departing person on what is shared and how. Respect their wishes about what is communicated regarding their reasons for leaving. This is their story to tell, not yours.
- Tell the team promptlyOnce agreed, communicate quickly. The team will find out regardless, and hearing it officially from their manager is far better than hearing it through the grapevine days later.
- Be honest and measuredAcknowledge the departure, express genuine appreciation for the person’s contribution, and share the practical plan. Do not be overly emotional or dismissive. Strike a tone that is warm, honest, and forward-looking.
- Inform stakeholdersExternal stakeholders, partner teams, and key contacts should hear about the departure directly from you or the departing person, not through a bounced email or an unanswered Slack message weeks later.
The exit conversation
Most organisations run formal exit interviews through HR. These are useful for institutional data but rarely produce honest, specific feedback. The most valuable exit conversation is the one you have as their direct manager: a genuine, reflective discussion about their experience, what worked, what did not, and what you could do better. This requires trust and humility, and it only works if the person believes you genuinely want to hear the truth.
Schedule this conversation well before their last day, not on it. Give them time to reflect and prepare. Ask open questions and listen without defending. The feedback you receive in an exit conversation is some of the most honest you will ever get, because the person has nothing left to lose by being direct. Treat it as a gift. Log the key themes and reflect on them honestly. If patterns emerge across multiple departures, you have systemic issues worth addressing.
- Ask the real questions"What would have made you stay?" and "What should I do differently as a manager?" are uncomfortable but invaluable. Most people will answer honestly if they trust that the question is genuine.
- Listen without defendingIf they share criticism, resist the urge to explain or justify. Thank them for the honesty and sit with it. Defensive reactions in exit conversations guarantee that nobody else will ever be honest with you either.
- Look for patternsOne person’s feedback is an opinion. Three people saying the same thing is a signal. Track exit conversation themes using Key Themes in Manager Toolkit so you can identify whether the same issues keep driving departures.
- Act on what you learnThe worst thing you can do with exit feedback is collect it and ignore it. If multiple people mention the same problem, fix it. Your current team is likely experiencing the same issues but has not yet reached the point of leaving over them.
Helping the team adjust
A departure creates a gap that is both practical and emotional. Someone the team relied on, collaborated with, and cared about is leaving. The remaining members may feel anxious about the increased workload, uncertain about the future, or simply sad to lose a colleague. Managers who rush past this emotional reality and focus only on redistributing tasks miss an opportunity to demonstrate that they see their team as people, not just resources.
Acknowledge the departure openly and give the team space to process it. Then move quickly to the practical side: how work will be redistributed, whether a replacement will be hired, and what the timeline looks like. Use your individual catchups to check in with each person about how they are feeling and whether their workload is sustainable with the change. Track any new responsibilities carefully so that a temporary redistribution does not become a permanent overload that nobody revisits.
- Acknowledge the lossDo not pretend it is business as usual. Say something like: "We are going to miss them, and it is okay to feel that. Let us talk about how we move forward together." This validates the team’s feelings and builds trust.
- Redistribute fairlyBe deliberate about where the departing person’s work goes. Do not let it default to the most willing or most available person. Spread the load, adjust priorities, and be transparent about what is changing and why.
- Set a hiring timelineIf a replacement is planned, share the timeline with the team. Knowing that relief is coming makes a temporary increase in workload far more bearable than open-ended uncertainty.
- Check in regularlyIn the weeks after the departure, pay extra attention in your catchups. The real impact often surfaces a fortnight later when the absence is felt in the daily work. Ask about workload, morale, and whether the handover was sufficient.
Making offboarding systematic
Like onboarding, offboarding suffers when it is reinvented each time. The same tasks need to happen for every departure: knowledge transfer, access revocation, stakeholder communication, equipment return, exit conversation. Without a system, things get missed. Accounts stay active for months. Documentation is never written. Stakeholders find out through a bounced email. Each of these small failures is preventable with a simple, repeatable process.
Create an offboarding checklist using Manager Toolkit's Journeys feature. Define milestones for each phase: the first week after resignation, the handover period, the final week, and post-departure follow-up. Populate each milestone with the tasks that need to happen every time. When someone resigns, create a journey for their departure and work through it systematically. Over time, this becomes a reliable process that ensures nothing falls through the cracks and every departure is handled with the same level of care and thoroughness.
- Repeatable checklistBuild a standard offboarding journey with milestones and tasks that apply to every departure. Include knowledge transfer, access revocation, equipment return, communication, and the exit conversation.
- Access and securityRevoke access to systems, repositories, and tools on the last day. This is not personal. It is a basic security practice that protects the individual and the organisation. Schedule it in advance so nothing is forgotten.
- Post-departure reviewTwo weeks after the person leaves, review the handover with the team. Are there gaps? Is anything missing? Is the workload redistribution sustainable? This final check catches problems while they are still easy to address.
- Preserve the relationshipPeople who leave well often come back, as employees, as customers, as collaborators, or as referrals. A strong offboarding experience turns a former employee into a lasting advocate for your team and organisation.
Frequently asked questions
Structure every departure
Use Journeys to manage offboarding with milestones, handover tasks, and systematic follow-up so nothing falls through the cracks.