Event Action Plan Template Ics

STANDARD OPERATING PROCEDURE: Enterprise Incident Command System (ICS) Event Action Plan (EAP) Generation

1. DOCUMENT CONTROL BLOCK

• Document ID: SOP-TR-ICS-EAP-042
• Effective Date: October 24, 2023
• Version: 3.2.0
• Review Cadence: Semi-Annual
• Classification: Internal Operations / Business Continuity

---

2. EXECUTIVE SUMMARY & PURPOSE

This Standard Operating Procedure (SOP) defines the institutional requirements for authoring, validating, and executing an Event Action Plan (EAP) utilizing the Incident Command System (ICS) framework at Template Registry. The purpose of this document is to establish a deterministic, repeatable workflow for operationalizing ICS-202 through ICS-209 forms, ensuring seamless interoperability during high-consequence technical deployments, facility migrations, or major security incidents.

---

3. SCOPE & PREREQUISITES

3.1 Scope

This procedure applies to all Site Reliability Engineering (SRE), DevOps, Facilities, and Information Security personnel designated as Incident Commanders (IC) or Section Chiefs within the Template Registry command hierarchy.

3.2 Prerequisites & Tools

• Active credentials to the Template Registry Enterprise ICS Management Portal.
• Standardized ICS EAP Template repository access (git@github.com:template-registry/ics-eap-templates.git).
• Collaborative real-time documentation workspace (Confluence / Secure Etherpad).
• Communication channels: Dedicated encrypted PagerDuty escalation policy and bridged War Room audio channels.
• Personal Protective Equipment (PPE): Not applicable for software/sysadmin operations; standard data center safety gear required if physical infrastructure is co-located.

---

4. ROLES & RESPONSIBILITIES (RACI MATRIX)

(R = Responsible, A = Accountable, C = Consulted, I = Informed)

---

5. STEP-BY-STEP PROCEDURE

Phase 1: Operational Period Initialization & Scoping

• 1.1 Convene the Command and General Staff via the designated bridge within 15 minutes of an incident declaration or 4 hours prior to a planned high-risk event.
• 1.2 Define the Operational Period duration (typically 4, 8, or 12 hours) in consultation with the Planning Chief.
• 1.3 Initialize the master EAP document using the standardized markdown template (template-ics-eap-v3.md).

Phase 2: Form Assembly & Drafting (ICS Forms 202 - 206)

• 2.1 Complete ICS-202 (Incident Objectives): Populate primary safety statements, measurable operational objectives for the period, and general situational awareness notes.
• 2.2 Complete ICS-203 (Organization Assignment List): Map active personnel to specific ICS roles, ensuring no single point of failure in command structures.
• 2.3 Complete ICS-204 (Assignment List): Detail specific tactical tasks, resource allocations, and reporting intervals for each operational branch or technical pod.
• 2.4 Complete ICS-205 (Incident Radio/Communications Plan): Document primary, secondary, and tertiary communication frequencies, Slack/Teams channels, and bridge coordinates.
• 2.5 Complete ICS-206 (Medical Plan): Outline emergency escalation paths, nearest physical medical facilities (if applicable), and mental health/fatigue management rotations.

Phase 3: Review, Validation, and Approval

• 3.1 Conduct a 10-minute "Read-Out and Sync" meeting led by the Planning Section Chief to review inter-form dependencies.
• 3.2 Verify that all resource constraints and safety protocols have been explicitly signed off by the Logistics Chief.
• 3.3 Secure formal sign-off from the Incident Commander (IC) to freeze the EAP for the designated operational period.

Phase 4: Promulgation and Execution

• 4.1 Publish the finalized EAP as an immutable artifact (PDF/Signed Markdown) to the Template Registry Incident Portal.
• 4.2 Broadcast the EAP location and critical objectives to all assigned operational units via PagerDuty broadcast and primary communication channels.
• 4.3 Initiate the Operational Period briefing, transitioning control of tactical execution to the Operations Section Chief.

---

6. QUALITY ASSURANCE & PRO-TIPS

• Best Practice (The Rule of Three): Never set more than three (3) primary objectives per ICS-202 form. Cognitive overload during incidents causes tactical drift.
• Metric Threshold: The entire EAP drafting-to-approval cycle must not exceed 45 minutes for emergent incidents or 4 hours for scheduled operational events.
• Common Pitfall: Failing to update ICS-205 (Communications). Ensure alternative channels are explicitly named if primary chat ops infrastructure is compromised.

---

7. FREQUENTLY ASKED QUESTIONS (FAQ)

Q: What happens if an operational objective changes midway through an active operational period?
A: Do not alter the active EAP mid-stream unless life safety or systemic data loss is imminent. Instead, issue an Incident Memorandum (ICS-221 style addendum) authorized by the Incident Commander, and fully integrate the change into the next operational period's EAP during the planning cycle.

Q: Who is authorized to bypass the standard RACI sign-off matrix during a P1 critical outage?
A: Only the designated Incident Commander may compress the review cycle in a P1 scenario, but they must verbally confirm safety and resource availability with Operations and Logistics leads before promulgation.

Q: Are paper templates required, or is digital execution acceptable?
A: Digital execution via the Template Registry Enterprise ICS Management Portal is mandatory to maintain an immutable audit trail and real-time synchronization across distributed teams.