Festival Operations and Site Management Software: How to Build a Temporary Town for a Weekend Without Losing the License That Lets You Open

Why a festival is a construction project, a licensing case and a show at the same time

Nine days before gates, the operations director has a build programme in a Gantt chart, a trader list in a spreadsheet, a contractor document folder on a shared drive, an artist advance running through email and a production manager's inbox, a site plan as a PDF that has been revised four times, and a WhatsApp group with 60 people in it. The local authority has asked for confirmation that medical provision matches the figure in the license application. A power contractor has just arrived on site and nobody can confirm whether their electrical test certificates are current, so they are waved through because the stage has to be lit tonight.

That last sentence is the one that matters. Nothing goes wrong ninety nine times. On the hundredth, an inspector asks the question and the answer is that a contractor worked on site without current certification, and the license conditions were breached by a decision taken under time pressure by someone who had no way to check.

Festival operations software is often sold as an event planning tool. What it actually needs to be is a compliance record for a temporary town that is built, occupied and demolished inside three weeks.

Problem 1: contractor and trader onboarding is a document expiry problem

Every trader needs public liability insurance, a food hygiene registration where relevant, gas safety certification if they cook with gas, electrical testing on their equipment, and a risk assessment. Every contractor needs insurance, method statements, competency evidence for the specific work, and often plant certification. All of these have expiry dates, and the expiry that matters is the date they are on site, not the date they applied.

FestivalPro covers a lot of this ground and is one of very few products built specifically for festival organisers rather than for conferences. Where organisers still struggle is when their approval chain involves several internal owners, when the document requirements differ by trader type and by pitch location, and when a document that was valid at application has expired by build week. Master Tour, meanwhile, is a touring product and does the artist side of the job well, which is why so many festivals run artist advancing in one system and everything else in another.

What a custom build does: each supplier has a requirement set generated from what they actually do and where they are placed, each document has an expiry, and site access status is computed rather than declared. A trader whose gas certificate lapses two days before gates goes amber automatically and their site manager is told. The gate list is derived from that status, so the decision at the gate is not a judgement call made by someone under pressure at 11pm.

Problem 2: the build programme is a dependency graph, not a schedule

The site build has an order. Ground protection before heavy vehicles. Power distribution before anything that plugs in. Fencing before deliveries that need a secure compound. Stage steel before rigging, rigging before lighting and audio, and all of it before a structural completion inspection that the license depends on. Weather moves everything.

What a custom build does: the build programme lives as tasks with dependencies, each owned by a contractor whose compliance status is already known, and each with an inspection or sign off where one is required. When ground conditions slip a day, the effect on the structural inspection date is visible immediately rather than being worked out in a production meeting. Sign offs are captured on site from a phone with a photograph, because that is the evidence the safety advisory group will ask for, and reconstructing it after the event never works.

The important design choice is that this must not become a project management tool nobody updates. The tasks that matter are the ones with a compliance consequence. Keep the graph small and tied to sign offs, and site managers will use it. Model every cable run and it will be abandoned by day two of build.

Problem 3: artist advancing and stage scheduling live in a different building

Every act has a technical rider, a hospitality rider, ground transport, arrival and departure windows, guest list requests and accreditation needs. Across five stages and eighty acts, that is a large volume of detail with hard deadlines, and it interacts with the operational plan in ways that are easy to miss. A stage change over that runs long affects the curfew. A headline act's production arriving late affects the rigging schedule. A guest list of forty affects accreditation capacity at a specific gate.

What a custom build does: the act, the stage slot, the advance and the accreditation requests are one record. Changes propagate. When a set time moves, the affected transport, catering and crew calls flag rather than sitting in a document somebody last opened on Tuesday. Artists and their tour managers get a portal to submit rider and travel detail themselves, which is the only realistic way to keep the information current as the lineup evolves.

Problem 4: incidents on a festival site are evidence, and the license depends on them

Welfare cases, medical calls, ejections, lost children, drug seizures, noise readings, weather decisions and the timing of any show stop are all recorded, and all of them are read afterwards by the licensing authority, sometimes by the police, and by your insurer. Most festivals capture this in a control room log book and a set of forms, and the quality of that record depends entirely on how busy the control room was at the time.

What a custom build does: structured incident capture from radio operators and from staff on the ground, with the timestamp fixed at the moment and detail added later. Noise readings from monitoring positions logged against the license limit for that time period, which is the condition most commonly breached and most commonly disputed. Weather decisions recorded with the reading and the person who made the call, because a wind related show stop is the single decision an organiser is most likely to be asked to justify. Then the debrief pack generates from the record instead of being assembled by an exhausted team in the week after the event.

What this costs and how long it takes

A first festival cycle, meaning supplier onboarding with document expiry and computed access status, the compliance linked build programme with mobile sign offs, accreditation, and structured incident capture, runs $70,000 to $170,000 and ships in 14 to 20 weeks. A full platform adding artist advancing with a tour manager portal, stage scheduling, crew rostering, trader sales reporting and pitch fee reconciliation, noise monitoring capture, and multi event configuration runs $220,000 to $500,000 phased over 9 to 18 months.

What pushes cost up in festivals specifically: connectivity, because a green field site has whatever network you build for it, so offline first mobile capture is a hard requirement rather than a refinement. The number of distinct supplier types, since a food trader, a bar operator, a fairground ride and a scaffolding contractor have completely different requirement sets. Multi event portfolios, where a shared supplier register across festivals is enormously valuable and also enormously more complex. And the fact that your deadline is a gates date that cannot move, which means the first cycle should ship deliberately narrow, ideally supplier compliance and incident capture only, with everything else following the year after.

Build versus buy, and when buying is the right call

Buy if you run a single day event with a small trader list and one stage. FestivalPro will cover a large share of what you need and the effort of building would exceed the value. If your primary problem is artist logistics and your site operation is simple, Master Tour handles the touring side well and you can run the rest on documents.

Build when compliance is the binding constraint. That means a license with specific numeric conditions you must evidence, several hundred suppliers with expiring documentation, a build programme where inspections gate other work, or a portfolio of events that should share one supplier register and one operating standard. Our position is that the supplier compliance module alone justifies most builds in this category, because it converts the single riskiest recurring decision on a festival site, whether to let someone through the gate, from a judgement call into a lookup.

How to choose a developer for festival operations software

Ask them what happens to a supplier whose insurance expires between application and build week. If their model has an approved flag rather than a computed status driven by document expiry dates, you will be waving expired contractors onto site exactly as you do now.

Ask how the mobile app behaves on a green field site with no signal on day one of build. Offline capture with local storage and later reconciliation is the only workable answer, and it needs to include photographs, which are large and awkward to sync.

Ask how they would keep the build programme from becoming a Gantt chart nobody updates. The right answer is to model only tasks that carry a sign off or a compliance consequence, and to make sign off a two tap action with a photo. If they propose a full project management implementation, your site managers will abandon it.

Ask who owns the code, the infrastructure and the event data, in writing before kickoff. Your supplier register, compliance evidence and incident logs are what you produce at the next license hearing, and they need to be under your control for as long as your retention policy requires. At Digital Heroes the client owns the repository and the data from the first commit.