CHECKLIST TEMPLATE
Step-by-step incident response for injuries, medical emergencies, lost children, and evacuations at ticketed attractions.
Most attraction and venue operators treat the Attraction Incident Response Protocol as a box-ticking exercise — and the ones who do are the ones who pay for it the hardest later. Fast, professional incident response saves lives and reputations. Fumbled response produces lawsuits and closures. The purpose of a disciplined checklist isn't to slow your team down; it's to make those failure modes impossible by building the catch into the workflow itself.
The good news is that this checklist runs in roughly 30 minutes once your team is used to it. Of the 10 total steps, 5 are marked critical — these cannot be skipped, rushed, or signed off from across the room. The work itself is designed to be handed off to any staff member who's had a proper induction, which means the savings scale as the habit settles — early runs are slower as staff learn to spot what they're looking for, and steady-state runs are faster than the time spent chasing the same problem in customer complaints after the fact.
This Attraction Incident Response Protocol is written for seasonal attractions, year-round museums and venues, experience centres, aerial parks, and ticketed venues of all sizes. The steps are calibrated to the realities of small-team operations (one person may be running it between customer interactions) and stay useful as you scale — the same checklist works for a busy Saturday in peak season as it does for a quiet Tuesday in April.
Treat the version below as the starting point, not the destination. As you run the Attraction Incident Response Protocol for a full season, you'll notice patterns specific to your operation — a particular model of equipment that fails earlier than the rest, a step that surfaces a recurring issue nobody's fixing upstream, a time-of-day when completions get rushed. Capturing those observations and feeding them back into the checklist is what turns a generic template into a genuine operational asset. That is exactly the kind of living, team-shared, auto-logged document EquipDash is built to host — so the checklist doesn't just live on someone's clipboard, it becomes part of the shop's compounding institutional memory.
Work through each step on every application. Critical steps must pass before the item leaves the shop.
First staff on scene: secure area, prevent further harm, call for backup.
Life-threatening: call ambulance/police immediately. Do not wait for manager.
Radio the duty manager. They take incident command.
Trained first-aider administers aid. No one else moves the casualty.
Assign staff to gently move crowds back. Protect guest dignity.
Photos before anything is moved. Written statements from witnesses. Names and contact details.
If casualty is a minor, notify guardian immediately. If adult, ask preference.
Duty manager decides if affected zone closes. Continue elsewhere if safe.
All involved staff debrief within 24 hours. Lessons captured.
Serious incidents reported per policy. File within required timeframe.
Build this into your regular operational rotation. In a small shop, the opener runs this as part of morning prep. In larger shops, dedicate a technician or staffer to the task during the opening hour. If you run EquipDash, attach the checklist to the relevant asset or booking so completions log automatically and build a maintenance history.
Train all staff quarterly. Run tabletop exercises. Have this checklist accessible at every staff station.
Incidents will happen. Preparation is the only defence. Practice, document, report, debrief — and your attraction emerges stronger after every event.
FREQUENTLY ASKED QUESTIONS
Duty manager. If they're incapacitated, the next most-senior staff member until relieved.
EquipDash turns checklist templates into repeatable workflows — assigned to equipment, completed by staff, logged for compliance. Start your free 21-day trial and import this checklist in seconds.
