IS-0100.c: Introduction to the Incident Command System (ICS 100) Student Manual Notes
Course Introduction, Goal, and Objectives
IS-0100.c: An Introduction to the Incident Command System, ICS 100, is a foundational course released in March . As the first in a series of Incident Command System (ICS) courses, it is designed for all personnel involved in incident management. The overall goal of the course is to promote effective response by familiarizing students with ICS and National Incident Management System (NIMS) principles, and preparing them to coordinate with partners across all levels of government and the private sector. The course provides the groundwork for further study in NIMS, such as the IS-700.b course.
Upon completion of IS-0100.c, students should be able to explain the basic principles and structure of ICS, describe the NIMS management characteristics, identify ICS functional areas and roles of the Incident Commander and Command Staff, describe General Staff roles, and identify how these characteristics apply across various disciplines. Successful completion requires participation in unit activities, a score of or higher on the final exam, and the completion of an end-of-course evaluation. The course agenda is divided into a morning session covering Units through ( total) and an afternoon session covering Units and , the final exam, and course wrap-up ( total).
Lesson 1: ICS Overview and the Whole Community Approach
Unit introduces the concept of the "Whole Community," which asserts that every part of society must be involved in managing incidents—not just the Federal Government. This includes all levels of government, non-governmental organizations (NGOs), and private-sector entities in fields such as transportation, health care, public works, and agriculture. The Incident Command System (ICS) itself is a standardized approach to incident management used nationwide for incidents of any size or type, including planned events like parades or the Olympics. It establishes common processes for planning and resource management and allows for the seamless integration of personnel, equipment, and facilities within a common structure.
ICS was developed in the following catastrophic wildfires in California. Post-incident analysis revealed that response failures were rarely due to a lack of resources or poor tactics; rather, they stemmed from management problems. Today, ICS is a core component of NIMS, alongside Resource Management and Communications and Information Management. Using ICS is a key requirement for jurisdictions receiving National Preparedness Grants and is mandated by federal laws. The Superfund Amendments and Reauthorization Act (SARA) of and OSHA rule (effective March , ) require all organizations handling hazardous materials to use ICS. Institutionalizing ICS happens at the policy level (through executive orders or legislation) and the organizational level (through training and exercises).
Lesson 2: The NIMS Management Characteristics
Lesson details the foundational characteristics of NIMS that guide ICS. These include:
Common Terminology: Ensures that organizational functions, resource descriptions (typing), and incident facilities have consistent names to prevent confusion during multi-agency responses. Radio codes and jargon are strictly avoided.
Modular Organization: The ICS structure develops from the top down and is flexible, expanding or contracting based on the incident's size and complexity. The Incident Commander is responsible for this expansion.
Management by Objectives: Operations are driven by specific, measurable incident objectives, strategies, and tactics.
Incident Action Planning: Every incident requires an Incident Action Plan (IAP), which can be oral or written (though hazardous materials incidents always require written IAPs). It must answer: What do we want to do? Who is responsible? How do we communicate? What is the procedure if someone is injured?
Manageable Span of Control: Refers to the number of individuals a supervisor can effectively manage. The optimal ratio is ( supervisor to subordinates), though variables like safety hazards or distance may alter this.
Incident Facilities and Locations: Standardized locations such as the Incident Command Post (ICP), Staging Areas, Bases, Camps, and Mass Casualty Triage Areas.
Comprehensive Resource Management: Standard mechanisms for identifying, acquiring, mobilizing, tracking, demobilizing, and restocking resources (personnel, teams, facilities, equipment, and supplies).
Integrated Communications: Uses common communication plans and interoperable systems (voice and data) to maintain situational awareness.
Establishment and Transfer of Command: Command must be established at the outset and transferred through a formal briefing. Reasons for transfer include the arrival of a more qualified individual, legal requirements (e.g., FBI taking over a terrorist incident), or the need for personnel to rest.
Unified Command: Established when multiple agencies have jurisdiction. There is no single "commander"; instead, agencies work together to set joint objectives while maintaining their own authority.
Chain of Command and Unity of Command: Chain of command defines the flow of authority; Unity of Command means each person reports to only one designated supervisor.
Accountability: Includes strict check-in/check-out procedures, adherence to the IAP, and personal responsibility for actions.
Dispatch/Deployment: Personnel should only deploy when requested through formal resource management systems to avoid "self-dispatching," which can overwhelm the scene.
Information and Intelligence Management: Processes for gathering, analyzing, and sharing incident-related data. In NIMS, "intelligence" specifically refers to threat-related information from law enforcement or medical surveillance.
Lesson 3: ICS Functional Areas and Command Staff Roles
There are five major functional areas in ICS: Incident Command, Operations, Planning, Logistics, and Finance/Administration. A sixth function, Intelligence/Investigations (I/I), is used for incidents requiring intensive investigative activity, such as criminal acts or epidemiological outbreaks. Command is defined as the act of directing or controlling through explicit authority. The Incident Commander (IC) is the only position always staffed and has overall responsibility for safety, information services for stakeholders, and liaison activities with other agencies. Qualifications for an IC are based on training and expertise, not just rank.
Command Staff support the IC and include the Public Information Officer (PIO), who manages media and public interface; the Safety Officer (SO), who monitors operations for hazards and has the authority to stop unsafe acts; and the Liaison Officer (LNO), who acts as the point of contact for assisting and cooperating agencies. Coordination differs from Command; while Command happens on-scene, coordination involves support entities like Emergency Operations Centers (EOCs), which relieve the IC of external burdens, and Joint Information Centers (JICs), which centralize public information messages.
Lesson 4: General Staff Roles
The General Staff consists of Section Chiefs who report directly to the IC. The Operations Section is usually the first to be established and is responsible for implementing tactics and managing response resources. The Planning Section manages information, tracks resource status, maintains documentation, and prepares the IAP and demobilization plans. The Logistics Section provides all support needs, including facilities, transportation, communications, and medical/food services for responders. The Finance/Administration Section handles contract negotiation, timekeeping, cost analysis, and injury compensation or reimbursement documentation.
If the IC does not staff a specific section, the IC remains responsible for that function. The ICS structure is unique because it does not correspond to an agency's daily administrative structure; for example, a daily "Director" might serve as a "Unit Leader" within ICS to ensure consistent management terminology and avoid confusion.
Lesson 5: Practical Application and Emerald City Flood Scenario
This unit applies course concepts through a severe weather scenario in Emerald City. Over several days, heavy rain causes rising river levels, leading to evacuations. Key applications of NIMS characteristics identified in the scenario include: Comprehensive Resource Management (organizing shelter volunteers), Modular Organization (the IC creating an Evacuation Group within the Operations Section), Integrated Communications (requiring plain language and specific radio frequencies), and Transfer of Command (moving from response to recovery under a Unified Command of Emergency Management, Health, and Public Works departments). The scenario emphasizes that accountability requires personnel to check out before being released and that the PIO must be used to reassure the public during the recovery phase.
Questions & Discussion
Student Introductions (Visual 4): Students are asked to provide their name, job title, emergency response experience, and potential roles in incidents.
Student Expectations (Visual 5): What do you expect to gain from this course?
ICS for Planned Events (Visual 14): What are some examples of planned events where ICS was used, and why was it beneficial? (Examples include state fairs, parades, and inaugurations).
Incident Response Problems (Visual 17): What are common causes of response problems? (The course notes that historical failures were linked to management, not lacks in tactics or resources).
Command Knowledge Check (Visual 22-24): Identify the Command Staff member.
"Wearing protective equipment and safe tactical options" = Safety Officer.
"Briefings to supporting Agency Representatives" = Liaison Officer.
"Primary contact for details about the incident and response" = Public Information Officer.
General Staff Review (Visual 14-18): Identify the Section Chief.
"Getting generators and equipment to Staging Areas" = Logistics Section Chief.
"Tracks all personnel participating in the response" = Planning Section Chief.
"Search and rescue and first aid services" = Operations Section Chief.
"Overseeing contracting for supplies" = Finance/Administration Section Chief.
Comprehensive Glossary of Key Terms
Access and Functional Needs: Individual circumstances requiring assistance or accommodation for mobility, communication, etc. Agency Administrator/Executive: Official responsible for administering policy for a jurisdiction. Authority Having Jurisdiction (AHJ): Entity with responsibility for overseeing the qualification process within an organization. Chain of Command: Orderly line of authority within the hierarchy of incident management. Clear Text: Communication not using codes; also known as Plain Language. Credentialing: Documentation that verifies an individual's qualification for a position. Demobilization: The safe return of a resource to its original location. Division: Organizational level responsible for operations within a defined geographic area. Emergency Management Assistance Compact (EMAC): Interstate mutual aid agreement for liability and reimbursement resolution. Group: Subdivisions established to divide the structure into functional areas of operation, not necessarily geographically bound. Incident Action Plan (IAP): Oral or written plan containing objectives and tactics for a specified operational period, usually to . Incident Management Team (IMT): Rostered group of ICS-qualified personnel including Command and General Staff. Interoperability: Ability of systems and personnel to provide and receive data/services to operate effectively together. Kind/Type: Resource classification based on nature (kind) and level of capability (type). Management by Objectives: NIMS fundamental involving establishing specific, measurable outcomes and taking corrective action. National Incident Management System (NIMS): Systematic approach to guide all levels of government and NGOs to work together. Span of Control: Number of subordinates a supervisor manages, typically expressed as a ratio (). Unity of Effort: Coordination through cooperation without interfering with agency authorities. Whole Community: Focus on enabling participation from private, nonprofit, and government sectors to foster coordination.