Last Updated: January 20, 2026
Who this is for
This guide is written for public safety professionals responsible for special event security, including:
- Law enforcement and venue security supervisors
- Fire and EMS officers and medical branch leaders
- Emergency management and EOC staff
- Public health, public works, transportation, and utilities partners are involved in major special events and mass gatherings
How this guide helps
Use this page as an operational playbook to align your special event or mass gathering with NIMS and ICS, from building a multi‑agency planning team to producing copy‑ready checklists, matrices, and incident planning documents.
Quick event security checklist
- Establish a multi‑agency planning team and designate an Incident Commander or Unified Command.
- Complete a risk and threat assessment for the planned event, including worst‑case scenarios.
- Define incident objectives and build an ICS organization for the event (org chart + position assignments).
- Develop a written Incident Action Plan (IAP-lite): objectives, org chart, communications, medical, safety, maps.
- Implement access control and credentialing for all venues, perimeters, and restricted zones.
- Coordinate crowd management, ingress/egress, and evacuation routes with fire, EMS, transportation, and venue ops.
- Integrate medical, fire, hazmat/WMD, and public health surge plans into the special event contingency plan.
- Stand up interoperable communications and Joint Information System (JIS) support for public information.
- Conduct pre‑event briefings, exercises, and just‑in‑time training for all sections and external partners.
- Complete a post‑event After‑Action Review (AAR) and improvement plan tied to future events.
Planning Team, Roles, and Outputs
Planning Team & Stakeholders
Special event security planning under FEMA guidance starts with a formal planning team that spans all agencies supporting the mass gathering or planned event.
- Include law enforcement, fire, EMS, emergency management, public health, transportation, public works, utilities, venue operations, and private security in the core planning group.
- Use a planning team charter that defines scope, authority, decision‑making, meeting cadence, and how recommendations feed into Unified Command and local policy groups or MAC Groups.
Sample responsibility matrix
- Role: Law Enforcement Operations → Responsibility: Perimeter security, access points, protest management, criminal investigations → Owner: LE Operations Section or Branch Director → Trigger: Crowd size thresholds, demonstrations, criminal incidents.
- Role: Fire/EMS → Responsibility: Fire suppression, medical surge, triage, ambulances staging → Owner: Fire/EMS Branch Director → Trigger: Medical calls, fire alarms, mass casualty incidents, hazmat/WMD indicators.
- Role: Emergency Management/EOC → Responsibility: Resource support, mutual aid, situational awareness, liaison with MAC Group → Owner: EOC Manager → Trigger: Escalating incident complexity, multi‑jurisdictional impacts, resource shortfalls.
- Role: Public Information/JIS → Responsibility: Public messaging, rumor control, media coordination → Owner: PIO / JIS Coordinator → Trigger: Public interest, misinformation, operational changes, life‑safety messaging.
NIMS/ICS for Planned Events
Command & Coordination (ICS, UC, EOC, MAC, JIS)
NIMS defines the standard structures for managing incidents and planned events: Incident Command System (ICS), Emergency Operations Centers (EOCs), Multiagency Coordination Groups (MAC Groups), and the Joint Information System (JIS).
- Use ICS or Unified Command at the event site to manage operations, planning, logistics, and finance/administration, assigning section chiefs and unit leaders as needed.
- Activate an EOC or similar coordination center for larger major special events to provide resource support, situational awareness, and policy coordination, with MAC Groups providing senior‑level guidance and prioritization.
When to stand up Unified Command
- Multiple agencies have legal authority or jurisdiction over aspects of the event (city police, county sheriff, state police, fire, EMS).
- The planned event or mass gathering has regional impacts, high threat levels, or complex risks such as terrorism, hazmat/WMD, or large protests.
Simple ICS org example for a major special event
- Incident Commander / Unified Command
- Command Staff: Safety Officer, Liaison Officer, Public Information Officer
- Operations Section: Law Enforcement Branch, Fire/EMS Branch, Crowd Management Group, Traffic Group, Venue Security Group
- Planning Section: Situation Unit, Documentation Unit, Resources Unit
- Logistics Section: Communications Unit, Medical Supply Unit, Ground Support Unit
- Finance/Administration Section: Time Unit, Cost Unit, Compensation/Claims Unit.
Risk & Threat Assessment for Mass Gatherings
Threats, Hazards, and Worst‑Case Scenarios
Special event contingency planning guidance stresses a structured threat and hazard assessment that covers both routine and worst‑case conditions.
- Identify threats such as severe weather, crowd crush and egress issues, criminal activity, active assailant, terrorism, hazmat/WMD releases, infrastructure failure, and medical surge associated with alcohol, heat, or high‑risk activities.
- Assess the likelihood and impact of each hazard and document mitigation measures, triggers for escalation, and which section or agency owns each control.
Risk & threat assessment steps
- Define event profile: type of special event, size, duration, venues, demographics, and critical dates.
- Map physical layout: stages, ingress/egress, choke points, VIP areas, critical infrastructure, shelter options.
- Analyze hazards and threats: weather, fire, crowd crush, violence, hazmat/WMD, traffic, cyber disruptions.
- Evaluate current controls: staffing, barriers, screening, medical coverage, communications, mutual aid.
- Set risk priorities and define additional controls, contingency annexes, and triggers for Unified Command or EOC support.
Crowd, Access, and Medical/Fire Integration
Crowd Management and Ingress/Egress
Managing crowd flow and evacuation/egress is central to public safety at mass gatherings and major special events.
- Design ingress and egress routes to avoid choke points, support emergency vehicle access, and allow rapid evacuation, coordinating with fire, EMS, transportation, and venue engineers.
- Use visible signage, lighting, and staffed posts to guide crowds, while monitoring density and behavior via CCTV, patrols, and real‑time reporting to the ICS chain of command.
Ingress/egress control checklist
- Mark primary and secondary evacuation routes, assembly areas, and shelter‑in‑place options on maps.
- Assign LE and venue security posts at gates, VIP entrances, and critical intersections, with clear post orders.
- Coordinate road closures, detours, and transit changes with transportation agencies and public works.
- Pre‑plan emergency vehicle routes, staging areas, and corridor protection with fire/EMS and hospitals.
Access Control and Credentialing
FEMA and law enforcement guidance emphasize strong perimeter control, screening, and credentialing for major special events.
- Establish layered perimeters (outer, middle, inner) with specific access rules, screening requirements, and staffing for each layer.
- Implement credentialing for staff, contractors, VIPs, media, and responders, and enforce no‑credential, no‑entry rules for restricted zones such as command posts and critical infrastructure.
Access management actions
- Screen bags and persons for prohibited items using magnetometers, wands, and trained personnel.
- Document access control procedures in the IAP and post orders, including escalation steps for suspicious persons and denied entry.
Medical, Fire, and Public Health Integration
Major event security guidance highlights fire, EMS, hospitals, and public health as critical partners in event planning and operations.
- Build a medical plan that covers first aid stations, EMS deployment, triage areas, ambulance staging, and hospital coordination for potential mass casualty incidents.
- Integrate fire protection, hazmat/WMD response, and inspection requirements, ensuring access to hydrants, utilities, and critical systems needed during an incident.
Communications, JIS, and Documentation
Communications (Interoperability + JIS)
NIMS notes that interoperability and coordinated public information are core components of incident management and planned events.
- Create a communications plan that lists all radio channels, talk groups, call signs, cell and data backup options, and how different agencies will interoperate during routine and emergency operations.
- Use a Joint Information System, potentially including a Joint Information Center, to coordinate public messaging, manage rumors, and support consistent safety information across agencies.
What to document in your comms plan
- Radio/channel plan with primary and backup options for each section and agency.
- Call‑out and notification procedures for command staff, EOC activation, mutual aid, and JIS.
- Pre‑approved message templates for evacuations, shelter‑in‑place, weather delays, security incidents, and event changes.
Core Documentation (IAP and Annexes)
Incident Action Planning guidance from FEMA describes a cyclical process that produces a written or digital IAP for each operational period, including planned events.
- Capture incident objectives, ICS organization, operational assignments, safety information, maps, and communications in a concise IAP for the special event, even if you adapt it as an “IAP‑lite” for a single period.
- Attach contingency annexes for severe weather, mass casualty, hazmat/WMD, active assailant, utility failure, and evacuation scenarios.
What to document
- Incident objectives and operational priorities for the planned event.
- ICS org chart with assigned names, agencies, and contact information.
- Communications plan (radio, cellular, dispatch, EOC, JIS).
- Medical plan (aid stations, EMS, hospitals, medevac).
- Site maps with ingress/egress, perimeters, staging, ICP/EOC, and shelters.
- Staffing plan and post orders for law enforcement, fire/EMS, security, and volunteers.
- Mutual aid agreements and resource inventories relevant to the event.
- Contingency annexes for weather, crowd emergencies, hazmat/WMD, and critical infrastructure failures.
Training, Exercises, and Post‑Event Improvement
Training and Exercises
FEMA special event manuals and NIMS guidance stress training and exercising plans before the event to validate roles, communications, and procedures.
- Conduct tabletop exercises and brief functional drills that walk through high‑risk scenarios such as crowd surges, severe weather evacuations, active assailants, or hazmat incidents.
- Provide just‑in‑time training briefs for all personnel on ICS roles, communications procedures, evacuation routes, and safety expectations before operations begin.
After‑Action Review (AAR) and Lessons Learned
Special events guidance recommends documenting what worked and what must change using structured After‑Action Reviews and improvement plans.
- Schedule a formal AAR with representatives from all major agencies within a defined period after the event to review objectives, performance, and major incidents.
- Capture strengths, areas for improvement, corrective actions, and responsible owners, then integrate changes into future special event plans and training calendars.
FAQs for Public Safety Professionals
How do public safety agencies use ICS for planned events?
Public safety agencies use ICS to organize command, operations, planning, logistics, and finance/administration for planned events, assigning section chiefs and functional units just as they would for incidents. ICS or Unified Command ensures that law enforcement, fire, EMS, and emergency management coordinate objectives, resources, and communications under a shared structure during the event.
What should be in a special event contingency plan?
A special event contingency plan should include hazard‑specific annexes for severe weather, crowd emergencies, medical surge, hazmat/WMD, active assailant, infrastructure failure, and evacuation or shelter‑in‑place, all tied back to the main security plan and ICS structure. It should define triggers, roles, communications steps, resource needs, and coordination with EOCs, hospitals, and mutual aid partners for each scenario.
Who is on the multi‑agency planning team for a mass gathering?
The planning team typically includes law enforcement, fire, EMS, emergency management, public health, transportation, public works, utilities, venue management, and private security, with additional partners such as hospitals and transit agencies for larger, major special events. These stakeholders meet before the event to complete risk assessments, build the pre‑event planning matrix, assign responsibilities, and align on ICS and communications structures.
Check other blogs:
Professional Security Systems: Top Home Security Options for 2024
Business Security Services: Secure Your Success
Essential Reasons Why Your Business Needs Security Guards
7 Serious Legal Consequences If You Hit a Security Guard in 2026
