Incident Action Plan Template Fema

Standard Operating Procedure: FEMA Incident Action Plan (IAP) Generation & Execution

---

1. Executive Summary & Purpose

This Standard Operating Procedure (SOP) defines the institutional protocol for authoring, validating, and executing an Incident Action Plan (IAP) utilizing the Federal Emergency Management Agency (FEMA) Incident Command System (ICS) framework. The purpose of this document is to establish a deterministic, repeatable workflow for multi-agency and enterprise-wide emergency response, ensuring full alignment with the National Incident Management System (NIMS). Compliance with this SOP is mandatory for all Template Registry engineering, operations, and incident response personnel deployed during declared emergencies.

---

2. Scope & Prerequisites

2.1 Scope

This procedure applies to all operational tiers within Template Registry, covering cyber-physical security incidents, infrastructure failures, and regional disasters requiring formal ICS activation.

2.2 Prerequisites & Required Tools

• Access Control: Active credentials for the FEMA ICS Forms Repository and Enterprise Incident Management (EIM) platform.
• Software: Adobe Acrobat DC (for Form 202-206 completion), GIS Mapping Suite (ArcGIS/QGIS for ICS-220 operational period mapping), and encrypted communication channels (Signal/P25 radio infrastructure).
• Physical/PPE: Standard Emergency Operations Center (EOC) workstation, redundant power supply, hardware-backed 2FA tokens.
• Certifications: FEMA IS-100, IS-200, IS-700, and IS-800 certifications required for lead roles.

---

3. Roles & Responsibilities (RACI Matrix)

Legend: R = Responsible, A = Accountable, C = Consulted, I = Informed

---

4. Step-by-Step Procedure

Phase 1: Operational Period Initialization & Objectives (ICS Form 202)

• Convene the initial Incident Command briefing to establish the operational period (typically 12 or 24 hours).
• Define primary incident objectives using the SMART criteria (Specific, Measurable, Achievable, Relevant, Time-bound).
• Populate FEMA ICS Form 202 (Incident Objectives) with safety statements, containment targets, and strategic priorities.
• Validate that the Incident Commander signs and dates Block 7 of ICS Form 202.

Phase 2: Organization and Resource Assignment (ICS Forms 203 & 204)

• Draft the Organization Assignment List (ICS Form 203) to map out the current command and general staff hierarchy.
• Construct Branch, Division, and Group work assignments on ICS Form 204 (Assignment List) for the upcoming operational period.
• Cross-reference available tactical resources against operational requirements to prevent under-resourcing or staging bottlenecks.
• Ensure specific reporting locations, tactical channels, and specialized equipment requirements are explicitly noted in Form 204 blocks.

Phase 3: Supporting Plan Integration (ICS Forms 205 & 206)

• Finalize the Incident Radio Communications Plan (ICS Form 205), assigning tactical, command, and support frequencies.
• Coordinate with regional communications units to ensure repeater availability and encryption key synchronization.
• Complete the Medical Plan (ICS Form 206), establishing primary/secondary transport routes, designated triage areas, and receiving hospital capabilities.
• Verify that the Safety Officer (SO) reviews and signs off on both the communications and medical contingency vectors.

Phase 4: Review, Approval, and Distribution

• Convene the IAP Review Meeting (Tactical Meeting) exactly T-minus 3 hours prior to the start of the operational period.
• Conduct a final audit of all attached FEMA forms (ICS 202 through 206) for structural consistency and data synchronization.
• Obtain formal digital approval signature from the Incident Commander.
• Distribute the compiled PDF packet to Section Chiefs, EOC leads, and external regulatory authorities via the secure EIM portal.

---

5. Quality Assurance & Pro-Tips

5.1 Pro-Tips & Best Practices

• Living Document Protocol: Treat the IAP as a dynamic document; minor tactical adjustments must be logged via ICS Form 233 (Open Incident Action Plan changes) rather than breaking core plan integrity.
• Concise Objectives: Limit ICS 202 objectives to a maximum of five to prevent operational diffusion and maintain tactical focus.
• Redundant Delivery: Always maintain local, offline paper copies of ICS 205 and 206 at the command desk in the event of enterprise network failure.

5.2 Common Pitfalls to Avoid

• Orphaned Resources: Assigning tactical units on ICS 204 without verifying their check-in status on ICS Form 211.
• Stale Frequencies: Utilizing unallocated or restricted radio channels without verifying spectrum clearance with the Communications Unit Leader (COML).

5.3 Metric Thresholds

• Draft Completion Time: $\le 90$ minutes from incident declaration to initial IAP assembly.
• Review Cadence Adherence: 100% compliance with operational period transition briefings (zero overlap or operational blackout windows).

---

6. Frequently Asked Questions (FAQ)

Q: What should be done if an operational objective cannot be met within the designated 12-hour operational period?
A: The Operations Section Chief must flag the deviation during the tactics meeting. The objective must be formally rolled over, modified for achievability, and updated with a revised target time in the subsequent cycle's ICS Form 202.

Q: Who holds the ultimate authority to alter the Medical Plan (ICS 206) during an active operational period?
A: The Safety Officer, in direct coordination with the Medical Unit Leader (MEDL) and Incident Commander, maintains unilateral authority to alter medical evacuation vectors and receiving hospital assignments based on real-time threat intelligence.

Q: Are digital signatures strictly required on FEMA ICS forms during high-urgency scenarios?
A: Cryptographically verified digital signatures are preferred. However, in low-bandwidth or infrastructure-failure scenarios, explicit verbal approval logged on the ICS Form 214 (Unit Log) by the authorized approver acts as a binding temporary authorization until digital systems are restored.