The ceremony is 20 minutes late. What happens next?

A ceremony is due to start at 16:00. At 15:55, the coordinator learns it will start twenty minutes late. The useful response is a revised plan with clear actions for the people affected. A text saying “everything is delayed” leaves too much for each supplier to guess.

This worked example uses a 30-minute ceremony, family photographs and cocktail service beginning at 16:30, an entrance at 17:30 and dinner at 17:45. Sunset portraits at 19:15 and pack out at 22:00 are fixed anchors. All names, times and roles here are illustrative.

First, separate the decision from the announcement

Keep the last published schedule available while you prepare the change. Establish whether the twenty minutes is a confirmed new start or an estimate. Name the person who can release the ceremony; otherwise suppliers may act on a prediction that changes again.

Preview the affected moments before committing the revision. The rehearsal below moves the selected movable moments by twenty minutes and holds fixed anchors in place. It does not assume that dinner can be shortened, that photographers will stay later, or that a transport booking can move.

The earlier cocktail and photo blocks are parallel work. Giving them the same revised start does not mean the same person can do both jobs. Review ownership and travel as well as clock time.

Turn the revision into role-specific actions

A catering message can say: “Ceremony now starts at 16:20. Hold cocktail service until 16:50; proposed dinner service is 18:05. Please confirm with the coordinator if that affects preparation or staffing.” The DJ’s action is different: prepare the entrance for 17:50 and wait for the named release cue. The photographer needs the revised family-photo start and the unchanged 19:15 portrait anchor.

Each notice should identify the event, old and new time, required action and current schedule link. Send it only to recipients whose responsibilities changed. Do not include the couple’s private conversation, supplier pricing or another business’s notes in a shared notice.

The vendor notification worksheet helps draft those distinct instructions. It sends nothing. Importing its result saves a worksheet; it does not establish phone consent or queue a message.

Make the delivery state visible

“Queued,” “accepted by the provider,” “delivered” and “acknowledged by a person” answer different questions. A delivered text does not prove the catering captain can accommodate the new dinner time. Choose which changes need acknowledgement and put an actual person in charge of unresolved responses.

If a critical recipient has not acknowledged the change, contact the on-site lead through the agreed fallback and record what happened. Keep a printable run of show available for poor signal. Replacing a schedule version should also replace obsolete reminders, so an old 16:30 cue does not compete with the approved 16:50 one.

Recover slack deliberately

The tool starts with zero assumed buffer. If you have confirmed recoverable slack before the moments you select, you can subtract that amount from the shift. This sandbox applies one net shift to the selected movable blocks; it does not infer an event dependency graph or decide where to shorten an activity. Keep a confirmed delayed ceremony time fixed while evaluating downstream recovery. Use the full workspace’s dependency preview and approvals for a more detailed change.

Rehearse before enabling live communication

Change the inputs below, inspect the fixed anchors, then export CSV, printable output or the complete JSON draft. Check off no capability merely because a sample message looks right: rehearse recipient permissions, consent, provider delivery, acknowledgement, failed delivery and recovery before relying on live texts.

The implemented workspace flow is documented in publish and review a wedding schedule. It includes selected-moment batch previews, scoped review, approvals and saved undo/redo. External messaging still requires the coordinated provider activation. Twilio’s message lifecycle explains provider statuses; it does not confirm that a particular workspace is configured.

Use the published-change template to adapt the message, and keep its assumptions visible until the responsible people have confirmed them.

Work the decision

A practice case

An original fictional scenario. Numbers are illustrative inputs; this is not a customer result or a provider performance claim.

Use a fictional 16:00 ceremony with a confirmed 20-minute delay. The caterer controls service release, the photographer controls the family grouping sequence, and the venue owns a 23:00 hard out. A supplier added to the wedding yesterday has not confirmed their phone number. Your goal is a usable revised plan and a traceable handoff, not the greatest number of notifications.

Three decisions and why each matters

Decision	Why it matters
Hold the unconfirmed number from the recipient list.	Ask its owner to confirm a reachable channel; a missing contact is a visible exception for the coordinator.
Keep the hard out fixed while reviewing the rest of the day.	A ceremony delay does not extend a venue agreement or authorize overtime.
Request a fresh acknowledgement for the changed supplier instruction.	Yesterday’s confirmation referred to a different time and cannot establish readiness for this revision.

Make one usable artifact

Produce a three-row change brief: old time, new time, recipient role, required action and fallback contact. Compare it with the interactive rehearsal below.

Then test the difficult case

The delivery provider accepts a text but no delivery receipt arrives. Explain what the coordinator can truthfully report and which human follow-up closes the gap.

Use the linked tool or structured template below to record the result. Confirm it against the actual people, agreements and permissions before using it for an event.