2.3 Standard Operating Procedures (SOPs), Incident Command System (ICS) & Safety Protocols

SOPs, Incident Command System (ICS) & Safety Protocols

Modern emergency operations depend on standardized command structures, written procedures, and life-safety rules. FCTC's essay subjects include "response considerations," and its official sample packet is itself a department policy: a grooming standard with a chain of command and an appeal route. Policy, SOP, and command-structure passages are therefore realistic FCTC reading material. This primer explains their vocabulary so the passages read quickly. As always on the FCTC, answer from what the passage says, not from what this primer or any academy taught you.

---

SOPs vs. SOGs & Standard Fireground Terminology

Fire departments govern operational readiness and tactical execution through written administrative documents:

• Standard Operating Procedures (SOPs): Rigid, binding directives that mandate exact actions for specific fireground evolutions. SOPs leave zero room for individual variance under normal conditions (e.g., mandatory donning of full PPE and SCBA when entering an IDLH atmosphere, vehicle seatbelt compliance, and response speed limits). Failure to follow an SOP constitutes a disciplinary and safety breach.
• Standard Operating Guidelines (SOGs): Flexible tactical frameworks that outline preferred methods of operation while granting company officers professional discretion to adapt tactics to unique or evolving field circumstances (e.g., choosing vertical vs. horizontal ventilation depending on fire extension).
• Clear Text / Plain Language: The National Incident Management System (NIMS) calls for plain language rather than agency-specific codes, especially when several agencies work together. Many departments have dropped "10-codes" (such as "10-4") for this reason, because a code that means one thing in one agency can mean something else in the next.

---

The Incident Command System (ICS) Architecture

The Incident Command System (ICS) is a standardized, on-scene, all-hazard incident management model originally developed by FIRESCOPE in California. It enables departments to operate with common organizational structures, unified terminology, and integrated communications.

graph TD
    IC["Incident Commander (IC)"]
    
    subgraph CommandStaff["Command Staff"]
        SO["Incident Safety Officer (ISO)"]
        PIO["Public Information Officer (PIO)"]
        LO["Liaison Officer"]
    end
    
    subgraph GeneralStaff["General Staff (FLOP Sections)"]
        OPS["Operations Section Chief"]
        PLAN["Planning Section Chief"]
        LOG["Logistics Section Chief"]
        FIN["Finance/Admin Section Chief"]
    end
    
    IC --> SO
    IC --> PIO
    IC --> LO
    IC --> OPS
    IC --> PLAN
    IC --> LOG
    IC --> FIN

The Incident Commander & Command Staff

The Incident Commander (IC) holds overall authority and responsibility for managing the entire incident. The IC formulates the Incident Action Plan (IAP), directs resource deployment, and ensures operational safety. The IC is supported by three designated Command Staff officers who report directly to Command:

1. Incident Safety Officer (ISO): The ISO monitors the incident scene for hazardous conditions, unsafe operations, and structural collapse indicators. Crucially, the Safety Officer has emergency authority to stop or prevent unsafe acts when there is an immediate threat to life, and informs Command of the action taken.
2. Public Information Officer (PIO): The single designated point of contact for the news media, community leaders, and public inquiries. The PIO prepares official briefings and coordinates with external agency communicators.
3. Liaison Officer: Serves as the primary operational conduit between the IC and representatives from assisting and cooperating agencies (such as law enforcement, public utilities, emergency medical transport, and red cross authorities).

The General Staff (The FLOP Sections)

When an incident expands beyond the direct span of control of the IC, four functional General Staff sections are activated, represented by the acronym FLOP:

---

Span of Control & Field Escalation

Span of control refers to the number of individual subordinates or tactical resources that a single supervisor can effectively direct:

• Optimal Span of Control: 1 supervisor to 5 subordinates (1:5 ratio).
• Permissible Operating Range: Between 1:3 (used during high-intensity, high-risk tactical operations requiring direct hands-on oversight) and 1:7 (used in low-complexity, static support or logistics operations).

When a supervisor's span of control grows past this range, ICS subdivides the organization:

• Divisions: Divide an incident geographically based on physical location (e.g., Division A [front of building], Division Roof, Division 2 [second floor]).
• Groups: Divide an incident functionally across geographic boundaries to perform a specialized operational task (e.g., Search Group, Ventilation Group, Water Supply Group).

---

The Two-In/Two-Out Rule (OSHA 1910.134 & NFPA 1500)

Federal OSHA regulation 29 CFR 1910.134 and NFPA 1500 strictly govern operations inside an Immediately Dangerous to Life or Health (IDLH) atmosphere. Any structural fire beyond the incipient stage is classified as an IDLH environment. Before interior structural firefighting begins, at least four firefighters are required, two inside and two outside:

• Interior Attack Team (Two-In): A minimum of two firefighters must enter the IDLH atmosphere together. They must remain in continuous visual or direct voice (vocal) contact at all times. Radio contact alone does not satisfy the contact requirement for the interior buddy pair.
• Standby Team (Two-Out): A minimum of two fully equipped firefighters must remain positioned outside the IDLH atmosphere, dressed in full PPE with SCBA donned, dedicated to rapid rescue should the interior team encounter distress.

Standby Duties & The Life-Safety Exception

• Standby Personnel: The two outside firefighters account for the interior crew and stand ready to rescue them. OSHA allows one of them to take on another role, such as incident commander or safety officer, as long as that person can still perform assistance or rescue without endangering any firefighter at the incident.
• Emergency Rescue: OSHA's rule states that nothing in it is meant to stop firefighters from performing emergency rescue activities before an entire team has assembled. NFPA 1500 treats this as a narrow exception: action that could prevent the loss of life of a person in imminent danger. It does not cover protecting property.

---

Rapid Intervention Crew (RIC / RIT) & Emergency Traffic

As incidents escalate, the exterior standby team is upgraded to a dedicated Rapid Intervention Crew (RIC) or Rapid Intervention Team (RIT) consisting of four or more firefighters assigned solely to firefighter rescue.

Proactive Softening

A true RIC never sits idle. While standing by near the command post, the crew actively "softens the building": they conduct a 360-degree survey, force secondary exterior security doors, remove window security bars, place ground ladders to upper-floor windows for emergency bailout egress, and stage specialized rescue equipment (RIC Universal Air Connection bag, search ropes, irons, rotary saws, thermal imaging cameras).

Distress Communications: Mayday vs. Emergency Traffic

graph TD
    DIS["Fireground Distress Situation Encountered"] --> CHK{"Is a Firefighter Lost, Trapped, Injured or in Life Danger?"}
    CHK -- "Yes" --> MAY["TRANSMIT: 'MAYDAY, MAYDAY, MAYDAY'<br/>(Exclusively for firefighter distress)"]
    MAY --> LUNAR["Broadcast LUNAR Information:<br/>Location, Unit, Name, Air/Assignment, Resources"]
    CHK -- "No" --> EMG["TRANSMIT: 'EMERGENCY TRAFFIC'<br/>(For catastrophic scene hazards & tactical evacuation)"]
    EMG --> EVAC["Sound evacuation air-horn signal<br/>(pattern set by local SOP)"]

• Mayday: The single designated emergency radio transmission reserved exclusively to declare that a firefighter is lost, disoriented, trapped, injured, entangled, suffering SCBA air failure, or facing structural collapse. When a Mayday is broadcast, the IC commands immediate radio silence on that channel, deploys the RIC, and directs operating units to maintain or switch tactical channels.
• The LUNAR Acronym: When broadcasting a Mayday, firefighters must transmit critical rescue data using the LUNAR format:
  • L — Location: Exact position (e.g., "Second floor, Alpha-Bravo corner, bedroom 2").
  • U — Unit: Assigned apparatus (e.g., "Engine 12").
  • N — Name: Firefighter identity (e.g., "Firefighter Johnson").
  • A — Assignment / Air: Assigned tactical role and remaining air pressure (e.g., "Primary search, 1100 psi").
  • R — Resources Needed: Specific equipment required to effect rescue (e.g., "Wire cutters for ceiling wire entanglement").
• Emergency Traffic: The radio designation utilized by Command or operating companies to clear the radio channel for urgent, non-Mayday hazard announcements—such as an order for tactical evacuation, imminent structural collapse, live power lines falling across apparatus, or a tactical shift from offensive to defensive mode.
• Evacuation Alert: Many departments back up an evacuation order with a set pattern of air-horn blasts from the apparatus, and crews exit immediately. The exact signal (number and length of blasts) is set by local SOP.