When to Tell Your Direct Reports You're Leaving

Tell your own manager and HR first, then your direct reports in a same-day one-on-one, then the wider team within hours. Most managers should break the news to their reports two to three weeks before their last day. Any earlier and the team spends weeks grieving a leader who is still in the room. Any later and they hear it from someone else.

You already know you are leaving. The question is when each person on your team hears it, and in what order. Get this wrong and the news reaches your reports from a Slack thread, a calendar invite, or a well-meaning peer. That is the kind of first impression of your departure that is impossible to take back.

This is a timing guide for managers, not a script. If you want the words, the last 1:1 with your own manager is a useful starting point for the top of the sequence. What follows is the clock.

Here's the short answer: a 72-hour sequence

Most clean manager exits follow the same four-step cadence over roughly 72 hours. The exact spacing bends to your company, but the order rarely should.

1. Hour 0 — You tell your own manager, in person or on video. This is the resignation itself.
2. Hour 0 to 24 — HR is looped in and your last day is confirmed in writing. Nothing else happens until this is done.
3. Hour 24 to 48 — Each direct report gets a private one-on-one, same day where possible, in reverse seniority or risk order (more on this below).
4. Hour 48 to 72 — The wider team and cross-functional partners hear it in a scheduled standup or a short written announcement.

Keep the gap between step three and step four under one working day. If a direct report hears Monday morning and the team-wide note goes out Thursday, you have created a three-day secret that someone will leak.

Two to three weeks: the window that usually works

Companies in the United States tend to assume two weeks of notice. For an individual contributor that is often enough. For a manager it is tight. You have a transition document to write, open roles to backfill, upcoming reviews to hand off, and relationships to pass on. Three weeks gives the team a chance to actually absorb the change.

Four weeks or more is a different animal. You keep the clarity of knowing, your team keeps the awkwardness of a leader who is one foot out the door. Decisions start getting deferred to the next person. If your contract requires a long notice period, stay deliberate about being useful. If it does not, three weeks is a strong default.

Under two weeks is almost always a signal that something else is wrong: a bad exit, a counter-offer that fell through, a surprise competing offer. If you are forced into a one-week window, the sequence above compresses into 24 hours, not 72. Everyone hears on the same day.

Why the "manager first, then HR, then reports" order is non-negotiable

This is the step people are most tempted to cut corners on, especially if they are close with their team. The temptation sounds like: I owe my reports a heads-up before the official channel.

You do not. You owe them a boss who still has standing to go to bat for them on the way out, which means not blindsiding your own manager. You owe them clarity about who their new manager will be, which means letting HR work the backfill. And you owe them discretion, which means not asking them to keep a secret from leadership.

A report who finds out before your boss does becomes an unwilling accomplice. They have to pretend not to know in the hallway. They have to decide whether to tell their peers. They start carrying your resignation for you. That is not a kindness. It is a transfer of load.

Tell your own manager first. Give HR a day. Then move fast on the one-on-ones.

The order of the one-on-ones

Not every direct report hears at the same hour. Someone goes first and someone goes last. Choose on purpose.

Three good orderings, pick the one that fits:

• Risk order. The report most likely to be destabilized hears first, from you, in a room with a door. Usually this is a newer hire, a report in the middle of a tough project, or a report who was counting on you specifically for promotion. The goal is to hand them certainty before the rumor arrives.
• Succession order. If one of your reports is a candidate to replace you, they hear first. They need a quiet half-day to decide whether they are interested before the question is public.
• Reverse seniority. Your most tenured report hears last, because they are the one who has seen this movie before and will handle a two-hour wait with grace. Everyone else goes first.

Whichever ordering you pick, know who is actually on the list. Dotted-line reports, former direct reports you still mentor, borrowed engineers from the project last quarter — they all deserve a slot. If your mental list stops at the formal org chart, you will miss half the people who worked for you. A quick calendar sweep with It Was Great Working With You surfaces the real list in a few minutes.

Then keep the window tight. If the first one-on-one is at 9am, the last one should be before lunch. The window where "some people know and some do not" is the window where trust corrodes.

What a direct-report one-on-one actually sounds like

Keep the opening clean. No throat-clearing, no "I have something to tell you" overture.

Try: "I wanted to tell you first before the wider team hears. I've resigned. My last day is the 24th. I wanted you to hear it from me, in this room, before anything else happens today."

Then stop talking. Let them react. Give them one full minute of whatever they need, which might be a question, might be silence, might be a thank-you.

Then cover three practical things, in this order: what the backfill plan is as far as you know, what will happen to their current projects, and whether you can be reached after you leave. Keep the whole conversation under 20 minutes. There will be time for the longer version in the next one-on-one.

The announcement to the wider team

By the time the all-hands or Slack post goes out, every direct report has already heard. The announcement is for the cross-functional partners, the adjacent teams, the people who had standing meetings with you.

Keep it to five lines. The news. Your last day. Who to escalate to in the interim. One line of thanks. A link to your calendar for 15-minute goodbye slots if you can offer them.

Resist the temptation to make this message the real goodbye. The real goodbye is in the one-on-ones you have already had and the ones you are about to have over the next three weeks. A long farewell post before you have even sent any personal messages reads like a eulogy for yourself.

If you need help deciding who gets a personal note on top of the broadcast, this guide to who deserves a personal goodbye message is a good starting point. Direct reports almost always do, and the message is usually different from the one you send a cross-functional partner.

Before the one-on-ones, know who is actually on the list

Here is the part most managers skip. Before you start booking those one-on-ones, you need a complete picture of who matters: the direct reports, yes, but also the former direct reports you still mentor, the dotted-line reports in other orgs, the two engineers you borrowed from infra last quarter, the designer who sat in on your weekly review. Each of those people deserves to hear from you, not from a Slack thread.

Your calendar already holds that list. It is not organized, and it is probably buried under a year of standing invites, but every real working relationship you have shows up there eventually. The problem is pulling it out before your last day pulls it away from you.

Four timing mistakes managers make

Watch for these. They are the ones that show up over and over.

1. Telling one trusted report "unofficially" a week early. This never stays contained. Even the most loyal report has one person they share bad news with. By Friday the whole team knows and you have broken the sequence.
2. Waiting until the all-hands to tell direct reports. Finding out your boss is leaving at the same moment as 200 strangers is a specific kind of betrayal. Do not do this, even once.
3. Scheduling the one-on-ones with a 90-minute gap in between. The person at 11am sees the person who had the 9am meeting walk out shaken, puts the pieces together, and feels like they were the backup slot. Keep the gaps to 15 minutes.
4. Dropping the news at 4:30pm on a Friday. Your team then spends the whole weekend processing without you. Tell them in the morning so they can ask you questions the same day.

What if the news is going to leak?

Sometimes HR fumbles the backfill posting. Sometimes a vendor congratulates you on LinkedIn. Sometimes a peer at your new company tweets before the ink is dry. When any of this happens the sequence collapses to one step: tell your direct reports in the next hour. By text if they are remote. By walking over to the desk if they are in office.

A rushed one-on-one you initiated is survivable. A one-on-one someone initiates with you because they already heard, is not. The first version keeps the trust. The second version spends it.

The timing in one line

Your own manager hears first. HR hears next. Each direct report hears from you, privately, within 24 hours of HR. The wider team hears within 48 hours of that. The last day is two to three weeks out. Everything else is detail.

Before any of those conversations happen, make the list. Pull your calendar, see who you have actually been working with, and decide who gets a one-on-one, who gets a personal message, and who gets the group note. It Was Great Working With You builds that list from your calendar in a few minutes, so none of this falls through on a Thursday afternoon when four people are waiting on your Slack.

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