BROKEN M RANCH

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.

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.

People ask me what a well-run rodeo security operation looks like. My honest answer is: you don't see it. The crowd moves cleanly. The gates open on time. Nobody's fighting to get in, nobody's wandering where they shouldn't be, and when something does go sideways — and something always does — it gets handled quietly, quickly, and without the moment bleeding into the main event.

That's the job. Invisible when it's working. Obvious when it's not.

The hardest thing to explain to a committee that's never had a professional operations team is that the absence of incident isn't luck. It's architecture. Every post assignment, every radio protocol, every decision about credential flow and gate sequence — all of it adds up to either a night that runs clean or a night that doesn't. And most of the time, the difference was made weeks before the first truck rolled through the gate.

"The plan doesn't survive contact with the arena unchanged. But the team that built it right can adapt. The team that winged it can't."

Here's what I've seen trip up even experienced committees: they treat security as a day-of concern. Hire some bodies, put them at the gates, and hope for the best. The problem is that by the time you're standing in the arena, you've already lost the ability to fix most of what's going to go wrong. The staffing holes are baked in. The communication gaps are baked in. The decision tree no one wrote down is now living entirely in one person's head — and if that person gets pulled in three directions at once (and they will), you have a problem.

Good operations work starts with a site walk and a hard conversation about what's actually happened at this venue before. Not what should have happened — what did. Then you build from there. Staff to the gaps, not to what looks good on paper. Write the protocols for the scenarios that scare you, not the ones that feel comfortable. And brief your people — really brief them — so that when something happens, they're not looking for permission. They're already moving.

That's what we build at Broken M Ranch. Not just a plan, but a team that can execute it without hand-holding. That's the invisible operation. And that's what your event deserves.

From the time I was old enough to follow my family through the gates, the American Royal was part of how I understood what a big event was supposed to look like. Kansas City in the fall. The livestock barns and the particular way sound moved differently in a crowd of thousands versus a crowd of hundreds. I wasn't thinking about operations then. I was thinking about the horses.

But something gets into you when you grow up at events like that. You absorb things you don't have words for yet — the way a gate backup feels before it turns into a problem, the look of a crowd that's moving right versus one that's about to bunch up. You learn where the bottlenecks are because you've stood in them. You learn what good looks like from the receiving end, which is the only end that actually matters.

When I eventually came to do this work professionally, the American Royal was always the reference point. Not because I had run it, but because I had experienced it — across a whole childhood. I knew how a well-run entry felt. I knew the difference between a site designed for the people moving through it and one designed for the people managing it. I knew what it felt like when the operation became invisible — which is the highest compliment you can pay any event.

"What I actually learned at the American Royal didn't come from a credential or a debrief. It came from being in the crowd, year after year, watching what worked and what didn't — and eventually understanding why."

The committees who run events like that have earned something: an institutional memory that lives in people, not paperwork. They know which gate sequence works for their crowd because they've tried three others. They know which contractor to call first because of something that happened six years ago that never made it into any debrief document. That knowledge is irreplaceable, and the best thing an outside consultant can do is find it, respect it, and build around it — not arrive with a plan that ignores it.

My job isn't to replace what's already working. It's to find the plan that's already working, understand why it works, and make sure there's a written version of it for the year when the person carrying it in their head isn't available.

The American Royal taught me that before I knew it was teaching me anything.

There's no shortage of Western apparel in this country. Walk into any feed store, any boot shop, any airport in the Southern half of the United States and you'll find hats, tees, and hoodies with a rope font and a longhorn on them. Most of it is fine. Some of it is good. Almost none of it has anything behind it.

That was the thing I kept coming back to when we started talking about putting a brand on clothing. We had to earn the right to put the iron on it. Not because the market demanded it — the market will buy anything with the right aesthetic — but because the people we're building for can tell the difference. They know when something is a costume and when something is the real article.

The Broken M iron comes from years in the arena. From events where the work was hard, the nights were long, and the reward was knowing the operation went right. It comes from a Western life that wasn't chosen as a brand strategy — it just is what it is. When we put that mark on a tee or a cap, we're not inventing credibility. We're extending something that already exists.

"A brand built backwards from a logo is a product. A brand built forward from a life is something people actually want to carry."

That shapes everything about how we approach the apparel side of this. We keep the line small because small means we can stand behind every piece. Heavyweight cotton, not the cheap stuff. Embroidery that holds up after a hundred washes. Colorways that look like they belong to the landscape, not to a shelf at the mall. And no chasing trends — because the people we're building for aren't trend followers. They're the people the trends are trying to imitate.

If you pick up something with the Broken M iron on it, I want you to still be wearing it five years from now. Not because it held together (though it will), but because it still means something. That's the standard we're holding ourselves to. Anything less isn't worth putting our name on.

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.

There's a version of this job that ends when the last contestant clears the gate. The crowd is gone, the lights are still up, and the dirt in the arena still has the shape of the night in it — the skid marks, the hoof prints, the scuff where somebody hit the fence and it held. Most people don't see an arena like that. Most people see it when it's loud and bright and full. I see it on both ends.

I've stood in empty arenas at midnight more times than I can count. After a long event, when the debrief is done and most of the crew has loaded out, there's usually a few minutes where it's just you and the space. The stands dark, the lights humming, the sound of someone running through their checklist somewhere off to the left. There's no version of my life where I don't love that moment.

It's the moment where you know how the night went. Not from reports or debrief notes — you know from how you feel standing there. Good nights feel clean. The kind of tired where you're already thinking about the next one. Bad nights feel different. Not always dramatically different — most of the time things that go wrong in operations go wrong quietly, and only you and your team know how close something was. But you know.

"The arena doesn't care how tired you are. It just asks whether the job got done."

That's the thing the Western life teaches you that's hard to put into words until you've lived it: accountability without an audience. The cattle don't know you're having a bad day. The arena doesn't care how tired you are. The job has requirements, and those requirements exist whether or not you feel up to meeting them. Meeting them anyway — that's the whole thing. That's what the brand is built on.

I started Broken M Ranch because the arena at midnight is one of the best classrooms I've ever been in. Everything we offer — the consulting, the gear, the operational resources — comes from what that classroom taught me. Hard work, family, sacrifice. Not as a slogan. As a set of instructions for how to do the job right.

When you're building a Western brand and you have a product development background, the temptation to expand the line is constant. Every conversation surfaces something that "would do well." A different colorway here. A canvas jacket there. Trucker hats, work shirts, keychains, coffee mugs — the catalog wants to grow the way weeds want to grow. You have to actually decide not to let it.

We decided not to let it. And it wasn't a close call.

The gear line at Broken M Ranch is small because small is the only way to stand behind everything in it. Every piece we put the iron on is a piece I can personally account for — the weight of the fabric, the hold of the embroidery, the way it fits after twenty washes. When the line is small enough that I know every piece that well, I know what we're selling. When the line gets big enough that I'm guessing, we've stopped selling gear and started selling a catalog. That's a different business, and it's not the one I want to run.

"A big catalog says: we think something in here will work for you. A small, intentional line says: we know this works. We're staking our name on it. That's a different promise — and a harder one to keep."

There's also an honesty argument. The Western apparel market is enormous, and most of it is fine — competently made, reasonably priced, perfectly serviceable. There's nothing wrong with it, but it's not what Broken M Ranch is for. We're for the person who already has a closet full of fine, and wants one or two things that are actually right. That person doesn't need forty options. They need a handful of things built with intention, by people who can explain every choice that went into them.

So we keep the line tight. Six pieces to start. Each one named for something real. Each one made to earn its place in a rotation for years, not a season. If it doesn't belong at that standard, it doesn't go in the line — no matter how well someone tells us it would sell.

If you pick up something with the Broken M iron on it, I want you still wearing it in five years. Not because it held together — though it will — but because it still means something. That's the only standard we're holding ourselves to. Anything less isn't worth putting our name on.