Change Management Review Template

Overview

A change management review is a recurring meeting designed to monitor, assess, and steer organisational change initiatives. Whether you are rolling out new technology, restructuring teams, or shifting business processes, change rarely succeeds without deliberate oversight. This meeting provides that oversight in a structured, repeatable format.

The review typically runs for 60 minutes and brings together change leaders, project managers, and functional representatives. The group examines adoption metrics, stakeholder sentiment, resistance points, and communication effectiveness. The goal is not simply to report on progress but to identify where the change is stalling and decide what adjustments are needed to get it back on track.

Most change initiatives fail not because the solution is wrong, but because the people side of change is poorly managed. Browse our operations templates for related frameworks that support organisational transitions. Employees are left confused about why the change is happening, managers are not equipped to support their teams through the transition, and communication is either too sparse or too generic. The change management review exists to catch these problems early, while there is still time to course-correct.

When to Use This Framework

Change management reviews should be held at regular intervals throughout the lifecycle of a change initiative. They are particularly valuable when:

• You are in the midst of a technology rollout that affects how people do their daily work, such as a new CRM, ERP, or collaboration platform
• Your organisation is going through a restructure, merger, or acquisition that changes reporting lines, team compositions, or ways of working, often requiring alignment through an all-hands town hall meeting
• A new process or policy is being introduced that requires people to abandon established habits and adopt new behaviours
• Early indicators suggest that adoption is lower than expected, or that certain teams are resisting the change
• You need to coordinate communication across multiple departments or geographies to ensure consistent messaging
• Leadership wants regular visibility into change readiness and the risks of delayed adoption, which can also be surfaced during a weekly leadership sync

Who Should Attend

Sample Agenda

Example Use Case

Consider a mid-size professional services firm rolling out a new CRM system across five regional sales teams over a three-month period. The old system has been in place for seven years, and many salespeople have built deeply personalised workflows around it. The switch is necessary because the legacy system cannot support the firm's growth targets, but adoption is far from guaranteed.

Six weeks into the rollout, the change management review reveals a split picture. Two regions are progressing well, with login rates above 80% and positive feedback from managers. However, the Northern Europe team is lagging significantly, with only 40% of reps logging into the new system regularly. The functional lead for that region explains that the team's top-performing salespeople view the change as an imposition and are quietly continuing to use spreadsheets alongside the old system.

The group decides on three interventions. First, the executive sponsor will join the Northern Europe team's next all-hands to explain the strategic rationale and personally address concerns. Second, the training lead will run targeted "power user" sessions showing how the new CRM can replicate the custom workflows that top performers rely on. Third, the change lead will work with the regional manager to set a firm cutover date for the old system, making dual-running no longer an option. Each action is assigned an owner and a two-week deadline. At the next review, the group will assess whether these interventions have shifted the adoption curve.

Best Practices

• Combine quantitative and qualitative data. Numbers tell you what is happening; conversations tell you why. Review both adoption metrics and team feedback in every session to build a complete picture.
• Hold reviews on a consistent cadence. Fortnightly reviews work well during active rollout phases. Monthly reviews suit the sustain phase once initial adoption targets are met.
• Make resistance visible, not punishable. People resist change for legitimate reasons. Create a safe space for functional leads to report resistance honestly, without fear of blame.
• Tailor communication by audience. Executives need strategic context; frontline staff need practical "what changes for me" guidance. A single generic email will not serve both groups.
• Celebrate early wins publicly. When a team or individual demonstrates successful adoption, highlight it. Success stories are more persuasive than mandates.
• Ensure the executive sponsor is visibly engaged. Consider having the sponsor address change topics in stakeholder update meetings. If the most senior person backing the change is absent or disengaged, the rest of the organisation reads that as a signal that the change is optional.
• Track sentiment over time, not just snapshots. A single survey result can be misleading. Trend data across multiple reviews reveals whether the change is gaining momentum or losing it.
• Set a clear definition of "done." Define what successful adoption looks like in measurable terms before the rollout begins. Without a target, it is impossible to know when the change initiative can transition from active management to business as usual.

Common Mistakes

• Treating the review as a status report. If the meeting is just a round-table of updates with no decisions or actions, it becomes a time sink. Every review should produce at least one concrete adjustment or intervention.
• Ignoring the "frozen middle." Middle managers are the most critical layer in change adoption, yet they are often the least supported. If managers do not understand or believe in the change, their teams will not either.
• Declaring victory too early. High initial login rates or training completion percentages can mask shallow adoption. People may be going through the motions without genuinely changing how they work. Sustain reviews for longer than you think necessary.
• Underinvesting in training. A one-hour webinar is rarely sufficient for meaningful behaviour change. Budget for hands-on workshops, coaching, and ongoing support resources.
• Failing to address "what's in it for me." People adopt change when they see personal benefit. If communication focuses only on organisational benefits, individual motivation remains low.
• Letting the change plan become static. The plan you wrote before the rollout is a hypothesis. Reality will differ. Use each review as an opportunity to adapt the plan based on what you are learning.
• Not involving HR early enough. Change initiatives that affect how people work, where they work, or who they report to have significant people and talent implications. Bringing HR in late creates unnecessary risk around employment law, wellbeing, and retention.

Related Templates

Related Tools