How to Tell Your Team You're Leaving: A Manager's 48-Hour Script

Here's the short answer: tell your own manager first, ask for one business day to plan, then announce to your direct reports inside 48 hours. Hold a brief group meeting, follow it the same day with 15-minute one-on-ones with each report, and send a written summary by end of day so nothing important is left to hallway gossip.

Your manager has just absorbed the news. You now have one or two business days before the question "is something going on with the team?" starts circulating. The next 48 hours are not about your resignation letter. They are about the people who reported to you, and the order you tell them in.

Resigning as a manager is a different problem from resigning as an individual contributor. Your departure changes their week, not just yours. Done well, your team has clarity by day one. Done badly, they hear it from someone who heard it from someone.

If you are still working out how to tell your own boss first, our three-sentence resignation script for managers is the upstream step. None of the moves below should happen before that conversation is done.

Hour 0 to 1: your manager knows. Now do nothing.

The most common mistake in the first hour is texting your closest report to "give them a heads up." Don't. A private heads-up to one report before the group hears it creates an information hierarchy that becomes resentment two weeks later. The same goes for telling your peer manager, your mentor inside the company, or anyone in a Slack DM that might get screenshotted.

Use this hour to ask your manager for one specific thing: a 24-hour window before the announcement, so you can plan the order. Most managers will say yes. If yours pushes for same-day, ask for two hours to book the meetings cleanly.

Hour 1 to 4: write the list, not the speech

Before you draft a single line, write four lists on one page.

1. Your direct reports, in the order you will speak to them in the one-on-ones (more on order below).
2. The reporting line above you: your manager's manager, your manager's peers if your team crosses orgs.
3. Cross-functional partners: peer managers, senior ICs your team depends on, key external partners or clients with active work.
4. The people who quietly shaped your time there: the senior sponsor who fought for budget, the IC who mentored your weakest hire, the cross-team peer who unblocked you twice a quarter.

Only lists 1 and 2 get told in the first 48 hours. List 3 hears within the first week. List 4 is the personal-goodbye list you will write over the next two weeks. The point of writing all four now is so you do not lose names to the rush.

Hour 4 to 24: book the meetings

Block your calendar before you tell anyone. The shape that works:

• A 30-minute group meeting with your direct reports on the morning of the announcement day. Title it neutrally — "Quick team sync" — so the calendar invite does not pre-announce.
• A 15-minute one-on-one with each direct report, all scheduled the same day, immediately after the group meeting. Do not space these out across the week. Same-day clarity matters.
• A 10-minute skip-level note to your manager's manager, ideally before the group meeting that morning.
• A 30-minute slot at end of day to send the written summary email.

If you cannot fit it all into one day because of timezones, hold the group meeting and the same-day one-on-ones for the people who can make it, and call the rest individually by phone or video that same evening. Do not let anyone read about your departure in a Slack channel.

Hour 24 to 26: the announcement

The group meeting script is short on purpose. Five beats, three minutes, then questions.

Beat 1 — the news, first. "I want to tell you something before you hear it from anyone else. I have given my notice. My last day is [date]."

Beat 2 — the why, in one sentence. Future-facing, no criticism of the company, no oversharing about the new role. "I am moving on to a role that takes me in a direction I have wanted to explore for a while." That is enough. Repeat it if asked.

Beat 3 — the handover plan, in three sentences. Who they will report to during the gap (usually your manager temporarily), what continues unchanged, what you will personally finish before you go.

Beat 4 — what you can answer now and what you cannot. "I can tell you about timing and my handover. I cannot tell you yet who your new manager will be — that decision sits above me." Naming the boundary stops the meeting from spiralling into speculation.

Beat 5 — the next step. "I have blocked time with each of you today. I want to spend 15 minutes one-to-one before end of day."

Then stop talking. Take questions for the remaining time. If nobody asks anything, give them the closing line — "I will see each of you shortly" — and let the meeting end early. Do not fill silence by speculating.

Hour 26 to 30: the one-on-ones

Order matters here in a way most managers do not think through. Take the most-affected person first: the one mid-project, the one you hired last quarter, the one whose career conversation you owe. Save the lower-stakes one-on-ones for the back of the day. By then you will be tired, and that is fine — the people who need a clear-headed you should not be at the end of the line.

Each one-on-one is three beats: acknowledgment of how this lands for them specifically, your plan for their open work, and an ask. The ask is the part most managers skip. It can be small. "Can you walk me through what you still want me to finish before I leave?" — that question gives them agency in a week when agency feels stripped.

What to leave out of the one-on-ones: do not promise to keep mentoring them after you leave unless you mean a specific thing on a specific cadence. Do not pre-criticise whoever will replace you. Do not reveal your new role unless they ask directly and you are comfortable saying. The team will form opinions about your new role from the title alone — keep the focus on them, not on what you are walking toward.

Hour 30 to 48: the written summary

End of the announcement day, send a short email to the team. Bcc your manager. Four sentences is plenty.

One: confirm what was said in the meeting (one line). Two: your last day. Three: who is the transition contact for what (split admin from technical handover if your team needs that). Four: that you will follow up on the people-handover one-on-one with each of them this week.

If you have not started a handover document yet, this is the night to begin one. Our five-section knowledge transfer template is the simplest place to start — your replacement will need the people-and-projects view before they need anything else.

This is also where the second-list problem begins. You have spoken to your direct reports. You have spoken to your boss's boss. You still have ten to forty other people across the company who shaped your work — peer managers, cross-functional partners, the senior IC who mentored your weakest report through Q2, the skip-level who fought for your team's budget last cycle. None of them appear on the org chart you will forward to your replacement. All of them deserve a personal note before your last day.

It Was Great Working With You builds that second list from your calendar in under three minutes. It pulls the people you actually met with across the last twelve months — including the cross-functional partners, senior sponsors, and quiet contributors you would forget when scanning Slack alone — and gives you a ranked starting point for the personal-goodbye list most managers never write.

Edge case: one of your reports is on PTO

Do not announce to the group without them. Phone or message them the morning of the announcement, give them the news in one sentence, and tell them you will catch them up properly when they are back. They will appreciate not being the last to know more than they will appreciate not being interrupted on holiday.

Edge case: remote teams

Run the group meeting on video, cameras encouraged but not enforced. Do not pre-announce in Slack. Use the same five-beat script. The one-on-ones are also video, not Slack DMs — your team is reading your face for whether the company is in trouble, and Slack does not transmit that signal.

One small adjustment for distributed teams: send the written summary email earlier — within a few hours of the meeting, not at end of day. Quieter team members in different timezones often need the written version before they will ask the questions they actually have.

Edge case: this was a layoff, not a resignation

If you are the one being let go, the sequence is different — you are not the one announcing, and the rules above mostly do not apply. The relational work still does. The layoff goodbye email playbook covers what to say, what to leave out, and how the personal notes still matter even when the official goodbye is rushed.

Three mistakes managers make in the first 48 hours

Telling your strongest performer privately first. This is the most common failure. The reasoning sounds caring — "they will take it hardest, I want them to hear it from me directly" — and the impact is the opposite. They feel singled out, the rest of the team finds out and feels excluded, and you have created a two-tier announcement. Tell the group first. Spend the longest one-on-one with your strongest performer.

Promising vague keep-in-touch. "I will stay in touch professionally" lands as a non-promise even when you mean it. If you mean something specific — a coffee in six weeks, a Slack-Connect channel, a standing call once a quarter — name the specific thing. Otherwise leave the door open without promising to walk through it.

Underestimating the feelings part. Most managers over-prepare the logistics ("who reports to whom on day 31") and under-prepare for the emotional layer of the meeting. Your direct reports do not need every transition detail in the first 30 minutes. They need to see you acknowledge that you are leaving people you cared about. Two sentences of that is worth more than five paragraphs of handover scaffolding.

What to actually finish before your last day

The 48-hour script gets the announcement clean. The two weeks that follow are where the real handover happens — and where most managers run out of time before they have written personal notes to the people who shaped their time there. Do the relational work in parallel with the operational handover, not after. Start the personal-goodbye list the same evening you send the team summary email.

The job of the next two weeks is to leave the team in better shape than they would be in if you were simply hit by a bus. The job of the same two weeks, in private, is to thank the people the org chart does not name. The list is at itwasgreatworkingwithyou.com.

Further reading: The people you'll forget to say goodbye to when you leave your job.