Staffing a city that exists for 72 hours

For one weekend, a large festival is a mid-sized city: its own gates and roads, its own sanitation and security, food service for a hundred thousand, medical, power, water. Unlike a city, it has no civil service. Every worker is sourced for the occasion, from somewhere — local agencies, gig platforms, touring crew, student groups, volunteers working for a wristband.

And unlike a stadium, there is no next home game to smooth the learning curve. The peak is the whole business. Whatever the fill rate is at Friday gates, that is the fill rate history records.

Why festivals break single-source thinking

No single labor source can staff a festival, structurally. The local market cannot surge 5,000 workers for one weekend; agencies cap out; gig platforms are deep in the city but thin in the field where the festival actually is. Multi-sourcing is not a strategy here — it is a law of physics. The question is only whether the sources are coordinated or merely simultaneous.

Merely simultaneous looks like: five spreadsheets, five staging tents, a radio channel of 'who do these people belong to?', and a Sunday-night settlement process that runs to Thanksgiving. Coordinated looks like: one demand plan by zone and day, every source filling against it, one check-in system at every gate that doesn't care whose payroll a worker is on, and coverage numbers the ops director can read from a golf cart.

The 72-hour city is the industry's future in miniature

Everything hard about event labor is concentrated at a festival: surge, source fragmentation, connectivity dead zones, compressed onboarding, one-shot reconciliation. Which is why we treat the festival as a design target rather than an edge case. Technology that keeps a temporary city staffed — offline-tolerant, source-agnostic, zone-aware — handles a stadium Tuesday without breaking a sweat. The reverse is emphatically not true.