THE VOLUNTEER
VARIABLE
Most rodeos don't run on paid staff. They run on volunteers — people who show up year after year because they love the event, know the committee, or were asked by someone they trust. This isn't a problem. It is, however, a fact that shapes every decision you make about how an event operates, whether you acknowledge it or not.
The benefits are real and worth naming. Volunteers carry institutional knowledge in a way no hired crew ever will. The person who's worked the contestant entry gate for twelve years knows things about that chute, that crowd, and that schedule that aren't written down anywhere and couldn't be hired at any price. Long-term volunteers are often more reliable than seasonal contractors, more invested in the outcome, and more willing to problem-solve when the plan stops being the plan. They know the venue. They know the people. In many ways, they're your best operational asset.
But the problems compound in ways that are easy to miss until something goes wrong.
"The biggest risk in a volunteer-staffed operation isn't that people won't show up. It's that the people who do show up won't know what to do when the situation changes."
Training is the first issue. A paid crew can be briefed and drilled in advance as part of their contract. A volunteer corps is often briefed once, briefly, on the day of the event — if at all. That means your security posture, your communication protocols, and your incident response depend on people who may be excellent at their usual post but have never done a real scenario walkthrough. When something happens, they default to instinct and improvisation. Sometimes that's right. Sometimes it isn't.
Accountability is the second issue. Not because volunteers are irresponsible — most aren't — but because the structures of employment don't apply. You can't reassign someone who has worked the same gate for a decade, even when that assignment isn't working anymore. The social dynamics of a volunteer organization make the hard operational conversations harder to have, and they often don't get had at all.
The third issue is year-over-year consistency. Volunteers cycle in and out. The person who ran a critical post last year may not be available this year. When institutional knowledge walks out the door, it usually doesn't leave a forwarding address.
None of this means volunteers are a liability. It means your written systems have to carry more weight than they would in a professional crew environment. SOPs aren't bureaucracy. They're what makes a volunteer operation reproducible. Clear radio protocols, written gate sequences, printed incident escalation guides — these aren't for the volunteers who've been doing this for twenty years. They're for everyone else, and for the year when the twenty-year veteran can't make it.
The events that run clean on volunteer labor aren't the ones with the most experienced committees. They're the ones that have done the work of capturing what they know and building systems that don't depend on any one person to hold them together.
Chapter 14 — Build From Within goes further: how to turn the volunteers you already have into an operations crew, and the four written tools that make a volunteer operation reproducible. The Invisible Operation →