Understand the public timeline builder's assumptions

The public timeline builder creates a deterministic draft from your ceremony, travel, portrait and venue-finish inputs. It does not claim that a generated schedule has been approved by your suppliers.

Use it

Choose whether portraits happen before or after the ceremony. Enter the ceremony duration, transfer time and hard out. The result includes preparation, arrivals, service, reception and pack out, with an owner role and working note for each block.

Understand the result

Check parallel work carefully. Guest cocktails and family photographs may overlap intentionally. The same person still cannot perform two demanding roles in different places at once. Use the crew-capacity tool to inspect staffing separately.

If something is unclear

If fixed reception blocks do not fit before pack out, the tool warns you. Change the anchors or the plan instead of treating a displayed row as proof that the schedule works. Midnight crossings include a day offset in the exported timeline.

Open the tool or return to the help index.

Rehearse a changed start

The separate delay rehearsal starts with a twenty-minute delay and no assumed buffer. It shifts movable events at or after the selected time, retains parallel offsets and leaves fixed anchors unchanged. If confirmed recoverable slack exists before that selected shift, enter it in the buffer field; the tool subtracts it from the net shift.

This sandbox does not infer dependencies or decide to shorten an activity. Review a fixed anchor conflict yourself, then use the workspace’s richer dependency and approval workflow when preparing an actual published revision. Neither public timeline tool sends a text or updates a live event.