An accountable wedding day

Wedding-day coordination keeps the published plan separate from what actually happened. Open a project's Wedding-day coordination page to use the incident desk, handoffs, actual observations, reminder policy and reviewed broadcasts.

Give each incident an owner

Log the issue and choose an active schedule recipient, or keep it with the planning team. Private incident details appear only to full-access workspace operators and the currently assigned recipient. They never appear in schedule texts or push notifications. Recipients can report an issue through their existing private schedule link; a report does not grant them access to other reports.

Every new report or edit retains its actor, revision and earlier values. Resolutions require an explanation. Two people cannot silently overwrite the same revision. Legacy incident records stay intact; their history begins with the first new attributable edit rather than inventing past authors.

Hand responsibility over explicitly

Choose the receiving person, write the summary both selected recipients should see, and optionally link the current incident. The recipient presses I have this responsibility before its assignment transfers. If the incident's owner or revision changed first, the old handoff cannot overwrite that change: cancel it and issue a fresh one. Acceptance, completion and cancellation remain in history. Completing a handoff does not itself resolve its incident.

Private schedule links are bearer capabilities, not proof of a person's verified identity. An action is attributed to that issued recipient link; workspace actions are attributed to the signed-in operator. Revoking or expiring the link blocks further reads and mutations, including retries.

Record actual times without moving the plan

Started now and Finished now record observations against the published moment visible to that recipient. For a past observation or a correction, enter an ISO timestamp with its offset and an explanation. Finish must follow start; future observations are rejected. Earlier values remain in the operation history. These records do not alter planned times, live completion checkmarks, resource reservations or payments. A later schedule publication retains the observations and the version against which they were recorded.

Set role reminders and acknowledgment follow-up

Recipients keep their existing personal reminder lead time by default. They can explicitly choose the planner's role policy instead. A moment with several matching roles uses the earliest configured reminder, or is held when the planner selects Hold for conflicting role times. Personal overrides remain available. Quiet hours still apply; reminders that would arrive after their moment are skipped. A changed role policy or preference invalidates an uncalled send, even after its durable claim. Already attempted reminders are not duplicated merely because a policy changes.

Important published changes require the recipient to acknowledge the exact current version. After five minutes, an unacknowledged change can create a follow-up for the explicitly on-call recipients, including a delivery that is failed or still pending. Select the workspace coordinators who should also receive push alerts on their enabled devices. Push content contains identifiers and a generic instruction to open the app; it includes no incident details or recipient contact information. A newer publication, revoked access or acknowledgment cancels a follow-up that has not been sent. A delivered text, accepted push ticket or ordinary reply never counts as acknowledgment.

Review the exact role-specific broadcast

An owning workspace owner or administrator chooses roles in the published schedule, writes the update and sets an expiry within 24 hours. Prepare exact review displays each eligible recipient's complete text, segment count and maximum configured SMS cost. The private schedule link in each text belongs only to that recipient. Review the complete audience before approving.

Approval freezes that content and its sender, recipient scope, consent, publication and quoted price. Changes require a new review. Dispatch rechecks the approver's current authority, opt-outs, quiet hours, feature availability and spending enrollment. These broadcasts have no automatic email fallback because that channel and cost were not part of the review. Ordinary published timeline changes retain their separately opted-in email fallback.

Cancel a review to stop messages that have not reached the provider. An accepted or uncertain provider attempt retains its original receipt and usage reservation. No automatic SMS or push resend occurs after an uncertain attempt; retries must not create a second message. A transport credential change holds reconciliation against the original generation rather than treating a new account as the old one.

During an interruption

If a form response is interrupted, Check original request resubmits the exact saved request identity and payload. Wait for that result before editing. Operation history is paginated, and retained broadcast reviews remain available. Recipient schedule pages refresh while online, but mutations require a connection; these controls are not an offline execution queue.

Actual SMS, email and push delivery remain behind the coordinated provider activation and workspace controls. Local fixtures and automated tests use simulated providers. This workflow does not activate phone numbers, send real messages or claim that carrier delivery is guaranteed. Ordinary vendor two-way conversations and channel-independent retry controls remain separate capabilities.