Emergency Response
Multi-agency, multi-stakeholder programs where procurement, compliance, and mission alignment determine success.
Inside this journey
-
Pre-Discovery
Align the room on outcomes, decision process, and constraints before deeper discovery.
-
Stakeholder Alignment
Confirm decision roles, timelines, concurrent activation risks, and each stakeholder’s ‘good’ outcome for readiness and surge response.
Alignment Questions
Setting the Table: A Quick Snapshot of Who You Are
- Please introduce yourself: name, title, agency/organization, and primary operating jurisdiction.
- Which of these best describes your primary mission area?
- Which geographic scope do you support (select all that apply)?
- What recent trigger brought you to consider supplemental surge/responder support?
- How do you currently define ‘readiness’ for surge response in one sentence?
- Who is the primary operational POC we should work with for discovery and onboarding (name, title, clearance level)?
Who Really Makes the Call When Time Is Tight?
- When minutes matter, is there a single person or a committee that signs off on surge activations—and which is it?
- List the decision authorities we must engage for activation (names/titles/roles).
- What are your typical approval timelines for a surge activation (from request to deploy order)?
- Describe the formal escalation path when two missions compete for the same cleared staff.
- Which stakeholders must be consulted before deployment (select all that apply)?
- How comfortable are you delegating 12-hour deploy authority to a contractor under pre-approved governance?
If We Had to Be Ready Tomorrow, What Would Break?
- If we were honest, which pieces of your current EOC staffing are most likely to fail to show up within hour zero to 24?
- Please provide current baseline counts for key roles (EOC director, operations, logistics, planning, public information):
- How many cleared, deployable personnel does your jurisdiction have on standby today?
- Which roles show the largest surge shortfalls in real missions (select all that apply)?
- What is your typical clearance/vetting timeline for new contractors (background check, PIV/credentialing, other)?
- Do you maintain a formal surge roster that can be accessed and mobilized within 12 hours?
What Keeps You Awake in Those First 72 Hours?
- What worries you most about bringing external staff into your Incident Command during the first three days?
- Tell us about a recent activation where integration or speed was a problem—what specifically went wrong?
- What onboarding, verification, or shadowing do you require before external staff take operational responsibilities?
- How do you currently validate NIMS/ICS certification and operational experience?
- Which logistical failures in early response have hurt operations most (select up to 3)?
Are Our Exercises Telling the Truth or Giving Everyone a Pass?
- When was your last full-scale exercise that tested EOC surge and first-72-hour operations?
- How realistic are your exercises in simulating concurrent missions, resource conflicts, and political pressures?
- Did your last AAR include clear corrective actions, owners, and timelines?
- Which AAR findings remain unimplemented and why (be specific)?
- How often do you run multi-agency exercises with FEMA and neighboring jurisdictions?
- Do your exercises explicitly test surge fill rates and ICS handoffs within 12/24/72 hour windows?
If Success Weren't Vague, How Would We Measure It?
- Which of these KPIs would definitively prove a successful activation for you (select up to 4)?
- What activation speed thresholds are non-negotiable for your agency?
- What surge fill rates would you require at 24 and 72 hours (enter percentages or ranges)?
- Which SLAs must be contractual (e.g., deploy timelines, clearance confirmations) versus recommended?
- How would you observe and score ‘good’ ICS integration in the field (concrete behaviors or outcomes)?
- Who in your organization will own ongoing KPI monitoring and post-activation reporting (name/title)?
Constraints No One Mentions Until It’s Too Late
- What hidden rules, standing commitments, or third-party contracts have tripped up surge plans before?
- Are your cleared staff frequently committed to other activations or mutual aid agreements?
- Which contractual, procurement, or legal constraints limit how quickly we can scale external staffing?
- What transport or staging limitations (airlift, ferry, road access) routinely slow responder movement in your region?
- Do you have a documented backfill plan for normal operations when staff deploy? If yes, how often is it rehearsed?
- How often has your agency declined federal assistance due to local constraints (political, legal, or resource conflicts)?
If We Start Tomorrow, What Would Earn Your Trust in 30 Days?
- If you gave us the green light today, what three tangible things must be in place inside 30 days for you to feel confident?
- What is an acceptable timeline for verifying clearances and credentials for an initial surge wave?
- Which staging hubs or logistics sites would you prefer we use for pre-positioning resources?
- What communications and interoperability systems must work out-of-the-box (select all that apply)?
- What governance cadence (reports, briefings, decision checkpoints) would make you comfortable during onboarding and initial deployments?
- Which initial contract acceptance criteria are non-negotiable for you (select all that apply)?
-
Current State Mapping
Document existing EOC staffing, cleared personnel rosters, surge shortfalls, exercise history, and failure modes in the first 72 hours.
Current State
Start Here: A Snapshot of Your Current Reality
- What agency and role are you representing in this conversation today?
- How many staff from your agency are currently rostered and available for external deployment under existing agreements?
- Briefly describe your steady-state EOC staffing model (roles, shift cadence, on-call arrangements).
- Which triggers most commonly prompt you to request external surge support?
- How confident are you that your current roster includes personnel cleared to the levels needed for federal mission assignments?
If the Alarm Rings Tomorrow, What Breaks First?
- What's the single biggest operational gap that appears in the first 24–72 hours of an incident?
- Which capabilities typically struggle most inside that window?
- How often have you experienced unmet surge needs during the first 72 hours across the last five activations or exercises?
- Give one concrete example where that gap created mission risk—what happened and what was the immediate impact?
- When those gaps occur, how does your organization typically respond operationally?
Who's Really in the Room When It Matters?
- Right now, what percent of your roster is cleared and deployment-ready within a 12-hour window?
- What clearance levels are required or preferred for personnel supporting federal mission assignments in your jurisdiction?
- Describe any recurring administrative or policy bottlenecks that delay getting staff fully cleared or deployment-ready.
- Have rostered staff ever been reallocated to other missions, and if so how often does that materially reduce your available surge?
- Which mechanisms do you currently rely on to backfill cleared roles quickly?
The First 72 Hours: What Feels Impossible vs. What’s Doable
- Which specific activity in the first 72 hours do you consider 'mission-critical but chronically under-resourced'?
- How do you prioritize tasks in that initial window—what must be resourced immediately and what typically waits?
- Which timelines are non-negotiable for your leadership (for example, 12-hour deploy, 24-hour surge fill)?
- Tell us about a recent activation where timelines slipped—what caused the delay and what downstream effects did you see?
- How does leadership define a 'failure' during the first 72 hours (missed SLA, public harm, mission re-classification, political scrutiny)?
Practice vs Reality: When Drills Lie to You
- What’s one thing your exercises consistently fail to simulate that reality always exposes?
- How often do your exercises incorporate real-life constraints like clearance delays, equipment shortages, or concurrent missions?
- Who usually designs and validates your exercises—internal staff, contractors, federal partners, or a mix?
- When AARs identify capability gaps, how consistently are corrective actions assigned and tracked to closure?
- Share a single AAR finding that should have changed practice but didn’t—what blocked the improvement?
Failure Modes: What Keeps You Awake at Night?
- If you had to name the single failure mode most likely to cripple your response in the first 72 hours, what would it be?
- Which of these root causes are present today in your organization?
- How do past failures change current planning—are they driving resourcing decisions or mostly forgotten after the event?
- What is the emotional and operational toll on your team after a rocky first 72 hours (burnout, loss of confidence, leadership scrutiny)?
- What single change—policy, resource, or tool—would most reduce the likelihood of that failure mode recurring?
Evidence & Data: How Do You Know You're Ready?
- When you ask for proof of readiness, which evidence convinces you most (exercise metrics, historical deployments, roster reports, etc.)?
- How frequently do you run formal readiness validations (tabletops, full-scale, checklist audits) and who signs off?
- Do you currently maintain SLAs for activation speed and surge fill rates? Please select all that apply.
- How accessible and current are your clearance and roster datasets to operational commanders during an activation?
- Please paste or describe a recent readiness metric (for example: surge fill % at 24 hours) and the date it was measured.
Where A Little Help Would Make a Big Difference
- If you could add one capability this month that would most improve your first-72-hour response, what would it be?
- Which engagement models would you be open to for delivering rapid support?
- Realistically, how long would onboarding need to take before the capability meaningfully improves your readiness?
- What are the primary concerns that would prevent you from contracting rapid surge capability today (select all that apply)?
- Who within your organization (roles or offices) would need to be engaged or sign off to move forward with a readiness program?
- Would you like us to prepare a short, tailored brief showing how pre-positioned NIMS-certified teams and logistics playbooks change 12–72 hour outcomes for your jurisdiction?
-
-
Outcome Discovery
Define measurable success signals (activation speed, surge fill rates, ICS integration, actionable after-action items) and non-negotiable SLAs.
Discovery Questions
Start Here: Which outcome keeps you up at night?
- Which single outcome would you prioritize above all else for the first 72 hours of a disaster response?
- Who on your team is the final arbiter of whether a deployed team is ‘mission-ready’—name role/title and contact cadence?
- How do you currently score readiness before activation (qualitative check, rostered clearance, exercise performance, other)?
- When you imagine that prioritized outcome achieved, what immediate operational or human impact do you expect to see?
- On a scale from 1–5, how urgent is resolving this outcome in the coming 6 months?
If the first 72 hours go sideways, who pays the price?
- If surge staffing fails to meet demand in the first 72 hours, what are the most serious consequences you worry about?
- Tell me about a recent incident or exercise where early surge or ICS integration fell short—what specifically failed and how did it feel to your leadership?
- How frequently do you experience concurrent activations that compete for your cleared personnel?
- When those shortfalls happen, who in your organization is pressured most—operations, legal, elected officials, or another group?
- What have you tried internally to mitigate early surge gaps, and where did those attempts fall short?
What would ‘mission-ready in 12 hours’ actually force you to change?
- What are your absolute, must-meet deploy timelines (e.g., 12-hour deploy, 24-hour surge) that you expect a contractor to commit to?
- What clearance levels, credentialing, or background checks must be verified before a contractor can self-deploy to your EOC?
- Describe the minimum team composition you’d accept in a first-wave deploy (roles, certs, and relative staffing levels).
- Which activation triggers would allow for immediate contractor push (governor declaration, FEMA MA, state emergency order, local request, other)?
- What verification or acceptance step do you insist on before handing over operational control to a deployed contractor team?
The SLA you’d never compromise—what is it?
- Which single SLA would you classify as non-negotiable for any vendor supporting your EOC?
- For surge fill rates, what minimum percentage by role would you require at 12, 24, and 72 hours? Please specify roles and percentages.
- If an SLA is missed, what remedies or consequences are reasonable to you (financial credit, replacement staff, corrective action plan, contract termination)?
- Are there legal, policy, or union constraints we must design SLAs around (e.g., collective bargaining, state hiring rules)?
- How important is having SLAs tied to measurable tools (dashboards, automated alerts) versus narrative reports?
How will we measure success without guessing?
- Which of the following KPIs matter most for your leadership to feel confident the mission is succeeding?
- What cadence and format of reporting do your decision-makers expect during the first 72 hours and the first 30 days?
- Who will be responsible on your side to validate KPI accuracy and sign off on acceptance criteria?
- Are there external stakeholders (FEMA, state legislature, public health) who require tailored KPI views or reports?
- How would you like AAR findings to be packaged so they are actionable—raw findings, prioritized actions with owners, timelineed roadmap, or another format?
When your door opens, will our people feel like they belong?
- How important is pre-existing NIMS/ICS certification versus practical EOC experience when you accept external staff?
- Describe any onboarding rituals you require—position shadowing, badge issuance, safety brief, ICS check-in—before contractors can work independently.
- What role do internal liaisons or mentors play in integrating external teams, and how soon must they be assigned?
- Have you seen cultural or communication mismatches between contractors and your in-house staff? If so, what were the clearest signs?
- Would you allow pre-deployment joint exercises or table-tops to validate integration before a real activation?
Who closes the loop so lessons become improvements?
- After an incident, how fast must AAR findings be translated into corrective actions to satisfy your leadership?
- Who on your team owns corrective action tracking today (title/role), and do they have bandwidth to manage vendor-driven action items?
- Which closure criteria make you confident an AAR action item is truly complete (evidence, verification exercise, sign-off)?
- Would you want a vendor-operated dashboard for tracking corrective actions, or integrated into your existing systems?
- How should responsibility be split when corrective actions require vendor and agency collaboration?
Make or break: what would you need to sign a pilot or MOU?
- What minimum evidence, trial length, or exercise result would convince you to move from pilot to full contract?
- Who needs to be at the table to finalize SLAs—roles/titles and non-negotiable approvers?
- What timeline is realistic for you to review and approve a proposed set of SLAs and acceptance criteria?
- What concerns would make you pause signing an activation agreement even after a successful pilot?
- What would be a fair first step for us to demonstrate value—joint exercise, small-scale deployment, or SLA-backed trial?
-
Solution Experience
Walk through realistic incident scenarios using the customer’s context to validate how pre-positioned teams, NIMS-certified staff, and logistics playbooks deliver the target outcomes.
Experience Meetings
- Current State & Consequence Alignment
- Scenario Selection & Design (Customer-context Tabletop)
- Live Scenario Walkthrough — 0–72 Hour Surge Simulation (Tabletop with Proof Points)
- Logistics Playbook Drill & Communications Handoff
- Validation, Acceptance Criteria & Next Steps (Decision & Mutual Commit Draft)
- Seller to update logistics playbook with customer-specific staging points, clearance owners, and alternate routes.
- Validate NIMS-certified staff integrate into ICS roles without extended orientation delays.
- Confirm logistics playbook actions produce modeled fill-rates that meet or exceed SLAs or capture precise shortfalls.
- Force customer validation at each checkpoint to convert interest into verified commitments or documented changes.
- Seller to produce a time-stamped runbook of the walkthrough showing personnel named/roles and timestamps for each activation milestone.
- Customer to indicate accept/modify for each validation checkpoint and provide reasons for any modifiers.
- Joint gap log entry for any SLA misses with assigned owners and target remediation dates.
- Playbook Overview Tied to Problem
- Confirm logistics playbook actions map to customer facilities and achieve required timelines.
- Ensure FEMA mission assignment processes are integrated and do not create administrative delays.
- Validate communications templates and reporting cadence are interoperable with the customer's EOC.
- Introductions & Purpose
- Customer to confirm preferred FEMA MA contacts and administrative POC for rapid processing.
- Schedule a field validation or tabletop drill to exercise vendor failover within 30 days.
- Results Snapshot vs Success Signals
- Obtain customer agreement on which success signals are satisfied and which require remediation.
- Translate unresolved SLAs into concrete remediation actions with owners and deadlines.
- Agree governance rules for prioritization during concurrent missions and prepare contract module language for mutual commit.
- Schedule the Pre-Deployment Readiness checkpoint with required artifacts and sign-off criteria.
- Seller to deliver a Validation Report summarizing run metrics, gap list, and suggested contract addenda within 3 business days.
- Customer to review and provide formal acceptance or comment on the Validation Report and acceptance criteria within 5 business days.
- Both parties to finalize remediation assignments and confirm the date for the Pre-Deployment Readiness checkpoint.
- Produce and gain customer sign-off on a one-sentence Current State describing exactly where operations break.
- Quantify the operational and political consequences of the current state in measurable terms.
- Agree a one-sentence Future State (operational outcome) that the Solution Experience will prove.
- Identify and commit to pre-work artifacts required for scenario design.
- Customer to provide recent AARs, cleared personnel roster, and typical activation timelines (within 5 business days).
- Seller to draft one-sentence Current State, Consequence summary (with metrics), and proposed Future State and circulate for approval.
- Schedule the Scenario Design meeting once artifacts are received.
- Recap Preconditions
- Select and scope 2–3 realistic scenarios grounded in the customer’s context.
- Define clear, measurable success signals and SLAs for each scenario.
- Confirm participants, data inputs, and inject owners required to run the scenario walkthroughs.
- Customer to confirm subject-matter expert attendees and provide facility/staging point details for each scenario.
- Seller to prepare scenario scripts, timeline injects, and a metrics tracking spreadsheet aligned to agreed SLAs.
- Both parties to schedule the Live Scenario Walkthrough and circulation of pre-reads 48 hours in advance.
- One-sentence Recap & Rules of Engagement
- Demonstrate activation within 12 hours and surge sustainment across 24–72 hours with evidence tied to customer risk.
- Acceptance Criteria & Outstanding Gaps
- 0–12 Hour Activation: Proof of Activation Speed
- Choose Priority Scenarios
- One-Sentence Current State
- Staging, Transport, and Clearance Walkthrough
- FEMA Mission Assignment & Administrative Handoff
- Remediation Plan & Timeline
- 12–24 Hour: ICS Integration & Role Attach
- Explicit Consequence Quantification
- Define Scenario Scope & Start Conditions
- Governance for Concurrent Missions
- One-Sentence Future State
- 24–72 Hour: Surge Fill Rates & Logistics Execution
- Map Success Signals & SLAs to Each Scenario
- Communications Interoperability & Reporting
- Agree Injects, Roles, and Data Inputs
- Forced Validation Checkpoints
- Validation Criteria & Pre-work Assignment
- Contingency Routes and Vendor Failover
- Mutual Next Steps & Sign-off
- Capture Deviations and Mitigations
-
Solution Scope
Define scope modules (readiness rosters, training & exercises, EOC staffing, logistics, mass care, damage assessment, AAR) with roles, SLAs, and acceptance criteria.
Scope Configuration
- Deploy NIMS-Certified EOC Command Team
- Staff 24/7 Emergency Operations Center Shifts
- Operate Joint Information Center (Public Information)
- Provide Interagency Liaison Teams for Unified Command
- Establish and Run Logistics Staging Area (SSA)
- Manage Material Distribution and Points of Distribution (PODs)
- Operate Mass Care Shelters and Intake Processing
- Run Bulk Feeding and Mobile Kitchen Operations
- Deploy Medical Surge Staffing for Alternate Care Site
- Operate Volunteer and Donations Reception Center
- Provide Fleet, Fueling, and Transportation Coordination
- Staff FEMA Mission Assignment and Funding Liaison Team
Scope Questions
Deploy NIMS-Certified EOC Command Team
- Should a NIMS-certified EOC command team be included in scope for this engagement?
- Which command roles must be provided (select all that apply)?
- What activation timeline do you require for the command team?
- Are there clearance, background check, or credentialing requirements for command staff?
- Which deliverables define acceptance for the command team (select all that apply)?
- Provide any agency-specific integration notes or point-of-contact requirements for the command team.
Staff 24/7 Emergency Operations Center Shifts
- Do you want 24/7 staffed EOC shifts included in scope?
- What shift model do you require?
- How many staff per shift are required (estimate)?
- What certifications or training must EOC staff hold?
- Are there equipment, workstation, or data-feed requirements for staffed shifts (e.g., secured comms, GIS feeds)?
- What SLAs or acceptance criteria should we meet for shift staffing?
Operate Joint Information Center (Public Information)
- Should operation of a Joint Information Center (JIC) be included?
- How many Public Information Officers (PIOs) do you expect to require?
- Which public communication channels must the JIC manage (select all that apply)?
- What approval or clearance process must the JIC follow before public messaging is published?
- Are language access and accessibility services required (e.g., translation, ASL)?
- What acceptance criteria should the JIC meet (response times, message accuracy, stakeholder approvals)?
Provide Interagency Liaison Teams for Unified Command
- Do you require interagency liaison teams embedded into Unified Command?
- Which partner agencies should be prioritized for liaison coverage (select all that apply)?
- How many liaison personnel per partner/agency are required (estimate)?
- Are there specific meeting, reporting, or situational products the liaison must produce?
- Do liaison staff require background checks, agency badges, or system access?
- What acceptance criteria define effective liaison (e.g., meeting attendance, issue resolution rate)?
Establish and Run Logistics Staging Area (SSA)
- Should establishment and operation of a Logistics Staging Area (SSA) be in scope?
- Expected daily throughput or SSA scale?
- Which logistics functions must the SSA perform (select all that apply)?
- What site requirements or constraints should we know (location, security, access hours, utilities)?
- Are SSA staff subject to specific security or credentialing requirements?
- Which SLAs should the SSA meet (e.g., time-to-available, inventory accuracy)?
Manage Material Distribution and Points of Distribution (PODs)
- Do you want material distribution and POD operations included?
- How many POD sites and approximate locations are anticipated?
- What operating hours are required per POD?
- What types of items will be distributed at PODs (select all that apply)?
- Preferred staffing model for PODs?
- What acceptance metrics should PODs meet (throughput, wait time, safety)?
Operate Mass Care Shelters and Intake Processing
- Should mass care shelter operations and intake processing be included?
- What is the expected maximum shelter capacity you need to support?
- Which mass care services must be provided (select all that apply)?
- What shelter duration do you anticipate (select one)?
- What credentialing or training requirements apply to shelter staff?
- What acceptance criteria should shelter operations meet (e.g., intake time, triage timeframe, safety metrics)?
Run Bulk Feeding and Mobile Kitchen Operations
- Do you want bulk feeding and mobile kitchen services included?
- Estimated meal volume required per day?
- Which feeding models should we provide (select all that apply)?
- Are there special dietary, cultural, or food-safety requirements to accommodate?
- Do local health permits or inspections apply to feeding operations?
- What acceptance criteria should feeding operations meet (timeliness, % meals delivered, safety)?
Deploy Medical Surge Staffing for Alternate Care Site
- Should medical surge staffing for an Alternate Care Site be included?
- Which clinical roles are required (select all that apply)?
- What level of clinical care will the ACS provide?
- What target patient census should staffing be sized for?
- Are there licensure, privileging, or rapid credentialing processes required for clinical staff?
- What acceptance criteria should medical surge staffing meet (staff-to-patient ratios, documentation integration)?
Operate Volunteer and Donations Reception Center
- Do you want a Volunteer and Donations Reception Center (VDRC) operated as part of scope?
- Which types of donations do you expect to process (select all that apply)?
- Which volunteer management services are required (select all that apply)?
- Where will donations be stored or staged (select one)?
- Are there legal, tax, or documentation requirements for donations processing we must accommodate?
- What acceptance criteria should the VDRC meet (processing time, inventory accuracy, volunteer throughput)?
-
Mutual Commit
Finalize contract modules, activation timelines (including 12-hour deploy and 24-hour surge commitments), priorities during concurrent missions, and governance.
Agreement Modules
- Master Services Agreement (MSA)
- Statement of Work (SOW)
- Activation & Mobilization Annex
- Service Level Agreement (SLA) & Performance Gates
- Pricing, Billing & Cost Schedule
- Priority Matrix for Concurrent Missions
- Governance, Escalation & Change Control
- Staffing Roster & Clearance Attachments
- Logistics & Prepositioning Annex
- Security, Data Sharing & Privacy Addendum
- Insurance, Liability & Indemnification
- Acceptance Criteria & After-Action Requirements
- Exercise & Readiness Schedule
- Continuity & Backfill Commitment
- Termination, Renewal & Extension Terms
- Regulatory & Compliance Acknowledgment
-
Deployment
Operationalize rollout with readiness checks, enablement, and outcome validation.
-
Pre-Deployment Readiness
Validate clearances, backfill plans, logistics staging, communications interoperability, and contingency staffing to prevent unmet surge needs.
Readiness Questions
Quick Read: Your Readiness Snapshot
- In one sentence, how would you describe your agency’s current ability to staff an EOC or surge team within a 12–24 hour window?
- Which triggers most often require you to scale to surge?
- How often does your agency activate an EOC or request federal surge support?
- What formal standby or pre‑positioned contracts (if any) do you currently rely on for staffing and logistics?
- Which statement best describes your cleared personnel roster today?
- If you had to name the single readiness worry that keeps you up at night, what would it be?
When the Clock Starts, What Falls Apart?
- In the first 24–72 hours of a major incident, what problem almost always eats up your bandwidth or causes mission failure?
- Select the failure modes you have seen repeatedly in early response.
- Tell us about a specific incident or exercise where that early failure played out—what happened and what were the immediate consequences?
- How long did it take to stabilize the situation in that case, and what backfill or mitigation steps were used?
- Who on your team still carries responsibility for those early failures, and how do those issues affect their ability to lead?
Who’s Actually Calling the Shots?
- If two concurrent missions require the same cleared personnel, how is priority decided—and has that process ever prevented a necessary deployment?
- Which roles are pre-authorized to approve activations and task orders in your organization?
- Describe your typical activation timelines and the specific decision points that trigger a 12‑hour deploy versus a 24‑hour surge.
- What political, legal, or logistical constraints most often extend those timelines?
- How do you document each stakeholder’s ‘good outcome’ so surge teams know what success looks like during activation?
Are Contracted Teams a Force Multiplier—or a Fragment?
- What has been the most painful mismatch between a contractor’s capabilities and your expectations for Incident Command integration?
- Which contractor shortcomings have you encountered in real responses or exercises?
- Describe an event where contractor onboarding slowed the response—how much time was lost and what specific onboarding steps caused delay?
- What training, verification, or pre-deployment actions would make a contractor truly 'plug-and-play' for your EOC?
- How confident do you emotionally feel about outside teams integrating under pressure—what would increase or decrease that confidence?
What Would a Perfect First 72 Hours Actually Look Like?
- Visualize a response where the first 72 hours go exactly as needed—what would you see, hear, and measure at hour 72?
- Which measurable success signals are most important to you during that period?
- What SLAs or non‑negotiables would make you comfortable signing a readiness contract today?
- How would you prefer after-action findings delivered so they reliably translate into corrective action?
- Which surge metrics do you currently track during activations, and which critical ones are missing from your current reports?
Where Policy and Practice Quietly Collide
- Which internal policies, union rules, or clearance processes have repeatedly delayed deployments when every hour mattered?
- Select the administrative hurdles that most often block or slow deployable staff.
- How do you currently backfill essential day-to-day roles when personnel are deployed?
- Tell us about a time a policy stopped a qualified responder from deploying—what was the downstream impact and how was it resolved (if at all)?
- If you could change one policy or rule tomorrow to materially improve surge performance, what would it be and why?
What Would Make You Say Yes—Today?
- If a vendor proposed a readiness program this week, what non-negotiable guarantees or governance elements would move you to sign?
- Which contractual guarantees are deal‑makers for your team?
- How should priorities during concurrent missions be codified so they are enforceable and transparent in real time?
- What reporting cadence and transparency (dashboards, meeting rhythm, SLA alerts) would you require after award to feel comfortable?
- Who else (roles, agencies, or elected officials) must be involved in final approval, and what evidence or assurances will they demand?
-
Deployment Enablement
Schedule and execute staffing mobilization, logistics playbook activation, EOC handoffs, and coordination with FEMA mission assignment timelines.
-
Validation Checklist
Verify ICS integration, surge fill rates against SLAs, exercise realism, and that AAR findings are routable into corrective action workflows.
Validation Questions
Quick Snapshot — Who You Are and What’s Urgent
- Please tell us your role, agency, and the jurisdiction you support (city/county/state/federal region).
- What event or trigger is driving this conversation today?
- How many active disaster or high-consequence activations has your organization managed in the last 24 months?
- Who will be the primary decision-maker for readiness and surge agreements on your side?
- Which of these outcomes matter most to you right now? (Select up to three)
What Keeps You Awake in the First 72 Hours?
- Imagine your worst first-72-hours scenario — what's the single thing that would make that initial period disastrous?
- How often have you faced a gap in cleared, deployable staffing during an activation?
- When surge staffing has arrived late in the past, what operational impacts did you see in those first three days?
- Who on your team bears the emotional burden of those early failures (roles), and how does it affect decision-making under stress?
- In your experience, which clearance or credentialing issue causes the most delays?
If We Could Measure Success in Real Time, What Would It Look Like?
- If you could pick one single metric that would prove a contractor is delivering in the first 72 hours, what would that be?
- How do you define acceptable activation speed for mission-critical teams?
- What minimum surge fill rate do you require for the first 24 and first 72 hours? (please specify percentages)
- Beyond raw numbers, what qualitative signs tell you a vendor has truly integrated into your ICS (examples or behaviors)?
- Which SLAs are non-negotiable for you? (Select all that apply)
- Who needs to see these metrics in real time (roles or external partners) and how frequently?
Where Past Plans Have Fallen Short — Tell Us the True Story
- When an exercise or real event exposed gaps, what was the single most surprising failing you discovered?
- How realistic were your most recent exercises in replicating concurrent mission pressures (e.g., multiple counties, overlapping activations)?
- Describe a recent AAR finding that never became an implemented corrective action — what stopped it from being resolved?
- How often do contractors or temporary staff require significant ICS orientation before they can be effective, and what does that orientation usually entail?
- Which systemic failure tends to repeat across incidents (staffing gaps, logistics, comms, clearances, decision delays)?
What Would Perfect Readiness Actually Change for You?
- If surge teams always arrived fully cleared and integrated within your target SLA, what's the first operational benefit you'd expect to see?
- How would steady-state preparedness (4–8 week onboarding + ongoing exercises) change your staffing confidence during off-season months?
- What acceptance criteria would you set for a readiness roster module (e.g., certification levels, time-to-deploy, percentage cleared)?
- In a perfect world, how would AAR findings be routed into corrective actions — who would own them and what timelines feel reasonable?
- What would early signs of success feel like to your leadership in the first 30 days after a new readiness program launches?
The Hard Trade-offs You’ll Have to Make
- What trade-off would you struggle with most: faster activation at higher cost, or lower cost with potentially slower availability?
- How flexible is your budget for pre-positioned teams versus pay-as-you-go surge resources?
- Would you accept partial role fills immediately (e.g., 60% of critical roles in 12 hours) if backed by a fast ramp plan for the rest?
- Which constraint most limits your ability to accept a vendor’s offer: procurement rules, clearance timelines, budget, or governance approvals?
- If we proposed an accelerated pilot that required temporary exception to one policy, which policy would you be most willing to adjust?
How You Prefer to See Corrections Happen — AAR to Action
- What’s your current process for turning an AAR recommendation into a funded corrective action?
- Who typically owns corrective action follow-through in your organization (title or team)?
- How long do you think is reasonable between identifying a gap in an AAR and seeing a validated fix in exercises or ops?
- What form of evidence convinces you a corrective action worked (exercise performance, deployment outcomes, external audit)?
- Would you find value in a routable corrective action platform that assigns owners, deadlines, and automated reminders?
Commitment Signals — When Would You Say Yes?
- What are the top three contractual assurances that would make you comfortable committing to a readiness/surge partner?
- How important is pre-authorization or pre-clearance of staff before a mission assignment is issued?
- Which governance mechanism would make you most confident (single decision authority, joint governance board, monthly readiness reviews)?
- If a vendor can demonstrate similar performance in three historical missions, would that materially affect your willingness to sign a modular contract?
- What internal approvals are required before you can sign readiness modules (list roles/committees)?
Validation Metrics & Reporting — Who Needs What and How Often?
- Who are the primary internal and external stakeholders that must receive operations/validation reports during an activation?
- How frequently do stakeholders need validation reporting during steady-state vs. during activation?
- Which dashboard views or KPIs do you expect to see in a contractor-delivered validation report?
- What format works best for your leadership: one-page executive brief, operational dashboard, raw data export, or formal report?
- Are there regulatory or audit requirements we should include in validation reporting (e.g., grant compliance fields)? Please specify.
Closing — Immediate Risks and Next Steps
- What is the single most important next step you want from us after this discovery (pilot, proposal, capability demo, clearance plan)?
- What immediate risk do you need mitigated in the next 30 days to avoid mission failure?
- Who should be on the core working team for next steps from your side (names and roles), and who is our point of contact?
- How soon can you schedule a 60–90 minute validation workshop or scenario walkthrough with your leadership?
- Is there any political, operational, or procurement constraint we should know about before proposing contract modules?
-
-
Success
Review performance vs success signals, document lessons learned, and maintain a shared channel for issues and enhancements.
Success Reviews
- Success Signal Review
- After-Action & Lessons Learned Workshop
- Corrective Action & Continuous Improvement Planning
- Shared Channel Setup & Operational Triage
- Executive Readout & Mutual Commit
Issues & Enhancements
- Produce a corrective action plan document with owners, acceptance criteria, budget impacts, and timelines for approvals.
- Validate data sources and agree a single source of truth for ongoing monitoring.
- Publish the consolidated performance dashboard and raw data extracts to the shared workspace.
- Assign owners and 30/60/90-day targets for each unmet success signal.
- Schedule the After-Action & Lessons Learned Workshop and distribute pre-work (timeline, evidence packets).
- Context & Timeline Review
- Produce a prioritized, evidence-backed list of lessons and corrective actions.
- Agree owners, acceptance criteria, and delivery timelines for top-priority actions.
- Ensure lessons are written in routable format for corrective action workflows.
- Draft the formal AAR document with embedded evidence and the prioritized corrective action register.
- Assign responsible leads for the top 5 corrective actions with due dates and acceptance criteria.
- Identify candidates for follow-on exercises that validate the corrective actions and schedule them.
- Review Prioritized Corrective Actions
- Finalize a corrective action plan with owners, timelines, and measurable acceptance criteria.
- Agree required contract or SLA amendments and next steps to implement them.
- Establish a monitoring and reporting cadence to ensure accountability.
- Executive Summary of Performance
- Draft SOW/contract addenda or change requests required to effect SLA or scope changes.
- Build the monitoring dashboard and schedule recurring status reports into the governance calendar.
- Define Channel Purpose & Users
- Launch a shared channel with defined purpose, access, and moderators.
- Agree a triage workflow and SLAs for issue acknowledgment and resolution.
- Provide templates and a cadence for routing issues into corrective action tracking.
- Create the shared channel, configure access, and invite the agreed user list.
- Publish the triage SOP, issue/enhancement templates, and escalation matrix to the channel.
- Schedule the channel onboarding session and the weekly triage checkpoint.
- Obtain executive approval for the corrective action plan and any required funding.
- Agree on revised SLAs/contract amendments and sign-off steps.
- Confirm governance cadence and escalation points for unresolved high-severity items.
- Prepare and distribute the executive decision memo and formal approval request.
- Obtain signed approvals for budget or SOW changes and route to procurement/legal.
- Schedule the next executive review and publish the governance calendar.
- Opening & Objectives
- Confirm which success signals met targets and which did not, with evidence.
- Establish root-cause hypotheses for each unmet signal.
- Assign immediate corrective actions with owners and deadlines.
- Top Risks & Recommended Fixes
- Evidence Review (Incidents & Metrics)
- Success Signals & Targets Recap
- Select Tooling & Access Controls
- Define Acceptance Criteria & Success Metrics
- Root-Cause Breakouts (by theme)
- Budget & Contract Implications
- Resource, Budget & Contract Implications
- Performance Dashboard Walkthrough
- Triage Workflow & SLAs
- Variance & Root-Cause Summary
- Mutual Commitments & Timeline
- Capture Lessons & Proposed Fixes
- Integration into Exercises & Training
- Issue & Enhancement Templates
- Validation from Field/Operations
- Prioritization (Impact vs. Effort)
- Monitoring & Reporting Framework
- Escalation Path & Governance
- Sign-off, Escalation Routing, & Next Review Date
- Decisions & Next Steps
- Finalize Commitments & Sign-offs
- Confirm Owners & Deliverables
- Q&A and Closing