9.2 Incident Command System (ICS) Structure and Command

9.2 Incident Command System (ICS) Structure and Command

The Incident Command System (ICS) is a standardized, on-scene emergency management concept designed to provide an integrated organizational structure. ICS is a key component of the Federal Emergency Management Agency's (FEMA) National Incident Management System (NIMS), mandated under Homeland Security Presidential Directive 5 (HSPD-5). Developed in the 1970s through the FIRESCOPE program in California following catastrophic wildfires, ICS addresses recurring issues such as communication failures, unstructured command hierarchies, lack of accountability, and overlapping responsibilities.

The Command Structure: Incident Commander and Command Staff

At the core of the ICS structure is the Incident Commander (IC), who holds sole, overall responsibility for the strategic direction, tactical objectives, and safety of all personnel on scene. The command structure is modular; on small incidents, the IC performs all functions, but as the incident escalates, the IC delegates authority by establishing Command and General Staff positions.

The Command Staff consists of specialized officers who report directly to the Incident Commander. They do not manage tactical operations directly, but provide support in key safety, media, and agency-integration areas:

1. Safety Officer (SO): The Safety Officer is tasked with identifying and mitigating hazardous conditions on scene. The Safety Officer has the autonomous, direct authority to immediately suspend, alter, or halt any tactical operations that present an immediate hazard to life safety or health (IDLH), without going through the chain of command. The Safety Officer must inform the Incident Commander of any such actions immediately after they are taken.
2. Liaison Officer (LNO): The Liaison Officer serves as the primary point of contact for representatives from assisting agencies (those providing resources) and cooperating agencies (those providing support or jurisdiction, such as utility companies, environmental agencies, or law enforcement).
3. Public Information Officer (PIO): The PIO manages all media relations, drafts official press releases, coordinates media briefings, and acts as the spokesperson for the incident command. The PIO ensures that consistent, accurate, and vetted information is released to prevent misinformation.

---

The General Staff: Functional Sections

The General Staff is comprised of the functional sections of the incident management organization. Each section is led by a Section Chief who reports directly to the Incident Commander:

• Operations Section: Responsible for the direct management and execution of all tactical operations on the scene to achieve the incident objectives. The Operations Section Chief coordinates the deployment of suppression, rescue, and medical resources.
• Planning Section: Responsible for the collection, evaluation, and dissemination of information regarding the incident status. Planning tracks all resources (assigned, available, out of service), develops the written Incident Action Plan (IAP) for each operational period (typically a 12-hour or 24-hour cycle), maintains historical incident documentation, and plans for demobilization.
• Logistics Section: Responsible for providing facilities, services, materials, and support to the incident. Logistics is divided into two branches:
  • Service Branch: Handles communications, responder medical care (rehab), and food/water.
  • Support Branch: Handles facilities, supply acquisition, and ground support (vehicle maintenance and fueling).
• Finance/Administration Section: Established on large, complex incidents where tracking costs is required. The Finance Section manages procurement, vendor contracts, personnel timesheets, cost analyses, and injury/illness compensation claims.

---

Span of Control Principles

One of the most critical principles of ICS is the Span of Control, which limits the number of individuals or resources that any single supervisor can effectively manage. Controlling the span of control prevents communication bottlenecks and ensures adequate supervision for responder safety.

• Recommended Ratio: The ideal span of control is one supervisor to five subordinates (1:5).
• Acceptable Range: The acceptable range is one supervisor to three to seven subordinates (1:3 to 1:7).

If a supervisor's span of control exceeds seven, the organization must expand by establishing geographic Divisions (e.g., Division A for the front of a structure, Division C for the rear, or Floor 2 Division in a high-rise) or functional Groups (e.g., Ventilation Group, Rescue Group, Salvage Group). Conversely, if the span of control falls below three, command layers should be consolidated to free up personnel.

                  +------------------------+
                  |   Incident Commander   |
                  +-----------+------------+
                              |
       +----------------------+----------------------+
       |                      |                      |
+------v------+        +------v------+        +------v------+
|   Safety    |        |   Liaison   |        |   Public    |
|   Officer   |        |   Officer   |        | Information |
+-------------+        +-------------+        +-------------+
                              |
       +---------+------------+------------+---------+
       |         |                         |         |
+------v----+ +--v-------+           +-----v----+ +--v-------+
|Operations | | Planning |           |Logistics | | Finance/ |
|  Section  | | Section  |           | Section  | |  Admin   |
+-----------+ +----------+           +----------+ +----------+

---

Unified Command (UC)

A Unified Command (UC) structure is utilized when an incident involves multiple jurisdictions (e.g., a forest fire crossing county boundaries) or multiple agencies with overlapping authorities within the same jurisdiction (e.g., a commercial plane crash involving fire, police, EMS, and federal investigators).

Under a Unified Command:

• Multiple agencies coordinate their activities through their designated commanders, who sit together at a single Incident Command Post (ICP).
• The commanders cooperatively establish a single set of incident objectives and approve a single Incident Action Plan (IAP).
• A single Operations Section Chief is appointed to direct tactical actions, preventing conflicting orders.
• No agency relinquishes its statutory authority or responsibility; rather, decisions are made collectively.

---

Resource Management and Tactical Units

ICS establishes standardized terminology for organizing tactical resources. Resources are categorized into three operational configurations:

1. Single Resource: An individual piece of equipment and its associated personnel crew (e.g., Engine 3 with 4 firefighters, or a single bulldozer with its operator).
2. Strike Team: An assembly of a set number of resources of the same type and class with common communications and a designated leader (e.g., five Type 1 structural engines, or five Type 3 wildland engines). Strike teams offer highly predictable performance.
3. Task Force: A combination of different types and classes of resources assembled for a specific, temporary tactical mission, with common communications and a designated leader (e.g., two engines, one ladder, and one rescue squad deployed to search a collapsed building).

Resource Status Tracking

The Planning Section must track all resources in one of three status conditions:

• Assigned: The resource is actively performing a tactical assignment on the fireground.
• Available: The resource is fully staffed, equipped, and ready for immediate tactical assignment, typically staged at a designated Staging Area.
• Out of Service (OOS): The resource is not ready for deployment due to mechanical issues, staffing shortages, or the need for personnel rest/rehab.