How to tell the team that someone is leaving
Echipa HR 365 · reviewed 2026-09-10 · 5 min read
A departure announcement is read by the team as a precedent: this is how they will talk about me. Which is why the wording matters more than it seems, and the difference between a resignation and a company-initiated exit is smaller than you would think — in both cases you say little, accurately, and without explanations you cannot stand behind.
The order and the timing
Who finds out and when
- The person leaving — agrees with you what is said and when — in a resignation, they have a say
- Those who work with them directly — individually or in a small group, before the general announcement
- The team — from you, the same day, not through rumour
- The wider organisation and external partners — after the team, with the name of whoever takes over
The four sentences
| Part | What you say | What you do not say |
|---|---|---|
| The fact | “X is leaving the team, their last day is [date]” | No speculation about the reason |
| The acknowledgement | One concrete thing they did well | No generic superlatives |
| Continuity | Who takes over and from when, area by area | Not “we will see”, if you already know |
| What comes next | Whether you are recruiting, when, and what changes meanwhile | No promises about a replacement if none are decided |
The third part is what the team listens to most closely, whatever is said in the others. Their first practical question is not why the person is leaving but who now does the things they did — and if the answer is missing, they will work it out themselves, usually in the version worst for them.
How much you say about the reason
For a resignation: whatever they agreed could be said, and nothing more. “They are moving on to another project” is enough, even if everyone senses more. For a company-initiated exit: nothing about the reason, ever — not even by implication, not even if pressed.
The reason the rule is absolute in the second case is not legal but practical: any explanation, however justified, is a conversation about someone who is not in the room and cannot answer. And that is precisely what the team remembers.
What follows in the team
- Questions about their own security, especially after an exit. Answer directly, not evasively.
- Concern about workload. It is legitimate and deserves a concrete answer, not encouragement.
- A period of personal reassessment: at least one person will consider leaving too. That is normal, not a crisis.
- Rumours, if the announcement was too vague. An information vacuum always fills with the worst version.
The second reaction is worth preparing for. “We will manage” is not an answer; “until we replace them, X takes over the reporting and the monthly analysis slips by two weeks” is. Even when the news is unwelcome, clarity settles people more than optimism does.
What if someone insists on knowing the reason?
Say once, clearly, that you do not discuss the reasons for a person’s departure — and add that you would not discuss theirs either. The second half is what closes the subject, because it explains the rule rather than merely applying it.
Do I organise a farewell?
Ask the person. For a resignation, usually yes; for an exit, often not, and you do not press. The rule is that the form is chosen by the person leaving, not by the company.
What do I tell clients or partners?
The name of whoever takes over and from when, and that is all. No explanations about the departure — for them, the only relevant information is continuity.
Where to start
Before the announcement, write down who takes over each area and from when. If you cannot complete the list, you are not ready to announce — and the question will come within the first thirty seconds.
Then ask the person leaving what they want said. It is a one-minute conversation that changes how the whole rest of the day is experienced, on both sides.
The period between the announcement and the last day
The most awkward part and the worst handled. The person is still there, but everybody knows. Without a clear position from you, a kind of strained politeness sets in where nobody speaks to them normally any more.
| Do | Do not |
|---|---|
| Keep them in the discussions that still concern them | Remove them from everything, “so as not to burden them” |
| Give them real work, right to the end | Leave them with nothing to do |
| Schedule the handover as an activity with allocated time | Hope the handover happens by itself |
| Talk normally about the team’s future in front of them | Wait for them to leave the room before discussing it |
The second row has a direct effect on handover quality: someone excluded from the work in their final two weeks has neither the motivation nor the context to document what they know. What you save in discomfort you pay in lost information.
When several people leave in the same period
Two or three departures close together completely change the nature of the announcement: the team no longer reads isolated events, it reads a pattern. What works is to name it yourself, before they do — and to say what you know about the cause, if you know anything.
Handover and takeover of work, as tasks with an owner
Who takes over each area is decided and visible before the announcement — so the question about continuity has an answer the moment it is asked.
Free account, every module for 7 days, no card required.