Crisis Management Survey Template
Use this crisis management survey to get fast, usable feedback that improves communications, coordination, and recovery. Choose a short mid-incident pulse when you need to remove blockers now, or send the post-incident AAR to capture lessons learned and prioritize fixes. Tag responses by site, function, and role-in-incident so you can triage gaps quickly.
Trusted by 5000+ Brands
When to Use This Crisis Management Survey (Pick the Right Version)
Mid-incident pulse (5-10 questions, 2-4 minutes)
Goal: confirm your messages landed and identify what is blocking work. If the incident is still unfolding, choose this version. First, send it now (or at the next shift change) and tag by site and role-in-incident.
Keep questions focused on: message reach, clarity, immediate needs, and safety status. Drop root-cause and detailed timeline questions until the AAR.
Post-incident AAR (20-35 questions, 8-12 minutes)
Goal: capture what worked, what failed, and what to change next time. If the event has stabilized, send this within 24-72 hours to reduce recall loss, then debrief while details are still concrete.
Use the survey as input to a structured debrief and action register. The CDC outlines a practical approach to debriefing after a crisis in its incident debriefing guidance.
Preparedness pulse (10-15 questions)
Goal: test readiness before the next disruption. If you have not exercised the plan recently, choose this version. First, run it quarterly or after major org/system changes and compare results over time.
Ask about role clarity, playbook awareness, and escalation paths. Follow core survey design standards (clear purpose, neutral wording, and data minimization) from AAPOR survey research best practices.
Do this: avoid collecting unnecessary sensitive incident details. Use prompts like "what step broke" and "what information was missing" -- and tell respondents not to name individuals or paste confidential content into comments.
Who Should Take It (Stakeholders + Safe, Honest Feedback)
Goal: hear from the people who lived the incident, not just the crisis team. If you need operational blockers, sample frontline and supervisors; if you need decision quality, sample the command structure. First, list the groups below and decide what tags you will collect.
- Employees/frontline: message reach, safety/wellbeing, practical blockers, tool access.
- Supervisors/shift leads: staffing, handoffs, local decision making, resource gaps.
- Crisis management team: escalation, decision cadence, roles, cross-functional coordination.
- Functional leaders: IT, Security, HR, Legal, Comms, Operations, Facilities, Finance.
- Optional external version: customers, vendors, partners (keep it shorter and brand-safe).
Tag responses with only what you will use. Start with: site/region, function, and role-in-incident (for example: "frontline responder", "approver", "on-call", "comms sender"). If you need more, add one field at a time (shift, tenure band, or incident type).
Default to anonymous for employees so they can be candid about leadership, workload, and safety. Use identified responses only when follow-up is truly essential (for example, to resolve a current blocker), and state who can access results, how long you will retain them, and how you will protect them -- align with your Security and Privacy requirements.
Use trauma-informed language: offer an opt-out, avoid graphic prompts, and include a support path if the event was distressing. SAMHSA's trauma-informed approach guidance is a helpful checklist for reducing harm.
Crisis Management Survey Questions (Core + Optional Modules)
"I know my role during a crisis and what I am expected to do."
Why it matters: Role confusion creates duplicate work and missed steps. Goal: pinpoint where the plan is not translating to action.
When to use: Use in every version. Segment hard by role-in-incident and site.
"I received timely updates about what changed and what to do next."
Why it matters: Late or inconsistent updates drive rework and unsafe decisions. Use it to check update cadence.
When to use: Mid-incident pulse and AAR. Pair with channel questions (email/SMS/chat/in-person).
"The instructions I received were clear and actionable."
Why it matters: "FYI" updates do not change behavior. This question separates awareness from usability.
When to use: Mid-incident pulse. If scores dip, add a follow-up: "What was unclear?" (no names, no confidential details).
"I knew where to find the latest official guidance (single source of truth)."
Why it matters: Competing documents and chat threads create version conflicts. This identifies information sprawl.
When to use: All versions. If you have multiple sites, this often explains site-to-site variation.
"Escalation paths were clear (who to contact, how, and by when)."
Why it matters: Delayed escalation is a common failure point. This helps you fix routing and on-call coverage.
When to use: Preparedness pulse and AAR. Add a "time to reach help" question for responders.
"Decision making was timely (not rushed, not stalled)."
Why it matters: Slow decisions extend downtime; rushed decisions create churn. This flags where approvals or authority were unclear.
When to use: Crisis team + functional leader AAR. Segment by function to spot bottlenecks.
"The tools and access I needed were available (systems, credentials, equipment)."
Why it matters: Tooling and access issues are fast to fix once you can name them. This helps you triage the top blockers.
When to use: Mid-incident pulse (as "available right now") and AAR (as "available when needed").
"I feel confident we can recover to normal operations within our expected timeframe."
Why it matters: Recovery confidence is a useful north-star outcome. It summarizes comms, coordination, and continuity in one item.
When to use: AAR and stabilization pulses. Trend this across events using the same wording.
Keep / Drop / Add by audience
- Frontline employees: Keep communications + operational blockers + safety/wellbeing. Drop internal command cadence. Add: "What support do you need in the next 24 hours?"
- Supervisors: Keep staffing, handoffs, and local escalation. Add: "Which work could not be performed and why?"
- Crisis team: Keep decision making, escalation, coordination, and single source of truth. Add: "Were roles in the incident command structure clear?"
- IT/Security: Keep tools/access and recovery confidence. Add: "Were runbooks and DR procedures usable under pressure?"
- HR/Comms: Keep reach, clarity, and trust in updates. Add: "Which channels were most reliable for your audience?"
- External customers/partners: Keep timeliness and clarity. Drop internal details. Add: "Did we set expectations about next updates?"
Optional modules (add only what you will act on)
- Communications effectiveness: channel reach, clarity, consistency, frequency, and confidence in guidance.
- Decision making and escalation: authority clarity, approval bottlenecks, time-to-escalate, and handoffs.
- Operational continuity: critical work stopped, workarounds used, supplier dependencies, and recovery readiness.
- Tools and resources: access, credentials, equipment, documentation, and support responsiveness.
- Coordination: cross-team handoffs, shared timeline, and conflict resolution between priorities.
- Safety and wellbeing: fatigue, workload, clarity of safety guidance, and support availability.
- Customer impact: service levels, expectation setting, and resolution speed.
Use consistent response options across events so you can trend results. A 5-point Likert scale is usually enough for crisis feedback. To reduce fear-based answering and response bias, keep wording neutral and avoid prompts that ask for names or confidential incident specifics.
Results Guide: Turn Feedback Into an Action Plan (SWOT + Scorecard)
-
Step 1: Clean and segment (same day)
Goal: make results comparable across sites and roles. If you only do one cut, split by site and role-in-incident. First, remove obvious test/spam entries and check that tags are filled.
- Tag set to keep stable: site/region, function, role-in-incident, shift (optional).
- Minimum base size rule: avoid reporting tiny groups that could re-identify people.
-
Step 2: Score Likert items with distributions and medians
Goal: find the top 3-5 gaps fast. If a site has more "Disagree" than "Agree" on a core item, flag it for triage. First, build a simple table per item: % favorable, % neutral, % unfavorable, plus the median.
Do not hide spread behind averages. Likert-type responses are ordinal, so report the distribution and median consistently (see guidance in Analyzing and Interpreting Data From Likert-Type Scales).
-
Step 3: Group comments into 5-10 themes (and handle sensitive text safely)
Goal: turn open text into fixable work. If you have fewer than 50 comments, code them manually; if you have more, code a sample then validate. First, group comments into themes like "unclear escalation", "tool access", "conflicting updates", and "handoff failures".
- Pull 1-2 anonymized example quotes per theme (remove names and identifiers).
- Route any safety or misconduct reports to the proper channel, not the survey report.
- Use open-ended questions sparingly mid-incident, and set clear instructions: no names, no confidential details.
-
Step 4: Synthesize into a one-page SWOT
Goal: give leaders a clear story they can act on. If themes conflict across sites, call that out and show the split. First, write 3-5 bullets each for Strengths, Weaknesses, Opportunities, and Threats using survey evidence.
- Strengths: what to standardize across sites.
- Weaknesses: what broke repeatedly (process or handoff).
- Opportunities: fixes that reduce time-to-recover.
- Threats: risks if gaps persist (safety, legal, customer).
-
Step 5: Prioritize fixes and close the loop (impact vs effort + scorecard)
Goal: move from feedback to execution. If you have more than 10 candidate fixes, force-rank them with an impact-vs-effort matrix. First, create an action register with owner, due date, and status for the top items.
- Executive-ready report outline: (1) incident snapshot, (2) top 5 gaps, (3) top 5 strengths, (4) site/role hotspots, (5) prioritized actions, (6) owners and dates.
- Balanced scorecard to trend: People (role clarity, wellbeing), Process (escalation, handoffs), Technology (tools/access), Customer (impact and expectation setting).
Track the same scorecard each cycle so you can show improvement over time; evaluations are most useful when they feed real corrective actions and follow-up checks (see Assessing the impact of evaluations of crisis management efforts).
You will have: top gaps by segment + a ranked fix list with owners and dates.
Frequently Asked Questions
How soon after an incident should I send the after-action review survey?
Send the AAR within 24-72 hours, while the sequence of events is still clear. If major fixes take time, run a short follow-up pulse 2-4 weeks later to confirm the changes landed. Keep the tone focused on what happened and what to change -- not fault-finding.
Should this crisis survey be anonymous or identified?
Default to anonymous for employees so they can answer candidly about decisions, workload, and safety. Use identified responses only when you have a specific follow-up need (for example, to resolve a current blocker). If you collect names, explain who can see results, how long you will retain them, and how comments will be used.
How long should the mid-incident pulse be?
Keep it to 5-10 questions and aim for 2-4 minutes. Focus on message reach, clarity, current blockers, and what support is needed now. Save root cause, decision review, and detailed continuity questions for the post-incident AAR.
What demographic or incident details should I avoid collecting?
Collect minimal, purpose-driven tags only (site/region, function, role-in-incident, shift). Avoid sensitive personal data and avoid asking for detailed incident narratives in open text unless you have a secure process and a clear need. Add an instruction that respondents should not name individuals or share confidential information.
How do I compare results across sites or events over time?
Keep question wording and response scales consistent, and keep segmentation fields stable. Trend a small set of metrics each cycle (role clarity, comms clarity, tool effectiveness, recovery confidence). Report distributions and medians for key items, and use the same scorecard categories (People/Process/Technology/Customer) every time.
How do I get a higher response rate during a busy recovery period?
Send a short invite that states the purpose and the time to complete, and keep the survey tight. Schedule 1-2 reminders and time them around shift changes or daily check-ins. If you plan follow-up contacts or incentives, keep them non-coercive and avoid over-burdening the most affected teams.
Related Survey Templates
FREE TO START -- NO CREDIT CARD REQUIRED