A speaker at a 600-person conference in Chicago collapsed onstage during his keynote. The room went quiet. The event staff's training kicked in: the session co-host identified herself as the emergency lead, the AV team cut the livestream, the closest staff member called 911 with the pre-saved venue address, and a pre-designated runner escorted paramedics from the loading dock directly to the stage. The speaker was stable within 8 minutes. The whole thing, from collapse to ambulance departure, took 22 minutes. A comparable incident at an event without this plan took 47 minutes and multiple wrong-turn trips through the building. The difference is not luck. The difference is written-down procedures rehearsed before the doors open.
Every event of 200+ attendees needs emergency procedures written down. They do not need to be elaborate. They need to exist, be briefed, and name specific people. This guide covers the four categories of emergency every conference should plan for — medical, fire, security, and weather — plus the one document every event needs: the day-of risk register.
1. Medical emergencies
Medical events are the most common emergency at conferences. The planning is proportional to event size.
Events of 200-500 attendees:
- Trained first-aid responder on event staff (CPR + AED certified).
- AED location identified and signed, ideally in the main room.
- Printed list of nearest 3 hospitals with addresses, phone numbers, and ambulance dispatch number.
- Named medical contact at the venue (facilities team lead).
Events of 500-2,000 attendees:
- On-site event medic (EMT or paramedic) for the duration.
- Designated quiet room usable for medical isolation (private door, accessible from corridor).
- AED at each venue floor.
- Medical lead in visible vest; radio link to event ops.
Events of 2,000+ attendees:
- On-site medical team (2-3 medics minimum).
- Mobile ambulance on standby for very large events or events with high-risk profiles (outdoor physical events, events with elderly or immunocompromised populations).
- Formal MOU with nearest hospital for rapid intake.
Standard medical kit per 500 attendees: adult AED, basic first aid, EpiPens (×2), naloxone, glucose gel, mylar blankets. Pre-brief the medical location to all staff. Tape a business card with emergency contact numbers behind every badge pocket.
2. Fire and evacuation
Fire evacuations at conferences rarely involve actual fire — they usually involve a pulled alarm, a kitchen incident, or a false alarm test. Plan for the procedure, not the rarity.
- Pre-brief all event staff on evacuation routes the morning of each event day. Every staffer should know the primary and secondary exit routes from every room they work in.
- Evacuation route signage matches the venue's emergency signage, not your event branding. Organizers sometimes mask venue exits with sponsor banners — don't.
- Assembly point identified in writing and shared with all staff. Typically a designated sidewalk area or parking lot 100+ meters from the venue.
- Accountability mechanism. Registration check-in system exports an "on-premises right now" list. In evacuation, the registration team has this list at the assembly point.
- Accessibility evacuation plan. Wheelchair users, mobility-limited attendees, and those needing assistance have a pre-identified "buddy" among staff and a safe refuge area if elevators are down. Brief this explicitly.
- Speaker handling mid-session. Practiced transition: "Hold tight everyone, we're making a quick safety check — please exit via the door on your left with [staffer name] and [staffer name]."
Fire drills at conferences are rare but worth running if you're the anchor tenant of a venue. A 5-minute tabletop exercise with the ops team covers 90% of the value.
3. Security incidents
Security covers a wide range — a disruptive attendee, a protest group entering the venue, a bomb threat, an active shooter. Each needs a different response.
- Venue security contact named and reachable by radio during the event. Not "call the venue front desk."
- Lockdown procedure for active security threats. Each room has a staffer briefed on how to lock doors from inside, when applicable.
- Suspicious-behavior reporting protocol. Staff escalate concerns to a named security lead, not to general ops.
- Credential/badge checks at entrances. Not airport-grade, but enough that non-attendees are visibly filtered.
- Spokesperson designated to handle media or attendee questions if an incident occurs.
- Communication tree. If an incident triggers a lockdown or evacuation, how does the organizer communicate with the 600 people in the building? A named lead, an SMS broadcast list, and the event app should all be primed.
For events with known security sensitivity (political topics, high-profile speakers, protest targets), consult with a private security firm 30 days out. Cost: $800-2,500/day for 1-2 trained officers. Cheap insurance.
4. Weather and venue emergencies
Weather kills events that over-rely on outdoor space or on attendees showing up despite travel disruption.
- Indoor backup for outdoor events. A signed contract with a covered alternative, not "we'll figure it out." Tent rental at 48-hour notice can cost $20-50K.
- Transportation contingency. For events in regions with weather-sensitive transport (DC in snow, Bay Area fog, any region with monsoon/hurricane seasons), identify transport alternatives in advance.
- Attendee SMS broadcast list built from registration, tested before event. "Event proceeding as planned" or "Day 2 delayed to 11am" in 20 minutes, not 2 hours.
- Hotel partnership for stranded attendees. If a weather event strands attendees overnight, a pre-negotiated hotel block rate helps more than a "sorry about the weather" email.
- Published weather-cancellation policy. What triggers a delay or reschedule? Who decides? What is the refund/transfer terms? Published in advance, not improvised.
Venue emergencies (power outage, HVAC failure, water damage) are less weather-driven. A named venue facilities contact with direct phone number and a backup venue option for hard failures cover most cases.
5. The day-of risk register
The document that ties this all together is a one-page risk register, reviewed by the ops team the morning of each day.
| Risk | Trigger | Owner | Action | |---|---|---|---| | Keynote speaker no-show | 30 min before start | Program lead | Activate backup from named list | | Main-stage AV failure | During session | AV lead | Switch to backup rig; communicate | | Medical emergency | Any time | Medic + ops lead | Medic responds; ops clears area | | Fire alarm | Any time | Venue lead + ops lead | Evacuate per venue procedure | | Severe weather | T-24h to T-0 | Event director | Trigger SMS broadcast; decision tree | | Security incident | Any time | Security lead + ops lead | Per incident-specific procedure |
The register fits on one page. Every ops team member has a copy. The morning stand-up walks through it in 5 minutes. Most of the time nothing on the register will happen. When something does, you have 20 seconds to act, not 20 minutes to plan.
Emergency planning checklist
- [ ] Named medical lead on staff (certified for event size)
- [ ] AED location identified, signed, and tested
- [ ] Evacuation routes briefed to all staff morning of
- [ ] Assembly point identified and shared
- [ ] Accessible evacuation plan documented
- [ ] Venue security contact named and reachable
- [ ] Indoor backup for any outdoor programming
- [ ] SMS broadcast list tested
- [ ] One-page risk register printed and circulated
- [ ] Morning stand-up includes 5-minute risk walkthrough
- [ ] Post-incident review scheduled in calendar (even if unused)
Modern event management software handles the SMS broadcast and attendee-count export; the human procedures still need to live on paper.
FAQ
Do I really need this for a small event? For 200+ attendees, yes. For under 200, at minimum: a first-aid kit, AED location identified, nearest hospital phone number written down, and a named ops lead. The difference between 200 and 2,000 is scale of response, not existence of a plan.
Who owns emergency planning — the venue or the event? Both. The venue has structural procedures (fire alarms, building evacuation); the event has attendee-specific procedures (accountability, communication, medical on staff). Neither can substitute for the other.
What about mental health emergencies? Under the medical category. A panic attack or mental health crisis is a medical event. Quiet room access, medical staff training, and a named "attendee welfare" contact cover most cases.
How do I rehearse without alarming attendees? Tabletop exercise before the event. 45-minute meeting with key staff walking through each scenario. No need to drill during the event itself.
Who should carry the emergency contact list? Every ops team member. Laminated card clipped to the lanyard. Plus a pinned message in the internal Slack/comms channel for the event.
Related guides
Ready to run your next event? Create your event on WebMobi →