Timeline scenario
Four hours of wedding photography: choose the story you need
Editorial team · Reviewed
Four hours is a coverage boundary, not a miniature version of every possible wedding photograph. Choose the essential story before assigning the start time.
Assumptions to confirm
Coverage from 14:00 to 18:00; one property; a 30-minute ceremony; a short family list. Travel and extra traditions need an explicit reallocation.
The decisions that make this schedule work
List the moments that must be photographed and decide which can happen without the photographer. Work backwards from the final essential event, then protect a short family list with a named gatherer. Confirm how overtime would be approved before the wedding; never assume the supplier will simply remain.
A worked revision
This hypothetical example illustrates a decision, not a promise about your suppliers' availability. The couple prioritizes the ceremony, immediate family, and a meal entrance. They skip extended getting-ready coverage and do their formal exit without a staged photograph. When preparation slips, optional detail images shrink before the family groups are rushed.
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
5
Texts sent
0 — preview only
| Event | Role | Previous | Proposed | Change note |
|---|---|---|---|---|
| Details and final preparation | Photographer | 14:00 | 14:10 | Photographer: Details and final preparation moves from 14:00 to 14:10. Check your next handoff. |
| Couple portraits | Photographer | 14:30 | 14:40 | Photographer: Couple portraits moves from 14:30 to 14:40. Check your next handoff. |
| Ceremony | Everyone | 15:00 | 15:00 | Fixed anchor — unchanged |
| Family photographs | Photographer | 15:30 | 15:40 | Photographer: Family photographs 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 candid coverage | Photographer | 17:00 | 17:10 | Photographer: Meal and candid coverage moves from 17:00 to 17:10. Check your next handoff. |
| Coverage ends | Photographer | 18:00 | 18:00 | Fixed anchor — unchanged |