We closed out 2024 with 40 completed events across 14 states. Some were flawless. A few were messy. All of them taught us something. Here is the honest rundown.
Venue contracts need a weather clause
We learned this in April when a freak late-season snowstorm hit Denver the night before an outdoor community event in Civic Center Park. The venue contract had no weather cancellation provision. We scrambled, moved the event indoors to a hotel ballroom 12 blocks away, and ate the cost of the tent rental we could not use. The event went fine. The invoice did not.
Since then, every outdoor event contract includes a weather fallback clause with a specific alternative venue and a cost-sharing arrangement between us and the client. We will never run another outdoor event without a Plan B locked in at the contract stage.
Catering estimates are always wrong in the same direction
For multi-day conferences, we consistently over-ordered food in the first half of the year. The standard formula (registered attendees minus 15% for no-shows) does not account for the fact that people leave conference venues for lunch if the surrounding area has restaurants. At Mountain West DevCon, we ordered lunch for 720 and served 480. That is a lot of wasted sandwiches.
Our revised approach: order for 60% of registered attendees on day one, then adjust for day two based on actual consumption. This cut food waste by about 35% across our last ten events.
The one mistake we kept making until October
We underestimated load-in time for events outside Colorado. When we produce events in Denver, we know the venues, the loading docks, the freight elevators, the parking situations. When we went to Austin, Portland, and Minneapolis, we used the same time buffers and ran late every time.
In Austin, the hotel's freight elevator was shared with a wedding setup on another floor. We lost 90 minutes. In Portland, the loading dock closed at 5 PM due to a city noise ordinance we did not know about. The AV crew had to carry equipment through the front lobby.
Starting in October, we added a mandatory site visit to every out-of-state event, at least two weeks before the date. The site visit includes a timed walk-through of the load-in process. This costs us a plane ticket and a day of someone's time. It is worth it every time.
Hybrid events need a dedicated remote producer
We already knew this in theory. In practice, we were assigning the remote production role to whoever on the team had the lightest load that day. The quality showed. Chat moderation was inconsistent. Virtual breakout rooms sometimes launched late. Remote Q&A questions would pile up because no one was actively monitoring the queue.
In July we hired Tyler Nguyen as a full-time AV and streaming lead. His only job during hybrid events is the remote experience. Since he started, our remote attendee satisfaction scores went from 4.1 to 4.6 out of 5. The difference is having someone whose entire focus is the people who are not in the room.
What we are changing for 2025
Three things. First, we are standardizing our event playbooks. Every event type (single-day conference, multi-day, community, hybrid) now has a documented template with checklists, timelines, and vendor requirements. We had informal versions of these before. Now they are in writing and every team member has access.
Second, we are capping our monthly event load at five. In September 2024 we ran seven events in four weeks and the quality suffered. People were tired, handoffs were sloppy, and we had a near-miss with a double-booked AV vendor. Five per month keeps the quality where we want it.
Third, we are investing in our own streaming infrastructure. We have been renting equipment for hybrid events, which means the gear varies from event to event and the setup takes longer. By Q2 we will own a standardized kit that goes to every hybrid production. Same equipment, same configuration, every time.