When something goes seriously wrong at a public event — a structural collapse, a medical mass casualty event, a fire that cannot be controlled by the venue’s systems — the response that arrives will be organized around a specific management framework called the Incident Command System, or ICS. Police, fire, and emergency medical services across the United States are trained and required to use it. Event organizers who understand ICS terminology, structure, and principles are better equipped to communicate with responding agencies, support rather than obstruct the response, and participate meaningfully in pre-event emergency planning conversations. Those who do not understand it often find themselves talking past the very people they need to work with most.

This article explains what the National Incident Management System (NIMS) and ICS are, how they work, why they exist, and what the performing arts and event production community needs to know to engage with them effectively.

What Is NIMS?

The National Incident Management System (NIMS) is a standardized framework established by the United States federal government to enable all levels of government, the private sector, and nongovernmental organizations to work together during emergencies. It was created by Homeland Security Presidential Directive 5 (HSPD-5), signed in 2003, which directed the Department of Homeland Security to develop a national system for managing domestic incidents. All federal agencies are required to use NIMS, and any state or local agency receiving federal preparedness funding — which includes virtually every fire department, police department, and emergency management office in the country — is required to adopt it as well.

NIMS does not tell responders what to do in a specific emergency. It defines how organizations should be structured, how they should communicate, and how they should manage resources so that agencies from different jurisdictions and disciplines can work together without confusion. The core operational component of NIMS — the system that actually organizes people and resources on the ground — is the Incident Command System.

What Is the Incident Command System?

The Incident Command System (ICS) is a standardized management structure designed to be used for any emergency, at any scale, in any location. It was originally developed in the 1970s following a series of catastrophic wildfires in California, during which investigators found that the primary obstacle to effective response was not a shortage of resources — it was a failure of communication and coordination among the many agencies responding. Firefighters from different departments could not talk to each other on the radio. No one was clearly in charge. Resources were ordered that were never used. People showed up without being dispatched.

ICS was designed to solve those problems by creating a common organizational structure, a common set of terminology, and a defined set of management principles that any agency could adopt. Over the following decades it was adopted by fire, law enforcement, emergency medical services, public health, and emergency management agencies across the country. Today, ICS is the standard for emergency response in the United States at every scale, from a single-vehicle accident to a multi-state natural disaster.

The Structure of ICS

ICS organizes every response around a single position: the Incident Commander (IC). The IC has overall authority and responsibility for the incident. All other positions report, directly or through the chain of command, to the IC. This unity of command is fundamental to ICS — every person has exactly one supervisor, and no one takes direction from multiple sources simultaneously.

The IC is supported by two groups of positions:

The Command Staff

The Command Staff positions report directly to the Incident Commander and handle cross-cutting functions that affect the entire operation:

• Safety Officer (SO): Monitors site conditions and operations for hazards that could harm responders or others involved in the incident. The Safety Officer has authority to stop any operation that presents an immediate danger to life without prior authorization from the IC. This is the only position in ICS with unilateral stop-work authority.
• Public Information Officer (PIO): Manages information released to the media, the public, and other external audiences. In a multi-agency response, the PIO coordinates with PIOs from other agencies to ensure consistent, accurate messaging.
• Liaison Officer: Serves as the point of contact for representatives from cooperating agencies and organizations that are not part of the command structure. This is the role through which an event organizer would typically interact with the ICS organization during a response.

The General Staff

For larger incidents, the IC may establish up to four General Staff sections, each led by a Section Chief:

• Operations Section: Directs all tactical activities — the actual work of responding to the incident. In a venue emergency, this is the section managing the fire suppression, the medical response, the evacuation, or the search and rescue.
• Planning Section: Collects and analyzes information about the incident, tracks resources, maintains situation awareness, and develops the Incident Action Plan. The Planning Section keeps the IC informed of what is happening and what resources are available.
• Logistics Section: Provides support, resources, and services needed by the response: communications equipment, food, fuel, facilities, transportation. For extended operations, Logistics keeps the response sustainable.
• Finance/Administration Section: Tracks costs, manages contracts, processes injury claims, and handles administrative documentation. Activated when the incident involves significant expenditures or when a post-incident financial accounting will be required.

Not every section is activated for every incident. A single-agency response to a small incident may have only an Incident Commander and a few direct reports. ICS is explicitly designed to expand modularly as the incident grows and to scale back as it is resolved. An IC who is managing a contained medical emergency at a venue may need only Operations (the paramedics) and perhaps a Liaison Officer (to communicate with venue management). If the incident escalates to a mass casualty event requiring mutual aid from multiple agencies, all four General Staff sections may be activated within minutes.

Key Management Principles

Several principles underpin how ICS works in practice. Understanding them explains why responders behave the way they do during an incident, and why certain event organizer behaviors — however well-intentioned — can create problems.

Unity of Command

Every person operating within the ICS structure reports to exactly one supervisor. This eliminates the confusion that arises when individuals receive conflicting instructions from multiple sources. For event organizers, this means that during an active incident, instructions to crew or staff that conflict with directions from the IC or Operations Section will create dangerous confusion. The practical rule is simple: when ICS is activated, event staff take direction from the incident command structure, and the event organizer’s role shifts to coordination and support rather than direction.

Span of Control

Each supervisor in ICS should oversee between three and seven people, with five being the recommended optimum. When a supervisor’s span of control exceeds seven, communication degrades and accountability is lost. ICS expands the organizational structure specifically to maintain appropriate span of control as an incident grows. For events, this principle is a useful guide for the event’s own management structure regardless of whether a formal ICS is in place — a stage manager calling a show and simultaneously managing a medical emergency and communicating with venue management has exceeded a manageable span of control.

Management by Objectives

ICS is driven by clear, documented objectives. The IC establishes overarching incident objectives — what the response is trying to accomplish — and the Operations Section develops tactics to achieve them. Progress against objectives is tracked, and objectives are revised as conditions change. This objective-driven structure is what makes it possible for agencies that have never worked together to coordinate effectively: everyone knows what they are working toward and why.

Integrated Communications

ICS requires that all organizations involved in the response use a common communications plan. This includes common radio channels, common terminology, and clear protocols for who communicates with whom. ICS terminology is intentionally standardized — terms like “incident commander,” “staging area,” “command post,” and “all clear” have specific meanings that do not vary between agencies or incident types. Event organizers who use those terms correctly when communicating with responding agencies will be understood immediately. Those who use them loosely or differently will create confusion at the worst possible time.

Accountability

ICS requires that the location and status of every resource — every person, every piece of equipment — be known at all times. Resources check in when they arrive and check out when they leave. This accountability system is what allows the IC to know how many people are working in a building, whether everyone is accounted for when evacuation is ordered, and whether the resources needed for the next operational period are available. For venue management, supporting accountability means having accurate attendance records, knowing the location of all staff and contractors on site, and being able to provide that information to the IC when requested.

Unified Command

When an incident involves multiple agencies with different jurisdictional authority, or multiple jurisdictions, ICS can operate under a Unified Command. Instead of a single Incident Commander, Unified Command consists of designated representatives from each agency, working together from a single command post to establish shared objectives and a coordinated response.

For large events — outdoor festivals, arena concerts, stadium events, large outdoor theatrical performances — Unified Command is the likely command structure if a major incident occurs, because the response will involve law enforcement, fire, emergency medical services, and emergency management, each with distinct authority and responsibility. Venue management and the event organizer typically participate as cooperating organizations rather than as members of Unified Command, represented through the Liaison Officer. Understanding Unified Command helps event organizers understand why there is no single person they can call to negotiate an outcome during an active incident — the command is intentionally shared.

The Incident Action Plan

Every ICS response, regardless of scale, operates from an Incident Action Plan (IAP). For routine incidents, the IAP may be verbal and informal — the IC communicates priorities and assignments directly. For complex or extended incidents, the IAP is a written document that captures the incident objectives, the organizational structure, the communications plan, the medical plan, and the assignment list for each operational period.

FEMA maintains a set of standardized ICS forms used to develop and document the IAP. These include ICS 202 (Incident Objectives), ICS 203 (Organization Assignment List), ICS 204 (Assignment List), ICS 205 (Incident Radio Communications Plan), and ICS 206 (Medical Plan), among others. A complete list of ICS forms is available at the FEMA NIMS Resource Center.

Event organizers who have developed a written emergency action plan for their event are essentially creating a pre-incident IAP. The elements overlap significantly: objectives (what are we trying to accomplish during an evacuation?), assignments (who does what?), communications (who talks to whom on what channel?), and medical plan (where is first aid, how are serious injuries handled?). An event organizer who has worked through these elements in advance is far better positioned to integrate with the ICS structure if an incident escalates.

When an Incident Occurs During Your Event

The ESA Event Safety Guide addresses directly what happens when an incident occurs within a special event. When an incident arises — a medical emergency that exceeds the venue’s first-aid capacity, a fire, a structural failure, a crowd crush — the ranking public safety responder on scene typically assumes the role of Incident Commander for that specific incident. The overall event may continue to be managed by the event’s own team, but the specific incident has its own command structure.

The Incident Commander for the incident may authorize use of the event’s resources and communication systems, or may establish an independent command post. Either way, the first actions of the responding IC include:

• Assessing the situation and determining whether human life is at immediate risk.
• Establishing immediate priorities and objectives.
• Determining whether adequate resources are on scene or have been ordered.
• Establishing a command post if needed.
• Developing an initial action plan.
• Ensuring adequate safety measures are in place for responders.
• Keeping the overall event Incident Commander (if one exists) informed.

For the event organizer, the critical behavior during this period is to support the response and stay out of its way. The most helpful things venue management and event staff can do are: provide accurate information about the venue layout, the location of utilities, the number of people in the affected area, and the location of emergency equipment; keep unaffected areas of the venue functioning calmly; and designate a single point of contact through whom the IC can request information or resources from the event organization. Attempting to direct the response, argue about resource allocation, or override IC decisions creates delay and puts people at risk.

Why Event and Production Professionals Should Know ICS

The practical case for understanding ICS goes beyond compliance. It has three dimensions.

First, pre-event planning is more productive when everyone speaks the same language. When an event organizer meets with the local fire marshal, police department, and emergency management office to plan a large event, those agencies will structure the conversation around ICS concepts: Who is your Incident Commander? Where is your command post? What is your communications plan? What is the staging area for responding vehicles? What is your evacuation plan and who initiates it? An organizer who can engage with these questions directly moves the planning conversation forward rather than requiring the agencies to translate.

Second, tabletop exercises are more realistic with ICS structure. A tabletop exercise that walks the event team through a simulated emergency is significantly more valuable when the simulated response is structured the way an actual response would be organized. Participants learn not just what to do but how to communicate with the agencies they will actually be interacting with.

Third, small-scale ICS principles are directly applicable to production management. Unity of command, manageable span of control, clear objectives, integrated communications, and accountability are not emergency management concepts — they are management principles that happen to be formalized in ICS because failures in each have cost lives during emergency responses. Productions that apply these principles without calling them by their ICS names are simply well-managed productions.

Free NIMS and ICS Training

FEMA offers a comprehensive catalog of free online NIMS and ICS training through its Emergency Management Institute. The following courses are the most relevant for event and production professionals:

• IS-700.b: An Introduction to the National Incident Management System — The foundational NIMS course. Covers the purpose, principles, and components of NIMS. Approximately 3 hours. Recommended as the starting point for anyone who has not previously studied NIMS.
• IS-100.c: Introduction to the Incident Command System — Introduces ICS terminology, structure, and principles. Covers the command structure, the General Staff sections, and how ICS scales to incident complexity. Approximately 3 hours. This is the most widely taken ICS course in the United States.
• IS-200.c: Basic Incident Command System for Initial Response — Builds on IS-100 with more detailed coverage of the Incident Action Plan, span of control, resource management, and the roles of Command and General Staff. Approximately 4 hours. Recommended for anyone who may serve in a formal ICS role during an event response.
• IS-15.b: Special Events Contingency Planning for Public Safety Agencies — Specifically addresses planning for public safety at special events, including the integration of event management and public safety agency coordination. Includes the Special Events Contingency Planning Job Aids Manual with a comprehensive checklist series. Approximately 6 hours.

Each course concludes with a multiple-choice final examination. Passing scores earn a completion certificate from FEMA that can be saved as documentation of training. All courses are free, self-paced, and accessible at training.fema.gov. No account is required to access course materials, though creating a free account allows scores and certificates to be stored in the FEMA student record system.

For organizations that want to go further, FEMA also offers in-person ICS courses through local emergency management agencies and state emergency management training programs. The in-person ICS 300 (Intermediate ICS) and ICS 400 (Advanced ICS) courses cover multi-agency coordination, complex incident management, and area command — relevant for large-scale event production organizations and venue management teams that regularly interact with public safety agencies.

ICS in the Context of Your Emergency Action Plan

Every venue and every event should have a written emergency action plan (EAP). OSHA requires written EAPs for most workplaces under 29 CFR 1910.38. The ICS framework provides a useful structure for organizing an EAP because it mirrors the structure that responding agencies will bring to any major incident.

A venue EAP organized around ICS concepts should address:

• Who serves as the Event Incident Commander? This is the venue manager, production manager, or designated event safety coordinator — the person with authority to initiate evacuation, stop a show, or commit venue resources to an emergency response. This should be a single, named individual for every event, with a clear alternate.
• Where is the Command Post? The command post is the location from which the Event IC operates during an emergency. It should be identified in advance, communicated to all department heads, and accessible to responding public safety personnel. For a permanent venue, this is often the house manager’s office or a dedicated security operations room.
• What is the Communications Plan? Which radio channel is used for emergency communications? Who has a radio? What is the protocol for communicating with responding agencies? How is the audience addressed during an emergency?
• What is the Staging Area? Where do responding vehicles and personnel assemble when they arrive? The staging area should be accessible, not blocking emergency egress, and communicated to responding agencies in advance.
• What are the Evacuation Procedures? Who initiates evacuation, by what signal, and by what routes? Who is responsible for sweeping each section of the venue? Where does the audience assemble after evacuation? How is an “all clear” communicated?
• What is the Medical Plan? Where is first aid located? Who is the medical coordinator? At what point does the venue’s first-aid response request additional EMS resources? Where do ambulances stage and enter the venue?

Aligning the EAP with ICS terminology makes it immediately legible to any responding public safety agency. It also makes the pre-event planning meetings with those agencies more efficient, because the organizer is presenting a plan in a format the agencies already understand.

Key Takeaways

• NIMS is the federal framework that requires all public safety agencies to use a common management system during emergencies. ICS is the operational component of NIMS — the structure that organizes people and resources on the ground.
• ICS is built on an Incident Commander with unity of command, manageable span of control (3 to 7 people per supervisor), clear objectives, integrated communications, and accountability for all resources.
• When an incident occurs at an event, the ranking public safety responder typically assumes the Incident Commander role for that incident. The event organizer’s job shifts to supporting the response — providing information, keeping unaffected areas calm, and designating a single point of contact — not directing it.
• Event organizers who understand ICS terminology and structure communicate more effectively with public safety agencies during pre-event planning and during actual incidents.
• FEMA offers free online ICS training at training.fema.gov. IS-700 (NIMS overview), IS-100 (ICS introduction), IS-200 (ICS for initial response), and IS-15 (special events planning) are the most directly relevant courses.
• An emergency action plan organized around ICS concepts — naming an Event Incident Commander, identifying a command post, defining a communications plan, specifying a staging area, and writing a medical plan — is both OSHA-compliant and immediately legible to responding agencies.

References and Resources

U.S. Department of Homeland Security. (2003). Homeland Security Presidential Directive 5: Management of domestic incidents. The White House.

Federal Emergency Management Agency. (2017). National Incident Management System (3rd ed.). U.S. Department of Homeland Security. Retrieved from https://www.fema.gov/emergency-managers/nims

Federal Emergency Management Agency. (2010). IS-15.b: Special events contingency planning for public safety agencies. FEMA Emergency Management Institute. Retrieved from https://training.fema.gov/is/courseoverview.aspx?code=IS-15.b

Federal Emergency Management Agency. (n.d.). IS-700.b: An introduction to the National Incident Management System. FEMA Emergency Management Institute. Retrieved from https://training.fema.gov/is/courseoverview.aspx?code=IS-700.b

Federal Emergency Management Agency. (n.d.). IS-100.c: Introduction to the Incident Command System. FEMA Emergency Management Institute. Retrieved from https://training.fema.gov/is/courseoverview.aspx?code=IS-100.c

Federal Emergency Management Agency. (n.d.). Incident Command System forms. FEMA NIMS Resource Center. Retrieved from https://www.fema.gov/emergency-managers/nims/resources/incident-command-system-forms

Event Safety Alliance. (2013). The Event Safety Guide (v1.1), Appendix A: NIMS and ICS. Event Safety Alliance. Retrieved from https://eventsafetyalliance.org

Occupational Safety and Health Administration. (n.d.). Emergency action plans. 29 CFR 1910.38. U.S. Department of Labor. Retrieved from https://www.osha.gov/emergency-preparedness/evacuation-plans

---

See Also:

• Hand Tools and Power Tools in the Performing Arts: What Every Theater Technician Must Know
• Indoor Air Quality and Ventilation in the Performing Arts: What Every Technician Must Know
• A Risk Management Matrix for the Performing Arts
• ADA Compliance in the Performing Arts: A Practical Guide for Theater Technicians

Was this article helpful?

0 out of 5 stars

5 Stars		0%
4 Stars		0%
3 Stars		0%
2 Stars		0%
1 Stars		0%

5 Submit

Please Share Your Feedback

How Can We Improve This Article?

Name

Email

Submit