Offboarding checklist: when someone leaves the team

A good offboarding checklist helps you at exactly the moment you are least prepared for as a leader: someone on your team asks for a quick chat, closes the door and tells you they are leaving. The next few weeks decide whether the team feels this departure as a hole or as a cleanly passed baton.

This topic matters to me because many teams now take onboarding seriously, while its counterpart is almost always improvised. Yet just as much happens when someone leaves: knowledge walks out the door, roles open up, and the team watches very closely how a person who is not staying gets treated. This guide gives you a four-phase process, a knowledge inventory, exit interview questions and a complete checklist.

In short

Offboarding is a leadership task, not an HR form: how you handle a departure shapes the trust of the people who stay. Pass on knowledge in handover pairs, not piles of documents. The biggest obstacle is time: the last weeks are always shorter than you think.

What you will learn in this article

• How to respond in the first conversation after a resignation
• In which order to inform the team and stakeholders
• How a knowledge inventory with handover pairs works
• Which questions belong in the exit interview and who should run it
• How the team reassigns roles after someone leaves

Why offboarding is a leadership task

Many teams treat a departure as an administrative process. HR, return the laptop, revoke access, done. That is necessary, but it is not enough. For your team, a departure is a social event. People wonder why someone is leaving, who will take over the work and whether they missed something themselves.

It is also worth taking an honest look at the numbers. In 2019, Gallup surveyed people who had voluntarily left their jobs. 52 percent said that their boss or their company might have been able to keep them. And 51 percent reported that nobody had spoken with them about how satisfied they were or where they were heading during their final three months. The study comes from the US, so I would not transfer the percentages one to one. Still, the direction is clear to me: many departures announce themselves, but nobody asks. How to have these conversations while there is still time is covered in the guide to the stay interview.

So offboarding really starts before the resignation, namely in your recurring one-on-ones. Once the decision has been made, though, the focus shifts, and that is exactly what an offboarding checklist is for: a good farewell for the person, a clean handover for the team and a few lessons for you.

The four phases of offboarding from the resignation to the team retro

The first 48 hours after a resignation

The first two days set the tone for everything that follows. During this time you want to achieve three things: show the person that you respect their decision, agree on a rough schedule and decide who finds out when.

The first conversation: listen instead of persuading

The first reaction is often a reflex. Some leaders go quiet, others immediately start negotiating. Neither helps much. Thank the person for being open, ask follow-up questions if they want to talk, and give them space if they don’t. A sentence like “Thanks for telling me directly. Would you like to share how this came about?” is all you need.

Avoid questions that sound like an interrogation, and don’t make promises you can’t keep. By the end of the conversation only two things need to be settled: you will meet again in the next few days to plan, and until then the news stays between the two of you (and HR, if that is how things work in your company).

Announcing it to the team

GitLab, for example, describes a good process in its public handbook: for voluntary departures, the person and their manager review the message together first. The direct team hears it first, then the key stakeholders, and only then the wider group. I think this order is right. Nothing is more awkward for a team than hearing about a departure from another department.

The person should be allowed to decide whether to tell the team themselves or whether you do it. What matters is that the announcement contains more than “X is leaving us”, namely a first sentence about the plan: when the last day is and that you will tackle the handover together. That takes the energy out of the rumor mill. This is why the announcement sits at the top of my offboarding checklist.

Separations initiated by the company follow different rules. There, HR and legal usually take the lead, communication is brief, and details don’t belong in the team. This guide focuses on voluntary departures.

Offboarding checklist for the knowledge handover

The biggest mistake in knowledge transfer is the sentence “Please write everything down.” The result is a long document that nobody reads, written under time pressure by someone whose mind is already halfway elsewhere. An offboarding checklist with two steps works better: first an inventory, then targeted handovers.

Step 1: a knowledge inventory in 45 minutes

Sit down with the person and go through these areas together. For each item, note whether it needs a handover and to whom.

The question “What do only you know?” is the most important one in the whole table. It shows you where your team has a bus factor of one. The bus factor describes how many people would have to drop out before a topic comes to a standstill. At one, it is exactly this person.

Step 2: handover pairs instead of piles of documents

For every topic in the “Knowledge in your head” column, you form a pair: the person leaving and someone who takes over. The two of them work through real tasks together, first with the leaving person in the lead, then with the roles switched. Only what comes up during this joint work gets documented. These notes are shorter and much more useful than a farewell document.

Schedule fixed slots for this, for example two blocks per week. Without a fixed slot, day-to-day business always wins. Also make sure not to dump everything on a single person in the team. Otherwise you are only moving the bus factor around.

What cannot be handed over

Relationships, experience and gut feeling cannot be passed on completely. That is fine. Tell your team honestly that some things will run more slowly after the departure, and plan buffer time for it. Pretending that everything is back to normal after three handover sessions puts unnecessary pressure on the successors.

Counteroffer or letting go?

I have a clear opinion here: a last-minute counteroffer is almost always a band-aid. When someone resigns, salary is rarely the only reason. Usually it is about prospects, tasks, collaboration or leadership. A higher offer changes none of that, it only postpones the question by a few months.

There are exceptions, for instance when a clear, solvable reason is on the table that you simply didn’t know about before. Then you may ask whether a change would make a difference. Pressure or guilt, however, have no place in this conversation. The more honest consequence is usually a different one: listen earlier, so it doesn’t get that far in the first place.

The exit interview: questions that actually reveal something

An exit interview is a structured conversation in the last days, in which the leaving person gives feedback on the team, the work and leadership. A case study by Everett Spain and Boris Groysberg in Harvard Business Review shows how much such conversations can achieve: a financial services company had hired a new manager for 17 people, and after one year only eight of them were still on the team. The exit interviews revealed weaknesses of this one manager and, behind that, a pattern in the system: promotions were based on technical skills instead of leadership skills. The company then changed its promotion process.

Who should run the conversation

If you are the direct manager, you will rarely get the whole truth. That is human, because nobody wants to burn bridges on the way out. It is better if someone outside the direct reporting line runs the conversation, such as HR or a leader from another area. You can additionally hold a personal closing conversation, which can be warmer.

Questions for the exit interview

These questions work well because they are concrete and forward-looking:

• When did you first seriously think about leaving, and what was going on at the time?
• Could anything have made you stay, and if so, what?
• Which things should the team never change?
• What would you advise your successor in their first week?
• What feedback would you still like to give me as a leader?

Write down the answers and read them side by side after three or four departures. Individual statements are opinions, recurring statements are signals.

Access, reference letter and formalities

Even if the human part matters more, the formal part belongs on every offboarding checklist. Clarify early with HR who takes care of what.

Access to systems, repositories and communication channels should reliably end on the last day. GitLab’s handbook, for example, names 24 hours as the target for critical tools. If you use AWS IAM Identity Center, you can even automate the removal of permissions, as I show in Identity Center EventBridge: automating offboarding. This also includes transferring ownership of documents, calendars and channels beforehand so that nothing is orphaned.

In Germany, there is also the reference letter (Arbeitszeugnis). Under Section 109 of the German Trade Regulation Act (Gewerbeordnung), employees are entitled to a written reference when their employment ends, on request including statements about performance and conduct. It must be clear and understandable and must not contain hidden messages. Other countries have different rules, and HR usually handles the process. I am not a lawyer, so if in doubt, ask them. Your contribution as a leader is an honest, concrete assessment that is not written at the last minute.

Shaping the farewell, remote too

A farewell doesn’t have to be big, but it should happen. A last team breakfast, a short round on a video call where everyone says one sentence, or a digital card. Remotely, it is especially easy for someone to simply go offline on their last day and that’s it. That feels wrong for both sides.

Also talk about how you will stay in touch. Some companies have alumni networks, in others a profile on a professional network is enough. People who leave on good terms recommend you or eventually come back. You want to keep that door open.

What the team learns after a departure

A few weeks after the last day, a short team retrospective is worth it, meaning a moderated session for looking back. The focus is on the team and its work. These questions help:

1. Which tasks have been left undone since the departure?
2. Where are we missing knowledge that we didn’t miss before?
3. Which roles do we need to reassign, and who would like to take something on?
4. What will we do differently next time someone leaves?

Use the opportunity to consciously reassign responsibility, too. The levels of delegation help you agree with each person on how much decision-making room they get for a new topic. Add the answers to question 4 directly to your offboarding checklist. And when a successor is hired, the circle closes with good onboarding for the first 30 days.

Common offboarding mistakes

Some patterns keep showing up, and an offboarding checklist helps you avoid them:

• The handover only starts in the last week because there is “still so much to do” before that.
• The team hears about the departure indirectly instead of directly.
• All the knowledge ends up with the one person who already carries the most.
• The exit interview happens, but nobody ever reads the notes again.
• On the last day, nobody is there to say thank you.

The complete offboarding checklist

To tick off, from the resignation to after the last day:

• First conversation held, thanks said, next meeting scheduled
• Process clarified with HR (last day, remaining vacation, reference letter)
• Announcement written together: first the team, then stakeholders, then the wider group
• Knowledge inventory done and handover pairs formed with fixed slots
• Recurring tasks and meetings reassigned, ownership transferred
• Exit interview planned with a neutral person
• Farewell organized and a way to stay in touch agreed
• Access removed on the last day and verified
• Team retrospective held after a few weeks

FAQ

How long does good offboarding take?

Ideally, as long as the notice period. Plan the knowledge handover for the first two weeks, because remaining vacation, the farewell and formalities pile up in the last days. With short notice periods, the phases run in parallel.

Who is responsible for offboarding?

Formal matters such as contracts, the reference letter and hardware usually lie with HR and IT. The handover, communication within the team and the farewell are the job of the direct manager.

Should the manager run the exit interview themselves?

Preferably not alone. Many people speak less openly with their direct manager on their way out. A neutral person from HR or another area often gets more honest answers.

What belongs in an offboarding checklist for managers?

The first conversation, the order of the announcement, a knowledge inventory with handover pairs, the exit interview, access and the reference letter, a farewell and a team retrospective afterwards.

Your next step

You don’t have to wait for someone to resign to use the offboarding checklist. Take the “What do only you know?” question from the knowledge inventory and go through it with your team this week, without any occasion. Every topic with a bus factor of one is a candidate for a handover pair, and that means now, not during the notice period.

How does it work for you: is there a fixed process in your team when someone leaves, or do you improvise every time? Feel free to share it in the comments.

Continue the series: Back to the “Leadership in brief” overview · Previous part: Remote onboarding: planning the first 30 days. Next part: Stay interview: holding stay conversations.

Sources

• Gallup: This Fixable Problem Costs U.S. Businesses $1 Trillion (Shane McFeely, Ben Wigert, 2019)
• GitLab Handbook: GitLab Offboarding
• Harvard Business Review: Making Exit Interviews Count (Everett Spain, Boris Groysberg, 2016)
• Gesetze im Internet: Section 109 Gewerbeordnung (reference letter, German)

This post was created with AI assistance.

---

👉 Next step: Preparing a first one-on-one? My question cheat sheet puts the best questions on one printable page.

Originally published on sascha-ms.de. More articles on serverless, AI in everyday development and leading tech teams: sascha-ms.de/en