The same show in a different building every night.
Same show. Different venue. Different load-in. Different problem tonight. One running order, twenty-two venues, and a local crew who have never seen it before. EventBlok carries the show as a structure you duplicate per date, so the only things that change are the ones that actually changed.
- 22
- dates from one showDescribes how EventBlok works — not a measured statistic.
- 1
- running order, duplicatedDescribes how EventBlok works — not a measured statistic.
- 0
- retyping per venueDescribes how EventBlok works — not a measured statistic.
- 1
- briefing for local crewDescribes how EventBlok works — not a measured statistic.
A tour is one show performed twenty-two times in twenty-two rooms. Rebuilding the paperwork for each date is where the errors come from — and it is the most avoidable work in touring.
Duplicate the whole show and shift the date.
The cue list, the timings, the departments and the script travel with it. What changes per venue is the room, the crew and the curfew — so those are the only things you touch.
- ✓Duplicate a full show in one action
- ✓Venue-specific detail without a new document
- ✓The core running order stays identical
Each venue modelled once, referenced by its date.
Load-in access, stage dimensions, curfew and local contacts attached to the place rather than living in an advance email nobody can find on the day.
- ✓Venues, stages and load-in access
- ✓Curfews and local restrictions per room
- ✓Contacts attached to the venue, not an inbox
A briefing that is right for tonight, not last Tuesday.
Local crew get the run of show for this venue, filtered to their department, current at the moment they open it. No pack emailed three days ago with the wrong get-in time.
- ✓Department views for local crew
- ✓One link, current when they open it
- ✓Prints cleanly for the ones who want paper
Twenty-two advances, or one show with twenty-two rooms.
The show is the constantOn the roadmap
Cues, timings and script are the show. They should not be re-entered because the postcode 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. The room is the variableOn the roadmap
Get-in, curfew, stage size and local contacts sit on the venue and appear on the date they apply to.
▤Hall A800 capacity · MainstageIn use▤Studio 2180 capacity · CraftIn use▷Stream stageOnline onlyOnline▤FoyerBreaks and registrationRooms and stages modelled once, then read by every other surface. The change reaches tonightOn the roadmap
A cut song or a moved encore lands in the running order, the prompter and the local crew view at the same time.
A change to tonight’s running order reaching every connected view.VOICE-LOCKEDCUE 47.1 · OPENING REMARKS00:00 ELAPSEDGood morning, and welcome to the Fintech Forum. Over the next two days we are going to take apart the payment rail everyone depends on and nobody talks about. Before we start, a word on the schedule: the fireside has moved to thirteen forty-five.142 WPMLOCKEDvoice follow142wpm0:48to next cueCONNECTEDmirrorSPACEpause / resume scroll↑ ↓nudge read positionMOUSE WHEELmanual override, auto re-locksWEBHOOKStream Deck via Companionsurface feed state Stage confidence monitor presenter view live Operator laptop mirror live Stream Deck webhook armed Comfort monitor — FOH mirror live
The touring parts.
Openers and guests
On the roadmapSupport acts, changeovers and guest spots as real sessions with their own timings.
Band intros per city
On the roadmapScripts attached to the block, so tonight’s city name is tonight’s city name.
What ran when
On the roadmapPost-show, each date records what actually happened. Useful for the next leg.
