Timeline scenario
Ten hours of wedding photography: decide where the extra time goes
Editorial team · Reviewed
Ten hours adds flexibility only when the extra time is assigned to a reason: separate preparations, a transfer, traditions, or a longer reception story.
Assumptions to confirm
Coverage from 11:00 to 21:00; a first look; family groups; dinner and dancing; a meal agreed with the photographer. Replace every sample duration with the team’s estimate.
The decisions that make this schedule work
Create a coverage map alongside the event timeline. Mark who photographs each location, when equipment moves, and when the photographer needs a pause. Protect the final essential image within the contracted window. If the desired exit falls later, decide whether it is candid guest footage, additional paid coverage, or a different timing.
A worked revision
This hypothetical example illustrates a decision, not a promise about your suppliers' availability. The couple adds a second preparation location. Rather than borrowing time from family photographs, the planner shows the travel block and asks whether a second photographer or a different start time serves the priority better. The coverage contract is reviewed before the change becomes a promise.
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 |
|---|---|---|---|---|
| Preparation coverage | Photographer | 11:00 | 11:10 | Photographer: Preparation coverage moves from 11:00 to 11:10. Check your next handoff. |
| Equipment and location transfer | Photographer | 12:30 | 12:40 | Photographer: Equipment and location transfer moves from 12:30 to 12:40. Check your next handoff. |
| First look and portraits | Photographer | 13:00 | 13:10 | Photographer: First look and portraits moves from 13:00 to 13:10. 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. |
| Dinner opening | Photographer | 17:00 | 17:10 | Photographer: Dinner opening moves from 17:00 to 17:10. Check your next handoff. |
| Agreed photographer meal | Photographer | 18:00 | 18:00 | Fixed anchor — unchanged |
| Speeches dancing and evening portraits | Photographer | 18:30 | 18:40 | Photographer: Speeches dancing and evening portraits moves from 18:30 to 18:40. Check your next handoff. |
| Coverage ends | Photographer | 21:00 | 21:00 | Fixed anchor — unchanged |