Change Management Transition Plan Template: Interim Setup

9 min read ยท 2026-11-21

A change management transition plan template covers the period between the old way of working and the new one. It sets who decides what while both setups are running, which groups move over and when, what makes you step back, and when the old setup is switched off for good. This template has six phases over 22 weeks and is built around that in-between period: the interim setup, cutover in waves, rollback gates and adoption checks at 30, 60 and 90 days.

It does not replace your change plan, which explains why people should adopt the change. It also does not replace a handover plan for one person leaving a role. It covers the gap between those two, where old and new run side by side and nobody is quite sure who approves what. Most transitions go wrong in that gap.

The roadmap at a glance

Goal: Move a team or a department from the current setup to the new one, with no service gap, a clear way to step back, and the old setup retired. Duration: 22 weeks

  1. Fix the start and end state (Weeks 1-2)

    Agree on where you are, where you are going and what stays the same.

    • Describe the current state in five lines: structure, tools, reporting lines, key processes, service levels.
    • Describe the future state under the same five headings so the two can be compared line by line.
    • List what does not change, so people know what they can rely on.
    • Get the sponsor to sign off on the scope and the date the old setup ends.

    Milestone: Start and end state approved by the sponsor.

  2. Decide who runs the gap (Weeks 2-4)

    Name the people who make decisions while both setups are live.

    • Name a transition lead who owns the plan until handover.
    • Agree who can approve a delay, a wave and a rollback, and write it down.
    • Name one champion inside each group that moves.
    • List every affected group and rate how much its daily work changes.

    Milestone: Decision rights published to all managers.

  3. Design the interim setup (Weeks 4-6)

    Write how work gets done while old and new run side by side.

    • Write temporary reporting lines and escalation contacts for the transition period.
    • Decide which processes run in parallel, and the date each parallel run stops.
    • Freeze non urgent changes to the old setup.
    • Write the rollback trigger for each wave: what must go wrong, for how long, and who decides.

    Milestone: Interim operating guide published and known by every team lead.

  4. Prepare the first wave (Weeks 5-8)

    Get the first group ready and test the switch on a small scale.

    • Brief managers before their teams, with the questions people will ask and the answers.
    • Train the first wave on the new process or tool, by role.
    • Run a dry run with one small team and fix what breaks.
    • Set up one place for questions during the transition and answer them weekly.

    Milestone: Dry run passed and first wave trained.

  5. Cut over in waves (Weeks 8-10)

    Move groups one at a time, with a go or no go call before each wave.

    • Move the first wave in week 8 and keep the old setup available as a fallback.
    • Hold a go or no go meeting before the next wave, using the rollback trigger.
    • Staff a daily support slot for the first two weeks after each wave.
    • Log every issue with an owner and a due date.

    Milestone: Last wave moved in week 10, no open critical issue.

  6. Stabilize, then retire the old setup (Weeks 10-22)

    Lock in the new way, then remove the option to go back.

    • Run adoption checks at 30, 60 and 90 days after the first wave, around weeks 12, 17 and 21.
    • Stop each parallel process on its planned date and archive the old documents.
    • After the 90 day check passes, hand ownership from the transition lead to the line managers.
    • Hold a post transition review in week 22 and record the lessons.

    Milestone: Old setup retired and ownership signed over in week 22, after the 90 day check.

Why the in-between period needs its own plan

Most change plans describe the starting point and the target in detail, then cover the move itself in a single line: "go live". In practice, the move is a period of several weeks where two setups exist at once. During those weeks, the usual questions have no obvious answer. Who approves a refund when the old manager has left the role but the new one has not started? Which queue does an urgent ticket go to? What happens if the new process fails on a Friday?

A transition plan template for change management answers those questions in advance. If your change is small, like a new approval form, you do not need one. If several groups move and the business has to keep running during the switch, you do. For the wider steps of building any plan, see the guide on how to make a roadmap.

The interim setup: running two systems at once

The interim setup is the part of the template most teams skip, and the part that prevents the most confusion. Write it as a short guide that any team lead can read in five minutes.

Give every parallel process an end date. A parallel run without an end date becomes permanent, and people keep the old way "just in case".

  • Temporary reporting lines: who each person reports to from the first wave until the old setup is retired.
  • Decision rights: who approves spending, exceptions and escalations during the period. Name people, not roles.
  • Parallel processes: which old processes stay live, why, and the date each one stops.
  • Freeze rules: what may no longer change in the old setup, so you are not moving a target.
  • Escalation path: one contact per group for "this is broken and I do not know who owns it".

Rollback gates: when to step back

A rollback gate is a check before each wave where you decide to go ahead, wait or reverse the last move. It only works if the trigger is written before the cutover, when nobody is under pressure.

A good trigger names three things: the signal (a service level, an error rate, a backlog size), the duration (one bad day is noise, a full week is a pattern) and the decision maker (one person, usually the sponsor). For example: "If response times in either region stay above the agreed limit for five working days, the next wave is paused and the sponsor decides whether to reverse the last one."

Rollback should be possible but not free. Keep the old setup available until the last wave has passed its first checks, then remove that option on a date that is already in the plan.

Example: merging two regional support teams into one

Here is the template filled in for a common case. A company has two customer support teams, one per region, each with its own manager, queue and escalation rules. Leadership wants one team with one shared queue and two shift leads.

  • Start and end state: today, two managers, two queues, two sets of saved replies, escalation by phone. Target: one support manager, two shift leads, one shared queue, written escalation rules. What stays: the support tool, working hours and the contact details customers use.
  • Who runs the gap: the VP of Customer Experience is the sponsor and decides on any rollback. The future support manager is the transition lead. One senior agent per current team is the champion.
  • Interim setup: from week 8 to week 14, both queues stay live, and tickets older than a set limit move to the shared queue. Both current managers keep approval rights until the second wave has moved. Escalations go to the transition lead during the whole period.
  • Waves and gates: the smaller region moves in week 8, the larger one in week 10. Before the second wave, the sponsor checks the rollback trigger: response times in the first region over the last week.
  • Adoption checks: at 30 days after the first wave (about week 12), every agent works from the shared queue. At 60 days (about week 17), the old saved replies are deleted and escalations follow the written rules. At 90 days (about week 21), response times are back to their level before the change. Only then is the old queue closed, and ownership passes to the support manager in week 22.

Who decides what during the transition

A transition fails when everyone is "involved" and nobody decides. Write one clear job per role.

People ask their direct manager first, not the project team. Ask managers each week what they are hearing, and treat skipped training or "just this week" workarounds as signals that something in the interim setup is unclear.

  • Sponsor: approves scope, end date and every rollback.
  • Transition lead: runs the plan week to week, chairs the go or no go meetings, owns the issue log.
  • Line managers: explain the change to their people, approve training time, report who still works the old way.
  • Champions: answer daily questions inside the team and flag what is not working.

Presenting the plan to leadership

Leadership will not read a long plan. Give them one page and one visual. The page holds the scope, the end date, the decision rights, the rollback triggers and the 30, 60 and 90 day targets. The visual is the timeline: six phases, the waves marked, the gates marked.

At each steering meeting, show the same visual with the current week marked and name the decision you need: approve the next wave, approve a delay, or sign off the retirement of the old setup. For more ideas on laying out a plan visually, see these roadmap templates.

Common mistakes to avoid

  • Writing no interim setup leaves nobody sure who approves what during the switch, so publish temporary reporting lines and decision rights before the first wave.
  • Moving everyone on the same day multiplies the risk, so cut over in waves with a go or no go meeting before each one.
  • Writing the rollback trigger after problems appear leads to rushed calls, so agree on it in week 6, when nobody is under pressure.
  • Keeping parallel processes with no end date makes them permanent, so give each one a stop date and an owner.
  • Handing over ownership at go live is too early, so wait until the 90 day check confirms the new way has stuck.

Frequently asked questions

What is a change management transition plan?

It is the plan for the period between the old way of working and the new one. It sets the interim setup, decision rights, the cutover in waves, the rollback triggers and the checks that confirm adoption. It works alongside the change plan, which covers why and how people adopt the change.

What is an interim operating model in a transition?

It is the temporary way the organization runs while old and new setups exist at once: who reports to whom, who approves what, which processes run in parallel and until when. It ends on a planned date, when the old setup is retired.

How long should a transition period last?

It depends on how many groups move and how deep the change is. The example in this template runs 22 weeks: about ten weeks to prepare and cut over, then 90 days of adoption checks after the first wave before the old setup is retired. Set the end date with the sponsor at the start and review it at each go or no go meeting.

When should you roll back a change?

When a trigger you agreed in advance is met, for example a service level below target for a full week after a wave. The sponsor makes the call. Pausing the next wave is often enough, and reversing a wave is the last resort.

Generate this roadmap with AI