2.2 ICS Roles, Divisions/Groups & Span of Control (JPR 5.1.2 / ICS 200)

2.2 ICS Roles, Divisions/Groups & Span of Control (JPR 5.1.2 / ICS 200)

NIMS and ICS: What Firefighter II Personnel Must Know

NIMS (National Incident Management System) is the national framework for incident management across all hazards and disciplines. ICS (Incident Command System) is the standardized on-scene organizational structure used to manage emergency incidents and planned events. NFPA 1001 Firefighter II JPR 5.1.2 requires competency in organizing and coordinating incident activities within an IMS—ICS is the model virtually all U.S. fire departments apply on the fireground.

ICS 200–level knowledge expected of Firefighter II candidates includes understanding how incidents are structured, who reports to whom, how geographic and functional assignments differ, and why span of control limits exist. You are not expected to fill every staff position on a Type 1 incident, but you must function effectively within assigned roles after command is established or transferred.

---

ICS Organizational Overview

At its simplest, ICS places one Incident Commander (IC) at the top with responsibility for overall incident management. As incidents expand, the organization grows modularly—positions are added only when needed.

+-----------------------------------------------------------------------+
|                    SIMPLIFIED ICS ORGANIZATION                        |
+-----------------------------------------------------------------------+
|                         INCIDENT COMMANDER                            |
|                    /         |         \                             |
|            COMMAND STAFF    OPERATIONS    (other General Staff        |
|            (Safety, PIO,    (tactics)      as incident grows)          |
|             Liaison)                                                  |
|                    |                                                  |
|              DIVISIONS / GROUPS / BRANCHES                            |
|                    |                                                  |
|                 RESOURCES (crews, units)                              |
+-----------------------------------------------------------------------+

Command Staff vs. General Staff

On a small residential structure fire, the IC may personally supervise companies without activating full General Staff sections. On a larger incident, the IC delegates Operations and may stand up Planning, Logistics, and Finance/Administration.

Firefighter II relevance: Know that the Safety Officer monitors conditions and can halt unsafe practices; the Operations Section Chief (or IC in smaller incidents) assigns tactical work. Bypassing the chain of command to reach the IC with routine tactical updates creates radio chaos—report through your supervisor.

---

Divisions and Groups

Tactical assignments below Operations (or the IC on smaller incidents) are often organized using divisions and groups:

Key Distinctions

• A division is tied to a location on the incident (side of building, floor level, city block quadrant).
• A group is tied to a function performed across the incident (search, ventilation, salvage).
• The same crew may work in Division Bravo performing ventilation—geographic division and functional group can coexist when the organization warrants both.
• Divisions and groups at the same level should not share the same designation letter/number in a way that causes confusion (e.g., avoid labeling both "Group Alpha" and "Division Alpha" without clear context).

When a Firefighter II is assigned to a division or group, your supervisor is the Division or Group Supervisor. Status updates, resource requests, and CAN reports flow up through that supervisor to Operations or Command.

---

Span of Control

Span of control is the number of subordinates one supervisor can effectively manage. ICS doctrine establishes general limits so supervisors are not overwhelmed and communication remains manageable.

Factors that may narrow span of control (fewer subordinates per supervisor):

• Hazardous or fast-changing conditions
• Night operations or poor visibility
• Complex terrain or building layout
• Inexperienced subordinates
• High life-safety risk

Factors that may allow slightly wider span:

• Routine, repetitive tasks
• Experienced, well-trained crews
• Stable conditions with low risk

On exam questions, "ideal span of control" answers center on about five; "acceptable range" answers cite three to seven.

---

Functioning Within an Assigned IMS Role After Transfer

Once command is transferred to a qualified officer, the Firefighter II does not continue to direct the incident unless reassigned to a command or supervisory role. Expected behaviors include:

1. Acknowledge your assignment (e.g., "Engine 12 assigned to Division Alpha, interior attack").
2. Report to your designated supervisor—Division Supervisor, Group Supervisor, or company officer as structured.
3. Execute assigned tactics within the Incident Action Plan (IAP) and department SOGs.
4. Communicate changing conditions using clear, brief reports (CAN format—Section 2.3).
5. Maintain accountability—stay with your crew, use assigned radio identifiers, respond to PAR.
6. Request resources through channels—ask your supervisor for additional lines, ventilation, or RIT; do not self-dispatch unrelated tasks.

---

ICS 200 Connections for Certification

Many jurisdictions align Firefighter II IMS knowledge with ICS 200 (ICS for Single Resources and Initial Action Incidents). Core concepts that overlap NFPA 1001 JPR 5.1.2 include:

• Modular organization that expands and contracts with incident needs
• Unity of command—each person reports to one supervisor
• Unified command when multiple agencies share authority
• Common terminology for facilities (Command Post, Staging, Base) and positions
• Transfer of command procedures and briefing content

Firefighter II candidates should visualize ICS as a scalable toolbox: small incidents use a small tool set; large incidents add sections, branches, and deputies—but the rules of span of control, unity of command, and clear reporting relationships never change.

---

Study Checkpoint

Before moving to size-up and reporting, confirm you can:

• Distinguish Command Staff from General Staff and state each primary function.
• Define division (geographic) versus group (functional) with examples.
• State span of control as 3–7, ideal ~5, and explain why limits exist.
• Describe how your role changes after command transfer—from coordinating the incident to executing within an assigned IMS position.