Many stages. One timeline. One public programme.
Sets, changeovers, curfews and unannounced acts across an entire site. Six stages running from midday to curfew, changeovers measured in minutes, and an audience deciding where to walk next. EventBlok holds every stage on one timeline and publishes the programme the field is actually reading.
- 6
- stages on one timelineDescribes how EventBlok works — not a measured statistic.
- 0
- republish stepsDescribes how EventBlok works — not a measured statistic.
- 1
- record, every stageDescribes how EventBlok works — not a measured statistic.
- 23:00
- curfew, heldDescribes how EventBlok works — not a measured statistic.
A festival timetable is a promise made to thousands of people at once. Change a stage time and the promise breaks in the field before it breaks anywhere else.
Six stages side by side, with the changeovers in the plan.
The twenty minutes between acts is a reset, not free time. Model it and the schedule can tell you when a changeover is impossible rather than letting stage management find out.
- ✓Parallel stages on a single timeline
- ✓Changeovers and line checks as real slots
- ✓Curfews and licensed hours locked
A programme people can plan a day around.
Filter by stage or time, save the acts you want, get the new time when something moves. The published timetable is the one production is working from.
- ✓Searchable programme with personal line-ups
- ✓Saved acts update when a set time moves
- ✓Stage, site and access information attached
Each stage crew sees their own stage.
Same record, filtered to the stage they are running, with the site-wide picture available to whoever is holding it. When a set runs long, the knock-on is visible immediately.
- ✓A run of show per stage
- ✓Site-wide view for the production office
- ✓Overruns show their consequence to curfew
A twenty-minute delay on one stage is a site-wide problem.
The clock is realOn the roadmap
Durations rather than fixed times, so the day reflows and the distance to curfew is a number rather than a feeling.
09:00Opening keynoteMainstage · Hall AConfirmed10:30A field guide to honest interfacesCraft · Studio 2Confirmed13:30Fireside with regulatorsSystems · Hall ADraft15:00Workshop: writing a run of showCraft · Studio 1The programme itself — every session with its track, room and speaker. The field is toldOn the roadmap
Saved line-ups update in place. Nobody walks twenty minutes across a site to an empty stage.
Attendee phones showing an updated set time.fintechforum.comLIVEMy agenda09:30Opening keynoteMain Stage★13:45Fireside — RegulatorsStudio★15:00Workshop — Fraud modelsHall 2☆LODr. Lena OrtizHead of Risk, NorthwindMAM. AdeyemiPolicy lead, BankCoRNR. NovakFraud architectMain StageLevel 0 · NorthStudioLevel 1 · EastHall 2Level 0 · South↻ fireside moved to 13:45 — updatedThe crew already knewOn the roadmap
Every stage sees the change where they are already looking, rather than on a radio call that half the site missed.
09:30Opening keynoteAida OkaforLive09:45Panel: honest interfaces3 speakersNext10:15BreakFoyer10:30Payments deep-diveSystems trackVIDEOVT-2AUDIOMic 4LXState 3The running order the crew calls from — one cue live, the next one staged.
The festival-specific parts.
Stages as places
On the roadmapStage, field, tent and site area, each with capacity, access and the walk between them.
Unannounced acts
On the roadmapPencil a slot without publishing it. The field sees it the moment you confirm, not before.
Three-day builds
On the roadmapMulti-day programmes with their own crews, curfews and site changes per day.
