What a written rodeo operations plan has to contain (and what happens without one)

6:47 PM, Thursday. The event is Saturday. The man who has run security for this committee for seven years — who knows where every post goes, which gate backs up first, which contractor always shows up late — is in a hospital two states away. His wife answers the chair's call. She doesn't know where the plan is. She isn't sure there is one.

"He just knows how it works," she says.

That isn't a dramatic failure. Nobody died. But it is the most common catastrophic failure in rodeo operations, and the one least likely to be recognized as catastrophic until it's thirty-six hours out.

Five things you need before you write a line

You can't build a plan from nothing, and you can't build one from incomplete inputs. The plan you write without one of these will have a gap shaped exactly like the thing that's missing.

The actual floor plan. From arena management, not from memory. If the venue doesn't have one, make one on the site walk.

Expected attendance. The ticket count or the best projection you have, not a guess. Staffing ratios, gate configuration, and where the floater goes all depend on this number.

Sanctioning body requirements. What PRCA, GCPRA, PBR, or whoever sanctions you mandates for credentials, floor access, and media. These aren't suggestions.

Confirmed staffing. The headcount you have, not the one you wish you had. Plans built on people who aren't confirmed create gaps on event night.

The full schedule including load-in and load-out. The plan starts when the first contractor arrives, not when the gates open.

What goes in, and what stays out

In: the staffing structure by name and role. Post assignments by location and coverage area. The credential tiers. The radio protocol with channels and callsigns. Protocols for the five situations most likely to happen. Escalation paths. The event timeline from load-in to load-out.

Out: aspirations, generalizations, anything that can't be executed. "We will maintain a strong security presence throughout the venue" is not a plan. It's a wish. "Zone B supervisor walks the Section 4 and 5 concourse every fifteen minutes from gate open to end of performance" is a plan.

The test for any line: can the person responsible for it tell you exactly what they're supposed to do, when, and why? If not, rewrite it until they can.

Committees write general plans because general plans feel thorough — they cover every scenario in principle without committing to a single action. Specific plans feel exposed, because when you name exactly what you'll do you can be wrong. Write the specific plan. Be wrong where you're wrong. Fix it at the debrief.

What the plan can't find on its own

The site walk finds what the floor plan hides. Where does the livestock path cross a walkway? Where will the line compress at intermission? Can a stretcher reach every section when the whole building is on its feet for the short go? Walk the medical route at capacity in your head, not at empty. Every venue has a spot people gather that nobody designed for gathering. The walk finds it before the crowd makes it your problem.

A plan built over six to eight weeks is a different thing from a plan built the week before. One has been questioned, refined, and confirmed. The other is one person's thinking under time pressure. And a plan that lives only in one person's head isn't a plan. It's a prayer with a good track record.