Timeline scenario
A timeline without a first look: give portraits a realistic home
Editorial team · Reviewed
If the couple wants their first meeting at the ceremony, protect that choice by budgeting the photographs that follow it. The reception transition must make room for the agreed list.
Assumptions to confirm
No pre-ceremony couple portraits; separate preparation coverage; family and couple photographs after the ceremony; guests move to a hosted cocktail period.
The decisions that make this schedule work
Build the family list before estimating the portrait window. Name a gatherer, a location, and an order that respects participant needs. Decide how much cocktail time the couple wants to attend, then compare that priority with the photograph list. Dinner cannot stay fixed if the portrait plan and transfer already exceed the gap.
A worked revision
This hypothetical example illustrates a decision, not a promise about your suppliers' availability. The initial family list needs 45 minutes and the couple also wants 20 minutes alone. With only a 60-minute gap, the planner shows the conflict. The couple reduces group variations and moves extended-friend photographs to the reception rather than asking everyone to rush.
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 |
|---|---|---|---|---|
| Separate preparation portraits | Photographer | 14:00 | 14:00 | Unchanged |
| Photographer ceremony setup | Photographer | 15:00 | 15:00 | Fixed anchor — unchanged |
| Ceremony | Everyone | 16:00 | 16:00 | Fixed anchor — unchanged |
| Family photographs | Photographer | 16:30 | 16:40 | Photographer: Family photographs moves from 16:30 to 16:40. Check your next handoff. |
| Couple portraits | Photographer | 17:00 | 17:10 | Photographer: Couple portraits moves from 17:00 to 17:10. Check your next handoff. |
| Reception transition | Planner | 17:20 | 17:30 | Planner: Reception transition moves from 17:20 to 17:30. Check your next handoff. |
| Dinner | Caterer | 17:30 | 17:30 | Fixed anchor — unchanged |