NIMS/ICS key terms

A standardized, on-scene, all-hazards management framework that integrates facilities, equipment, personnel, procedures, and communications under a common organizational structure to improve incident response.

A comprehensive, national approach to incident management that provides a common framework for all levels of government and private-sector organizations to work together effectively.

An ICS application where multiple agencies with jurisdictional or functional responsibility for an incident jointly manage it through a single command structure, sharing authority and responsibility.

The individual responsible for overall management of the incident, including establishing objectives, approving the Incident Action Plan, and ensuring responder safety.

The IC's direct advisors who handle critical functions not included in the General Staff: Public Information Officer, Safety Officer, and Liaison Officer.

The ICS organizational element responsible for the primary functional areas of Operations, Planning, Logistics, and Finance/Administration, each led by a Section Chief.

The General Staff section that directs and coordinates all tactical actions to achieve incident objectives, including managing resources at the incident scene.

The General Staff section that collects, evaluates, and disseminates incident information; prepares the Incident Action Plan; and tracks resource status.

The General Staff section that provides facilities, services, and material support to meet incident needs, including communications, medical, food, and supplies.

The General Staff section that monitors incident costs, handles procurement, and manages financial aspects such as compensation and cost documentation.

A Command Staff member who serves as the conduit for information to internal and external stakeholders, including the media and public.

A Command Staff member who monitors safety conditions, develops safety measures, and has authority to stop or modify unsafe actions.

A Command Staff member who serves as the primary contact for supporting agencies and assists the IC in coordinating with external representatives.

The fourteen foundational principles that guide incident management, including common terminology, modular organization, management by objectives, and accountability.

The use of standardized words and phrases-such as clear text, plain language, and common titles-to ensure consistent communication among all responding organizations.

An ICS principle where the organization expands or contracts based on incident complexity, adding or releasing functional units as needed.

A NIMS principle requiring that incident objectives be established, communicated, and used to guide all activities, with progress measured and objectives revised as needed.

A written or oral plan containing general objectives, specific tactical actions, and support activities for a specified operational period.

The time period established by the IC for which the Incident Action Plan is prepared and during which tactical activities are executed.

The principle that each individual reports to only one supervisor, ensuring clear lines of authority and avoiding conflicting directions.

The orderly line of authority within the incident organization through which orders and information flow from the IC down to all personnel.

The number of subordinates that a supervisor can effectively manage, typically ranging from three to seven with five being optimal in ICS.

A NIMS principle that allows agencies with different legal, geographic, or functional responsibilities to jointly manage an incident without relinquishing their authority.

The NIMS principle that all resources and personnel are tracked, all actions are documented, and all responders are responsible for their assigned duties.

The process by which all resources and personnel arriving at an incident are recorded and assigned to a specific function or location.

The systematic process of monitoring the status, location, and assignment of all resources throughout an incident to maintain accountability.

The NIMS principle that ensures incident-related information and intelligence are collected, analyzed, and shared to support decision-making.

The NIMS principle that ensures a common communications plan, interoperable equipment, and standardized protocols are used across all responding agencies.

The NIMS principle that command is clearly established at the start of an incident and formally transferred when a more qualified or appropriate person assumes authority.

The NIMS principle that resources are deployed only when requested and dispatched by an appropriate authority, avoiding self-dispatch.

The NIMS principle that resources are categorized, ordered, tracked, and demobilized in a systematic way to ensure efficient use.

A classification (Type 5 to Type 1) that describes the severity and difficulty of an incident, guiding resource needs and organizational structure.

An organization established to oversee multiple incidents that are each managed by separate Incident Commanders, typically when incidents are complex or numerous.

The physical location where the Incident Commander and Command Staff operate, coordinating the incident response and managing the IAP.

A facility from which jurisdictional authorities coordinate overall support and policy decisions during an incident, without directing tactical operations.

The process that allows all levels of government and private-sector entities to coordinate activities and share information to support incident management.

The formal assignment of specific authority and responsibility from a higher-ranking official to a subordinate, such as from an agency administrator to an Incident Commander.