Hotels, resorts, arenas, festivals, and attractions share two problems: those affected are guests, not employees, and video is public before you have a headcount.
A drowning, a balcony fall, an outbreak, or a security event leaves a property caring for a family flown in to collect somebody, while guest privacy, authorities, insurers, and the story on property land on a general manager who has never done this.
What changes in a hotel: family reception on property, guest and staff support, authority and consular coordination, and communications that keep the property out of the story.
A venue knows its footprint and staff, but not who was in the building. Reunification is the whole problem: parents at a cordon, people split by an evacuation, a hospital list that matches nothing.
What changes in a venue: a reunification center, a public information line from hour one, staff and contractor support, and coordination with security and local responders.
A festival is a city built in a week by people who mostly met that week; crowd, weather, and medical risks scale with attendance, and the team is exhausted before anything goes wrong.
What changes at a festival: response that spares show staff, family lines and reunification, support for young attendees and distant parents, and vendors and contractors accounted for.
At attractions most incidents are individual: a medical event, a ride incident, a drowning. Each is a family and a public story, and the season’s pattern matters as much as any one event.
What changes at an attraction: a scaled single-incident family response; support for guests, families, and staff who saw it; consistent handling across many events.
Nothing else we work moves this fast. Assume video is public in minutes, before anyone calls the families.