Skip to main content
Guides After the offer Resigning as a Manager — Telling Your Team, Your Skip, and Your Reports in the Right Order
After the offer

Resigning as a Manager — Telling Your Team, Your Skip, and Your Reports in the Right Order

9 min read · April 25, 2026

Resigning as a manager is a sequencing problem: protect trust, reduce team anxiety, and avoid surprising the wrong people. Use this order, scripts, and transition plan to leave cleanly without creating chaos.

Resigning as a manager is different from resigning as an individual contributor because your departure immediately creates uncertainty for other people. Your direct reports wonder who will evaluate them, whether priorities will change, and whether you knew something they did not. Your manager needs a transition plan. Your skip-level leader may care about retention risk. The order matters: tell the right people at the right time, keep the message consistent, and do not let your team learn through rumor.

This guide explains how to resign as a manager, who to tell first, what to say to your boss, your skip, and your reports, and how to build a transition plan that protects the team after you leave.

The right order for resigning as a manager

Use this sequence unless your company has a specific policy:

  1. Accept and clear contingencies for the new offer. Do not resign on a verbal offer or before key contingencies are resolved.
  2. Tell your direct manager privately. This is the formal resignation moment.
  3. Align with your manager on communication plan. Decide timing for skip-level, HR, peers, and direct reports.
  4. Tell your skip-level leader if appropriate. Usually after your manager knows, sometimes in the same day.
  5. Notify HR through the required process. Follow policy, but do not let HR be the first human conversation if you have a real manager.
  6. Tell your direct reports live. Do this quickly after leadership alignment, not days later.
  7. Tell peers and cross-functional partners. Share transition contacts and continuity plan.
  8. Send written transition summary. Document responsibilities, risks, decisions, and recommended interim ownership.

The biggest mistake is telling favorite employees or peers before your manager. The second biggest is waiting too long to tell direct reports after leadership knows. Once leaders know, rumors travel fast.

Before you resign: prepare the transition packet

You do not need a fifty-page binder, but you should prepare a practical packet before the conversation.

Include:

  • Current team goals and status.
  • Direct report list with role, strengths, development areas, and current projects.
  • Performance review notes or upcoming review obligations.
  • Critical deadlines in the next 30-90 days.
  • Open hiring, backfills, contractor, or vendor issues.
  • Key stakeholder relationships and escalation paths.
  • Risks that need leadership attention.
  • Recommended interim owner for each major workstream.
  • Decisions that should be made before your last day.

Do not include gossip or sensitive personal details beyond what is necessary for responsible management continuity. Your job is to hand off context, not write secret dossiers.

Script for telling your manager

Keep the first conversation short, respectful, and clear.

"I wanted to tell you directly that I have accepted another opportunity and will be resigning from my role. My proposed last day is [date], which gives [notice period]. I am grateful for the work we have done here, and I want to make the transition as smooth as possible for the team. I have started a transition plan covering current priorities, direct-report context, and recommended interim ownership. I would like to align with you on how and when to communicate this to [skip], HR, the team, and key partners."

Then stop. Do not over-explain. Your manager may be surprised, disappointed, or supportive. Let them respond.

If they ask why you are leaving:

"The new role is a better fit for the next step I want to take. I am not leaving because of one incident, and I want to keep the transition constructive. I am happy to share feedback separately if useful, but my priority today is making sure the team is covered."

This protects you from turning the resignation into a debate.

Should you tell your skip-level leader?

Usually, yes, but not before your manager unless there is a serious trust, ethics, or reporting issue. In a healthy organization, your manager should either tell the skip or join you for that conversation.

Skip-level leaders care about three things:

  1. Is there retention risk on the team?
  2. What work is now at risk?
  3. Who can cover management duties?

Script:

"I wanted to share directly, now that [manager] knows, that I am resigning and my proposed last day is [date]. I know this creates transition risk for the team, so I have documented current priorities, direct-report context, and recommended interim ownership. My goal is to leave the team stable and avoid surprises for customers or partners."

Do not use the skip conversation to criticize your manager unless there is a legitimate issue that must be escalated. If you have feedback, separate it from the resignation logistics.

When and how to tell your direct reports

Tell direct reports as soon as reasonably possible after your manager and communication plan are aligned. Ideally, tell them the same day or next business day. If you manage a small team, a live team meeting followed by individual one-on-ones is usually best. If you manage a larger org, tell your direct leadership layer first, then cascade quickly.

Team script:

"I want to share news directly with you. I have accepted another opportunity and will be leaving [Company]. My last day is planned for [date]. I know manager changes create uncertainty, so I want to be clear about what I know and what I do not know yet. [Manager/leader] and I are working on the transition plan, including interim coverage for approvals, priorities, and support. I will spend my remaining time making sure work is documented, decisions are clear, and each of you knows where to go for help."

Then address emotion directly:

"I also want to say that this decision is about my next step, not a lack of belief in this team. I care about the work and about each of you, and I want to leave in a way that helps you succeed."

Do not say "nothing will change." Something will change. Say what is true: priorities will be covered, information will be shared, and you will help with the transition.

What to say in one-on-ones with reports

Each report will process the news differently. Some will be happy for you, some anxious, some frustrated, some quiet.

Use this structure:

  1. Acknowledge the change.
  2. Reassure them about near-term support.
  3. Share what you know about interim coverage.
  4. Ask what they are worried about.
  5. Clarify what you will document for their continuity.

Script:

"I know this may create uncertainty for you, especially around [project/performance review/growth plan]. Before I leave, I want to make sure your current work, accomplishments, and development priorities are documented clearly. What are you most concerned could get lost in the transition?"

For high performers:

"I want to make sure your scope and impact are visible after I leave. I am going to document your current ownership and the outcomes you have delivered so the next manager has context."

For someone on a performance plan:

"I know transitions can be especially sensitive when expectations are already being discussed. I will document the current plan factually and make sure you know who your point of contact will be."

Do not promise promotions, protection, or outcomes you cannot control.

How much detail should you share?

You do not owe the team every detail about your new role. Share enough to be human and reduce speculation.

Good:

"I am moving to a role that gives me a different scope and is aligned with what I want next."

Risky:

"Leadership here is a mess, and I finally found a better company."

Good:

"The timing is based on the new opportunity and my personal career goals."

Risky:

"I would have stayed if compensation had been handled differently."

Even if your reasons are valid, your reports still have to work there after you leave. Do not make your exit interview their emotional burden.

Transition plan for manager responsibilities

A manager transition plan should cover the work and the people.

| Area | What to document | Interim owner | |---|---|---| | Team priorities | Current goals, milestones, blockers, deadlines | Manager or acting lead | | People management | 1:1 cadence, performance cycles, development plans | Interim manager | | Approvals | Budget, time off, hiring, vendor, access approvals | Named approver | | Stakeholders | Key relationships and current commitments | Peer or leader | | Risks | Attrition risk, delivery risk, customer risk | Leadership owner | | Rituals | Staff meetings, planning, retros, reviews | Acting facilitator | | Hiring | Open roles, candidate stage, interview loops | Recruiting partner + interim HM |

Make the plan easy to skim. Leaders are busy. Your successor or interim manager should be able to understand the next thirty days in one sitting.

Handling counteroffers

Managers often receive counteroffers because replacing management continuity is expensive. Decide before resigning whether you would seriously consider one.

Be careful. A counteroffer may solve money but not scope, trust, burnout, commute, leadership alignment, or career direction. If you would consider staying, be explicit about what would need to change.

Script if you are not considering a counteroffer:

"I appreciate that, but I have made my decision and accepted the new role. I want to focus on transition rather than reopening the decision."

Script if you are open to discussion:

"I am willing to listen, but I want to be transparent that this was not only about compensation. The issues I would need to solve are [scope/support/reporting line]. If those are not realistically changeable, I do not want to waste anyone's time."

Do not use a resignation as a bluff unless you are ready to leave.

Common mistakes when resigning as a manager

Avoid these:

  • Telling direct reports before your manager.
  • Letting your team hear from calendar changes, Slack rumors, or HR notices.
  • Over-sharing negative reasons with reports.
  • Under-documenting performance context.
  • Making promises about the next manager.
  • Leaving critical decisions unresolved.
  • Disappearing emotionally after giving notice.
  • Recruiting your reports to follow you, unless allowed and ethically appropriate.
  • Staying too long in a half-committed state.

Your notice period is not a victory lap. It is a handoff.

Final announcement template

After live conversations, send a short written note:

Subject: Transition update

Team,

As I shared today, I will be leaving [Company], and my last day will be [date]. I am grateful for the chance to work with this team and proud of what we have built together.

Over the next [X weeks], my focus will be on transition: documenting current priorities, clarifying ownership, supporting handoffs, and making sure each of you knows where to go for decisions and support. [Interim owner/leader] will share more about coverage as details are finalized.

Thank you for the trust, effort, and partnership. I care about this team and want to leave things in the strongest possible place.

[Name]

Leave like your leadership brand follows you

Resigning as a manager is a leadership act. People will remember less about the exact reason you left and more about whether you protected the team while leaving. Tell your manager first, align on the cascade, tell your reports live, document the people and work carefully, and keep your reasons clean. The goal is not to make everyone happy. The goal is to make the transition honest, humane, and operationally safe.