Timeline scenario
Classic wedding timeline: formal moments with clear cues
Editorial team · Reviewed
A formal sequence can hide dozens of small dependencies: introductions, processional order, meal release, speeches, and the first dance. Give each transition an owner.
Assumptions to confirm
An officiated ceremony; a seated meal; introductions; scheduled speeches; a first dance. Adapt these events to the couple’s own traditions and choices.
The decisions that make this schedule work
Ask the couple to approve names and pronunciations before the rehearsal. Give the music lead the exact entrance order and one person authorized to release each cue. Confirm service timing with the catering captain, then place speeches where they can be heard without requiring servers to improvise around plates.
A worked revision
This hypothetical example illustrates a decision, not a promise about your suppliers' availability. A speaker arrives late. The planner holds that speech until the approved later slot and keeps meal service on schedule. The DJ receives the revised running order while the caterer receives only the service cue that affects the kitchen.
Try the schedule below
The editable rehearsal starts with the sample blocks and a 15-minute delay. Fixed events remain fixed so you can see where a human decision is needed. Change durations and roles to match the real team, then export the result as CSV or JSON. The rehearsal does not send messages, reserve people, or change a live wedding.
Before sharing, have each supplier confirm the blocks that affect their work. Name the person who approves the final revision and include a date or revision number in the handoff. A useful schedule makes responsibilities visible as well as start times.
Rehearse the change yourself
One start|duration|event|role|move or fixed per line. Parallel events keep their relative offset.
No account required. Inputs stay in this browser until you choose to import them.
How this tool works
This sandbox shifts movable events at or after the selected time by delay minus available buffer. Fixed anchors remain fixed and collisions are flagged for a human decision. It previews messages; it never sends them.
The change, before you publish it
Only movable downstream events shift. Fixed anchors need an explicit decision.
Net shift
10 min
Changed events
3
Texts sent
0 — preview only
| Event | Role | Previous | Proposed | Change note |
|---|---|---|---|---|
| Ceremony | Everyone | 16:00 | 16:00 | Fixed anchor — unchanged |
| Portraits and cocktail hour | Host | 16:30 | 16:40 | Host: Portraits and cocktail hour moves from 16:30 to 16:40. Check your next handoff. |
| Formal introductions | DJ | 17:15 | 17:25 | DJ: Formal introductions moves from 17:15 to 17:25. Check your next handoff. |
| Seated dinner | Caterer | 17:30 | 17:30 | Fixed anchor — unchanged |
| Scheduled speeches | Host | 18:30 | 18:40 | Host: Scheduled speeches moves from 18:30 to 18:40. Check your next handoff. |
| First dance | DJ | 19:00 | 19:00 | Fixed anchor — unchanged |