This blog guides you through measuring how employees experience change: 40+ survey questions across six categories, a merger and restructuring set, the RAC Framework, and industry benchmarks.

Jennifer is a keynote speaker and executive coach who works with HR and executive teams on leading transformation and change. She has spoken to more than 100,000 people across 11 countries, and her clients include Procter & Gamble, General Electric, IBM, SAP, and LinkedIn. She reviewed this guide for accuracy and practical relevance.
A change management survey is a structured feedback tool used to gather employee perspectives during organizational transitions. It measures how well employees understand the change, how supported they feel, and whether the transition is producing the intended outcomes.
Unlike a general engagement survey or an annual engagement survey, a change management survey is timed to specific milestones: before, during, and after the transition. It creates a longitudinal view of how the change is landing across teams, locations, and roles.
Organizations that use structured change management surveys identify resistance early, close communication gaps before they widen, and confirm that changes are sustained rather than abandoned. The questions in this guide are organized into six categories aligned with survey design best practices and validated by people science research.
The oft-cited 70% change-failure figure is debated, but the driver isn't: change stalls on employee resistance and weak leadership support.
Change management surveys matter because transitions fail on the human side: resistance stays silent, teams experience the same change differently, and leaders consistently overestimate buy-in. A structured survey surfaces those gaps while there is still time to act. Here are six reasons organizations that skip structured feedback pay for it later.
The widely quoted claim that 70% of transformations fail traces to a 1993 estimate by Hammer and Champy, repeated by McKinsey and Kotter without new evidence (Mark Hughes, Journal of Change Management, 2011). What holds up in study after study: change stalls when employees resist and managers disengage. Surveys surface both before they become terminal.
Employees rarely announce their opposition to change. They comply publicly and disengage privately. By the time resistance becomes visible, through attrition, productivity drops, or open conflict, the window for intervention has closed. Surveys make the invisible measurable.
A technology migration might energize the engineering team and terrify the operations team. Company-wide messaging treats all employees as a monolith. Surveys segmented by team, role, and location reveal where the change is landing well and where it is failing.
Executives consistently report feeling far more supported through change than the individual contributors doing the adapting. That perception gap widens with every layer of hierarchy. Without survey data from every level, leadership decisions are based on an optimistic distortion of reality.
Gallup estimates that replacing a single employee costs one-half to two times their annual salary. When a mishandled restructure or system rollout pushes a whole team out the door, the bill compounds fast. Employees do not leave because of the change itself. They leave because they were not informed, involved, or supported.
A survey creates a record: what was promised, what employees experienced, and what happened next. Without this record, change management becomes a series of announcements without feedback. With it, leaders have measurable accountability for follow-through.
Change management surveys solve a specific problem: the gap between what leadership plans and what employees experience during transitions. Use this checklist to confirm the fit.
A change management survey asks employees about six things: readiness, communication, leadership, involvement, training, and adoption. Ask readiness and communication questions before the change, leadership and involvement questions during it, and training and adoption questions after. Select a category, copy individual questions, or grab the full set of 42 in one go.
During a merger, acquisition, or restructuring, ask employees about three fears a routine change survey misses: job security, role clarity, and acquirer-versus-acquiree culture friction. Ask a targeted set before close to measure readiness, and again after close to measure integration.
Ask employees to rate their agreement with the following statements before and after the transition.
The before column maps to the RAC Readiness phase and the after column maps to the RAC Adoption phase, so this set slots straight into the survey cadence described below. Watch two splits closely when you segment results: acquired employees versus acquirer employees, whose trust and belonging scores routinely diverge, and frontline teams versus headquarters, who often hear about the deal on very different timelines.
For deeper playbooks, see our guides to employee engagement during mergers and acquisitions and navigating organizational restructuring.
Run change management surveys across email, Slack, Teams, and WhatsApp. Built-in anonymity thresholds, AI-powered analysis, and action tracking, so you catch resistance before it becomes attrition.
In CultureMonkey's Q1 2026 benchmark of 10.2M responses across 500+ companies, leadership scores ranged from 4.55 out of 5 in hospitality to 3.68 in telecom, with a global median of 3.92. Leadership is the engagement driver most predictive of change adoption speed.
| Rank | Industry | Leadership score / 5.0 |
|---|---|---|
| 01 | Hospitality | 4.55 |
| 02 | Food & Bev | 4.42 |
| 03 | Finance | 4.18 |
| 04 | Technology | 4.02 |
| 05 | Manufacturing | 3.98 |
| 06 | Retail | 3.90 |
| 07 | Healthcare | 3.76 |
| 08 | Telecom | 3.68 |
| Global median | 3.92 |
| Driver | Technology score / 5.0 | YoY |
|---|---|---|
| Involvement #1 FASTEST | 4.05 | +1.51% |
| Leadership #2 FASTEST | see table above | +1.50% |
The RAC Framework (Readiness, Adoption, Closure) times change management surveys to three phases: a readiness survey before the change, adoption surveys at 30, 60, and 90 days, and a closure survey at six months.
| RReadiness | AAdoption | CClosure | |
|---|---|---|---|
| Timing | Pre-change | During change | Post-change |
| Focus | Awareness, preparedness, anticipated resistance | Participation, confidence, manager support | Sustained adoption, satisfaction, embedding |
| Overview | Assess employee awareness and preparedness. Build a communication plan. Identify potential resistance points. Deploy the readiness survey 2 to 4 weeks after announcement. | Deploy surveys at 30, 60, and 90 day milestones. Segment results by team and role. Close the feedback loop within 2 weeks of each cycle. | Measure sustained adoption at 6 months. Document lessons learned. Archive baseline scores for future transitions. |
| Key actions |
|
|
|
To run a change management survey, define the change scope, pick two to three question categories, draft 10 to 15 questions, deploy at 30/60/90-day milestones, and close the loop within 30 days. The seven steps from scope to sustained outcomes:
Clarify what is changing, who is affected, and what outcomes the survey needs to measure. A restructuring affecting 200 people requires different questions than a software migration affecting 2,000. Scope determines which question categories to prioritize.
Choose from change readiness, communication effectiveness, leadership trust, employee involvement, training support, or post-change evaluation. Fewer categories with deeper coverage produce more actionable data than surface-level coverage across everything.
Mix rating-scale questions for trend tracking with open-ended questions for context. Avoid leading language and double-barreled prompts. Test question clarity with a pilot group before full deployment.
Deploy at 30, 60, and 90 days post-announcement. Each wave maps to a RAC phase: Readiness at pre-launch, Adoption at 30 and 60 days, Closure at 90 days. The cadence creates a narrative arc, not just snapshots.
Send a pre-survey message explaining what the survey measures, how results will be used, and how anonymity is protected. Employees who understand the purpose participate at meaningfully higher rates.
Break results by team, location, tenure, and role. A department scoring 8.5 overall might have one team at 4.2 driving all the negative sentiment. The value of the survey is in the variance.
Share findings with employees, assign action owners with deadlines, and re-survey in the next RAC phase. The feedback loop is the survey. Without it, you are collecting data, not managing change.
Case study · LINKBANK

The 6-Flag Diagnostic checks six warning signs that a transition needs a change management survey now: attrition spikes, readiness perception gaps, compliance without adoption, one-way communication, undifferentiated surveys, and change fatigue. If any flag describes your organization, run a survey before the next milestone, not after.
If a previous restructuring, merger, or system migration led to higher-than-expected voluntary turnover, employees were not heard during the transition. A change management survey catches flight-risk signals before they become resignation letters.
When executives report the organization is ready and frontline employees report confusion, you have a perception gap. This gap predicts resistance. Only survey data from both levels reveals the true state of readiness.
If teams are using new processes when monitored but reverting to old behaviors when unsupervised, you have compliance without adoption. Post-change evaluation surveys at 90 days distinguish genuine integration from surface-level compliance.
When leadership sends updates but receives no questions, no pushback, and no suggestions, employees have disengaged from the process. This silence is not alignment. It is withdrawal. Surveys create the upward feedback channel that town halls and emails cannot.
A one-size-fits-all survey for a change that affects engineering, sales, and operations differently produces averaged data that helps no one. If different teams experience the change differently, your survey must segment by team to produce actionable insights.
Change fatigue shows up before burnout as two signals: leaders and teams making rushed, poorly-anchored decisions, and once-vocal employees going quiet and passively accepting whatever is decided. If you see either pattern, survey now, before fatigue hardens into disengagement.
The seven best practices for change management surveys are: define clear objectives, guarantee anonymity visibly, mix rating scales with open-ended questions, act on at least one finding per cycle, segment results by team, time surveys to RAC phases, and pilot test before full deployment. Each practice below is paired with the mistake it prevents.
| Do | Don't | |
|---|---|---|
| 01 | Define clear objectives before drafting questionsEvery survey cycle needs a stated outcome: diagnosing readiness, measuring adoption, or confirming closure. Without a defined objective, questions drift and results lack focus. Write the action plan before the questionnaire. | Do not launch a survey without a defined objective, hoping the data will suggest its own purpose. |
| 02 | Guarantee anonymity and communicate it visiblyUse a platform with built-in anonymity thresholds that strip identifying metadata. Explain threshold rules and data access policies before the survey opens. Employees evaluate anonymity by evidence, not promises. | Do not simply add a line saying 'This survey is anonymous' without any supporting detail or platform safeguards. |
| 03 | Mix rating scales with open-ended questionsScale questions track trends across cycles. Open-ended questions explain the why behind the numbers. A survey with only scales produces benchmarks without context. A survey with only open-ended questions produces insights you cannot trend. | Do not use only rating scales and skip open-ended questions entirely, leaving no room for context. |
| 04 | Act visibly on at least one finding per cycleThe fastest way to destroy survey participation is to collect feedback and change nothing. Pick the most actionable finding, implement it within 30 days, and communicate the change. One visible action builds more trust than ten promised improvements. | Do not archive the results until the next planning cycle without sharing outcomes or taking any visible action. |
| 05 | Segment results by team, not just companyA company average of 7.8 means nothing if one team is at 4.2. Use manager-level analytics to identify outliers. The value of change management data is in the variance between teams, not the average across them. | Do not present only org-wide averages and call the analysis complete. |
| 06 | Time surveys to RAC phases, not calendar quartersDeploy surveys at transition milestones: pre-change for readiness, 30/60/90 days for adoption, and 90 days post-implementation for closure. Calendar-based scheduling misses the moments that matter for change-specific feedback. | Do not schedule surveys by calendar quarter; timing that ignores transition milestones makes trends invisible and misses the moments that matter. |
| 07 | Pilot test before full deploymentRun the survey with a small group first to identify unclear questions, technical issues, or question-order bias. Adjust based on pilot results. A 15-minute pilot saves weeks of interpreting ambiguous data from a flawed full-scale launch. | Do not skip the pilot and deploy a flawed survey at full scale; you will spend weeks interpreting ambiguous data. |
If you don't provide managers with the tools to keep messaging consistent and bring everyone along in the change journey, things get lost in translation.
A change management survey is a structured set of questions that measures how employees experience an organizational transition: their readiness for it, the quality of communication around it, their trust in the leaders driving it, their involvement in shaping it, the training that equips them for it, and whether they are actually adopting it. Timed to the transition itself rather than the calendar, it turns the human side of change from guesswork into data.
This guide gives you everything needed to run one well: 40+ questions across six categories, a dedicated merger and restructuring set, the RAC Framework for timing surveys to Readiness, Adoption, and Closure milestones, Q1 2026 industry benchmarks to compare your scores against, and the 6-Flag Diagnostic to confirm whether your transition needs a survey right now.
CultureMonkey is built for exactly this workflow. Deploy surveys across email, Slack, Teams, WhatsApp, and SMS with built-in anonymity thresholds, let context-aware AI analysis surface the themes inside open-text responses, and use survey-over-survey heatmap comparison to track adoption across your 30, 60, and 90 day milestones, with multilingual delivery reaching every employee. Organizations like Robertshaw and LINKBANK run their change management feedback on CultureMonkey.
From the first pulse check to post-change retrospectives, CultureMonkey gives HR teams the signal they need, when they need it.
Deploy change management surveys in minutes. Omni-channel delivery across email, Slack, Teams, WhatsApp, and SMS, with anonymity thresholds built in. Catch resistance before it becomes attrition.