The first 24 hours after a key employee resigns: what to tell your team and clients

One person leaving affects many colleagues

On Monday, the lead designer hands in her notice. The manager is worried about deadlines, the sales team are asking about clients, and her colleagues are trying to work out whether they should be looking for a new job too. Research by Felps and colleagues on turnover “contagion” suggests that co-workers’ job-search behaviour and their ties with colleagues can influence individual decisions to leave. That does not mean one resignation will automatically trigger a wave of others.

The biggest mistake is to react as if the employee’s decision were an attack on the company. Saying “You’re leaving us at the worst possible moment” can sour the working relationship during the notice period. It is better to treat the departure as a fact that calls for a good handover. In the first few hours, what counts is the order of conversations and keeping the work going, not looking for someone to blame. If the manager stays calm, it is easier to set priorities without making unnecessary promises.

Talk to the person who is leaving first

Your first question doesn’t have to be “Where are you going?” The employee may not want to reveal their new employer or the personal reasons behind their decision. It is enough to acknowledge the resignation, agree the next formal steps with HR and ask what needs to be handed over. You might say: “Thank you for telling me directly. I’d like us to work out how we keep current tasks covered and when it would be best to let the team know.”

Give them room to explain briefly why they are leaving, but don’t make it a condition of parting on professional terms. If you want to talk about trying to keep them, separate that from the organisational questions. A hasty counter-offer should not hold up the plan for keeping work going. Agree, too, who will inform clients and how much they will be told. Being caught off guard does not justify unilaterally announcing someone else’s decision along with details that don’t need to be shared.

Before you announce the departure, settle five specifics

You need: the leaving date, the person responsible for communication, a list of urgent tasks, cover until the work has been handed over, and the date of the next update. Not every element will be ready on day one. Whatever has not yet been decided should be named openly. If you ask the team for suggestions on cover, don’t hand them responsibility for the decision at the same time. Someone has to have the authority to set priorities.

Prepare a short working note that does not turn into a public catalogue of the departing person’s problems. “Project A needs a decision by Friday, client B is waiting for a reply, work on contracts C is still in progress” – these are useful facts. “Nothing works without her” is an emotional judgement that puts extra weight on the team. The best plan for the first day is short, assigns owners and shows which questions will only be settled later.

The team needs the news and a new work plan

Say: “Anna has decided to leave and will finish on the agreed date. We’d like to thank her for her contribution to the project. Specific people will temporarily take over the most urgent tasks, and on Thursday we’ll present the plan going forward.” Don’t add judgements such as “she chose the money”, “she got scared of the changes” or “she walked out on the company”. If there is no agreement yet to share details, limit yourself to the information needed to organise the work. People can ask questions, but not everything about someone else’s life calls for an answer.

Often the greatest anxiety comes from the unspoken expectation that everyone else will absorb the extra work. If three people are to take over one person’s duties, say which tasks have been put on hold and for how long. Don’t pretend the departure won’t affect deadlines. Let the team flag risks without being accused of “spreading panic”. Research on turnover and team performance shows relationships that depend on context, not a simple rule that losing a specialist always causes the same damage.

Explain to clients who will take over their work

An important client hears by chance from an acquaintance that their account manager is leaving. They start to wonder whether the project is at risk. That is why, before any external conversation, you need to establish who takes over the contact, where decisions sit and what will happen to open commitments. The message might be: “From next Monday, Marta will take over the project. Anna will hand over the documentation and everything agreed so far to her beforehand. The date of our next meeting stays the same.”

Don’t describe to the client any conflict with the company, or the departing employee’s health, family situation or new employer. If the change affects a deadline, say so straight away and offer a realistic alternative. The client will judge, above all, whether they have a contact who is responsible and whether they can still count on what was promised. Honest information about limitations is better than a reassuring “nothing will change” that won’t survive the first delay.

Start the knowledge handover with risks and decisions

The easiest thing is to ask the person who is leaving to “put everything on the drive”. That produces plenty of files, but it doesn’t show what has to be done tomorrow. First collect the open decisions, client dependencies, critical points and deadlines. Only then turn to documents, instructions and contacts. For each matter, agree a new owner and a way of confirming that they understand what has been handed over. That way the team doesn’t discover a week later that the most important piece of information was missing from the folder.

The first 24 hours are the start of a process, not a deadline for completely replacing an expert. Plan short knowledge-transfer meetings and check that the people taking over responsibilities feel free to ask questions. At the end, it is worth thanking the departing person in a way that reflects your actual relationship, without forcing a ceremony. People remember not only why someone left, but also how the company treated them in their final weeks.

After a key employee resigns, what matters most is the order in which information is shared, a calm conversation and a realistic plan for handing over tasks. First establish the facts with the person who is leaving, then tell the team what changes in their work, and give clients the new contact arrangements. You won’t solve every problem on the first day, but you can prevent chaos, gossip and hidden overload for those who stay.

How Empatyzer helps you structure the first conversations after a resignation

A manager learns one morning that the person leading two major projects is leaving. Before sending an emotional message, he describes three separate situations to Em: the conversation with the employee, the announcement to the team and the update for clients. Em helps him organise the information to be shared, prepare questions about taking over responsibilities and work out how to keep anxiety from turning into accusations. For the team, Em prepares an announcement that takes into account people’s different needs for predictability without revealing private details about the person who is leaving. If context about the manager’s relationship with her is available, Em can also suggest how to set the tone for the handover meeting. The manager asks to rehearse a reply to the question: “So are we supposed to do the work of two people now?” Em helps him name the need to change priorities instead of offering an empty promise. The result is practical: three consistent conversations, clear agreements and a list of decisions to be made. The company remains responsible for formal announcements and for reallocating duties.