Timeline scenario
Six hours of wedding photography: protect the transitions
Editorial team · Reviewed
A six-hour package can cover a focused wedding story when the schedule makes travel and group gathering visible. It cannot promise every moment merely by shortening each block.
Assumptions to confirm
Coverage from 13:00 to 19:00; preparation, ceremony, family photographs, and reception opening; one short transfer at most. The example uses one location.
The decisions that make this schedule work
Decide whether the beginning or end of the day matters more before locking the coverage window. Keep a small preparation list and collect family groups by name. If the ceremony and reception are separate, replace optional coverage with the measured transfer instead of squeezing an uncounted journey between them.
A worked revision
This hypothetical example illustrates a decision, not a promise about your suppliers' availability. The couple values speeches more than early styling photographs. They start coverage after hair and makeup, reserve a clear family-photo window, and place speeches before 19:00 only after agreeing that timing with the caterer and speakers.
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
6
Texts sent
0 — preview only
| Event | Role | Previous | Proposed | Change note |
|---|---|---|---|---|
| Final preparation | Photographer | 13:00 | 13:10 | Photographer: Final preparation moves from 13:00 to 13:10. Check your next handoff. |
| First look and portraits | Photographer | 13:45 | 13:55 | Photographer: First look and portraits moves from 13:45 to 13:55. Check your next handoff. |
| Ceremony | Everyone | 15:00 | 15:00 | Fixed anchor — unchanged |
| Family groups | Photographer | 15:30 | 15:40 | Photographer: Family groups moves from 15:30 to 15:40. Check your next handoff. |
| Reception opening | Photographer | 16:00 | 16:10 | Photographer: Reception opening moves from 16:00 to 16:10. Check your next handoff. |
| Meal and speeches | Photographer | 17:00 | 17:10 | Photographer: Meal and speeches moves from 17:00 to 17:10. Check your next handoff. |
| Evening candid coverage | Photographer | 18:30 | 18:40 | Photographer: Evening candid coverage moves from 18:30 to 18:40. Check your next handoff. |
| Coverage ends | Photographer | 19:00 | 19:00 | Fixed anchor — unchanged |