Incident command system Study Guide

📖 Core Concepts Incident Command System (ICS) – A standardized, flexible hierarchy for coordinating multi‑agency emergency response. Incident vs. Event – Incident: unplanned emergency; Event: planned activity. Unity of Command – Each responder reports to only one supervisor, preventing conflicting orders. Span of Control – Ideal supervisor → 5 subordinates (range 3–7); expand structure if >7, consolidate if <3. Modular Organization – Structure expands or contracts with incident size, complexity, and resources. Incident Action Plan (IAP) – 12‑hour (or variable) plan answering: what, who, how (communications), and safety/medical contingencies. Command Staff vs. General Staff – Command staff (Safety, Public Information, Liaison) support the Incident Commander; General staff (Operations, Planning, Logistics, Finance/Administration) run the incident. Transfer of Command – Formal hand‑off of authority with a briefing and documented forms to keep continuity. --- 📌 Must Remember Unity of Command → one supervisor per individual. Span of Control ideal = 5 (acceptable 3‑7). IAP duration = usually 12 h; written for haz‑mat incidents. Command Transfer Briefing must cover safety, objectives, and resource status. Unified Command → ≥2 incident commanders sharing authority (large, multi‑jurisdiction). Area Command provides logistics/admin support, no operational control. Resource Statuses – Assigned, Staged (available but not assigned), Out‑of‑service. Facility hierarchy – Incident Command Post (IC P) → Staging Area → Base → Camp → Helibase/Helispot. --- 🔄 Key Processes Establishing Command First arriving unit designates Incident Commander (IC). Add staff positions as incident grows; remove as it contracts. Developing the IAP Identify incident objectives (specific, attainable, time‑framed). Assign strategies (overall plan) and tactics (how to execute). Document: what, who, communication plan, safety/medical plan. Transfer of Command Outgoing IC gives oral/written (or combined) briefing → concise situation, resources, pending actions. Incoming IC confirms understanding, asks clarifying questions, assumes responsibility. Complete Transfer of Command form (time, names, summary). Inform all staff to maintain unified command. Resource Management Cycle Categorize → Order → Dispatch → Track → Recover. Integrated Communications Planning Develop communications plan pre‑incident → assign frequencies, hardware, network procedures. --- 🔍 Key Comparisons Incident Commander vs. Unified Command IC: single authority, typical for most incidents. Unified: multiple ICs sharing authority, used when several agencies/jurisdictions are involved. Oral vs. Written Transfer Briefing Oral: rapid, verbal, best for time‑critical hand‑offs. Written: detailed, permanent record, useful for complex or long‑duration incidents. Assigned vs. Staged Resources Assigned: actively working under a supervisor. Staged: ready and available but not yet tasked. Division vs. Group Division: organized by geography/jurisdiction. Group: organized by function, agency line, or resource type. --- ⚠️ Common Misunderstandings “More staff = better control.” Adding staff beyond the span of control dilutes supervision; expand the structure instead. “Transfer of command is optional.” Formal transfer is required for continuity and legal accountability. “All incidents need a written IAP.” Only hazardous‑material incidents must have a written IAP; others may use oral plans. “Unified Command replaces the Incident Commander.” It adds additional commanders; the original IC remains part of the unified team. --- 🧠 Mental Models / Intuition “Zoom Lens” Model: Think of ICS as a camera lens that zooms in (adds sections) as the incident enlarges and zooms out (removes sections) as it shrinks. “Chain of Command” as a single‑thread rope – pulling on any knot (staff) moves the whole system; if a knot is tied to two ropes (dual reporting), the rope tangles (conflict). Resource status pyramid: Assigned (top), Staged (middle), Out‑of‑service (bottom). Visualize moving resources up/down the pyramid as the incident evolves. --- 🚩 Exceptions & Edge Cases Jurisdictional Transfer – When an incident crosses legal boundaries, command shifts to the authority with jurisdiction, regardless of current span of control. Turnover During Night Operations – May require written briefings only (limited oral communication). Hazardous Material Incidents – Must have a written IAP and often a dedicated Safety Officer with specialized training. Small‑scale incidents – May be managed by a single IC with no staff; “Command Transfer” can be a quick oral hand‑off without formal forms if documented elsewhere. --- 📍 When to Use Which Choose Oral vs. Written Transfer Briefing → Use oral for rapid, low‑complexity hand‑offs; use written (or combined) when the incident is complex, long‑lasting, or when documentation is required for legal/record‑keeping purposes. Select Unified Command → Activate when two or more agencies/jurisdictions have equal authority and responsibility. Deploy Strike Team vs. Task Force → Use a Strike Team when resources are identical (e.g., 5 identical fire engines); use a Task Force when mixing different resource types is needed. Assign a Division vs. Group → Use Division for geographic separation; use Group for functional separation (e.g., all medical assets). --- 👀 Patterns to Recognize “Three‑to‑Seven” pattern → Any time a manager’s sub‑team is described, check the count; >7 → need new branch/section. “12‑hour IAP” cue → When an operational period is mentioned, expect an IAP covering objectives, assignments, communications, and safety. “First‑arriving unit” trigger → Immediate designation of an Incident Commander without waiting for higher‑level approval. “Transfer of command” wording → Look for “briefing,” “time of transfer,” and “documentation” – signals a formal hand‑off. --- 🗂️ Exam Traps Trap: “The Incident Commander can delegate authority to any subordinate at any time.” Why wrong: Delegation must respect Unity of Command and span of control; authority transfers only to qualified personnel following formal procedures. Trap: “A written IAP is always required.” Why wrong: Only hazardous‑material incidents mandate a written IAP; others may rely on oral plans. Trap: “Unified Command eliminates the need for a single Incident Commander.” Why wrong: Unified Command adds multiple commanders who share authority; each still functions as an IC within their agency. Trap: “If a Division has more than five resources, create a new Division.” Why wrong: Use the span of control rule (3‑7) for supervisors, not necessarily to create new divisions; a Division can contain multiple branches as needed. Trap: “Transfer of command can be done verbally without any record.” Why wrong: All transfers must be documented on the appropriate ICS form for accountability and post‑incident analysis.