Change readiness isn't a feeling, it's a score you can run

At a glance

"I think we're ready" is not a plan. It's a guess dressed up in confidence, and it's usually wrong in one direction or the other: either leadership overestimates how ready the front line actually is, or a nervous project team underestimates a workforce that's more resilient than anyone gave it credit for.

Either way, you're making a multi-million dollar transformation decision on a hunch.

A change readiness assessment replaces that guess with a number. This guide walks through how to score readiness before you announce anything, find out exactly where the gaps are, close them, and confirm the fix worked. If your specific change is a merger or acquisition, the cultural due diligence questions are different enough to warrant their own guide to post-merger integration; this piece covers readiness for change in general.

Readiness is the first checkpoint in a longer listening arc. Once you've assessed readiness and closed your gaps, the same employees still need a pulse check while the change is underway and a confidence check once it's done.

Change readiness is how prepared your workforce is, practically and psychologically, to absorb a specific upcoming change.

It's not the same as engagement, and it's not the same as morale.

A highly engaged team can still be unready if they don't trust the people leading the change or don't have the resources to execute it.

Most change management literature treats readiness qualitatively: employees either "trust leadership" or they don't, either have "the right mindset" or they don't.

That's a useful starting frame, but it doesn't give you a number to track, and it doesn't tell you which lever to pull first.

Two scores do more work than a paragraph of description: a leadership-trust score (how much employees believe leadership will execute this well) and a resource-confidence score (how much employees believe they'll personally have what they need to do their part).

Together, they form what this guide calls the readiness signal.

The reason two scores beat one blended average comes down to what each one tells you to do next. A low blended score could mean almost anything.

A low resource-confidence score paired with a high leadership-trust score tells you precisely where to spend your budget: training and staffing, not another reassurance email from the CEO.

That specificity is the entire point of scoring readiness instead of just describing it.

Treat this as a repeatable process, not a one-time survey. Each step feeds the next, and skipping straight to "close the gaps" without first measuring them is how organizations end up solving the wrong problem.

Send a short survey, 10 to 15 questions, to the population that will be affected by the change. Ask separately about trust in the people leading the change and confidence in having the tools, time, and training to succeed. Keep the scale consistent, typically a 1-to-5 or 1-to-7 agreement scale, so you can track the same number over time.

Run this as an anonymous survey. Employees rating their own leadership's ability to execute a change are describing a power dynamic, and an assessment that isn't anonymous will just measure how diplomatic people are, not how ready they actually feel.

Break your two readiness scores down by department, tenure, and management layer, not just as one company-wide number. A readiness signal of 72 out of 100 company-wide can hide a frontline team sitting at 40 and an executive team sitting at 95, and those two groups need completely different interventions.

Look specifically for the gap between the two component scores. High leadership trust paired with low resource confidence means people believe in the plan but doubt they can execute it. Low leadership trust paired with high resource confidence means the opposite problem: people feel equipped but skeptical of the direction.

Match the intervention to the gap, not to a generic "communicate more" instinct. A resource-confidence gap usually needs training, staffing, or tooling investment. A leadership-trust gap usually needs visible, consistent behavior from leaders over time, not another all-hands announcement.

Give each intervention an owner and a deadline, the same way you would any other project deliverable. A gap-closing plan with no owner tends to quietly become a slide in a deck instead of something that actually happens, and a structured engagement strategy is a useful reference for building interventions that stick rather than fade after the kickoff meeting.

Run the same readiness survey again, four to six weeks after your interventions launch, using identical question wording. If the resource-confidence score moved and the leadership-trust score didn't, you'll know your training investment worked but your communication plan still needs work.

This is also the point where a pulse survey template becomes useful as a lighter-weight check-in between full readiness re-assessments, so you're not waiting for the next big survey cycle to notice a score sliding backward.

Once your readiness score clears the bar and the change actually launches, the job isn't finished. Long rollouts have a way of wearing down even a workforce that started out genuinely ready, and that specific mid-change symptom pattern is covered in how to catch change fatigue before it becomes resistance.

Generic "how do you feel about the upcoming change" questions produce generic answers. Sharper, more specific wording produces a signal you can actually act on.

Questions worth building into your readiness survey include:

Pair each rating-scale question with one open-ended follow-up, something like "what would make you feel more ready for this?" The quantitative score tells you how big the gap is; the open-ended comment tells you what's actually causing it.

Frameworks like ADKAR do useful work describing the stages an individual moves through during change: awareness, desire, knowledge, ability, reinforcement.

They're worth knowing, and Prosci's material on the model is a solid primer if you want the underlying theory.

What that kind of framework doesn't give you is a way to score where your specific workforce sits on any of those stages before you commit resources to a rollout plan.

That's the gap a readiness assessment fills.

It's not a replacement for change management theory; it's the measurement layer that tells you which part of the theory to apply first, and to which group of employees.

Think of it as the difference between a map and a GPS.

The stage model tells you the territory everyone eventually crosses.

A readiness score tells you exactly where your specific workforce is standing on that map right now, which is the piece of information that actually changes what a project team does on Monday morning.

A handful of mistakes show up often enough to name directly. Watch for these before you launch your own assessment:

Benchmarking your scores against industry data, rather than judging them in isolation, also helps leadership calibrate what a "good" readiness score even looks like. SurveyMonkey Benchmarks gives you that outside reference point instead of guessing whether 72 out of 100 is strong or concerning for your industry.

One more mistake worth naming on its own: running the assessment, getting an uncomfortable result, and then quietly shelving it instead of acting. Employees who take the time to answer a readiness survey and never hear anything about the results become measurably harder to survey honestly the next time. If you're not ready to act on what a readiness score tells you, it's worth asking whether you're ready to run the survey at all.

A readiness assessment turns "we think people are ready" into something you can actually defend to a steering committee: a leadership-trust score, a resource-confidence score, and a plan to close whatever gap shows up between them. Skipping that step is how organizations get blindsided by resistance that a five-minute survey would have flagged months earlier.

SurveyMonkey features built for this exact workflow, from anonymous response settings to benchmarking and AI-powered analysis of open-ended comments, make it possible to run a full readiness cycle, from baseline to re-survey, without hiring outside consultants. Once you know where your organization actually stands, keeping employees on side for the rest of the change gets a lot more straightforward.

See how to assess whether your organisation is ready to change

Start with a pulse survey