ICS-200: Basic Incident Command System – Comprehensive Study Notes

Course Context and Purpose

• IS-0200.c “Basic Incident Command System for Initial Response (ICS 200)”
  • Developed collaboratively by EMI, NWCG, USDA, USFA, USCG
  • Aligns with National Incident Management System (NIMS) Baseline Training
  • Part of the all-hazards, all-agency ICS course series (ICS 100, 200, 300, 400, etc.)
  • Target: Operational personnel who must manage the first four hours of an incident
  • Estimated course time: ≈ 4 hours; completion + final exam → certification

Overarching Learning Objectives

• Summarize ICS & NIMS fundamentals
• Relate NIMS Management Characteristics to Incident Command / Unified Command (UC)
• Explain delegation of authority, scope, management by objectives & preparedness plans
• Identify ICS components, Command & General Staff, and supporting tools
• Differentiate staff, field & section briefings; conduct an Operational Period Briefing
• Demonstrate structural flexibility, transfers of command, and incident typing
• Manage an incident/event with ICS principles

NIMS & ICS Foundations

• ICS = standard, nationwide management system for emergency / non-emergency events
  • Applies to planned events, disasters, terrorism, day-to-day ops
  • Not just an org chart; a doctrine of leadership, logistics, planning & finance
• NIMS = consistent framework across all jurisdictions, causes & complexities
  • Mandated by HSPD-5 (Management of Domestic Incidents) & HSPD-8 / PPD-8 (National Preparedness)

Major NIMS Components

• Resource Management
• Command & Coordination (ICS, EOCs, MAC Groups)
• Communications & Information Management

NIMS Management Characteristics (14)

1. Common Terminology
   • Standard names for functions, resources & facilities → reduced confusion
2. Modular Organization
   • Build "building blocks" as incident size/complexity grows
3. Management by Objectives
4. Incident Action Planning (IAP)
5. Manageable Span of Control
   • Optimal 1:5 supervisor : subordinates guideline (flexible)
6. Incident Facilities & Locations
   • ICP, Base, Camps, Staging Areas, PODs, Shelters, Mass-casualty triage, etc.
7. Comprehensive Resource Management
8. Integrated Communications
9. Establishment & Transfer of Command
10. Unified Command (UC)
11. Chain of Command & Unity of Command
12. Accountability
13. Dispatch / Deployment (no self-dispatch!)
14. Information & Intelligence Management
    • Identify Essential Elements of Information (EEI); processes for gather→analyze→share

Command Concepts

Chain vs. Unity vs. Unified Command

• Chain – orderly line of authority down the structure
• Unity – each person reports to ONE supervisor
• Unified – multiple legal authorities share command; still preserves unity for subordinates

Formal vs. Informal Communication

• Formal: work assignments, resource requests, progress reports (follows chain)
• Informal: data exchange lateral/vertical (never for tasks or requests)

Leadership Values & Responsibilities

• Values: Duty • Respect • Integrity
• Leader actions:
  • Give clear instructions → ask for feedback
  • Supervise & evaluate plan effectiveness
  • Modify plans when needed; ensure safe work practices
  • Build & brief the team; develop subordinates; debrief & capture lessons (AAR)

ICS Organizational Elements

• Incident Commander (IC)
  • Overall responsibility, sets objectives, approves IAP & resource orders
  • May appoint Deputy IC (must be fully qualified)

Command Staff

• Public Information Officer (PIO) – one authoritative voice; JIC participation
• Safety Officer (SOFR) – develops Safety Plan, can stop unsafe acts
• Liaison Officer (LNO) – interface for assisting / cooperating agencies
  • Assistants allowed for workload or specialized expertise

General Staff (Section Chiefs)

1. Operations Section
   • Directs tactical actions; often first section activated
   • May include: Branches (geographic/functional), Divisions, Groups, Task Forces, Strike Teams, Single Resources
   • Staging Area Manager reports to Ops if established
   • Air Operations Branch → Air Tactical & Air Support Groups
2. Planning Section
   • Situation, Resources, Documentation, Demobilization Units; hosts Technical Specialists
   • Looks beyond current & next operational period
3. Logistics Section
   • Service Branch → Communications, Medical (for responders), Food Units
   • Support Branch → Supply, Facilities, Ground Support Units
4. Finance/Administration Section
   • Time, Procurement, Compensation/Claims, Cost Units
5. Intelligence/Investigations Function (I/I) – placed in Planning, Operations, Command Staff, or stand-alone section as needed

Incident Facilities Snapshot

• Incident Command Post (ICP) – command hub; usually safest practical location
• Incident Base – support & logistics center; houses primary service & support activities
• Camps – temporary locations within incident area
• Staging Area – waiting, assigned & ready resources
• Other – Helibase/Helispot, Mass-casualty triage, PODs, Shelters

Resource Management Essentials

• Six-phase cycle: Identify Requirements → Order/Acquire → Mobilize → Track/Report → Demobilize → Reimburse/Restock
• Resource Typing (Capability → Category → Kind → Type I–IV)
  Example: Type 3 Ambulance Ground Team = 2-person crew (EMT-1 + Operator) with BLS & 2-patient transport
• Task Force (mixed kind) vs. Strike Team (same kind/type)

Delegation & Scope of Authority

• Authority: legal right/obligation of elected/appointed officials (AHJ)
• Delegation of Authority (DoA):
  • Written or verbal grant when IC operates outside normal jurisdiction/authority
  • Must include legal & financial limits, priorities, reporting, PIO plan, comms & evaluation criteria
  • Does not relieve delegator of ultimate responsibility
• DoA not required when IC already has statutory authority (e.g., fire chief at local structure fire)

Management by Objectives & Incident Action Planning

• SMART objectives: Specific, Measurable, Action-oriented, Realistic, Time-limited
• Six-step cycle:
  1 Understand policy → 2 Assess situation → 3 Set objectives → 4 Select strategies → 5 Tactical direction → 6 Follow-up
• Incident Action Plan (IAP) covers ONE operational period; becomes written when:
  • Incident > 1 operational period, multi-jurisdiction, or increasing complexity
• Operational Period (OP) = scheduled timeframe for tactical actions (may be 2–24 h)
• Planning P diagram: sequence of meetings (IC/UC meeting → Tactics → Planning → OP Briefing)

Preparedness & Mutual-Aid Frameworks

• Emergency Operations Plans (EOPs) – Fed/State/Local all-hazard
• SOPs/SOGs – agency-specific step-by-step or guideline documents
• Mutual Aid Agreements / Compacts (EMAC, NRF authorities) – define reimbursement, licensure recognition, voice/data interoperability, resource typing protocols

Briefings & Meetings Menu

Briefing checklist: Current situation, Objectives, Safety, Tasks, Facilities, Comms, Expectations, Resource process, Schedule, Q&A

Flexibility & Incident Typing

• ICS expands/contracts per complexity, hazards & objectives; only necessary functions are activated
• Avoid creating non-standard titles; one person may hold multiple standard positions if span-of-control allows

Incident Complexity Analysis → 5 Types

• Type 5 – ≤ 6 responders; < 1 OP; no IAP
• Type 4 – Several single resources; < 1 OP; command staff as needed
• Type 3 – Extended; some/all Command & General Staff; written IAP; may activate IMT (local/State)
• Type 2 – Regional/National resources; most Command & General Staff; > 200 Ops staff/OP, > 500 total
• Type 1 – National resources; all sections & branches; > 500 Ops/OP, > 1,000 total; potential disaster declaration

Incident Management Teams (IMT)

• Typed 5 → 1 mirroring incident typing; rostered, pre-qualified ICS leadership cadres

Transfer of Command

• Reasons: legal requirement, complexity change, relief, emergency, higher qualification
• Protocol: Face-to-face when possible; include ICS 201 or full IAP; announce effective time/date to all personnel
• Briefing elements: Situation, Objectives, Org, Resources (assigned/en route), Facilities, Comms Plan, Prognosis/Concerns, Intro of key staff

ICS Tools & Forms (selected)

• ICS 201 – Incident Briefing (8-part); often initial IAP
• ICS 202 – 208 – Core IAP forms (Objectives, Org List, Assignment, Radio Plan, Medical, Org Chart, Safety Msg)
• ICS 209 – Incident Status Summary
• ICS 214 – Unit Log; ICS 215/215A – Operational Planning & Safety Analysis
• ICS 220 – Air Ops Summary; ICS 221 – Demobilization Plan; ICS 308 – Resource Order

Reference: FEMA ICS Forms Library / RTLT for typing & PTBs

Scenario Recap: Liberty County Tanker-Truck Crash @ Fairgrounds

• Setting: Rural county fair; multi-agency public safety presence but no unified command
• 17:00 hrs – Tanker veers into crowd, impacts exhibit hall → fire ignites
• Initial IC (Fire) establishes single IC (could also justify UC)
• Size-up considerations:
  • Fire & potential explosions, structural collapse, damaged utilities
  • Casualty extraction, crowd movement, traffic congestion
• Objectives examples (SMART):
  1. Evacuate/treat injured within 30\text{ min}
  2. Extinguish vehicle fire within 45\text{ min}
  3. Control perimeter by 18{:}00
• Incident Type: Begins Type 4; escalates to Type 3 (< multi-OP)
• ICS Growth: Activate Ops Section, PIO, SOFR
  • Later add Planning, Logistics, LNO, HazMat Tech Specs, Intelligence/Investigations, transition to Unified Command (Fire, EMS, Law Enf, Public Works)
• Transfer of Command: Senior IC & UC assume; face-to-face briefing w/ updated IAP

Rapid Reference (Cheat-Sheet)

• Optimal span of control: 1:5 (flex 3-7)
• 14 NIMS Characteristics = backbone of ICS
• IC sets Objectives → Strategies → Tactics
• Written IAP triggers: > 1 OP, ↑ complexity, multi-agency
• Delegation of Authority = grants function authority, never relieves responsibility
• Incident Typing ties to resource need & IMT level
• Transfer of Command briefing uses ICS 201 if no IAP yet
• Formal requests/assignments ONLY via chain; no spontaneous deployment
• Use standard position titles: IC → Chief → Director → Supervisor → Leader/Boss

Ethical & Practical Implications

• Public information must be accessible & timely to maintain public trust
• Safety is non-negotiable; SOFR can halt operations
• Mutual aid relies on clear reimbursement & licensure terms to prevent post-incident disputes
• Leadership must balance life safety, incident stabilization, property preservation simultaneously – not sequentially

End of Study Notes – ready for exam & real-world application.