30 60 90 Day Plan for Internal Promotion (Example)

8 min read ยท 2026-11-16

A 30 60 90 day plan for internal promotion is a 90-day transition plan for a new role inside the company where you already work. It has three phases, each with a checkpoint at 30, 60 and 90 days. It is built around three problems that only a promoted employee has: handing over the old job, leading people who used to be peers, and showing results at the new level.

You don't need to learn the company again. You do need to show everyone, on purpose, that your role has changed. The plan below does that. It includes a filled example you can copy and measurable goals for four common promotions.

The roadmap at a glance

Goal: Finish the move from your old role to the new one in 90 days, plus one or two weeks of preparation: your old work belongs to someone else, your team knows how you will lead, and your manager can measure your first results. Duration: 90 days

  1. Prepare the transition (1-2 weeks before the start date)

    Agree on the terms of the move before day one, so no task gets lost between the old role and the new one.

    • Confirm the start date and who announces the change.
    • List every task, project, report and client you own today.
    • Name a new owner for each item, with a transfer date.
    • Ask your manager which three outcomes will define success at day 90.

    Milestone: Your manager has signed off the handover list and you have three success outcomes in writing.

  2. Hand over and reset relationships (Days 1-30)

    Close the old job and set the tone with your team.

    • Have a one to one with each direct report in the first two weeks.
    • Work alongside each new owner of your old tasks.
    • Measure the starting point for each of your three outcomes.
    • Stop attending meetings that belong to your old role.

    Milestone: All one to ones are done, your old tasks are fully handed over, and your manager has reviewed a one-page summary of what you heard.

  3. Set priorities and make the first change (Days 31-60)

    Turn what you heard into priorities.

    • Choose two or three improvements your team raised more than once.
    • Agree on quarter goals and the metric for each one.
    • Set your routine: a weekly team meeting, regular one to ones and a monthly report.
    • Meet the peers and stakeholders at your new level.

    Milestone: Your team and your manager agree on the quarter goals and the first improvement is live.

  4. Deliver results at the new level (Days 61-90)

    Show that the team works better with you in the role.

    • Report each goal against the starting point measured in month one.
    • Finish one improvement from start to end and record its effect.
    • Give each team member feedback and a development goal.
    • Draft your plan for months 4 to 6.

    Milestone: A day 90 review with your manager that measures your results against the three outcomes.

How a promotion plan differs from a new hire plan

Your plan should spend less space on learning and more on change. You already know the tools, the product and who makes decisions. The risk is that people keep seeing you in your old job, and that you keep doing it.

A simple test helps. If an outside candidate could copy your plan without changing anything, it is too generic. A good promotion plan names the tasks you are giving away, the people you used to sit next to, and the habits you are dropping.

Handing over your old work

The fastest way to fail a promotion is to keep doing your old job. Each task you keep takes time away from the new role, and it blocks the person who should own it.

For each item, write four things: the task, the new owner, the transfer date, and where the notes are kept. Then hand it over in two steps.

After day 30, you're out. Share the transfer dates with your manager so they can protect them when work gets busy. If no successor has been named yet, agree on a temporary owner rather than keeping the task "for now".

A common trap is the client or stakeholder who keeps calling you. Introduce the new owner on a joint call or email, then point every new request to them. Do this once, clearly, rather than half answering for weeks.

  • Weeks 1 and 2: shadowing. The new owner does the task while you work next to them. You explain the context, the usual traps and who to call when something breaks.
  • Weeks 3 and 4: backup only. The new owner runs the task alone and comes to you only with questions. You don't step in, even when you could do it faster.

Leading former peers after a promotion

This is the part most people worry about, and most plans skip it.

  • The announcement. Ask your manager to announce the change first. Then send your own short note the same day. For example: "As you may have heard, I'm stepping into the team lead role from Monday. Over the next two weeks I'll book time with each of you to hear what's working and what you need. My current projects are moving to Sam, and the handover will be done by the end of the month."
  • The first one to ones. Ask everyone the same three questions: What works today? What blocks you? What do you expect from me now? Listen more than you talk, and write the answers down. The patterns become your priorities for days 31 to 60.
  • New limits. You will now give feedback, set priorities and sometimes say no. You can stay friendly. You stop commenting on other team members, and you stop discussing decisions before they are final. Say this openly once instead of letting people guess.
  • The colleague who also applied. Talk to them first, in private, before the team meeting. Recognize their work, and ask what they want to grow into. Often you can give them ownership of a visible project in the first 60 days.

Filled example: analyst promoted to analytics team lead

Here is a complete plan for a senior analyst promoted to lead a team of five analysts she used to work beside. Copy it and replace the details with your own.

Three success outcomes agreed with the manager: every old task is transferred by day 30, and none comes back; every request to the team goes through one shared queue with a clear owner; turnaround time on standard reports is lower at day 90 than at day 30.

  • Before the start date: handover list with the weekly sales dashboard to Priya, finance data checks to Tom and marketing ad hoc requests to Leo, all three transferred by the end of week 4. Announcement note drafted for the day of the manager's message.
  • Days 1 to 30: five one to ones booked in week 1 and held by day 10. Shadowing in weeks 1 and 2, backup only in weeks 3 and 4. Starting point recorded: number of open requests, average turnaround on standard reports, number of requests with no clear owner. Day 30 checkpoint: a one-page summary of what the team said and the handover marked as complete.
  • Days 31 to 60: two priorities chosen from the one to ones, a single request queue and a shared definition of "done" for reports. Weekly 30-minute team meeting and a one to one every two weeks. Request queue live by day 45, with every open request moved into it. Introduction meetings with the finance and marketing leads.
  • Days 61 to 90: turnaround on standard reports compared with the day 30 starting point. A development goal written with each analyst. The analyst who also applied for the role owns the report definition project. Day 90 review: results against the three outcomes, plus a draft plan for months 4 to 6.

30 60 90 day plan internal promotion example by role

The phases stay the same. The goals change with the role. Each goal below can be checked with a yes, a date or a number you measure yourself.

  • Team manager promoted from the team. Day 30: all one to ones held and every old task transferred. Day 60: quarter goals written and a weekly meeting in place. Day 90: one team process changed, with its before and after measured.
  • Product manager promoted from analyst or designer. Day 30: your design or analysis work handed to a named owner, and the backlog reviewed with the engineering lead. Day 60: a quarter roadmap agreed with stakeholders. Day 90: the first planned release shipped and its result reported.
  • Project manager promoted from a team member. Day 30: your delivery tasks transferred and every open project reviewed for scope, budget and risk. Day 60: one status report and one risk log used across all projects. Day 90: one late project back on schedule or closed.
  • Senior expert or lead specialist. Day 30: your daily tickets moved to the team and the main quality issues mapped. Day 60: one standard or review practice proposed and agreed. Day 90: the practice used on real work and one junior colleague coached.

How to present your plan to your manager

Lead with outcomes. Use one page. Put the three success outcomes at the top. Below them, list each phase with two or three goals and the measure for each one. At the bottom, list the support you need, such as system access, introductions, budget or a successor's time.

Book the three checkpoints on the day you present the plan. At each one, keep the same order: what you planned, what you did, what changed, and what comes next.

You can also write a shorter version before the decision, to pitch yourself for the role. Keep it to the handover and the first 30 days, then turn it into the full plan once the promotion is confirmed.

Common mistakes to avoid

  • Changing too much in month one unsettles the team, so wait until day 31 to launch changes and use the first 30 days to listen and measure.
  • Keeping old tasks because you are faster blocks their new owners, so set transfer dates and stick to them, even in a busy week.
  • Treating former peers exactly as before blurs your new role, so have an honest one to one with each of them in the first two weeks.
  • Writing goals without a starting point makes progress impossible to prove, so measure each goal in month one and report real change at day 90.
  • Skipping checkpoints when work gets busy lets the plan drift, so book all three reviews on day one.

Frequently asked questions

Can I write a 30-60-90 day plan before I am promoted?

Yes. A one-page version can help you pitch yourself for an internal role. Focus on how you would hand over your current work and what you would do in the first 30 days. After the decision, expand it into the full plan.

How do I hand over my old job after a promotion?

List every task with its new owner, its transfer date and where the notes are. Shadow the new owner for two weeks, act only as backup for two more, and stop doing the task after day 30.

How do I manage people who used to be my peers?

Have a private one to one with each person in the first two weeks. Explain what changes in your role, set clear limits, and talk first to anyone who also applied for the job.

What should I do in the first 30 days of a promotion?

Finish the handover, hold all your one to ones, and measure the starting point for your goals. End the month with a one-page summary reviewed with your manager.

Generate this roadmap with AI