Multi-track, multi-hall, and still one programme.
Four tracks, sixty speakers and rooms changing underneath you. Four tracks running at once across three halls, sixty speakers, and a running order that has to survive contact with the day. EventBlok holds the whole thing as one structure so the programme, the crew and the audience never disagree.
- 12
- tracks on one timelineDescribes how EventBlok works — not a measured statistic.
- 0
- republish stepsDescribes how EventBlok works — not a measured statistic.
- 1
- record, every hallDescribes how EventBlok works — not a measured statistic.
- live
- change → downstream surfaceDescribes how EventBlok works — not a measured statistic.
A conference is not one show, it is nine running at once. The hard part is not any single session — it is keeping nine parallel programmes, three crews and two thousand phones in agreement.
Twelve tracks, one timeline. Each with its own hall, crew and audience.
Attendees filter to the track they care about. Production sees the hall they are running. Both are reading the same programme rather than two documents that were the same on Monday.
- ✓Parallel tracks with their own rooms and crews
- ✓Filtered views per hall, per day, per format
- ✓Clashes flagged as you build the programme
Buildings, floors, halls and breakouts. With the walk between them accounted for.
Back-to-back sessions on different floors are a promise the event cannot keep. Model the estate properly and the programme can tell you before the delegates find out.
- ✓Multiple halls, floors and breakout spaces
- ✓Turnarounds and room resets made visible
- ✓Capacity checked against registrations
Each hall gets its own showflow. Derived from the programme, not retyped from it.
Hall 2 crew see Hall 2. The show caller sees the whole day. When the keynote overruns, every downstream room sees the consequence rather than hearing about it on comms.
- ✓A cue-level run of show per hall
- ✓Department views for GFX, LX, A/V and FOH
- ✓Live position shared across every connected device
One overrun, nine programmes to correct. Or none.
The change lands onceOn the roadmap
Move the keynote and every downstream time recalculates — in the hall running it and in the three halls waiting on the same lunch break.
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. Crew see it where they workOn the roadmap
Not as a screenshot in a group chat. The running order they are already reading is the one that changed.
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. So does the roomOn the roadmap
Two thousand saved agendas update inside the attendee portal. Nobody walks to a hall that emptied twenty minutes ago.
An attendee phone showing a saved session with its new 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 — updated
The conference-specific parts.
Sixty of them
On the roadmapProfiles, bios, headshots and session context collected once, published everywhere they appear.
Slots that cannot move
On the roadmapMark contracted sessions as hard windows. The schedule absorbs overruns around them instead of through them.
The online hall
On the roadmapAn online space is a place with a capacity and a programme, alongside the physical halls.
