ICS Command Structure — The Firefighter Medic

Incident Commander

Overall responsibility · One IC per incident

Command Staff

Public Info Officer

Media · Public messaging

Safety Officer

Hazards · Incident safety

Liaison Officer

Agency coordination

General Staff — Section Chiefs

Operations

Section Chief

Branches (if needed)

Geographic or functional
Activated for large incidents

Divisions / Groups

Division = geographic area
Group = functional task

Resources

Strike Teams
Task Forces
Single Resources

Planning

Section Chief

Planning Units

Resources Unit
Situation Unit
Documentation Unit
Demobilization Unit

Produces

Incident Action Plan (IAP)
Situation Status (SITREP)
Resource tracking

Logistics

Section Chief

Service Branch

Communications Unit
Medical Unit
Food Unit

Support Branch

Supply Unit
Facilities Unit
Ground Support Unit

Finance / Admin

Section Chief

Finance Units

Time Unit
Procurement Unit
Compensation/Claims
Cost Unit

Tracks

Personnel time
Equipment costs
Contracts & claims

⚙️ ICS Foundational Principles

👥

Span of Control

3–7 (Optimal: 5)

Each supervisor manages no more than 7 resources. Too wide = loss of control. Too narrow = inefficiency.

🔗

Unity of Command

One Supervisor Per Person

Every individual reports to exactly one supervisor. Eliminates conflicting orders and confusion.

📖

Common Terminology

Standardized Language

All agencies use the same terms. No 10-codes. No agency-specific jargon. Clear communication.

🧩

Modular Organization

Activate Only What's Needed

ICS expands and contracts with incident complexity. Only activated positions are filled.

🎯

Management by Objectives

Goals Drive All Actions

IC sets clear, measurable objectives. All operations support those objectives. IAP documents them.

📋

Incident Action Plan (IAP)

Written or Verbal

Every operational period has an IAP. Complex incidents require written IAP. Guides all crews.