Change Readiness Survey (Pre-Implementation)

This template fits major organizational changes that require employee behavior shifts, such as new systems, process changes, policy updates, restructures, or operating model changes. It is designed for pre-implementation use, when you still have time to adjust communication and support plans. If the change is minor or purely technical with little employee impact, a shorter pulse may be enough.

Send it after the change has been defined enough for employees to understand the basics, but before implementation starts. That timing lets you measure awareness, acceptance, and perceived support while there is still time to fix gaps. If you send it too early, people may not know enough to answer accurately; too late, and the results are less useful for action.

HR, internal communications, change management, or the project owner can run it, ideally with visible leadership sponsorship. The key is that the team collecting responses must also be able to act on the findings, especially around manager effectiveness, training, and communication. If anonymity is promised, keep the response handling separate from direct managers.

Yes, anonymity should be the default for employee surveys like this one. Employees are more likely to give honest feedback about acceptance, leadership support, and readiness barriers when they trust their responses cannot be traced back to them. If you need segmentation, use broad, optional demographics only after the core questions and avoid collecting anything that could undermine trust.

This template is usually a one-time pre-implementation survey, not a recurring pulse. For large or phased changes, you can reuse it before each major rollout wave or milestone to compare readiness by group or location. If you need ongoing monitoring after launch, pair it with a short post-implementation adoption pulse instead of repeating the full survey too frequently.

The highest-value questions are the ones that reveal whether employees understand the change, believe it is necessary, and feel supported by leadership and their manager. The open-ended follow-ups are especially important because they explain why someone is uncertain or resistant. Those answers usually point to the communication, training, or process gaps that matter most for adoption.

Common mistakes include asking leading questions, using vague agreement statements without context, and failing to follow up on low readiness scores. Another pitfall is collecting demographics before the core questions, which can make anonymity feel questionable and reduce response quality. It is also a mistake to treat the survey as a checkbox instead of using the results to change the rollout plan.

Yes, and it should be customized to name the specific change, timeline, and impacted workflows. You can also tailor the wording for different audiences, such as frontline staff, managers, or office-based teams, while keeping the same core structure so results remain comparable. If you need department-level comparisons, keep the response scale and question order consistent across versions.

An ad hoc email usually produces scattered feedback that is hard to compare, summarize, or act on. This template gives you a consistent structure for measuring awareness, acceptance, leadership support, and adoption risk, plus open-text prompts that explain the scores. That makes it much easier to identify where the rollout plan needs adjustment before implementation begins.