Timeline scenario
Bohemian wedding timeline: relaxed guests, precise backstage work
Editorial team · Reviewed
A relaxed celebration works best when guests can be spontaneous without suppliers having to guess. Use flexible social blocks and precise service handoffs.
Assumptions to confirm
Informal seating; a live music set; shared food service; a short ceremony. These choices define this example and can be replaced.
The decisions that make this schedule work
Agree with the caterer how guests will know food is ready and with the music lead how the service cue is heard. Confirm the approved seating and circulation plan with the venue. Keep any spontaneous toasts inside a bounded window so speeches do not consume the meal or contracted music time.
A worked revision
This hypothetical example illustrates a decision, not a promise about your suppliers' availability. Two friends ask to add toasts. The couple approves one combined ten-minute slot and the coordinator confirms it with the music and catering leads. The added speaking time uses social buffer instead of silently extending the supplier booking.
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 |
| Open gathering and portraits | Host | 16:20 | 16:30 | Host: Open gathering and portraits moves from 16:20 to 16:30. Check your next handoff. |
| Food service readiness | Caterer | 17:00 | 17:00 | Fixed anchor — unchanged |
| Shared meal | Caterer | 17:15 | 17:25 | Caterer: Shared meal moves from 17:15 to 17:25. Check your next handoff. |
| Toasts | Host | 18:15 | 18:25 | Host: Toasts moves from 18:15 to 18:25. Check your next handoff. |
| Live music set | Musician | 18:45 | 18:45 | Fixed anchor — unchanged |