Restructuring Action Plan Template: Organisational Change Format

A restructuring action plan is the document that converts a strategic intent (collapse two teams, eliminate a layer, re-align reporting, reduce headcount in one area to invest in another) into a sequenced execution with explicit stakeholder management, legal compliance, and human dignity. Restructurings done badly damage retention, morale, and execution capacity for years. Restructurings done well produce a stronger organisation with the change absorbed cleanly. The difference is largely in the planning. This page covers the phased change-management framework grounded in established change-management research, a worked example for a SaaS company collapsing two product teams, the stakeholder communication cascade, and the four mistakes that quietly damage outcomes.

Updated 11 May 2026

Why Restructurings Need a Different Plan Shape

Most action plans assume the team will be the same before and after. Restructuring action plans operate under the opposite assumption: the team itself is changing. People are leaving, joining, switching roles, switching managers. The execution discipline that works when the team is stable does not translate cleanly to a period when the team itself is the variable. The plan has to manage the change of structure, the human consequences of that change, and the maintained execution capacity through the transition simultaneously.

John Kotter's eight-step change framework remains the most widely-cited reference for organisational change of this scale. The Kotter steps are useful as a framework but require translation to the specific reality of a restructuring. The plan structure below incorporates Kotter's discipline into the more specific demands of restructuring execution: announce, separate, settle, deliver.

The plan also has legal dimensions that ordinary action plans do not. In the UK, collective consultation requirements apply when 20 or more employees are at risk of redundancy. In the US, the WARN Act applies for layoffs over certain thresholds. In the EU, works council consultation is required in many jurisdictions. The legal and HR partner is essential, not optional, and the plan should explicitly name the compliance steps and timing requirements. Skipping or rushing these is one of the most expensive failure modes available.

The Four-Phase Plan Structure

Phase 1

Prepare (2-4 weeks)

Strategic decision finalised. New structure designed. Legal and HR consultation. Communication cascade planned in detail. Severance and transition packages defined. Individual conversations rehearsed. Nothing announced externally. The most senior leadership team is fully aligned.

Phase 2

Announce (1-3 days)

Cascading announcement: executive, then affected managers, then affected individuals, then the broader company. Concentrated in a tight window. Communication materials prepared in advance. HR available throughout for individual conversations. Empathy and clarity prioritised equally.

Phase 3

Separate (2-6 weeks)

Departing employees transition out with explicit support. Notice periods worked or paid out. Knowledge transfer completed. Outplacement services delivered. Internal moves implemented. Remaining team adjusts to new structure. Leadership is highly visible during this phase.

Phase 4

Deliver (4-12 weeks)

New structure operational. Goals reset to match new capacity. Execution rhythms re-established. Retention attention on remaining team. Post-restructure retrospective at week 8 to capture lessons. Trust rebuilding is the multi-month overlay across this phase.

Worked Example: SaaS Company Collapsing Two Product Teams

Company: 80-person SaaS company. Two product lines (A and B) with separate teams of 12 and 8 engineers, each with its own product manager and designer. Strategic decision: Product B becoming a feature of Product A, collapsing the dedicated team.

Net impact: 8 Product B engineering roles eliminated. 3 highest-performing engineers absorbed into Product A team. 5 engineers transition out with severance. Product B product manager and designer roles eliminated; both individuals offered roles on Product A team if interested, otherwise transitioned with severance.

Phase 1: Prepare (Weeks 1-3)

Strategic decision signed off by board. New structure mapped: Product A team grows from 12 to 15 engineers, absorbs Product B feature roadmap. HR partner engaged. Severance terms defined (8 weeks base salary plus accrued PTO, plus outplacement services). Communication cascade scripted. Individual conversation messages rehearsed with HR.

Phase 2: Announce (Day 1)

9:00 AM: executive team briefing. 10:00 AM: Product A and Product B managers briefed. 11:00 AM-1:00 PM: individual conversations with each of the 8 affected engineers (split between the senior product leader and HR). 2:00 PM: Product A team meeting announcing the structure change and the joining engineers. 3:00 PM: all-hands company meeting acknowledging the change at company level. 4:00 PM: optional Q+A with HR for affected individuals.

Phase 3: Separate (Weeks 2-7)

Departing engineers complete 6-week notice period (extended from minimum 4 weeks). Knowledge transfer to absorbing team. Outplacement service introductions in weeks 1-2 of notice. Internal moves completed by end of week 4. New Product A team kickoff in week 5. Leadership weekly small-group sessions with affected team throughout.

Phase 4: Deliver (Weeks 7-19)

New Product A team operating with 15 engineers. Q4 OKRs re-baselined to reflect new capacity and combined roadmap. Engineering velocity measured monthly to validate the team is rebuilding execution rhythm. Retention conversation with each remaining engineer in week 12. Post-restructure retrospective at week 16: what worked, what damaged trust, what to do differently next time.

The plan converts a difficult strategic decision into a sequenced execution with explicit stakeholder care. The communication cascade prevents anyone from learning about their own role through a group meeting. The notice period is generous enough to support honest transitions. The post-restructure retrospective captures lessons rather than letting them be quietly forgotten. The execution is harder than the plan suggests, but the plan is what gives the leadership team a defensible structure to operate from.

The Stakeholder Communication Cascade

The single highest-leverage discipline in restructuring is the communication cascade. People should learn about decisions affecting them in the right order: top first, individual before group, affected before unaffected. Restructurings where this order is broken (someone learns through a company email that their role is being eliminated, or a manager hears about a change to their team through Slack) damage trust in ways that take years to recover.

The cascade should be planned in detail before any announcement happens. Each conversation has a script, a designated speaker, a designated time, and a backup plan for absence or technology failure. The senior leader running the restructuring should personally conduct or be present at the most difficult conversations (individuals whose roles are being eliminated, especially long-tenured employees). Delegating these to HR alone signals that leadership is unwilling to face the consequences of its own decision, which is one of the most corrosive perceptions a leader can create.

For the broader company communication, three messages need to land. First, what is changing and why. Second, who is affected and how they are being supported. Third, what this means for the people who remain. The third message is the one most commonly under-developed. The remaining team is acutely watching how the change is handled and forming views about whether the company is one they want to continue investing in. Strong remaining-team communication, with concrete signals of leadership intent to retain and support them, is what distinguishes restructurings that produce stronger organisations from those that produce damaged ones.

4 Mistakes That Damage Restructuring Outcomes

Broken communication cascade

Affected individuals learn about their own situation through a group meeting, a company email, or a leaked Slack message. This is the single most damaging mistake available. It is preventable with disciplined planning and a tight time window for the cascade. Leaders who allow it to happen, even through inattention rather than intent, damage retention of the people who remain.

Treating departing people poorly

Severance below market norms, abrupt termination of access, withholding references, public framing of departures as performance issues when they are structural. The remaining team observes the treatment closely. Restructurings that economise on transition support save short-term cost and pay long-term retention cost.

Compressing the timeline for the sake of speed

Leaders sometimes compress the active execution into a single week to get the change done quickly. The team then spends three months recovering trust and rebuilding capacity. The original timeline would have done a better job and cost less in total. Speed is occasionally necessary but more often a defensive reflex against the discomfort of a longer transition.

No attention to the remaining team

Restructurings often focus all leadership energy on the departing or affected individuals, leaving the remaining team to interpret the change for themselves. Survivor guilt, anxiety about future changes, and unclear new expectations damage execution capacity. Explicit retention conversations, clear new roadmap, and visible leadership investment in the remaining team are what rebuild forward momentum.

Frequently Asked Questions

When should a company use a restructuring action plan?
When the change involves meaningful headcount movement (layoffs, role eliminations, significant team restructures), reporting line changes affecting more than one team, or strategic re-alignment that requires people to do different work than they signed up for. Smaller team adjustments do not need a formal restructuring plan. Once the change crosses these thresholds, the plan becomes essential because the downside of getting it wrong is severe in retention, morale, and execution capacity.
How long should a restructuring plan take to execute?
The active execution phase is typically 4-12 weeks from announcement to new structure operational. Larger or cross-functional restructurings take 12-26 weeks. The temptation to compress the timeline for the sake of getting the change done quickly almost always backfires; the team spends the time recovering trust and rebuilding capacity later, often more expensively than the original timeline would have cost.
Who should own the restructuring plan?
The senior leader whose authority covers the affected scope, with HR or People partner as co-owner. For a single team restructure, that is the team's senior leader. For cross-functional restructuring, the executive sponsor whose remit covers all affected teams. The plan should not be HR-owned with leadership as a stakeholder; HR is the partner that ensures legal and process discipline, but the leadership accountability sits with the senior business leader.
What is the right communication cascade for a restructuring?
Top down, tier by tier, in a tight time window. The executive team is informed first. Direct reports and the managers of affected teams are informed next, usually one to two days before the broader announcement. Affected individuals are informed before any group communication. The full company is informed only after each individual whose role is changing or eliminated has been told personally. Inverting this cascade (the company learning before the individuals) is one of the most damaging mistakes a restructuring can make.
How should the plan handle people whose roles are being eliminated?
With explicit transition support: severance terms, outplacement services, generous notice periods where possible, references and recommendations from leaders, and timeline transparency. The treatment of departing people is observed closely by the people who remain, and shapes the trust they will extend to the leadership team going forward. Restructurings that treat departures harshly damage the retention of those who stay, often more than they save in transition costs.
What is the right cadence for reviewing the restructuring plan during execution?
Daily leadership stand-up during the first two weeks of active execution, weekly for the next month, then bi-weekly until the new structure is operational. The cadence is intentionally tight at the start because the first two weeks produce the largest concentration of difficult conversations, surprises, and need for course correction. Once the announcement is made and individual conversations have happened, the cadence can step back, but only after the acute phase is complete.

Related Templates

Updated 11 May 2026