THE FIVE THINGS THAT BREAK A RODEO OPERATION
I've seen events almost come apart from each of these. Some didn't almost — they did. Here's what actually goes wrong, and it's almost never what the committee was worried about.
Every committee I talk to has a list of things they're anxious about. Crowd fights, weather, animal incidents, medical emergencies. Those things happen. They need to be planned for. But in my experience, the events that struggle don't usually fall apart because of the dramatic stuff. They fall apart because of five structural problems that were invisible until they weren't.
One: The plan lived in one person's head. Somebody knew exactly how this event ran. They'd done it for years and carried the whole operational model in their memory. Then they got sick, or overwhelmed, or unavailable at exactly the wrong moment, and everyone else was flying blind. Written SOPs exist for this reason. Not because bureaucracy is good, but because knowledge that's only in a head is knowledge the organization can lose.
Two: Gate operations were treated as an afterthought. Nothing creates a bad first impression faster — and a longer-lasting operations headache — than gates that don't work. Backups, confused credential flows, the wrong person making access calls on the fly. Gate operations are the first thing your audience experiences. Treat them like it.
"The problems that actually break events are boring. No committee ever goes home saying they failed because of the radio protocol. But I've been at events where the radio protocol was the whole reason things went sideways."
Three: The radio protocol was improvised. If your security and operations staff doesn't have a clear, practiced communication structure before the event starts, you will have coordination failures when something goes wrong. Not might. Will. Radios aren't magic — they just amplify whatever communication culture you already have. Make that culture deliberate.
Four: Nobody owned incident documentation. Something happened. It got handled. Nobody wrote it down. The next event ran the same way and the same thing happened again. Post-event documentation isn't paperwork for its own sake — it's how an organization gets better. Every incident that doesn't get captured is an opportunity to learn that you declined.
Five: The pre-event site walk didn't include the hard questions. Every venue has a history. Things that happened there before, access points that look good on paper and don't work in practice, relationships between spaces that create flow problems under load. The site walk that finds these things is the one where you're asking "what went wrong here before?" — not the one where you're just confirming the layout matches the diagram.
None of these are dramatic. None of them make for good stories. But in my experience, these five things — or some combination of them — are behind most of the events that don't go clean. Fix these, and most of what committees worry about either doesn't happen or gets handled when it does.
Chapter 10 — When Things Go Wrong: The Five Incident Protocols goes further: the five situations most likely to happen at any rodeo, who acts first, and what the protocol has to say before the night starts. The Invisible Operation →