Move One Block and Watch Everything Follow

The problem with static run-of-show documents

A static run-of-show is a list of times and events. It works great right up until the moment anything changes - which is to say, it works great at the planning meeting and falls apart on the actual day.

The traditional fix is a frantic round of mental arithmetic mid-event. Ceremony started 15 minutes late, so first dance is now 8:45 not 8:30, which means cake cutting pushes to 9:10, and now you are doing the math in your head while also setting up for the grand entrance. Nobody hired you to do math. They hired you to run the event.

Zenvents360 Event Documents replaces that static list with something that adapts - and extends well beyond a bare timeline into a full, rich event document.

Auto-adjusting timeline blocks

Every item in Event Documents is a time block with a known duration. When you move a block - drag it, shift its start time, extend it because cocktail hour is running long - the blocks that follow it adjust automatically. The cascading math happens in real time, across the entire document.

The result is a run-of-show that is always current. If the ceremony is 20 minutes late and the cocktail hour needs to compress to make up time, those adjustments propagate forward. You do not have to audit every entry below the change. The system does it for you.

This is the capability that event professionals react to immediately when they see it in action. It sounds obvious in retrospect - of course times should cascade when something shifts - but no event document tool has ever done it smoothly until now.

Each block carries its own duration and settings - move it and everything downstream follows automatically

Conditional visibility

Not every event runs the same program. A wedding with a unity candle has different timeline items than one without. A reception with a hora needs a different setup than one without. Event Documents handles this with conditional visibility - sections and blocks that only appear if they are relevant to this specific event.

Conditional visibility is controlled by questions you define. The client answers them during the planning process - or you fill them in based on your consultation - and the timeline self-selects the right sections to include. You are not maintaining a separate template for every event variation. You maintain one smart template that adapts.

This keeps the timeline clean and relevant for each event rather than a sprawling checklist where the client has to mentally sort what applies to them and what does not.

Individual fields can carry their own conditions - this one only appears when introductions are confirmed for the couple

Dynamic field inputs

Individual timeline blocks can contain dynamic inputs - fields for names, song choices, pronunciations, specific instructions - that get filled in as the event details are finalized. The ceremony processional entry knows to ask for the song. The first dance block prompts for the couple's selection and the exact title to announce.

These inputs are embedded directly in the timeline item, not in a separate form somewhere else that you have to cross-reference. The information lives where you need it - visible at a glance when that moment in the event arrives.

Music previews built into the document

Song fields inside Event Documents are not plain text boxes. When you or a client types an artist name into a music field, a live search pulls up matching tracks with album art. Every result has a play button so you can preview the actual song before locking it in.

This matters more than it sounds. How many times has a client typed "the slow one by Bruno Mars" only to mean three different songs depending on the day? With previews directly in the timeline, both sides confirm they are talking about the same recording before it ever hits the run-of-show. No back-and-forth texts, no wrong song playing at the first dance.

Music fields work alongside every other field type in the document. A single introductions block can carry the couple's names, how they want to be announced, and the entrance song - all confirmed and playable from the same card.

Type an artist name in any music field and preview results with album art - confirm the right song before it ever hits the run-of-show

Drag-and-drop sorting and real-time updates

Reordering the document is as simple as dragging a block to a new position. The surrounding items adjust, times recalculate, and the document stays coherent. There is no export-edit-reimport cycle. Changes happen live.

Real-time updates mean that when you make a change - from your laptop, from your phone on the way to the venue, or from anywhere - anyone else looking at that event document sees the current version. Staff assigned to the event, vendors with portal access, your second shooter checking times from the parking lot - all seeing the same live document.

The running-order problem that event professionals have managed with printed sheets, group texts, and shouted corrections is a software problem. Event Documents treats it like one.

The Live indicator means every collaborator on the event sees changes as they happen - no refresh required