← Field guides

Timeline scenario

Garden wedding timeline: make the weather decision early

Editorial team · Reviewed

A garden plan needs two complete paths to a ceremony: the intended setting and the agreed alternative. A weather decision has to arrive before the team commits to the wrong installation.

Assumptions to confirm

Outdoor ceremony; indoor alternative; shared floral pieces; a named venue decision maker. The example contains no weather prediction.

The decisions that make this schedule work

List the last reversible setup step, who owns the weather decision, and which suppliers need that decision. Ask the venue to define the actual safety thresholds and approved alternatives. Give guests a clear arrival destination only after the active plan is confirmed; keep both location names in the crew brief.

A worked revision

This hypothetical example illustrates a decision, not a promise about your suppliers' availability. At the decision checkpoint, the venue selects the indoor plan. The floral team changes installation location before guests arrive. Portraits shorten by ten minutes, while the officiant retains the approved ceremony start and the caterer receives a revised cocktail location.

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

EventRolePreviousProposedChange note
Venue weather decisionVenue13:0013:00Fixed anchor — unchanged
Install selected ceremony layoutFlorist13:1013:20Florist: Install selected ceremony layout moves from 13:10 to 13:20. Check your next handoff.
Venue readiness checkCrew14:3014:40Crew: Venue readiness check moves from 14:30 to 14:40. Check your next handoff.
PortraitsPhotographer15:0015:10Photographer: Portraits moves from 15:00 to 15:10. Check your next handoff.
Guest arrivalHost15:3015:30Fixed anchor — unchanged
CeremonyEveryone16:0016:00Fixed anchor — unchanged