Change Readiness Pulse Survey Template

A pulse survey anchored to one named change rather than to the company in general. It separates understanding what is changing from understanding why, asks whether the reasoning is convincing, separates the size of the impact on someone's own role from its direction, and then tests the three things that actually predict readiness — information, training, and knowing who to ask. A support checklist turns the answers into a work list, and a round field lets you run the identical form before, during and after and compare.

Use this template

Last updated 21 August 2026

Fields in this template

Which change is this survey about?required
Which round of this survey is this?required
Before the change starts · Early in the rollout · Midway through · After the change has landed
Your team or department
Engineering · Sales · Marketing · Operations · Finance · Human Resources · Customer Support · Product · Design · Other · I would rather not say
I understand what is actually changing.required
5 — Strongly agree · 4 — Agree · 3 — Neutral · 2 — Disagree · 1 — Strongly disagree
I understand why this change is happening.required
5 — Strongly agree · 4 — Agree · 3 — Neutral · 2 — Disagree · 1 — Strongly disagree
I find the reasons given for this change convincing.required
5 — Strongly agree · 4 — Agree · 3 — Neutral · 2 — Disagree · 1 — Strongly disagree
How much do you expect this change to affect your own day-to-day work?required
A great deal — most of what I do changes · Quite a lot · Some · Very little · Not sure yet
Do you expect the effect on your own role to be positive or negative?required
Clearly positive · More positive than negative · Neutral or mixed · More negative than positive · Clearly negative · Too early to say
I have the information I need to prepare for this change.required
5 — Strongly agree · 4 — Agree · 3 — Neutral · 2 — Disagree · 1 — Strongly disagree
I have the training and the skills I need to work in the new way.required
5 — Strongly agree · 4 — Agree · 3 — Neutral · 2 — Disagree · 1 — Strongly disagree
I know who to ask when I have a question about this change.required
5 — Strongly agree · 4 — Agree · 3 — Neutral · 2 — Disagree · 1 — Strongly disagree
What support would help you most? Choose as many as apply.
Written guidance or a step-by-step reference · A hands-on training session · A recorded walkthrough I can watch when I need it · Time set aside to practise before go-live · A named person I can ask questions · A session for my team specifically · Fewer competing priorities during the transition · A clear decision about what stops when this starts · Nothing — I feel ready
What is your biggest concern about this change?required
What is going well so far?
Overall, how ready do you feel for this change today?required
Ready — I know what to do · Mostly ready — a few gaps · Somewhat ready — significant gaps · Not ready — I need help · I do not know enough to say
Anything else the change team should know?

Who uses this template

Change managers and transformation leadsHR and people teams supporting a restructureIT teams rolling out a new system across a companyInternal communications teams testing whether a message landedOperations leads moving a team to a new processProgramme management offices tracking adoption riskLeadership teams after announcing a merger or reorganisationAnyone who has to move a team from one way of working to another

About this template

A change readiness survey is not a satisfaction survey run during a difficult month. It is tied to one named change, and it measures the specific things that determine whether people can actually do the new thing: do they know what is changing, do they know why, do they believe the why, what does it do to their own job, and do they have the information, the training and the named contact they need. Company-wide sentiment polls answer none of that. They tell you morale dipped; they do not tell you that the support team never got the training and finance never got the reasoning.

Several splits in this form are deliberate. Understanding what is changing and understanding why are separate questions because people routinely grasp the mechanics and reject the rationale, and one merged question hides it. Expected size of impact and expected direction of impact are separate for the same reason — a team bracing for a large negative change and a team expecting a large positive one both score high on impact and need opposite responses from you. The support checklist exists so a round of this survey produces something to do: edit its options down to the help you can actually provide, because asking about support you cannot deliver is worse than not asking at all.

The round field is what makes this repeatable. Run the identical form before the change starts, early in the rollout, midway and after it has landed, then filter your CSV export by round and watch whether understanding and readiness move. Keep the wording identical between rounds or the trend means nothing. On anonymity, be straight with people: the form does not ask your name, but formformform records the IP address and browser of every submission, the owner can see both, and IP address is a column in every CSV export, encrypted forms included — encrypting the form seals the answers from the platform, it does not make a respondent anonymous to the person holding the key. The optional team dropdown is the field to think hardest about — it is genuinely useful, because a change lands differently in support than in finance, but on small teams it narrows a critical comment to one or two people. This template ships flat with no conditional logic, so it cannot hide that field for small groups. If your teams are small, delete it.

10 form ideas you can build with this template

CRM Migration Readiness Survey

Find out before go-live whether the sales team has actually had the training, or has only had the announcement about the training.

Return-to-Office Policy Readiness Pulse

Separate the people who do not understand the new policy from the people who understand it perfectly and disagree with it.

Post-Merger Integration Pulse

Run the same form on both sides of a merger and compare the rationale scores, which is usually where the two populations diverge first.

Restructure Communication Check

Test a week after the announcement whether people know who to ask about their own role, which is the question that predicts the flood of one-to-one meetings.

New Process Rollout Survey

Check whether an operations team has the written guidance they need before the old process is switched off.

ERP or Finance System Go-Live Readiness

Collect a support checklist from finance and operations a fortnight before go-live, while there is still time to book a practice session.

Pre-Launch Baseline Survey

Establish the before reading for a programme so that later rounds can show movement rather than just a snapshot.

Post-Implementation Review Pulse

Run the after round three months later to find out whether the new way of working actually stuck or quietly reverted.

Leadership Change Confidence Pulse

Ask whether people find the stated reasons for a leadership change convincing, which is a different question from whether they understand it.

Office Relocation Readiness Survey

Surface practical blockers and date clashes through the open concern field, weeks before the moving date rather than during the move.

What's included

Anchored to one named change, so the answers are about something specific

Understanding what is changing and understanding why are asked as two separate questions

Size of impact and direction of impact are separated, because they need opposite responses

Three readiness questions — information, training, and who to ask — that name the gap rather than the mood

A support checklist that produces a work list, not just a score

A round field for before, during and after, so the identical form is repeatable and comparable

Biggest concern is a required field, because it is the answer that most often changes the plan

Free to use with unlimited responses

How to create a change readiness pulse survey

1
Click Use this template to load the change readiness pulse survey into your free formformform account.
2
Name the change. Either pre-fill the change name field in the editor, or rename the field label to the change and delete the input so nobody has to type it.
3
Decide about the team dropdown before you send it. Keep it if your groups are big enough that no answer points at a person; delete it if they are not, because the template cannot hide it conditionally.
4
Trim the support checklist to the help you can actually offer, and add anything specific to this change.
5
Edit the intro paragraph to say who reads the responses, when results will be shared, and what happens to the biggest-concern answers.
6
Publish, then duplicate the form for each round if you want each round in its own response list — or keep one form and rely on the round field and a CSV filter.
7
Run round one before the change starts. A readiness survey with no before reading cannot show you whether anything improved.

Best practices for your change readiness pulse survey

Get a baseline before the change begins. Without a before round, every later number is uninterpretable.

Keep question wording identical across rounds. Rewording a scored item mid-programme resets the trend and you will not notice until you try to chart it.

Act on the support checklist within one round. It is a list of specific, cheap requests; leaving it unactioned teaches people that answering achieves nothing.

Read the biggest-concern field in full every round. The scores tell you where the problem is; this field usually tells you what it actually is.

Do not average the impact question. Size of impact is not a quality score

a five there is not good or bad until you read the direction question next to it.

Keep it short and keep the cadence sane. Two or three rounds across a programme is enough; monthly rounds measure survey fatigue.

Separate this from any decision about individuals. If people suspect that a low readiness score marks them as resistant, they will report readiness they do not have.

Share something back after every round, even if the answer is that a concern was heard and cannot be resolved. Silence after round one is the reliable way to get a thin round two.

Frequently asked questions

Is this change readiness survey free?

Yes. Use it, customise it, and collect unlimited responses at no cost, with no per-response fees.

How is this different from a general employee opinion poll?

An opinion poll asks how people feel about the company's direction in general. This survey is anchored to one named change and measures capability rather than sentiment — whether people have the information, the training and a named contact — and it produces a support checklist you can act on. It also carries a round field so the identical form can be run before, during and after and compared.

How do I run it before, during and after?

Use the same form each time and ask people to select the round. Then export to CSV and filter by that field. Do not reword the scored questions between rounds, or the comparison stops meaning anything.

Should I keep the team or department field?

Only if your groups are large enough that a single critical answer cannot be traced to one person. It is genuinely useful, because a change lands differently in different functions — but the template ships flat, so it cannot hide the field for small teams. On small teams, delete it.

Are responses anonymous?

The form does not ask your name or email. But formformform records the IP address and browser of every submission, the form owner can see both, and IP address is a column in every CSV export, encrypted forms included — encrypting the form hides the answers from the platform, not from the form owner, who holds the key. Anonymous means the questions do not ask who you are, not that the submission has no trace; the optional team field is the one question here that narrows the pool, so delete it if your groups are small.

Why are understanding what and understanding why asked separately?

Because they fail separately. People often understand exactly what is changing and completely reject the reasoning, and a single combined question would show a middling score with no idea which half is broken.

Can I show extra questions only to people who say they are not ready?

Not from the template — generated templates ship flat, with every field visible. The form editor supports conditional rules, so you can add that after cloning.

Can I use this for a system rollout as well as a reorganisation?

Yes. The questions are about readiness rather than about the type of change, so a CRM migration, a new process, an office move and a restructure all work — just name the change in the first field and trim the support checklist to the help you can offer.