Should safety information be a static or dynamic code?

Static. Anything safety-critical, like a welfare tent location or an emergency contact, needs to work even when the site's phone network is jammed, and a static code needs no connection to be read.

What happens if the festival's phone network is overloaded?

A static code still decodes with no connection at all. A dynamic code has to resolve a redirect, which can be slow or fail entirely when tens of thousands of phones are competing for the same signal, so reserve dynamic codes for content where an occasional slow load is acceptable.

How big should festival stage signage be?

Size for the real distance it's read from: a car park sign read from a moving car needs to be far larger than a stage schedule board read from a nearby queue. See the print size guide for the distance-to-size ratio.

QR Codes for Festival Wayfinding and Signage

Create a QR code

QR codes for festival wayfinding and signage

A festival site is not a poster wall, it's a temporary town: a main stage, two or three smaller ones, a campsite, a food court, a box office and a welfare tent, each needing its own signage and each drawing a different crowd from a different distance. A single QR code bolted onto the site map covers none of that well. This page is the per-zone version: which stops get a code, what each one is for, and the two failure modes specific to a festival rather than any other kind of event, a running order that changes on the day, and a phone network that tens of thousands of attendees have already saturated by lunchtime.

One code per zone, not one for the whole site

Each zone's audience and job are different enough that a single code crammed onto a printed site map serves none of them well. A car park entrance code is read from a queueing car; a welfare tent code is read up close, often in a stressful moment. Splitting by zone means each one can be sized, worded and updated on its own, without the box office's code changing every time a stage's running order does.

Zone	Typical scan distance	What the code should do	Static or dynamic
Car park / gate entrance	5-10m, often from a moving car or a queue	Site map and car park reference	Static, this rarely changes mid-festival
Stage schedule board	1-2m, from the queue or a nearby bench	That stage's running order for today	Dynamic, running orders shift on the day
Food court / trader row	0.3-1m, close up	Trader list, allergen info, payment options	Static unless traders change between days
Welfare / medical tent	Close up, often in a stressful moment	Contact details and directions to help	Static, this must work when it matters most

Stage times change, the printed timetable doesn't have to

An act pulls out, a changeover overruns, a stage's whole afternoon shifts by twenty minutes. A printed timetable is wrong by lunchtime on a multi-stage day; a code pointing at a live running-order page isn't.

Repointing the code isn't the only lever

There are two separate tools here, and it's worth being precise about which one you're reaching for. If the running order itself changes, update the page the code already points to, no repoint needed. Only repoint the code itself if the destination has to move house entirely, for example the whole schedule moving off a paper flyer host onto a proper page.

Signal at a festival is congestion, not absence

This is a different failure mode from an outdoor heritage trail with genuinely no coverage. A festival site usually has signal; the problem is tens of thousands of phones in one field competing for it, so a full signal bar is no guarantee a redirect resolves quickly. For anything safety-critical, welfare tent location, an emergency contact number, use a static code so it works even when the network is jammed. Reserve dynamic codes for nice-to-have content, like a running order, where an occasional slow load is tolerable.

Planning a festival code set:

1
List every zone that needs its own signage
Not just the stages: car parks, campsite, food court, box office and welfare all need their own entry.
2
Decide static or dynamic per zone
Use the safety-critical test: if it must work when the network is jammed, it's static.
3
Size each code for its own realistic scan distance
A car park sign and a food stall menu are not the same sizing problem; don't use one size for the whole site.
4
Choose weatherproof, trample-resistant mounting
A multi-day outdoor event takes more abuse over one weekend than a gig poster takes over its whole eight-week run.

A five-zone festival site already uses the entire free allowance of three dynamic codes within one weekend, before accounting for a second stage or a second day. Any genuinely multi-stage, multi-day event will need Pro at £9/month, decided at the planning stage rather than discovered mid-build.

One per zone that needs its own signage: typically car park, each stage, food court, box office and welfare, so five or more even for a modest single-stage day. That's already over the free allowance of three dynamic codes.

Part of Events & posters

QR codes for festival wayfinding and signage

One code per zone, not one for the whole site

Stage times change, the printed timetable doesn't have to

Signal at a festival is congestion, not absence

Related