When the show changes, everyone sees it.
Live events move quickly. EventBlok keeps connected showflow views aligned across devices, helping teams act on the current plan rather than an old version.
Fewer screenshots, message chains and version-control problems.
| cue | action | dept | state |
|---|---|---|---|
| 47.0 | House to half | LX | done |
| 47.1 | VT roll — opener | A/V | done |
| 48.0 | Keynote walk-on | LX | ● GO |
| 48.1 | Lower-third: name | GFX | stby |
| dept | last call |
|---|---|
| FOH | standing by on 48.1 |
| LX | house at half, holding |
| A/V | VT armed |
| GFX | lower-third loaded |
The change itself takes ten seconds. Propagating it to five documents, three teams and a published programme is what costs the day.
One write, many reads. Show caller, operators, crew and presenters on connected views.
Nothing is being reconciled between five documents. Every view is a projection of the same record, so a change is visible everywhere it is relevant.
- ✓Real-time updates across connected devices
- ✓Shared timing and cue changes
- ✓Better coordination between show caller, crew and presenters
| cue | action | dept | state |
|---|---|---|---|
| 47.0 | House to half | LX | done |
| 47.1 | VT roll — opener | A/V | done |
| 48.0 | Keynote walk-on | LX | ● GO |
| 48.1 | Lower-third: name | GFX | stby |
| dept | last call |
|---|---|
| FOH | standing by on 48.1 |
| LX | house at half, holding |
| A/V | VT armed |
| GFX | lower-third loaded |
A view that rearranges itself while somebody is reading it is dangerous.
Structural reorders announce themselves instead of jumping the list. The item under an operator’s focus holds position while everything around it updates.
- ✓Changes surface as a notice, not a jump
- ✓Live cue changes flagged loudly
- ✓Attendee notifications debounced during rehearsal
Any live system that assumes a good connection has not been to enough venues.
Views that matter during delivery cache their state, keep rendering on a dead connection, and say plainly that they are doing so. A stale view that admits it is stale is safe.
- ✓Views keep working on a bad connection
- ✓Reconciles and reports what changed
- ✓Every department view still prints
Seven surfaces, one action.
What travels
The change, its recalculated consequences, the new shared position, and an annotation saying it moved — so a person joining mid-show can see it rather than guess.
| cue | action | dept | state |
|---|---|---|---|
| 47.0 | House to half | LX | done |
| 47.1 | VT roll — opener | A/V | done |
| 48.0 | Keynote walk-on | LX | ● GO |
| 48.1 | Lower-third: name | GFX | stby |
| dept | last call |
|---|---|
| FOH | standing by on 48.1 |
| LX | house at half, holding |
| A/V | VT armed |
| GFX | lower-third loaded |
Order over speed
Everyone must see the same sequence of changes, so two people acting on one screen are acting on one state. Latency matters less than agreement.
| surface | feed | state |
|---|---|---|
| Stage confidence monitor | presenter view | live |
| Operator laptop | mirror | live |
| Stream Deck | webhook | armed |
| Comfort monitor — FOH | mirror | live |
One owner during the show
Others propose and annotate; the show caller moves the show. That is how it works on comms, and the software should not invent a more democratic model than the room has.
The reasons it earns trust.
Who moved it, and when
Not to blame anyone — to answer the question without searching three chat threads.
What actually happened
After the show the running order reflects the night, not the plan from Tuesday.
The right lens
Same change, rendered for the person who has to act on it.
The room and the stream cannot disagree.
Preview, programme and the room itself, all being watched at once. Presenters, operators and the people at home are downstream of one running order — so a change at 17:25 reaches every one of them together.
Plan your branded event →Stop sending screenshots.
Make looking at the live thing faster than taking a picture of it.