Case study: running a festival with perfect timing

Festivals are the hardest timing challenge in live events. Multiple stages running in parallel, artists who each have their own relationship with punctuality, stagger changeovers that must not collide, sound curfews that are non-negotiable, and an audience that decides in real time where to go next. Get the timing wrong on one stage and the whole site ripples. Last summer we ran the full production technology stack for a three-day music festival in southern France with six stages and forty artists. Twenty thousand attendees per day, eight hundred crew and volunteers, two FOH positions per stage, and a common curfew at 02:00 every night enforced by the local authority. Here is what worked and what we would do differently next time. The central decision was to put every stage on the same Timers Studio session, even though each stage had its own local show caller and its own physical timer displays. The session was hosted on our cloud instance and every stage connected to it as a participant. This meant that the festival production office had a real-time view of every stage, every artist slot, and every running delta in a single dashboard. When the main stage headliner ran eight minutes late on day one because of a monitor issue, the secondary stage manager saw the drift within seconds and delayed the following artist by the same amount. The audience moving from the main stage to the secondary stage never noticed a gap. In a traditional setup with separate timers per stage, this correction would have required radio calls, manual calculations, and a few minutes of confusion. With a shared clock it happened automatically. The moderator console was the second critical piece. Each stage manager had a tablet backstage showing the current artist, the remaining minutes, the next artist, and any flash messages from the production office. When the wind picked up on day two and the sound engineer needed to drop the SPL by three decibels across all stages, the production office pushed a message to every moderator console simultaneously. Every stage manager saw the same text within a second. No voice chatter, no misunderstanding, no stage missing the memo. Curfew management was where the system really proved itself. The local authority enforces a hard stop at 02:00 with no tolerance. The main stage was scheduled to end at 01:45 to leave a fifteen-minute margin for audience evacuation and equipment shutdown. On day three the closing DJ ran long because she was reading the crowd and the set was building. At 01:40 the moderator console pushed a flash message that said "curfew hold, wrap in three minutes". The DJ saw it, closed her set cleanly at 01:43, and we avoided a fine that would have cost more than the entire technology budget. Changeovers between artists were automated through Gateway workflows. Each artist slot had a pre-programmed changeover sequence: stage lights to neutral, house music up, stage crew call, artist entry cue, artist walk-on flash. The changeover ran from a Stream Deck at FOH with five physical buttons. The stage crew moved faster because they knew exactly which cue was live and which was next. Changeover time dropped from an average of twenty-two minutes in our previous festival to fourteen minutes at this one. The post-event archive gave us one more gift. The session exported a clean log of every artist slot, every flash message, every delta, every curfew hold. The festival director used this log to write the post-event report in a few hours instead of the usual two-day reconstruction. The local authority received a detailed compliance summary showing every sound level decision with a timestamp. What would we do differently? We underinvested in the moderator console training for the stage managers. Three of the six stages had new staff who had not practised enough with the flash message workflow before the festival opened. We lost about ten minutes of production time on day one figuring out workflows that should have been muscle memory. Next year we run a half-day rehearsal with the full stage team and a simulated crisis scenario. A festival with perfect timing is not a festival where nothing goes wrong. It is a festival where the team catches and absorbs every drift before the audience feels it. The clock is the backbone. [See the demo] to explore how Timers Studio builds that backbone for your next festival, and [Create an account] when you are ready to run your first session.