Festival Event Operations Checklist

Use this checklist when you are running a multi-zone festival site — not a single-room conference or a one-hall corporate event. It focuses on what festival production offices actually argue about: who owns which field, whether changeovers are real, whether traders can load in without blocking artist convoys, and who holds the live issue log when weather or a gate queue shifts the plan.

Not the general operations checklist: For ticketing, RSVP, POS, and cross-format supplier readiness, start with the general event operations checklist. Return here when you are zoning a site, running multiple stages, and coordinating traders, camping, and strike on the same clock.

Festival failure modes are spatial and simultaneous: the wrong truck on the wrong track, a trader energising before power sign-off, a stage hold that never reached security, a camping gate opened without welfare cover. A general checklist catches commercial and staffing gaps; a festival checklist forces zone ownership, movement, and site services to be explicit before thousands of guests arrive.

Split the site into zones the way crews experience it — public arenas, backstage compounds, trader rows, camping, car parks, production compounds — not the way the map was drawn in month one. Assign a single owner per zone with a deputy and a published escalation path. If two teams can both say “not my field,” you will lose an hour at load-in every time.

• Master zone map posted in production office and gate briefings • Zone owners named on comms board with mobile and radio • Shared services (medical, power distro, waste) tagged to zones they serve

Programming truth and production truth must be the same grid: set times, changeover lengths, backline windows, artist holds, and security sweeps. Publish changeovers to stage managers, monitor engineers, and access teams at the same time — not via separate PDF versions. Multi-stage festivals should pair this section with a structured schedule template and a run-of-show playbook.

Traders are mobile factories on your infrastructure. Confirm setup windows, vehicle bands, power declarations, and named show-day contacts before you print pitch plans. High-density trader villages need the same discipline as headline stages — especially when food, fuel, and waste interact on shared routes.

Ingress is a product: queue design, search posture, accessibility lanes, wristband or credential rules, and re-entry. Egress and dispersal matter for transport, noise curfews, and neighbour relations. Staff every control point with written overrides for artists, crew, traders, and press — not verbal exceptions that security hears differently on shift change.

Gate rule: If credential rules are not in the access system and on the gate brief, expect duplicate wristbands and angry artists at the same door.

Walk power distro, water points, waste routes, and lighting for camping or auxiliary areas before energising traders. Tie sign-off to zone owners — production should not discover an unterminated feed when the headline act is on. Document environmental and licensing contacts beside utilities so night issues do not start with “who has the mobile number?”

Assign radio channels or groups by function, not by personality. Run a single live issue log with an owner who can prioritise weather, medical, security, and programming impacts — and push updates to gate, stage, and trader leads in the same breath. Pre-write disruption templates for queue pauses, stage delays, and site sheltering so social, SMS, and on-site PA do not contradict.

Strike is operations, not cleanup: teardown order, noise curfews, reinstatement, and trader exit windows. Name a post-event reporting owner before doors open — attendance truth, incident summary, vendor fulfilment, power and waste close-out, and finance handoff. Festivals that defer reporting to “next week” lose sponsor proofs and insurance narratives while crews are still on site.

EventSuite connects festival ticketing, itineraries, vendors, workforce, payments, marketing, and reporting so zone owners work from shared records — not parallel tabs that diverge on hour one. Use this checklist to align the production office; book a demo when you want live status, access rules, and commercial data on the same spine.