50+ ADKAR Awareness Survey Questions (Template + Scoring)
Use this pulse to check whether employees understand why the change is happening and whats happening next. Pick your audience (all vs impacted teams), choose anonymous vs confidential, and lock in one Likert scale youll reuse each wave. Copy the Core 10 items first, then add 3-5 diagnostics based on what youre seeing (rumors, manager cascade, timeline confusion).
Trusted by 5000+ Brands
When to Run an ADKAR Awareness Survey (3 best moments)
Run #1: Right after the announcement (message check)
Confirm basic comprehension so you can fix the story before teams form their own version.
- Position it as a comprehension check (not a vote): "This 5-minute pulse checks whether our message is clear and what questions we still need to answer."
- Customize this: Replace "the change" with your initiative name and 1-2 concrete examples of what will change (tool, process, policy).
Run #2: After a comms wave (town hall, email, manager cascade)
Check which messages landed and which channels people actually saw. Keep the pulse short (3-7 minutes) and repeatable so you can trend results after each wave.
- Scale: Lock one agreement scale and reuse it each time (example: 1-5 Strongly disagree to Strongly agree).
- Keep trends clean: Use Likert scale best practices and TASO's guidance on designing Likert scales so changes over time reflect messaging, not measurement drift.
Run #3: Pre-rollout when frontline impact begins
Catch confusion right before behavior has to change (new steps, new approvals, new systems).
- Segment by impact level: Target follow-ups where operational risk is highest.
- Watch out: Avoid sending only to leaders. Include the people whose day-to-day work changes, plus their managers, so you can spot cascade gaps.
Next: Pick your audience (whole organization vs high-impact groups), then copy the Core 10 questions below and run the first pulse within 24-72 hours of the next major message.
ADKAR Awareness Question Bank (copy/paste, then tailor)
Do this first: Copy the Core 10 items and keep them unchanged across waves so you can trend Awareness from announcement to comms wave to pre-rollout.
- Recommended scale (Likert): 1-5 Strongly disagree, Disagree, Neither agree nor disagree, Agree, Strongly agree
- Customize this: Swap in your initiative name and the specific process/tool that changes.
- Watch out: Keep wording neutral and behavior-specific (avoid leading language like "I support" in Awareness). AAPOR's Best Practices for Survey Research page is a solid checklist for question clarity and bias control.
Core 10 (use these for your Awareness score)
"I understand what is changing."
Why it matters: If people cannot name the change, every downstream message gets interpreted differently.
When to use: Every wave. Trend it as your baseline clarity signal.
"I understand why this change is happening now."
Why it matters: Timing confusion drives rumors and "why are we doing this" churn.
When to use: Every wave, especially right after major announcements.
"The reasons for the change make sense to me."
Why it matters: Sense-making is the bridge between hearing a message and repeating it accurately.
When to use: Every wave. If low, you likely have a message gap.
"I understand what success looks like for this change."
Why it matters: People need a concrete end-state to interpret updates and priorities.
When to use: Every wave, and again pre-rollout.
"I know where to find the latest updates about this change."
Why it matters: If people do not know where updates live, they fill gaps with hallway news.
When to use: Every wave. Low scores often signal a channel gap.
"Communications explain how the change affects my work."
Why it matters: Generic updates do not help people decide what to do differently.
When to use: Every wave; expect the biggest gaps in high-impact groups.
"I know what will happen in the next 30 days."
Why it matters: Near-term uncertainty is what turns "I get it" into anxiety.
When to use: Add early, then keep it in the Core 10 for trending.
"I feel the information shared so far is honest and complete."
Why it matters: Low credibility scores predict rumor growth and selective listening.
When to use: Every wave; treat drops as an early warning.
"My manager can explain the change in a way I understand."
Why it matters: Managers translate enterprise messages into local reality.
When to use: Every wave to detect cascade gaps by team.
"I know who to ask when I have questions about this change."
Why it matters: Clear escalation paths reduce repeated questions and inconsistent answers.
When to use: Every wave; if low, publish "where to go" guidance.
Required open-text prompts (keep both)
"What is unclear right now?"
Why it matters: You get the exact language people are using to describe gaps and confusion.
When to use: Every wave. Use it to write the next FAQs and manager talking points.
"What question should leadership answer next?"
Why it matters: It forces prioritization. You see the next missing piece of the story.
When to use: Every wave, especially when rumor volume is rising.
Optional diagnostics (rotate 3-5 per wave)
1) Clarity of the change (rotate)
"I can explain this change to a colleague in one sentence."
Why it matters: Summary ability is a stronger test than "I understand" alone.
When to use: After the announcement and after major town halls.
"I understand which parts of the business are in scope for this change."
Why it matters: Scope confusion creates duplicate work and misaligned priorities.
When to use: When you hear "Does this apply to us?" repeatedly.
"I understand what is NOT changing."
Why it matters: Naming non-changes reduces unnecessary anxiety and churn.
When to use: When you see broad fear or overreach assumptions.
"The language used to describe the change is consistent across leaders and channels."
Why it matters: Inconsistent terms signal competing narratives and drive mistrust.
When to use: After multiple leaders present the change in different forums.
2) Reason and urgency (rotate)
"I understand the risks of not making this change."
Why it matters: Risk clarity reduces "why now" debates and message drift.
When to use: When urgency is part of the narrative.
"I understand how this change connects to our strategy and goals."
Why it matters: Strategy linkage stops the change from sounding like a random project.
When to use: After leaders share strategy updates or quarterly priorities.
"I understand what problem this change is intended to solve."
Why it matters: Problem clarity makes tradeoffs easier to accept later.
When to use: Early waves and whenever scope shifts.
"I believe the stated reasons for the change are credible."
Why it matters: Credibility issues often show up before open resistance does.
When to use: When trust is fragile or rumor volume is high.
3) Perceived impact (rotate)
"I know which of my current tasks will change because of this initiative."
Why it matters: Task-level awareness is what reduces rollout friction.
When to use: Pre-rollout and during pilots.
"I understand how this change will affect our customers or end users."
Why it matters: Customer impact clarity helps people prioritize the right behaviors.
When to use: When customer outcomes are a key message pillar.
"I understand which teams we will need to coordinate with differently."
Why it matters: Cross-team confusion often looks like "process problems" later.
When to use: When the change affects handoffs or approvals.
"I understand what decisions will be made differently after this change."
Why it matters: Decision clarity reduces rework and escalation loops.
When to use: When governance or approvals are changing.
"I understand what will be expected of me during the transition period."
Why it matters: Transition expectations (parallel work, cutovers) drive workload perceptions.
When to use: 2-6 weeks before rollout.
"I understand how my performance measures or goals might be affected."
Why it matters: Metric ambiguity leads to defensive behavior and workarounds.
When to use: When roles, targets, or KPIs are changing.
4) Comms effectiveness (rotate)
"I am receiving updates about this change often enough."
Why it matters: Too few updates creates rumor space; too many creates noise.
When to use: After each comms wave to calibrate cadence.
"The updates I receive about this change are easy to understand."
Why it matters: Complexity kills retention and increases local re-interpretation.
When to use: When the change involves technical or policy language.
"I can find answers quickly when I look for information about this change."
Why it matters: Slow searching becomes "no one told us" in hindsight.
When to use: When you have a hub, intranet page, or FAQ channel.
"I know which communication channel(s) to rely on for accurate updates."
Why it matters: People default to whatever channel feels most current.
When to use: When multiple channels are active and messages differ.
"Leadership communication about this change is consistent."
Why it matters: Consistency reduces "which leader should I believe" debates.
When to use: When multiple executives communicate in parallel.
"I have opportunities to ask questions about this change (live or async)."
Why it matters: Two-way comms reduces misinformation and builds acceptance later.
When to use: After town halls or manager cascades.
5) Information gaps (rotate)
"Which topic is most unclear right now? (Pick one)"
Why it matters: A forced choice tells you what to address next, fast.
When to use: When you need prioritization for the next comms wave.
"I have the information I need to answer basic questions from my team or customers."
Why it matters: If local leaders cannot answer basics, the narrative fragments.
When to use: When managers and supervisors are the primary messengers.
"I understand who is making decisions about this change (and how decisions are made)."
Why it matters: Governance confusion often becomes blame and distrust.
When to use: When priorities or scope are shifting frequently.
"I understand what input employees can provide (and what is already decided)."
Why it matters: Clear boundaries reduce frustration and false expectations.
When to use: When you are collecting feedback but not changing core decisions.
6) Rumors and misconceptions (rotate)
"I have heard conflicting information about this change."
Why it matters: Conflicts are your earliest measurable rumor signal.
When to use: When comms happen across many channels or locations.
"I know which information about this change is confirmed vs not yet decided."
Why it matters: "Not decided" is fine if people can tell it apart from "hidden."
When to use: When decisions are staged over time.
"I have heard rumors about job impacts related to this change."
Why it matters: Job-impact rumors spread fast and distort every other message.
When to use: When restructuring, automation, or role shifts are involved.
"I have heard rumors about system/tool readiness related to this change."
Why it matters: Readiness rumors predict adoption slowdowns and workaround behavior.
When to use: During pilots and right before go-live.
"When I hear a rumor, I know where to go to verify it."
Why it matters: Verification paths reduce the half-life of misinformation.
When to use: When you have an FAQ hub or dedicated Q&A channel.
7) Manager cascade (rotate)
"My manager discusses this change with our team regularly."
Why it matters: Regular team-level reinforcement is how messages stick.
When to use: After manager toolkits are distributed.
"My manager can answer common questions about this change (or knows where to get answers)."
Why it matters: Escalation and follow-through beats guessing.
When to use: When you rely on a manager cascade to reach frontline teams.
"My manager explains what the change means for our team's priorities."
Why it matters: Priorities are where Awareness becomes day-to-day behavior.
When to use: When you see competing priorities or "business as usual" drift.
"I feel comfortable asking my manager questions about this change."
Why it matters: Low comfort suppresses questions and pushes confusion underground.
When to use: When you're seeing quiet disengagement or low Q&A volume.
8) Timeline and next steps (rotate)
"I understand the high-level timeline for this change (key milestones)."
Why it matters: Timeline clarity reduces "surprise" moments and last-minute panic.
When to use: After publishing the roadmap or milestone plan.
"I know what I need to do next related to this change."
Why it matters: Next-step clarity is the fastest way to reduce anxiety.
When to use: Pre-rollout and right after cutover communications.
"I know what will be required of my team on go-live week."
Why it matters: Go-live confusion is where small gaps turn into operational incidents.
When to use: 1-2 weeks before rollout for high-impact groups.
Next: Add 3-5 optional diagnostics based on what you're seeing, then rerun the same Core 10 after the next comms wave to prove what's improving (and what's not).
Anonymous vs Confidential: Pick the Right Setup for Change Pulses
| Decision point | Anonymous | Confidential |
|---|---|---|
| What you can promise | You cannot identify people (no names, IDs, or traceable links). | You can identify people in the dataset, but you will restrict access and report results in groups. |
| Best when | Trust is low, rumors are high, or you need maximum candor fast. | You need targeted follow-up (for high-impact teams, sites, or roles) and can protect privacy. |
| Tradeoff | Higher candor, weaker ability to follow up 1:1. | Better targeting and support, but some people may hold back. |
| Segmentation | Use only broad tags (location, function, impact level) and avoid tiny groups that are identifiable. | You can use richer segmentation, but still suppress small cells in reporting. |
| Follow-up | Follow up by publishing FAQs, manager toolkits, and site/team actions. | Follow up with targeted listening sessions, manager check-ins, or support for specific groups. |
| Suggested invite language | "Your answers are anonymous. We cannot see who submitted responses. We will share results by group only." | "Your answers are confidential. Only the change team will access raw data, and we will report results in groups (no individual attribution)." |
| Watch out | Do not claim "anonymous" if you collect anything that can identify people (directly or indirectly). Use the definition check from Penn State's guide to anonymity vs confidentiality in surveys. | Do not over-promise privacy. Document who can access raw data and how you will handle it (see privacy and data handling guidance). |
Next: Write your privacy promise into the first page of the survey and repeat the same promise in the invitation email so people do not have to guess what you mean.
Customization + Deployment Checklist (SuperSurvey-ready)
- Rename the initiative everywhere: Replace "the change" with the program name employees hear (project nickname included) so you can match comments back to the right comms wave.
- List 2-3 concrete examples of what changes: Name the system/process/policy and one workflow step so people can answer from real experience, not guesswork.
- Keep the Core 10 scale items consistent: Update examples around them, but do not rewrite the Core 10 wording so you can trend results across waves.
- Adjust only the context for frontline vs managers: Keep the question, change the noun (example: "customers" vs "internal partners") so comparisons stay fair.
- Pick minimum segmentation tags up front: Use impact level, location/site, function, and manager vs IC as your defaults. Use sampling and segmentation basics to decide when to survey everyone vs only high-impact groups.
- Use a manager-enabled + direct-link distribution plan: Send the link centrally, then give managers a short script to reinforce why you're asking (comprehension check) and when it closes.
- Run a simple reminder cadence: Send 2 reminders (example: day 3 and day 6) and close in 7-10 days. If you want proven tactics for invitations and reminders, use Dillman's Tailored Design Method overview as your operating playbook.
- Close the loop within 5 business days: Share the top 3 "unclear" themes, what you will change in comms, and what is still undecided. Example line: "You told us the timeline and local impacts are unclear - next week we will publish a site-by-site rollout view and manager FAQs."
- Watch out for accidental re-identification: If you report results for a tiny team (or a rare role at one site), people will feel exposed even if you said "confidential." Suppress small groups in reporting.
Next: Schedule the next pulse date now (after the next comms wave) so the survey becomes a repeatable comms QA step, not a one-off event.
Scoring ADKAR Awareness and Turning Results Into Actions
- Score: calculate one Awareness index from the Core 10
Awareness score (1-5): Average the 10 Core items (treat Strongly disagree=1 through Strongly agree=5). Report the overall average plus the percent favorable (Agree/Strongly agree).
- Items to include: "I understand what is changing"; "I understand why this change is happening now"; "The reasons for the change make sense to me"; "I understand what success looks like for this change"; "I know where to find the latest updates about this change"; "Communications explain how the change affects my work"; "I know what will happen in the next 30 days"; "I feel the information shared so far is honest and complete"; "My manager can explain the change in a way I understand"; "I know who to ask when I have questions about this change".
- Starter interpretation bands (calibrate after your baseline): 4.0-5.0 = generally clear; 3.2-3.9 = mixed clarity; below 3.2 = likely comprehension gaps. Treat these as internal starting targets and adjust once you see your first-wave distribution and segment spread.
Watch out: Do not turn the score into a faux-precise KPI. Use it to pick where to act first.
- Show distribution, not just the mean
Report: percent Strongly disagree/Disagree, percent Neutral, and percent Agree/Strongly agree for each Core item. Use the distribution to spot polarization (high Disagree and high Agree in the same team).
Customize this: Add 1-2 segmentation cuts that match your change plan (example: impacted vs less-impacted; pilot sites vs non-pilot sites).
- Cut results by the segments that drive action
Start with: team, location/site, tenure band, impact level, and manager vs IC. These cuts tell you where to focus comms and manager coaching.
Watch out: Do not publish results for tiny groups. Protect privacy and keep trust intact.
- Confirm the "why" in comments before you change the plan
Use the two open-text prompts as your validator: Pull the top themes for "What is unclear" and "What should leadership answer next" and link each theme to a comms fix (FAQ update, leader script, manager toolkit).
Do this fast: Tag comments into 5-8 buckets (timeline, local impact, job impact, tools/process, decision making, training, rumors, other). Use how to analyze open-ended responses to keep coding consistent across waves.
- Diagnose the gap: message gap vs channel gap vs cascade gap
- Message gap: Low on "what is changing" and "why now". Action: Rewrite the case-for-change story in plain language and add 2-3 concrete examples.
- Channel gap: Low on "know where to find updates" or "receiving updates often enough". Action: Pick one primary channel, publish an update cadence, and repeat the same link every time.
- Cascade gap: Low on manager items. Action: Give managers a short script, 3 FAQs, and an escalation path for unanswered questions.
Example mapping: If Awareness is fine overall but one site is low on "next 30 days," run a site-specific huddle and publish the local milestone view within a week.
- Route your next move to the right ADKAR stage
- Awareness low: Fix the case for change, scope, and timeline before you push Desire or training.
- Awareness high, but buy-in is still low: Switch to Desire work (WIIFM by role, sponsorship visibility, local impact mitigation).
- Awareness high, but task confusion is high: Shift to Knowledge planning (training needs, job aids, role-based comms).
Response rates: Treat low response as a risk signal, not proof of failure. Pew offers a practical explainer on what low response rates mean, and you can standardize how you report rates using AAPOR Standard Definitions.
Next: Run the same Core 10 again after the next comms wave and compare segment movement (especially high-impact groups and sites).
Frequently Asked Questions
How many questions should an ADKAR Awareness pulse include?
Keep it to a 3-7 minute pulse: 8-12 Likert items for scoring plus 1-2 open-text questions. Keep the Core 10 unchanged each wave so you can trend results cleanly and avoid "apples to oranges" comparisons.
What is a good way to score ADKAR Awareness without overcomplicating it?
Use one Awareness score: average your fixed Core 10 (1-5 Strongly disagree to Strongly agree). Report the score alongside percent favorable (Agree/Strongly agree) and your biggest segment gaps, then confirm the reasons in the two open-text prompts before you change your comms plan.
Should this survey be anonymous or confidential?
Pick anonymous if trust is low or rumors are high and you need maximum candor. Pick confidential if you need targeted follow-up for high-impact groups and you can clearly explain who can access raw data and how results will be reported.
Who should take the survey (everyone or just impacted teams)?
Send to everyone for an enterprise-wide change where awareness needs to be consistent across the org. Otherwise, focus on high-impact groups plus the manager layer, and include only the demographics you will actually use for action (impact level, location, function, manager vs IC).
How often should we run an Awareness survey during a change?
Use a simple cadence: right after the announcement, after each major comms wave, and pre-rollout. Repeat only when the message changes or confusion spikes, and keep the Core 10 wording stable so movement is real trend, not rewording noise.
What if Awareness is high but resistance is still high?
Understanding is not the same as buy-in. If Awareness is strong but you still see resistance, switch to Desire-focused follow-up and pair it with a lightweight pulse like the temperature check survey template or a comms deep dive using the employee communication survey template.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED