Incident Action Plan Sample Philippines

Standard Operating Procedure: Incident Action Plan (IAP) Formulation

Template Registry Engineering Division

---

1. Document Control Block

---

2. Executive Summary & Purpose

This SOP establishes the standardized framework for developing an Incident Action Plan (IAP) within the Philippine operational context, compliant with NDRRMC and international ICS (Incident Command System) standards. The purpose is to formalize resource mobilization, objective setting, and tactical execution during high-impact technical or environmental contingencies.

---

3. Scope & Prerequisites

• Scope: Applies to all Template Registry assets, physical infrastructure, and remote workforce operations within the Philippine archipelago.
• Required Tools:
  • Unified Command Software (e.g., PagerDuty, Slack, Notion).
  • Hard-copy IAP templates (ISO 22320 compliant).
  • Satellite-capable communication devices (Iridium/Starlink).
• Mandatory PPE: Level 1 Emergency Go-Bag (contains offline site maps, local emergency contact matrix, and multi-day power backup).

---

4. Roles & Responsibilities (RACI)

---

5. Step-by-Step Procedure

Phase 1: Situational Assessment (T+0 to T+30m)

• Establish Command Post (CP) at the designated site or virtual war room.
• Execute initial "Size-Up": Identify nature of incident, current weather/infrastructure data (DOST-PAGASA alerts).
• Define the Operational Period (e.g., 6-hour or 12-hour shifts).

Phase 2: Objective Setting (T+30m to T+60m)

• Draft SMART Objectives (Specific, Measurable, Achievable, Relevant, Time-bound).
• Prioritize Life Safety -> Incident Stabilization -> Property Preservation.
• Identify critical resource gaps (e.g., fuel for gensets, telecommunications outages).

Phase 3: Tactical Planning

• Assign functional units (Logistics, Planning, Finance).
• Develop the "Communications Plan": Primary, Alternate, Contingency, and Emergency (PACE) channels.
• Document Medical Plan (Identification of nearest Level 3 hospitals and transport logistics).

Phase 4: Execution & Monitoring

• Distribute the IAP to all Section Chiefs.
• Conduct operational briefings at the start of every shift.
• Implement "Check-in" logs to track personnel and assets.

---

6. Quality Assurance & Pro-Tips

• Pro-Tip (PH Context): Always maintain a physical "Analog Folder" containing contact lists for local government units (LGUs) and BFP (Bureau of Fire Protection). Digital networks in the Philippines are prone to high latency/failure during severe weather.
• Metric Threshold: Total IAP creation time should not exceed 120 minutes from incident detection to deployment.
• Common Pitfall: Over-complicating the IAP. Focus on "What" and "Who" rather than excessive technical minutiae.

---

7. Frequently Asked Questions

Q: How do we handle IAP updates during a power grid failure? A: Shift to the "Offline Protocol." Use pre-printed IAP physical templates. Designate a runner to transport physical updates to the Incident Command post every 180 minutes.

Q: Does this IAP align with local Philippine disaster regulations? A: Yes. This framework is mapped to the Philippine Disaster Risk Reduction and Management Act (RA 10121), ensuring that private sector actions remain interoperable with public sector response efforts.

---

Signed,

Julian Vance Chief Architect, Template Registry