Study guide

13.1 National Incident Management System (NIMS) & ICS Architecture

NENA Emergency Number Professional ENP

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the NENA ENP Exam

2 Chapter 1: 9-1-1 Evolution & Legacy Network Architecture

1.1 Evolution of 9-1-1 & Central Office Tandem Architecture 1.2 Legacy Location Infrastructure: MSAG, ANI, ALI & ESN/ESZ 1.3 Legacy Network Signaling: CAMA, SS7 & Selective Routing 1.4 Network Design: Originating Service Providers, Local Loops & Transport Facilities 1.5 Signaling, Transport Protocols & Transmission Systems 1.6 Types and Features of 9-1-1 Systems: Basic, Enhanced & NG9-1-1

3 Chapter 2: Modern Location Technologies & MLTS

2.1 Wireless 9-1-1: Phase I, Phase II & Location Accuracy 2.2 Device-Based Location, Supplemental Data & RapidSOS 2.3 MLTS Compliance: Kari's Law & RAY BAUM'S Act

4 Chapter 3: NG911 i3 Core Network & Security

3.1 NG911 Architecture: The ESInet & Core Services 3.2 Border Control Function (BCF) & Security Edge 3.3 SIP Signaling in NG911 (RFC 3261) & Emergency Call Flow

5 Chapter 4: NG911 Location Services & Call Routing

4.1 Location Information Server (LIS) & PIDF-LO 4.2 Emergency Call Routing Function (ECRF) & LoST 4.3 Location Validation Function (LVF) & Legacy Gateways 4.4 NG9-1-1 PSAPs, EIDO, Additional Data & Transitional Elements

6 Chapter 5: Public Safety Radio, Broadband & FirstNet

5.1 Land Mobile Radio (LMR) Architecture & P25 Standards 5.2 Conventional vs. Trunked Radio Systems & Frequency Bands 5.3 Public Safety Broadband, FirstNet & Mission-Critical Services

7 Chapter 6: Call Processing, Accessibility & Protocol Systems

6.1 Call Answering Standards & Answering Point Workflows 6.2 Accessibility: TTY/TDD, Text-to-911 & Real-Time Text (RTT) 6.3 Emergency Protocol Systems & Medical Direction 6.4 PSAP Types & 9-1-1 Call Handling Equipment

8 Chapter 7: Computer Aided Dispatch & Information Systems

7.1 Computer Aided Dispatch (CAD) System Architecture 7.2 CAD Interfaces: Mobile Data, RMS & External Telematics 7.3 Logging Recorders & Synchronized Master Clocks 7.4 Non-Voice Communications & Information Networks 7.5 NENA Standards & Other Documents

9 Chapter 8: GIS for Next Generation 9-1-1

8.1 NG911 GIS Data Layers: Road Centerlines & Address Points 8.2 Boundary Polygons: PSAP, Law, Fire & EMS Jurisdictions 8.3 GIS Data Quality, Topology & Provisioning Workflows 8.4 9-1-1 Databases: Service Orders, ALI & Routing Records, Number Portability & Database Management

10 Chapter 9: Cybersecurity & CJIS Compliance

9.1 PSAP Cybersecurity Frameworks: NENA NG-SEC & NIST CSF 9.2 CJIS Security Policy: Access Control, MFA & Encryption 9.3 TDoS, Ransomware & Cyber Incident Response Planning

11 Chapter 10: Telecommunications Policy, Funding & Civil Rights

10.1 Regulatory Governance: FCC Authority & Part 9 Orders 10.2 9-1-1 Surcharges, Fee Diversion & Federal Grant Programs 10.3 Civil Rights & Language Access: Title VI & ADA Title II 10.4 Telecommunications Service Priority, Public Utility Commissions & the Canadian Framework 10.5 Special Legislative Areas: Alarms, Mass Notification, Pipelines & Other 9-1-1 Laws

12 Chapter 11: PSAP Governance, Strategy & Facility Design

11.1 PSAP Governance Models: Standalone, Co-Located & Consolidated 11.2 Strategic Planning & Performance Management 11.3 PSAP Facility Architecture, Physical Security & Ergonomics 11.4 Management Decision Making & Short-Range, Long-Range & Strategic Planning

13 Chapter 12: Power Redundancy, COOP & Disaster Recovery

12.1 Electrical Power Redundancy: UPS Systems & Generator Sets 12.2 Continuity of Operations Planning (COOP) & Alternate Facilities 12.3 Disaster Recovery, Redundant Connectivity & Evacuation 12.4 Emergency Management: Disaster Types & the Four Phases

14 Chapter 13: Emergency Incident Management & NIMS/ICS

13.1 National Incident Management System (NIMS) & ICS Architecture 13.2 Emergency Operations Centers (EOC) & Incident Command Interfaces 13.3 Mutual Aid & Interagency Interoperability: MACS & MABAS

15 Chapter 14: Procurement, Contracts & Financial Management

14.1 Capital Budgeting, Operational Expense & Financial Auditing 14.2 Public Procurement: RFPs, RFQs & Bid Evaluations 14.3 Vendor Contracting: MSAs, SLAs & Life-Cycle Management

16 Chapter 15: Staffing Models, Scheduling & Wellness

15.1 PSAP Staffing Models: Erlang C & NENA Staffing Calculator 15.2 Shift Scheduling Models, Overtime & Fatigue Mitigation 15.3 Telecommunicator Wellness: CISM, Peer Support & PTSD

17 Chapter 16: Training, CTO Coaching & Quality Assurance

16.1 Adult Learning & Communications Training Officer (CTO) Models 16.2 Quality Assurance & Continuous Quality Improvement (APCO/NENA ANS 1.107) 16.3 Continuing Education, Certifications & Professional Pathways 16.4 Performance Management, Employee Feedback & Customer Service

18 Chapter 17: Employee Relations, Labor Standards & Legal Protections

17.1 Fair Labor Standards Act (FLSA) & Dispatcher Overtime Rules 17.2 EEO, Title VII, FMLA & ADA in the PSAP Workplace 17.3 Progressive Discipline, Just Cause & Union Negotiations 17.4 Employee Relations, Employment Rights & Labor-Management Relations 17.5 Employment Laws: ADEA, Pregnancy Protections, Uniform Guidelines, OSH Act & Canadian Law 17.6 Compensation Laws: Equal Pay Act, COBRA, Social Security Act & Affordable Care Act

19 Chapter 18: Records Governance, Liability & Public Relations

18.1 Public Records, FOIA & Recording Retention Schedules 18.2 Legal Liability, Tort Claims Acts & Immunity Doctrines 18.3 Public Relations, Media Inquiries & Community Outreach

20 Chapter 19: Recruiting, Hiring, Compensation & Retention

19.1 Recruiting: Workforce Needs, Outreach & Sourcing 19.2 Hiring Procedures: Testing, Interview Panels, Agency Tours & Background Checks 19.3 Compensation & Benefits: Job Analysis, Pay Structures & Medical Benefits 19.4 Employee Retention & Succession Planning

13.1 National Incident Management System (NIMS) & ICS Architecture

Key Takeaways Explain This Topic AI

Born from the 1970s FIRESCOPE program and codified under HSPD-5 and PPD-8, NIMS comprises three core components: Resource Management, Command and Coordination (ICS, EOCs, MAC Groups, JIS), and Communications and Information Management.

ICS is governed by 14 core management characteristics, prominently including a manageable span of control (NIMS treats about one supervisor to five subordinates as the optimal guideline), modular organization, and unity of command (each individual reports to only one supervisor).

The ICS organizational hierarchy separates the Command Staff (Safety Officer with unilateral stop-work authority, Public Information Officer, Liaison Officer) from General Staff Section Chiefs (Operations, Planning, Logistics, Finance/Administration).

Unified Command (UC) co-locates multi-jurisdictional and multi-agency leaders at a single Incident Command Post (ICP) to establish shared incident objectives and execute a single Incident Action Plan (IAP) without forfeiting any agency's legal or statutory authority.

The Incident Action Planning (IAP) cycle follows the operational 'Planning P' process across designated operational periods (typically 12 to 24 hours), beginning with initial size-up (ICS Form 201) and progressing to a formal consolidated IAP.

Last updated: September 2026

13.1 National Incident Management System (NIMS) & ICS Architecture

Quick Answer: The Incident Command System (ICS) is a standardized, on-scene, all-hazards incident management architecture born out of the 1970 Southern California FIRESCOPE initiative and formally codified nationwide under Homeland Security Presidential Directive 5 (HSPD-5) and Presidential Policy Directive 8 (PPD-8). Governed by 14 core NIMS management characteristics, ICS enforces a manageable span of control (NIMS treats about 1:5 as the optimal guideline), unity of command (each responder reports to only one designated supervisor), and modular scalability. The Incident Commander is supported by a Command Staff (Safety Officer, Public Information Officer, Liaison Officer) and General Staff Section Chiefs (Operations, Planning, Logistics, Finance/Administration). When incidents cross jurisdictional borders or functional agency authorities, Unified Command (UC) co-locates agency leadership at a single Incident Command Post (ICP) to establish common objectives and execute a single consolidated Incident Action Plan (IAP) via a single Operations Section Chief without compromising individual statutory authority.

1. Historical Evolution, FIRESCOPE & Federal Directives

During the catastrophic wildfires of autumn 1970 in Southern California, multi-agency response operations suffered catastrophic systemic collapses. Over about two weeks, more than 500,000 acres burned, 16 lives were lost, and more than 700 structures were destroyed across multiple municipal, county, state, and federal jurisdictions. Subsequent post-incident investigations conducted by the U.S. Forest Service revealed that the failures were not rooted in lack of bravery, personnel, or firefighting apparatus. Instead, the disaster exposed severe structural breakdowns:

Incompatible organizational structures and competing chains of command across neighboring jurisdictions.

Absence of common terminology, resulting in contradictory radio codes and 10-codes (e.g., a code signifying 'officer in distress' in one department meant 'routine traffic stop' in another).

Unmanageable spans of control, with individual incident commanders attempting to direct 20 to 30 single companies directly over saturated radio frequencies.

Incompatible radio networks and overlapping, uncoordinated tactical frequencies.

Total absence of a standardized, timely multi-agency incident action planning process. [1970 Southern California Wildfire Disasters]

  • │
  • ▼
  • [FIRESCOPE Program Established (1972)]
  • (Developed ICS for tactical on-scene command & MACS for regional coordination)
  • │
  • ▼
  • [Homeland Security Presidential Directive 5 (HSPD-5, 2003)]
  • (Directed DHS to create NIMS; tied federal preparedness grants to NIMS/ICS compliance)
  • │
  • ▼
  • [Presidential Policy Directive 8 (PPD-8, 2011)]
  • (Established National Preparedness Goal: Prevention, Protection, Mitigation, Response, Recovery)
  • │
  • ▼
  • [Third Edition NIMS Architecture (Modern All-Hazards Public Safety Standard)]

In 1972, Congress funded the FIRESCOPE initiative ( Firefighting Resources of Southern California Organized for Potential Emergencies ), led by the U.S. Forest Service in partnership with California fire agencies. FIRESCOPE engineered two foundational disciplines that underpin modern public safety management: the Incident Command System (ICS) for on-scene tactical operations, and the Multiagency Coordination System (MACS) for interagency strategic prioritization.

Federal Legislative Codification

Homeland Security Presidential Directive 5 (HSPD-5, February 2003): HSPD-5 directed the Secretary of Homeland Security to develop and administer the National Incident Management System (NIMS) . HSPD-5 mandated that all federal departments adopt NIMS and made federal preparedness assistance (grants, cooperative agreements, and emergency contracts) to state, territorial, local, and tribal governments contingent upon formal NIMS compliance and ICS adoption.

Presidential Policy Directive 8 (PPD-8, March 2011): PPD-8 established the National Preparedness Goal , organizing national readiness across five core mission areas: Prevention, Protection, Mitigation, Response, and Recovery . ICS operates as the primary operational management vehicle within the Response mission area, ensuring that emergency responders nationwide share a unified operational doctrine.

2. NIMS Foundational Architecture: The 3 Core Components

NIMS is not an operational plan for specific emergencies; rather, it is a standardized, nationwide framework that enables diverse government agencies, non-governmental organizations (NGOs), and private sector partners to work together seamlessly across all incident types and operational environments. ┌─────────────────────────────────────────────────────────────────────────────┐

  • │ NATIONAL INCIDENT MANAGEMENT SYSTEM (NIMS) │
  • ├──────────────────────────┬──────────────────────────┬───────────────────────┤
  • │ RESOURCE MANAGEMENT │ COMMAND & COORDINATION │ COMMUNICATIONS & │
  • │ │ │INFORMATION MANAGEMENT │
  • ├──────────────────────────┼──────────────────────────┼───────────────────────┤
  • │ • Standardized Typing │ • Incident Command │ • Standardized Plain │
  • │ • Credentialing & Badging│ System (ICS) │ Language (No Codes) │
  • │ • Inventorying & Tracking│ • Emergency Operations │ • Technical Inter- │
  • │ • Mobilization & Demob │ Centers (EOCs) │ operability (P25) │
  • │ • Mutual Aid Agreements │ • Multiagency Coord. │ • Information Security│
  • │ │ Groups (MAC Groups) │ • Common Data Formats │
  • │ │ • Joint Information │ & Situational GIS │
  • │ │ System (JIS / JIC) │ │
  • └──────────────────────────┴──────────────────────────┴───────────────────────┘

Resource Management: Standardizes the mechanics of categorizing, ordering, mobilizing, tracking, and demobilizing emergency resources. Resources are categorized by Category (function, e.g., Fire, EMS, Law Enforcement), Kind (specific item, e.g., engine, helicopter, ambulance), and Type (performance capability, where Type 1 represents the highest capability and Type 4 represents basic capability).

Command and Coordination: Establishes standardized leadership structures across four organizational pillars: on-scene tactical management via ICS , off-scene operational and policy support via EOCs , executive policy and scarce resource prioritization via MAC Groups , and public outreach via the Joint Information System (JIS) .

Communications and Information Management: Enforces interoperability, plain language voice communications, strict data architecture standards, and cybersecurity controls across voice, video, CAD, and GIS systems.

3. The 14 Core NIMS Management Characteristics

The entire ICS operational architecture is anchored by 14 core management characteristics that dictate how public safety responders and emergency communications personnel interact during an event:

NIMS Characteristic Technical Standard & Operational Definition PSAP & Telecommunicator Impact

1. Common Terminology Eliminates 10-codes, phonetic alphabets, and agency jargon; mandates standard plain language for personnel titles, incident facilities, and resources. Telecommunicators must broadcast using plain text across all tactical and mutual aid channels (e.g., 'Officer Needs Emergency Assistance' instead of 'Signal 13').

2. Modular Organization Incident structure expands and contracts top-down based on incident complexity, size, and hazards; only activated positions are staffed. Dispatchers do not auto-populate an entire General Staff in CAD; units and roles activate dynamically as requested by the Incident Commander (IC).

3. Management by Objectives Establishing measurable incident objectives, identifying strategies, selecting tactics, and documenting task completion. Dispatchers monitor tactical channel benchmarks against stated objectives (e.g., 'Primary search completed; fire under control').

4. Incident Action Planning Centralized operational guidance for each operational period; initial operations utilize ICS Form 201, while protracted events mandate a full written IAP. Telecommunicators log the initial operational briefing (ICS 201) in CAD, recording deployed units, hazardous parameters, and tactical radio channels.

5. Manageable Span of Control Keeps the number of subordinates reporting to one supervisor manageable; NIMS (2017) treats 1:5 as the optimal guideline, adjusted to the incident. When an IC is directly directing more than 5 tactical units over the radio, dispatch must recognize the span-of-control breach and suggest establishing Divisions or Groups.

6. Incident Facilities & Locations Standardizes designated areas: Incident Command Post (ICP), Staging Areas, Incident Base, Camps, and Helibases. The PSAP records exact geographic coordinates and safe access corridors for each facility in CAD to route incoming mutual aid apparatus.

7. Comprehensive Resource Management Standardized processes to catalog, order, dispatch, track, and demobilize equipment and personnel. Telecommunicators track three discrete unit statuses in CAD: Assigned, Available (e.g., in Staging), or Out-of-Service, preventing duplicate dispatches.

8. Integrated Communications Unified communications planning connecting voice talkgroups, data networks, cross-band patches, and frequency assignments. The PSAP assigns dedicated tactical channels following the Incident Radio Communications Plan (ICS Form 205).

9. Establishment & Transfer of Command Clear establishment of command at the onset of an incident; transfer of command follows a formal, structured oral or written briefing. Dispatch broadcasts the formal command transfer over primary dispatch channels so all responders recognize the active Incident Commander.

10. Chain of Command & Unity of Command Chain of command provides an unbroken line of authority. Unity of command mandates that every individual reports to only one designated supervisor. Responders receive operational orders exclusively from their assigned supervisor, eliminating conflicting directives over the radio.

11. Unified Command (UC) Joint command structure used when incidents cross jurisdictional borders or functional agency authorities. Telecommunicators coordinate across multi-agency PSAPs to route tactical communications to a single co-located Unified Command team at the ICP.

12. Accountability Systematic tracking of all personnel through check-in (ICS 211), resource tracking, and periodic Personnel Accountability Reports (PAR). Dispatch initiates and logs timed PAR checks over the tactical channel at regular intervals (e.g., every 15 to 20 minutes) per local SOGs.

13. Dispatch / Deployment Resources deploy only when formally dispatched or requested through authorized channels. Freelancing and self-dispatching are prohibited. Telecommunicators must reject unauthorized self-dispatches and alert the IC immediately if unassigned units report arriving on scene.

14. Information & Intelligence Management Systematic gathering, analysis, and dissemination of operational intelligence, weather forecasts, and threat assessments. Dispatch pushes real-time CAD premise history, hazardous materials plume models, and GIS weather radar alerts directly to command.

4. Organizational Structure: Command Staff & General Staff

ICS enforces a clean, functional separation between executive command oversight and tactical execution. The organizational hierarchy expands from the top down as complexity demands. ┌─────────────────────────┐

  • │ Incident Commander │
  • │ (or Unified Command) │
  • └────────────┬────────────┘
  • │
  • ┌──────────────────────────┼──────────────────────────┐
  • ▼ ▼ ▼
  • ┌─────────────────────┐ ┌─────────────────────┐ ┌─────────────────────┐
  • │ Safety Officer │ │ Public Information │ │ Liaison Officer │
  • │ (Unilateral Stop- │ │ Officer (PIO) │ │ (Interagency Partner│
  • │ Work Authority) │ │ (Media & Public Com)│ │ Representatives) │
  • └─────────────────────┘ └─────────────────────┘ └─────────────────────┘
  • │
  • ┌──────────────────┬────────────┴───────┬──────────────────┐
  • ▼ ▼ ▼ ▼
  • ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐
  • │Operations │ │ Planning │ │ Logistics │ │ Finance / │
  • │ Section │ │ Section │ │ Section │ │Admin Sect.│
  • └─────┬─────┘ └───────────┘ └─────┬─────┘ └───────────┘
  • │ │
  • ├──────────────────────┐ ├──────────────────────┐
  • ▼ ▼ ▼ ▼
  • ┌───────────┐ ┌───────────┐ ┌───────────┐ ┌───────────┐
  • │ Geographic│ │Functional │ │ Service │ │ Support │
  • │ Divisions │ │ Groups │ │ Branch │ │ Branch │
  • └───────────┘ └───────────┘ └─────┬─────┘ └───────────┘
  • │
  • ┌─────┴─────┐
  • │ Comms │
  • │ Unit │
  • │(COML/COMT)│
  • └───────────┘
  • The Incident Commander (IC)

The Incident Commander has overall responsibility for managing the incident. The IC establishes incident objectives, determines overall operational strategy, approves resource releases, authorizes the Incident Action Plan (IAP), and maintains ultimate responsibility for responder safety.

The Command Staff

Command Staff officers report directly to the Incident Commander to handle specialized functions:

Safety Officer: Monitors incident operations and advises the IC on all matters relating to operational safety. The Safety Officer holds the absolute, unilateral authority to immediately bypass the chain of command and alter, suspend, or terminate any tactical operation presenting an imminent hazard.

Public Information Officer (PIO): Serves as the official conduit for information between the incident command structure, news media, and the public. Coordinates press briefings, monitors social media rumors, and integrates with the Joint Information Center (JIC).

Liaison Officer: Serves as the primary contact point for assisting and cooperating agency representatives (e.g., utility companies, Red Cross, state environmental agencies, transit authorities) who lack operational seats within Unified Command.

The General Staff (FLOP)

The General Staff consists of four operational sections, remembered by the acronym FLOP :

Operations Section (Operations Section Chief / OSC): Directly manages all tactical operations executed to accomplish the incident objectives. Develops tactical organization, directs tactical resources, and requests additional resources through the IC.

Planning Section (Planning Section Chief / PSC): Collects, evaluates, and disseminates incident intelligence. Tracks resource status through its Resources Unit, prepares the Incident Status Summary (ICS 209) and the Incident Action Plan (IAP), and develops the demobilization plan.

Logistics Section (Logistics Section Chief / LSC): Provides all facilities, services, and material support needed to sustain incident personnel and equipment. Organized into two branches:

Service Branch: Communications Unit (housing the COML, COMT, and RADO), Medical Unit, and Food Unit.

Support Branch: Supply Unit, Facilities Unit, and Ground Support Unit.

Finance / Administration Section (Finance Section Chief / FSC): Tracks all incident costs, personnel work hours, vendor procurement contracts, worker injury compensation claims, and post-incident financial recovery audits.

5. Tactical Sub-Elements: Divisions, Groups, Branches, Strike Teams & Task Forces

To prevent span-of-control breakdown within the Operations Section, resources are organized into structured sub-elements:

Divisions: Divide an incident into geographic areas of operation (e.g., Division A for the street-front exterior, Division 1 for the first floor, Division Roof for roof operations).

Groups: Divide an incident into functional areas of operation that cut across geographic lines (e.g., Ventilation Group, Search and Rescue Group, Water Supply Group).

Branches: An intermediate organizational tier established between the Operations Section Chief and Divisions/Groups when the span of control becomes unmanageable or when operations span distinct disciplines (e.g., Fire Branch, Law Enforcement Branch, EMS Branch).

Strike Teams: A combination of a specified number of resources of the same kind and type , with common communications and a designated leader (e.g., a strike team of 5 Type 1 structural fire engines).

Task Forces: A combination of mixed resources assembled for a specific tactical mission, with common communications and a designated leader (e.g., 2 engines, 1 ladder truck, and 1 paramedic rescue unit assembled for high-angle technical rescue).

Single Resources: An individual piece of equipment and its operational crew, or an individual specialist.

6. Manageable Span of Control & Unity of Command

Span of control is a core NIMS management characteristic:

The Guideline: NIMS (2017) describes 1:5 as the optimal ratio of subordinates to supervisor, while recognizing that incidents may call for different ratios (older guidance cited a range of 3 to 7).

Judgment: Supervisors weigh the type of incident, the nature of the work, hazards, and the distance between resources.

Corrective Actions:

If a supervisor oversees very few resources, the organization may be over-built and can be consolidated.

If an IC is directing well beyond the guideline (for example, 8 or more tactical units directly over the radio), the supervisor should delegate by activating Divisions (geographic) , Groups (functional) , or intermediate Branches . UNSAFE SPAN OF CONTROL (1:9 Ratio - Overloaded)

  • [Incident Commander]
  • ┌───┬───┬───┬───┼───┬───┬───┬───┐
  • ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
  • Eng1 Eng2 Eng3 Eng4 Trk1 Trk2 Med1 Med2 Squad1
  • PROPERLY MODULATED SPAN OF CONTROL (1:3 Ratio - Compliant)
  • [Incident Commander]
  • ┌───────────┼───────────┐
  • ▼ ▼ ▼
  • [Division A] [Division B] [Rescue Group]
  • ┌─────┴─────┐ ┌─────┴─────┐ ┌─────┴─────┐
  • ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
  • Eng1 Eng2 Trk1 Eng3 Eng4 Trk2 Med1 Med2 Squad1
  • Unity of Command vs. Unified Command

Candidates must never confuse these two distinct concepts:

Unity of Command: An accountability principle governing individuals— every responder reports to only one designated supervisor and receives orders from only that supervisor.

Unified Command: An organizational leadership structure governing multi-agency incidents— multiple agencies collaborate at a single Incident Command Post to manage an incident jointly.

7. Unified Command (UC) Mechanics in Multi-Agency Operations

When an incident affects multiple jurisdictions (e.g., a wildland fire burning across municipal, state forest, and federal parklands) or involves multiple agencies with separate statutory responsibilities (e.g., an active shooter event involving local police, county sheriff, municipal fire, and federal law enforcement), Unified Command (UC) is implemented.

Foundational Principles of Unified Command:

Co-Located Command: Participating agency leaders gather at a single Incident Command Post (ICP) . Operating from separate command posts or separate vehicles is strictly prohibited.

Common Objectives & Single IAP: The commanders jointly determine incident objectives, agree on operational strategies, and approve a single consolidated Incident Action Plan (IAP) .

Single Operations Section Chief: Tactical execution is directed by a single Operations Section Chief selected from the agency with the primary operational responsibility for the current operational period.

Preservation of Legal Authority: No participating agency forfeits its legal authority, statutory mandates, or jurisdictional responsibilities. Decisions are made by consensus; if an agency cannot legally agree to a tactic, the commanders negotiate a lawful alternative within the UC framework.

Integrated General Staff: Planning, Logistics, and Finance/Administration sections are staffed jointly by personnel from all participating agencies, preventing duplicate support footprints.

8. The Incident Action Planning (IAP) Cycle & The 'Planning P'

Incident Action Planning is the structured process that transforms incident objectives into an executable operational plan for each Operational Period (a designated timeframe, typically 12 to 24 hours, during which tactical operations are executed). [THE PLANNING 'P']

  • [Execute IAP & Assess] ◄──────────────┐
  • │ │
  • ▼ │
  • [Operational Period Briefing] │
  • │ │ (Phased Planning Cycle
  • ▼ │ Repeats for Each
  • [IAP Preparation & Approval] │ Operational Period)
  • │ │
  • ▼ │
  • [Planning Meeting] │
  • │ │
  • ▼ │
  • [Tactics Meeting (ICS 215)] │
  • │ │
  • ▼ │
  • [Strategy Meeting / Objectives (ICS 202)] ──┘
  • ▲
  • │ (Incident Onset / Initial Response Leg)
  • ┌──────────────┴──────────────┐
  • │ Incident Occurs / Intake │
  • │ Initial Response & Size-Up │
  • │ Incident Briefing (ICS 201) │
  • └─────────────────────────────┘

The planning process is visually represented by the Planning P . The vertical 'leg' represents the initial response phase from incident onset through the initial command briefing. The circular top 'head' of the P represents the recurring operational planning cycle:

Phase 1: Understand the Situation: Size-up, intelligence gathering, and damage assessment.

Phase 2: Establish Incident Objectives: IC/UC issues overall objectives using ICS Form 202 .

Phase 3: Develop the Plan: Operations and Planning chiefs conduct the Tactics Meeting using the ICS Form 215 (Operational Planning Worksheet) and ICS Form 215A (Incident Safety Analysis) to determine resource assignments.

Phase 4: Prepare and Approve the IAP: The Planning Section compiles the full IAP package, the Safety Officer reviews safety parameters, and the IC/UC formally approves it.

Phase 5: Execute, Evaluate & Assess: The plan is briefed to supervisors at the Operational Period Briefing, executed in the field, and evaluated continuously.

Essential ICS Forms for the Public Safety Telecommunicator:

ICS 201 (Incident Briefing): Documents initial incident situation, map sketch, tactical actions taken, and assigned resources during the initial response.

ICS 204 (Assignment List): Details the specific tactical assignments, supervisors, and resources allocated to a Division or Group for an operational period.

ICS 205 (Incident Radio Communications Plan): Compiles all assigned radio talkgroups, frequencies, channel functions, and CTCSS/NAC tones for the incident.

ICS 205A (Communications List): Documents non-radio telephone numbers, cellular contacts, and pager assignments for incident personnel.

ICS 214 (Activity Log): Documents chronological operational actions, events, and unit milestones for legal and historical record-keeping.

9. The PSAP's Role in ICS Initiation & Initial Tactical Command

In public safety incident lifecycles, the first official operational phase occurs inside the Emergency Communications Center (ECC) / PSAP:

Initial Incident Sizing & Threat Classification: Telecommunicators extract caller location, assess hazards, filter duplicate calls, and establish the initial CAD incident profile.

Automated Alarm Assignment (Run Cards): The telecommunicator initiates the dispatch of pre-configured run card assignments tailored to the specific incident classification, assembling the initial tactical resources.

Designating Tactical Radio Channels: The PSAP assigns dedicated tactical frequencies and issues safe staging directions and hazardous approach warnings to responding units.

Interim Command Oversight: Until the first field unit arrives on scene and broadcasts an official arrival report, the telecommunicator manages radio telemetry, initiates unit safety timers, and coordinates incoming mutual aid.

Formal Transfer of Command: When the first qualified field unit arrives on scene, they transmit a formal on-scene size-up and command establishment message (e.g., 'Engine 1 on scene, two-story commercial building, heavy smoke showing from Side Alpha. Engine 1 assuming Main Street Command'). The telecommunicator repeats the command establishment broadcast, enters the Incident Commander's identity and ICP location into CAD, and shifts to supporting on-scene command.

10. Operational Traps & ENP Exam Watch

Span of Control Ratio: Know that NIMS treats 1:5 as the optimal guideline (older materials cite 3 to 7). If an scenario depicts a commander directing 8, 9, or 10 single units directly over the radio, the correct action is establishing Divisions (geographic) or Groups (functional) .

Unity vs. Unified Command: Candidates frequently mix up these terms. Unity of Command means a responder answers to one supervisor . Unified Command is the multi-agency leadership structure co-located at the ICP operating under a single IAP.

Safety Officer's Absolute Authority: The Safety Officer is the only Command Staff officer authorized to bypass the chain of command and halt unsafe tactical operations immediately without prior approval from the Incident Commander.

ICS Facilities Rules: Remember that an incident has only one Incident Command Post (ICP) and only one Incident Base (housing logistics), but may have multiple Staging Areas and multiple Camps .