run-employee-offboarding

Run Employee Offboarding

Manage a departing direct report's final weeks with a structured plan for knowledge transfer, team communication, and the relationship — so the team remains functional, the departure strengthens the organization's alumni network, and critical knowledge does not leave with the person.

Why This Is Best Practice

Adopted by: SHRM's offboarding best practice guide is the HR industry standard; Microsoft, Google, and McKinsey maintain structured alumni programs precisely because how employees are treated at exit determines whether they return as clients, rehires, and referrers; the US Army's "transition assistance program" is a structured 3–6 week offboarding process that the Department of Labor considers a model for workforce transitions; Deloitte runs one of the largest corporate alumni networks in consulting (500,000+ members) specifically because alumni generate client referrals and return talent Impact: Workforce Institute (2020, 3,500 employees surveyed) found that 28% of employees who quit their jobs had returned to a former employer — and those "boomerang employees" performed at or above the level of never-left peers; LinkedIn data (2019) found that employees hired through alumni referrals have 45% higher retention at 2 years than external hires; BambooHR (2021) found that 20% of employees experienced "offboarding that made me less likely to speak positively about the company afterward" — each unhappy departure is a reputational risk in the talent market Why best: Most managers treat offboarding as an administrative process — collect the laptop, delete the accounts, post the job req — and not as a management responsibility; this approach creates three preventable failures: (1) critical knowledge leaves undocumented; (2) the team's morale is unmanaged during a period of uncertainty; (3) the departing employee leaves with a damaged or ambivalent relationship that turns an asset (alumni) into a liability (negative word-of-mouth)

Sources: SHRM "Employee Offboarding" knowledge center; Groysberg & Slind "Talk, Inc." (HBS Press, 2012); Workforce Institute "The Impact of Workforce Decisions on Employee Experience" (2020); BambooHR "The Ultimate Guide to Employee Offboarding" (2021)

Steps

1. In the first 48 hours after resignation: manage the sequence of communication

The first 48 hours after a voluntary departure are the highest-risk period for information disorder. Control the sequence:

Step 1 (immediate): Accept the resignation gracefully. Do not pressure, guilt, or make a counteroffer without deliberation. "Thank you for telling me. Can we find time today to talk about what comes next?"

Step 2 (within 24h): Notify your own manager and HR before telling the team. This ensures they are not blindsided and can support the transition plan.

Step 3 (within 48h): Notify the team — before they hear through informal channels. Ideally, co-coordinate with the departing employee: "Would you like to tell the team yourself, or would you prefer I share it?" Employees who control their own departure narrative feel respected; managers who announce departures before the employee has told their own colleagues create awkward situations and signal lack of regard.

The announcement should include:

• What: [Name] is leaving on [date]
• Why (if the employee is comfortable sharing): "[Name] is pursuing [next step] — an exciting opportunity they shared with me."
• What's next: "Here's how we'll cover [critical responsibilities] during the transition."

What NOT to say: "We wish [Name] well and will miss them." Platitudes without operational clarity signal to the team that the manager is not in control of the situation.

2. Build the knowledge transfer plan in week 1

The departure deadline is fixed. Work backward from it. In the first week after resignation:

Map critical knowledge:

• What does this person know that no one else knows?
• What ongoing work will they hand over, and to whom?
• What relationships do they hold that need to be introduced to someone else?

Categories of knowledge to capture:

1. Ongoing work: status, next steps, blockers (document in project tool)
2. Tacit process knowledge: how things actually get done vs. how the doc says they do
3. Relationship context: key contacts, their preferences, history with the team
4. Institutional history: why decisions were made, what was tried and didn't work
5. Access and credentials: systems, accounts, repositories, permissions

Who captures what: The departing employee writes the documentation. The manager's role is to define the scope and review the output for completeness — not to do the documentation themselves. Block specific time in the departing employee's calendar for documentation.

Knowledge transfer meetings: For each significant handover, schedule a 30–60 minute recorded walkthrough between the departing employee and their successor on that function. Documentation without walkthrough misses tacit knowledge.

3. Manage the team's morale through the transition

A departure creates uncertainty: "Why are they leaving? Is this a sign of something? Should I be looking too?" Left unaddressed, this uncertainty produces morale degradation and can trigger a cascade departure — especially if the person leaving is respected.

Address the concern directly in a team meeting within 48 hours of the departure announcement:

"[Name] leaving creates a real gap — they were a key part of how we work. 
I want to be honest with you about the transition:
- Here's what's changing immediately [specifics]
- Here's what I'm doing to manage the coverage [specifics]
- Here's the timeline for the replacement search [specifics]
- I'd like to hear your questions directly — what are you concerned about?"

Do not minimize the impact. "We'll be fine" delivered without a plan sounds hollow. "Here's specifically how we're managing it" delivered with a plan builds confidence.

Individual check-ins: in the week following the announcement, individually check in with team members who had close working relationships with the departing employee. Acknowledge the disruption; ask what they need.

4. Manage the final weeks of the departing employee

The departing employee's last 2–4 weeks are a management responsibility, not an administrative one. Three failure modes:

Ghost the departing employee: stop including them in decisions, discussions, and meetings because "they're leaving anyway." This signals that contribution only matters while someone is employed; it produces bitter departures and incomplete knowledge transfer.

Pressure for more than the notice period: asking someone who has resigned to stay extra weeks or take on more to compensate for the gap. This produces resentment, usually doesn't succeed (they've already committed to their next role), and damages the relationship.

Ignore the relationship: treating the last day as purely logistical — laptop return, access revocation — without acknowledging the relationship.

What to do instead:

• Continue including the departing employee in team activities and decisions where their institutional knowledge is relevant
• Have a final one-on-one in the last week focused on: "What am I not aware of that I should know before you leave? What advice do you have for me as a manager?"
• Organize a team send-off that is sincere, not perfunctory — this signals to the rest of the team how departures are treated

5. Conduct the exit conversation and document what you learn

Separate from HR's exit interview (which focuses on organizational data), conduct your own final manager-level conversation with the departing employee. This is a gift to yourself as a manager:

"I'd like to ask you a few things now that you're on your way out 
and don't have to worry about career impact:
- Is there anything about how I managed you that I could improve?
- Is there anything about how the team operates that I should know 
  but might not be hearing?
- What made you decide to leave now, if you're comfortable sharing?"

Departing employees are more candid than current employees. What they tell you is often more honest than anything you'll get in a normal feedback cycle. Take it seriously. Document it. Act on patterns that appear across multiple departing employees' feedback.

6. Maintain the alumni relationship

The employee's last day is not the end of the relationship. A simple, genuine message within a week of departure:

"Now that you've had a few days in the new role — hope the transition 
is going well. Genuinely glad for this opportunity for you. If there's 
ever a way I can be helpful as you navigate the new chapter, feel free 
to reach out."

This is not transactional. It is the maintenance of a professional relationship. Employees who are treated well at departure become:

• Alumni who speak positively about the team in the talent market
• Potential boomerang hires (28% of leavers, per Workforce Institute data)
• Client referrers in their next roles
• Professional references for team members who move on next

Rules

• Control the communication sequence — team should hear before they find out informally; departing employee should have the option to tell their own story first
• Document knowledge before it walks out the door — the departing employee writes it; the manager defines scope and reviews completeness; block calendar time in week 1
• Address team morale explicitly — "we'll be fine" without a plan creates more uncertainty, not less; name what is changing, what you're doing about it, and what questions you'll answer
• Treat the final weeks as management responsibility — ghosts, overloads, and logistical-only endings produce bitter departures; maintain the relationship through the last day
• Conduct a final candid conversation — departing employees are your most candid feedback source; use it

Common Mistakes

• HR announces the departure before the employee's team knows: co-coordinate announcement sequence; the team should know before the org-wide email goes out.
• "Knowledge transfer" that means "write it down somewhere": documentation without walkthroughs produces incomplete transfer; record and review walkthroughs.
• Immediately posting the role before telling the team: if team members see the job posting before they've been told about the departure, the sequence signals that headcount mattered more than people.
• Skipping the final manager feedback conversation: the honest exit data is irreplaceable; most managers skip it out of awkwardness; the information cost is high.
• No alumni follow-up: one message six weeks after departure costs 5 minutes; the relationship asset it preserves is significant.

When NOT to Use

• For involuntary departures (layoffs, terminations) — the offboarding process for involuntary departures involves HR, legal, and a different communication strategy; follow the organization's process rather than this one.
• When there is no notice period — if an employee departs immediately (for cause, or in some voluntary departures), compress Steps 2–3 and focus exclusively on emergency knowledge triage and team communication.