Resilient festival schedule

How it works

EQR sends a HEAD request to the festival's schedule site on the interval set on the code and records every result. A failed check sends an alert email to the address on the code — EQR does not swap the destination by itself. The crew makes that call in the panel, repointing the band at a hyper-light text schedule hosted on content.eqr.link, light enough to open on a weak connection deep in a crowd.

What you get

• The crew hears about a dead schedule site from an alert, not from the queue.
• One edit moves every wristband onto the fallback — nothing is reprinted.