Five people. Five screens. One truth.
One event. Completely different information depending on who's looking. An organiser, a producer, a show caller, a speaker and an operator need completely different views of the same afternoon. EventBlok gives each of them the one they need, rendered from a single event record.
- 5
- roles, one recordDescribes how EventBlok works — not a measured statistic.
- 0
- copies to reconcileDescribes how EventBlok works — not a measured statistic.
- 1
- change, every viewDescribes how EventBlok works — not a measured statistic.
- live
- change → downstream surfaceDescribes how EventBlok works — not a measured statistic.
The views differ because the jobs differ. The problem was never that a speaker and a vision mixer see different screens — it is that each screen used to be a separate document somebody maintained by hand.
The whole programme, and what is still missing from it.
Sessions, speakers, rooms and the gaps. Who has sent a biography and who has not, which rooms are double-booked, and what is still marked provisional two weeks out.
- ✓The full programme across days and tracks
- ✓Chasing shown as status, not an email thread
- ✓Publish when it is ready, not before
Cue-level, with a shared position everyone is on.
One current cue, one next in standby, and a projected finish that recalculates as the day drifts. Everyone on comms is looking at the same place in the same document.
- ✓Cue-level run of show with department views
- ✓Planned, actual and projected timing
- ✓One owner moves the show, others annotate
Narrow on purpose. Their session, or their department.
A speaker gets where, when, who introduces them and what happens next. An operator gets their cues and the two either side for context. Neither is reading the whole programme.
- ✓Speaker view: their slot, current when opened
- ✓Crew view: their department, their room
- ✓Both print, for the ones who want paper
Move a session and nobody has to be told twice.
The organiser decidesOn the roadmap
They see the consequence before they commit: the turnaround that gets tight, the break that disappears, the hard window at risk.
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. Production already has itOn the roadmap
The running order is a deeper view of that programme, so it moved when the session moved. Nothing was re-entered.
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. And so does the roomOn the roadmap
The speaker’s page and every saved attendee agenda say the new time. The only call left to make is the human one.
Speaker and attendee views showing the 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
Who sees what.
Permissions that match the job
On the roadmapOrganisers edit the programme. Crew read their department. Speakers see their session.
In for two days
On the roadmapGive someone the one event and the one department, for the days they are working.
A view, not an attachment
On the roadmapShare a link that is current when they open it rather than a PDF that was true on Tuesday.
