The five incidents most likely to happen at a rodeo, and the sixth one most plans forget
Medical emergency, animal in a public area, crowd disturbance, weather, and an arena disruption — most often an unauthorized person on the floor. Then the sixth one that belongs in every plan and is in almost none of them: a parent who can't find their kid. Each has a first responder, an escalation point, and a decision that must be written and briefed before the event.
8:22 PM, middle of the short go. "Medical, Section C, Row 14. Man down."
The post staff member was new. He did the right thing: radioed immediately, stayed on scene, cleared a radius. The supervisor was already moving. The Director was already clearing the access route. EMS was already rolling. The patron — a man in his late sixties, cardiac — was receiving care inside four minutes. He survived.
What made the difference wasn't heroism. It was a written protocol every person in the operation had heard that morning. The first ten seconds were already decided. Nobody froze.
Why five, and why written
Most events run clean. Minor situations handled quietly, the crowd goes home, the stock loads out. But the incidents that do occur escalate fast. An untrained medical response can cost a life. A poorly managed loose animal can injure a patron and end a committee's ability to sanction events. A disturbance handled wrong is a social media story before the night is over.
Panic is the product of no plan. The protocol exists so the first ten seconds of any incident are decided before the pressure, before the radio call, before anyone is standing in front of a real problem with the next few seconds deciding the outcome.
The five, and who moves first
Medical. Post staff secures the scene and radios the supervisor — location, what they see. Nobody moves the patient, nobody attempts treatment. The supervisor calls EMS on every medical situation without evaluating it first, and alerts the Director at the same time. The Director clears the access route and puts someone at the venue entry to walk EMS in. EMS owns the scene the moment they arrive. And the words matter: "please give them some space" is right; "medical emergency" over the PA is not.
Animal in a public area. The instinct that gets people hurt: moving toward the animal to help. Don't. The stock contractor handles the animal. Your job is the space around it — maximum space, immediately, people moved away in every direction, the contractor's response path kept clear. I've watched two staff members step toward a bull that cleared the chute gate and add thirty seconds to containment by cutting across the contractor's path. In those thirty seconds three patrons moved toward the animal instead of away. Nobody was hurt. The protocol was rewritten that week.
Crowd disturbance. The disturbance itself is rarely the hard part. The three thousand people watching it are. Treat the surrounding section as part of the incident, don't let one supervisor be the only escalation point when two things happen at once, and correct the rumor before it outruns the response. Silence reads as something worse than what happened.
Weather. The only one with advance warning and the one most often improvised. Public alerts are a last warning, not an early one. Monitoring starts hours before the event. Who calls shelter-in-place, at what threshold, with what PA script — decided before, not during. I've seen the Director learn about a tornado warning from a patron's phone. The response window was already gone.
Arena disruption. Unauthorized floor access is the most time-critical of the five. Anyone who sees it calls it; the Director routes it. The announcer gets one instruction: fill or hold, because dead air tells three thousand people something is wrong. The stock contractor is told immediately, not after. The stop decision is a judgment call with a written threshold: any threat of injury to anyone, including the livestock, is a full stop.
The sixth one, and the one most plans forget
Five protocols cover the incidents that make an operations plan look necessary. Here's the one that happens more often than any of them and appears in almost nobody's plan: a parent can't find their kid.
A rodeo is a family event. Kids move through it the way kids move through everything — fast, low, and in the opposite direction from where they were last seen. Most of these resolve in under ten minutes. The protocol exists for the version that doesn't, and for the fact that a panicking parent doesn't know which version they're in. Neither do you.
Two things happen the moment it's reported. A staff member stays with the parent, because a parent sprinting through a crowd creates a second incident and can't be found when the child is. And the description goes out on the radio — age, height, clothing, last location. Clothing is the item that finds kids. Nobody in a crowd can judge age at a distance. Everybody can spot a red shirt.
Gates go on notice. Every exit and the lot posts get the description. Not a lockdown — a set of eyes at every point a small person could leave through. At most venues that's three or four posts, which is exactly why the post plan has names at those positions all night.
A found child goes to one fixed point and stays there. Decided in the planning room, briefed to everyone — the announcer stand, the medical station, wherever is staffed continuously and easy to describe. The child does not get walked around the venue while someone looks for the parent. Movement is how a found child becomes lost twice. Two staff members with the child, never one. That rule protects the child and it protects your people, and it is not optional.
Law enforcement comes in early, not late. If the posts and the lot are covered and the child isn't found within minutes, or if anything about the situation reads wrong, the call gets made while the search is still ahead of the problem. That call is free. Making it late is not.
Nobody writes this protocol because the incident almost always ends fine. Write it anyway. The night it doesn't end fine, this is the only page of the plan anyone will remember your event by.
What every protocol ends with
Documentation. Time, location, description, response timeline, unit numbers. Before the end of the night, not the end of the week. It's legal protection and it's next year's plan. If the same corner of your venue produces the same wandering kids every year, that's a venue fact, and next year's plan should know it.
“Nobody writes the lost child protocol because it almost always ends fine. Write it anyway. The night it doesn't, it's the only page of the plan anyone will remember your event by.”
Chapter 10 — When Things Go Wrong: The Five Incident Protocols is the step-by-step version of all five plus the lost child protocol in full, with the case studies of the ones that went right and the ones that didn't. Appendix C is the incident report form; the lost child line is on the written plan template in Appendix G.
Get the BookFree Templates