Rodeo Event Operations PlaybookModule 07 of 07
The event is over. Most operations stop here. The ones that keep improving don't. This final module covers the post-event debrief, what to document and why, how to build institutional knowledge your committee keeps long-term, and how to use every event to make the next one better.
Every rodeo committee and event promoter who does this long enough has the same experience: you run the same event three years in a row, make the same mistakes each time, and wonder why nothing gets better. The answer is almost always that nothing was written down. The lessons from Year One were in someone's head, and they left — or they forgot — or they were too busy running Year Two to remember what Year One actually taught them.
The debrief and documentation process in this module is the difference between an operation that improves and one that just repeats itself. It does not require a lot of time. It requires discipline — specifically, the discipline to do it before the exhaustion of event day convinces you to skip it.
"The debrief is not a postmortem. It is a deposit into the institutional memory of your operation — one that pays out at every future event."
Run your debrief within 48 hours of the event — not two weeks later when the details have faded and the energy has dissipated. The debrief does not need to be long. It needs to be honest and structured.
Attendance: Event Director, all Zone Supervisors, and the operations coordinator. Optional: stock contractor liaison, committee representative. Keep it to the people who were running the operation — not everyone who was present.
The debrief gets harder to run as the operation gets more experienced — because experienced teams tend to normalize problems. "That's just how it goes" is the enemy of improvement. Create a debrief culture where nothing is too small to name and every problem has a potential fix. The best operations are run by people who are never fully satisfied with how the last one went.
The After-Action Report (AAR) is a written summary of the debrief — the document that preserves everything discussed in a format that can be referenced, shared, and built upon. It is written by the Event Director within 72 hours of the event.
It does not need to be long. It needs to be complete and honest. A two-page AAR that captures what actually happened is more valuable than a ten-page document that presents the event in the best possible light.
Event name, date, venue, attendance, sanctioning body, staffing count. One paragraph. The facts of the event on record.
Every documented incident from the event, in chronological order. Time, location, description, response, outcome. This is your legal protection and your operational history.
Specific elements of the plan that performed well. Staff members who performed above expectation (named). Protocols that held. Things to replicate at the next event.
Specific failures with specific fixes assigned to specific people with deadlines. Not generalizations — actionable changes that will be reflected in the next event's plan.
Institutional knowledge is the accumulated understanding of how your operation works — built over multiple events, preserved in documentation, and accessible to anyone who needs to run the operation in the future. It is the difference between an operation that depends on one person and one that survives turnover.
Most rodeo committees lose institutional knowledge every time a key volunteer moves on, a committee chair rotates, or a security director takes a different role. Years of hard-won operational learning disappears because it was never written down. The systems below prevent that.
The goal of all this documentation is a simple one: each event should be operationally better than the last. Not dramatically — incrementally. One fewer problem. One faster response. One staffing decision made better because of what you learned the year before.
Before each new event cycle, run a plan review session using the previous year's AAR and Lessons Learned Log as your starting documents. Work through the plan from the top. Every section gets asked the same question: has anything changed, and does anything in this section need to be updated based on what we learned last time?
Seven modules. Risk assessment, security planning, arena operations, access control, event day execution, incident response, and the debrief process that makes each event better than the last. This framework has been tested across more than a dozen PRCA, GCPRA, PBR, and invitational events. It works because it is practical, specific, and built for the actual environment of professional rodeo — not adapted from a general event management textbook. Take it, make it yours, and run a clean event.