Engagement After Reorg Survey Template
Run this 5-10 minute pulse 2-6 weeks after a reorg to spot where people are stuck (clarity, workload, comms, trust, manager support, psychological safety). Use the results to target support by impacted vs not impacted groups, then set a 30/60/90-day stabilization plan you can track with 1-2 follow-up pulses.
Trusted by 5000+ Brands
When to Run This Post-Reorg Engagement Pulse (with a simple rollout calendar)
Run it 2-6 weeks after the reorg (your baseline reset)
Goal: spot reorg risk areas (clarity, workload, comms, trust) so you can set a 30/60/90 plan.
Default: field for 5-7 days with 2 reminders.
- Announce (Day 0): why you are running it, what will be shared/won't be shared, and when results will come back.
- Open (Days 1-7): keep it to 5-10 minutes (same spirit as a temperature check pulse template).
- Remind (2x): one mid-field and one 24 hours before close.
- Close + share toplines (within ~2 weeks): protect trust by showing actions fast.
Run it right after reporting lines or teams change (manager support + cohesion check)
Default: launch once people have had 1-2 weeks of real work in the new team.
Change it if: you are still moving seats/roles weekly -- wait until the moves pause so answers reflect the new reality.
- Announce: managers will review results in team meetings and pick 1-2 actions.
- Field: keep the question set stable so you can trend the next pulse.
- Share back: focus on where to add support (not who to blame).
Use it as a monthly pulse for 2-3 cycles (or when rumors/attrition spike)
Default: pulse every ~30 days for 2-3 rounds to verify fixes are working.
Change it if: you are already running a company-wide pulse monthly -- add only a small reorg module to avoid fatigue.
- Keep the core the same: repeat driver items so movement is comparable.
- Limit changes: rotate only 2-4 optional reorg-specific questions per month.
- Hold the timeline: open 5-7 days, 2 reminders, share within ~2 weeks.
Next: pick your first launch date, then lock your core driver questions.
Post-Reorg Engagement Questions (core drivers + optional impacted branching)
"Overall, I feel engaged in my work."
Why it matters: This is your headline outcome. Track it, but fix drivers (clarity, workload, comms) to move it.
When to use: Include in every run as your trend anchor. Default: 5-point agree scale. Do this now: keep the core stable, add only 2-4 reorg-specific items, and plan a 30-day follow-up pulse.
"Were you directly impacted by the reorg (role, manager, team, or location)?"
Why it matters: This lets you separate reorg friction from your baseline culture and workload issues.
When to use: Put this near the start. Use neutral options like "Yes, significantly" / "Yes, somewhat" / "No" / "Not sure".
"I understand what is expected of me in the new structure."
Why it matters: Role ambiguity creates rework, conflict, and slow decisions after a restructure.
When to use: Always. Treat low scores as a signal to rewrite role charters and success measures.
"I know who owns key decisions that affect my work (decision rights)."
Why it matters: Reorgs often break decision paths before they break morale.
When to use: Use when teams or reporting lines changed. Pair with a short follow-up: "Which decisions are unclear?"
"My workload is manageable right now."
Why it matters: Workload spikes are common after a restructure (handoffs, new tools, new priorities).
When to use: Always. If this drops, ask leaders to stop work, not just add headcount.
"I can raise concerns or mistakes without fear of negative consequences."
Why it matters: Psychological safety drops when people feel uncertain about status, roles, and future opportunities.
When to use: Include in every reorg pulse. Use results to set manager norms (invite dissent, ask for risks, close loops).
"I receive timely, useful updates about changes that affect my work."
Why it matters: Weak comms creates rumor cycles and inconsistent decisions across teams.
When to use: Always. If comms is the top issue, run a deeper follow-up module using an employee communication survey.
"I trust senior leaders to make decisions that are good for the organization."
Why it matters: Trust is the multiplier. When it breaks, even good plans land poorly.
When to use: Always. Pair with an open text item asking what would increase trust.
"My manager helps me prioritize when goals or priorities change."
Why it matters: After a reorg, the manager is the buffer between shifting priorities and daily work.
When to use: Always. If this is low, fix operating rhythm (1:1s, priority resets, removing blockers).
"I have the tools, access, and resources I need to do my job well."
Why it matters: Reorgs often break enablement (systems access, approvals, unclear owners).
When to use: Always. Use low scores to drive a short "top 10 blockers" fix list with owners and dates.
"I see myself working here 6 months from now."
Why it matters: This flags retention risk early, especially in high-demand roles.
When to use: Include when you need an early-warning signal. Report it carefully by larger groups only.
"What should we stop, start, and continue to make the new structure work better?"
Why it matters: This turns sentiment into practical actions teams can test in 30 days.
When to use: Always. Keep it optional and cap text length to reduce fatigue.
"What is the #1 barrier making it hard to do great work right now?"
Why it matters: Barriers after a reorg are often fixable (handoffs, approvals, unclear owners).
When to use: Use when you want a short backlog of fixes leaders can assign and track.
"If leadership could change one thing in the next 30 days, what should it be?"
Why it matters: You get a concrete 30-day action list instead of general frustration.
When to use: Always. Use it to shape your 30/60/90 plan and your share-back message.
Default: keep 8-10 core driver items identical every pulse. Add a small optional module (2-4 items) for what changed in your reorg.
- Swap wording: replace "new structure" with your org names, levels, or team labels.
- Add reorg-specific items: handoffs, decision owners, approval steps, systems access, priority changes.
- Keep scales stable: same 5-point agree scale each cycle so movement is comparable.
| Driver you are measuring | Core item to keep every pulse | Optional reorg module (add 1-2) | Related engagement theme |
|---|---|---|---|
| Role clarity | I understand what is expected of me in the new structure. | I know my top 3 priorities for the next 30 days. | Role clarity (common engagement theme) |
| Decision rights | I know who owns key decisions that affect my work. | For most decisions, I know the decision owner and the escalation path. | Enablement + clarity |
| Workload/capacity | My workload is manageable right now. | We reduced or paused low-priority work after the reorg. | Demands and prioritization |
| Communication | I receive timely, useful updates about changes that affect my work. | I know where to find the latest decisions, org charts, and team responsibilities. | Information flow + alignment |
| Manager support | My manager helps me prioritize when goals or priorities change. | My manager explains how our team fits the new direction. | Coaching + alignment |
Use the mapping above to keep questions anchored to common engagement themes. If you want a familiar reference point, align a few items to themes commonly used in engagement measurement (for example, the areas reflected in the Gallup Q12) without copying any proprietary item set.
Next: lock your core 8-10 items, then add a 2-4 item reorg module.
Sampling, anonymity, and safe segmentation (impacted vs not impacted)
Invite the right people (impacted first, then add a comparison)
Goal: see where the reorg is creating friction so you can target support in the next 30-90 days.
Default: invite all impacted employees. Add an "unimpacted" comparison group if you need separation from baseline issues.
- Impacted: role changed, manager changed, team moved, location changed, or scope changed.
- Not impacted: stayed in the same reporting line and day-to-day work stayed mostly stable.
- Do this now: write your invitation list rule in one sentence so it stays consistent next pulse.
Segment safely (start broad, then drill down)
Rule first: cut results by impacted vs not impacted before any other breakouts.
Rationale: you avoid mixing two different experiences and missing hotspots.
- Then add: org/unit, tenure band, location, role level (only when groups are large enough).
- Avoid: slicing into small teams or unique combos (role title + location + tenure) that can identify people.
- Go deeper: use sample size and reporting basics to set cut rules before you launch.
Set your minimum reporting threshold (and suppress anything smaller)
Rule first: do not publish any result below your minimum n threshold.
Default: set a clear minimum (a common starter rule is n>=10, then adjust for your context) and roll up anything smaller.
- Write it down: what you will share (themes, toplines, big groups) and what you will not share (small cuts, raw comments tied to tiny teams).
- Apply it everywhere: dashboards, slide decks, and manager toolkits.
- Use a standard:anonymisation and set expectations similar to common staff survey confidentiality approaches.
Next: finalize your minimum n and the exact segments you will report.
How to analyze results after a reorg (drivers, distributions, and prioritization)
- Build a driver readout (keep it consistent each pulse)
Goal: identify the 2-3 biggest friction points so you can assign fixes in the next 30-90 days.
- Default: keep a stable core set, then trend it monthly for 2-3 cycles.
- Do this now: list your drivers (clarity, workload, comms, trust, manager support, psych safety) and map each to 1-2 questions.
- Compute top-2 box (favorability) and show the distribution
Report each item as favorable/neutral/unfavorable, not just an average. Distributions show whether you have a broad issue or a polarized one.
- Default: use top-2 box for prioritization.
- Change it if: you need more nuance, and add the full 5-point breakdown in an appendix.
- Compare impacted vs not impacted (your first and most useful cut)
Start with one chart per driver that compares impacted vs not impacted.
- Internal starter target: flag drivers with a clearly material gap, then set your exact cutoff after you see your first pulse baseline and group sizes.
- Default: show this cut in every share-back.
- Change it if: the reorg impacted nearly everyone, and compare by major unit or tenure band instead.
- Rank issues by impact x prevalence (pick the top 3)
Impact: which drivers most relate to your engagement anchor and retention risk item. Prevalence: how many people are unfavorable.
- Default: pick 2-3 priorities max per cycle. Too many priorities kills follow-through.
- Keep the process simple and repeatable (for example, using the planning and follow-through steps outlined in SHRM guidance on conducting employee surveys).
- Close the loop within ~2 weeks (and say what will not change)
Publish what you heard, what will change in 30/60/90 days, and what will not change (with a short rationale). Speed matters more than perfect slides.
- Default: share toplines within about 2 weeks of close to protect trust.
- Change it if: you need legal review, then share an interim update with dates.
- Make the share-back part of your operating rhythm, consistent with employee voice guidance such as the CIPD factsheet on employee voice (ask, listen, communicate outcomes).
Next: pick your 2-3 priorities and assign owners before you share results.
Turn findings into a 30/60/90-day stabilization plan (leader + manager actions)
- 30/60/90 plan (set it in writing): Goal: turn survey signals into a short fix list. Default: 2-3 priorities total, not per team. Do this now: name the owner, the change, and the date for each priority.
- Share team results in a 20-minute meeting: Managers should review themes, confirm "what we heard," then ask for one concrete improvement idea.
- Pick 1-2 focus actions per team: Default: one clarity/operating change (decision rights, handoffs) and one rhythm change (1:1 cadence, comms cadence). Change it if workload is the top issue -- then focus on stopping work.
- Clarify decision rights and handoffs: Publish decision owners for the top cross-team decisions. Reset RACI-like documents only where confusion is real.
- Reset priorities and reduce work in progress: Default: stop or pause 1-2 lower-value workstreams per team for 30 days. Make tradeoffs visible to reduce silent overload.
- Strengthen manager support: Set a weekly 1:1 minimum for impacted employees for the first 60 days. If manager support is the top driver, follow up with a focused manager effectiveness survey to pinpoint coaching and priority-setting gaps.
- Improve comms cadence (what, when, where): Default: one weekly written update, one live Q&A every 2-4 weeks, and a single source of truth for decisions. Repeat the same channels so rumors have less room.
- Use guardrails that protect trust: Do not use results for performance evaluation. Avoid blame framing. Keep core questions stable so people see honest trending, not moving goalposts.
- Re-pulse in 30 days: Default: run the same core drivers, then check if your 2-3 priorities moved. Change it if adoption is slow -- re-pulse at 45-60 days, but keep the share-back date firm.
Next: draft your 30-day commitments and manager talking points before you publish results.
Frequently Asked Questions
When is the best time to run an engagement survey after a reorg?
Run your first pulse 2-6 weeks after the reorg, once people have lived in the new structure. Then run 1-2 follow-up pulses at ~30-day intervals to confirm your fixes are working. Keep it short (5-10 minutes), keep the core questions stable, and show actions after each cycle to avoid fatigue.
Should the survey be anonymous or confidential -- and what minimum group size should we report?
Default to anonymity for reorg feedback so people answer candidly about clarity, trust, and manager support. Set a minimum reporting size (often n>=10) and suppress or roll up any cut smaller than your threshold. If you want a deeper methodology walkthrough, use sample size and reporting basics to set your rules before you launch.
How do we compare impacted vs not impacted employees without making it political?
Use one neutral self-report item like "Were you directly impacted?" and explain why you are asking: to target support, not to assign blame. Report the comparison as "where to focus help" (for example, clearer decision owners or workload resets) and avoid naming small teams. Share the same action-planning process for both groups so it feels fair.
How do we customize the template for our reorg without losing trend visibility?
Keep a stable core driver set (8-10 items) in every pulse so movement is comparable. Swap in your reorg terminology (new org names, levels, team labels) without changing the meaning. Add a small optional module of 2-4 reorg-specific items (handoffs, decision rights, access) and keep the same scale each cycle.
What should we share back to employees after the survey closes?
Share topline results, the 2-3 priorities you will focus on, and what will change in 30/60/90 days. Also share what will not change and why, so people do not fill gaps with rumors. Reinforce what you will share and won't share to protect anonymity, then ask managers to review team-level themes and actions.
How should we analyze results beyond average scores?
Show distributions (favorable/neutral/unfavorable) so you can see polarization, not just the mean. Compare impacted vs not impacted first, then look for consistent patterns across larger segments. Rank issues by impact x prevalence and pick 2-3 priorities you can realistically move in the next 30-60 days.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED