Timeline scenario
Eight hours of wedding photography: build in a real pause
Editorial team · Reviewed
Eight hours should not become eight hours of consecutive obligations without room to move, eat, or recover from a small delay. Plan the photographer’s work as a resource with boundaries.
Assumptions to confirm
Coverage from 12:00 to 20:00; preparation, first look, ceremony, portraits, and reception; a planned pause agreed with the photographer.
The decisions that make this schedule work
Ask which preparation details need to be ready at the first frame and who will gather them. Schedule the photographer’s meal or break with the service team, then identify the moments that must be covered during that interval. If two locations need simultaneous coverage, discuss a second professional instead of assigning one person to both.
A worked revision
This hypothetical example illustrates a decision, not a promise about your suppliers' availability. The couple wants both guest arrivals and private pre-ceremony portraits. The photographer explains the overlap, so they either add a second shooter or choose which moment takes priority. Their main timeline now reflects that decision rather than hiding the conflict.
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 and details | Photographer | 12:00 | 12:10 | Photographer: Preparation and details moves from 12:00 to 12:10. Check your next handoff. |
| First look and wedding party | Photographer | 13:00 | 13:10 | Photographer: First look and wedding party moves from 13:00 to 13:10. Check your next handoff. |
| Photographer reset | Photographer | 14:00 | 14:10 | Photographer: Photographer reset moves from 14:00 to 14:10. Check your next handoff. |
| Ceremony | Everyone | 15:00 | 15:00 | Fixed anchor — unchanged |
| Family portraits | Photographer | 15:30 | 15:40 | Photographer: Family portraits moves from 15:30 to 15:40. Check your next handoff. |
| Reception opening | Photographer | 16:30 | 16:40 | Photographer: Reception opening moves from 16:30 to 16:40. Check your next handoff. |
| Agreed photographer meal | Photographer | 17:30 | 17:30 | Fixed anchor — unchanged |
| Speeches dance and candid coverage | Photographer | 18:00 | 18:10 | Photographer: Speeches dance and candid coverage moves from 18:00 to 18:10. Check your next handoff. |
| Coverage ends | Photographer | 20:00 | 20:00 | Fixed anchor — unchanged |