Publish a schedule people can confidently follow

Coordination separates the plan you are editing from the version people have been asked to follow. The shared recipient link always shows a published version. Text and email delivery remain queued until the corresponding service is activated.

Work through one timing change

Open a wedding’s Coordination page and save the first draft. Each moment can have a date, duration, buffer, location, roles, resources and dependencies. Keep a ceremony start fixed when it cannot move. Put independent preparation work on parallel paths; assigning the same resource to overlapping moments produces a conflict to review.

Suppose portraits need twenty more minutes. Change their time, review the proposed downstream schedule and resolve any fixed-time or resource conflict. The impact preview shows old and new values. Saving this draft does not notify recipients. Publish the reviewed version when it is ready to become the working plan.

A recipient assigned the photographer role receives only changes to moments that match their roles or explicit assignments. Private notes from the original timeline are excluded. A newer publication cancels unattempted reminders for the older version. Live Mode timing changes can publish immediately; review the live timing controls before making a day-of adjustment.

Keep a useful fallback

Save a named scenario before trying a rain plan. Restoring a scenario or published version changes the draft; it does not publish the restored version or send messages. Any conflicting edits from another operator require a reload rather than silently replacing their work.

Publication history and delivery history describe different things. A published plan is committed even if a provider is unavailable. The delivery board shows pending, sent, delivered, failed or uncertain outcomes. An uncertain text is held for provider reconciliation rather than automatically sent again. A delivery receipt also does not mean the person has acknowledged the plan.

For recipient controls and day-of reports, read delivery preferences and handoffs.

Move several moments with a preview

Open Explore a different version of the day, select moments by day, role, individual checkbox, or a starting moment, then choose an elapsed-minute shift, a new location, replacement roles, a section, or a buffer. Reviewed locations keep their source revision and are checked again when you save and publish. A twenty-minute ceremony delay moves the selected ceremony once, then follows its dependency edges. Kitchen work on an independent path stays put. A fixed venue handback is skipped by a bulk time shift; a dependency that cannot fit before it appears as a conflict.

The preview lists direct and downstream changes before you apply them to the unsaved draft. Save after reviewing those changes. Times use the wedding timezone and elapsed durations through daylight-saving transitions. Ambiguous repeated times must be changed to an unambiguous time before publication. Drag a moment’s handle, use its space-and-arrow keyboard controls, or open Edit and use Move up/down to change presentation order. Ordering does not create a scheduling dependency.

Undo saved edit and Redo saved edit retain the last thirty saved operations across reloads. The sticky draft toolbar also provides thirty local undo/redo operations before saving. Consecutive typing in one field is grouped into one operation. Use Ctrl/Command+Z or Shift+Ctrl/Command+Z outside a text field, or the toolbar buttons; typing fields retain normal text undo. Local history lasts until the editor reloads; saved history remains available across reloads. Unsaved work can be discarded separately. A new saved edit after undo clears the redo branch. Checkpoints, scenarios, and published versions can be compared field by field, including private dependencies and resources. Restoring one creates another saved draft and retains the draft you replaced in history. If a checkpoint refers to a deleted timeline moment or wedding day, the restore stops for review.

Collect separate, scoped signoffs

In Review before publication, name a reviewer, choose a role label, select the roles or exact moments they can see, and set an expiry. Each link freezes a view of the saved draft. Create a separate link for each person whose decision you need to track, including each partner if they are deciding independently.

The link contains only that review’s visible titles, times, dates, durations, locations, and time-sensitive markers. Private resource names, dependencies, and original timeline notes are excluded. Copy the link when it is created: the server stores its hash. Revoking the link ends access and explicitly removes its publication requirement. If its URL is lost, revoke that entry and create a replacement.

A reviewer can leave a general or moment-specific comment and, if permitted, suggest a title, date, time, duration, or location. Applying a suggestion requires the workspace operator to preview its effect, confirm it, and save against the current draft revision. A stale suggestion cannot silently replace newer changes. Suggestions never publish by themselves. Recorded decisions remain in the review conversation.

Required reviews must be approved against the current visible schedule. A timing or location change visible to that reviewer marks the old review outdated. A private resource-name edit or an unrelated vendor’s change does not invalidate an otherwise matching approval. For an updated review, make the old requirement optional or revoke it, then issue the replacement link. An expired required review also blocks manual publication until it is explicitly replaced or made optional.

This is capability-link review: anyone holding the private URL can respond with a typed name. That name is a record of the response, not verified identity or a legal signature. Review approval is separate from acknowledging a published schedule. Committed Live Mode timing updates retain their wedding-day dispatch behavior and never publish an unrelated saved draft.

Confirm the actual recipient impact

Choose Review publication and recipients after saving. This checks each recipient’s latest acknowledged or sent baseline, current role scope, enrollment, and required signoffs. Expand a recipient to see the old and new values they will receive. A changed draft, scope, delivery destination, or required review invalidates that preview and requires a fresh review.

Confirm the preview, then select Publish and notify. Applicable updates enter the durable queue; publication is not evidence of SMS or email delivery. Recipient opt-in, quiet hours, spending limits, provider configuration, and delivery outcomes still apply. No draft save, comment, approval, undo, or scenario restore sends a schedule notification.

Add structure without losing the published plan

Your working timeline has compact, searchable moment cards. Filter by day, role, or section. Add a moment and Duplicate first create local draft moments; Save draft creates their source timeline records and the saved coordination draft atomically. A failed save keeps the local draft on screen. New moments are not sent in notifications until publication. Duplicate copies preparation details but clears reviewed crew, vendor, and equipment assignments so you can deliberately assign their resources.

Remove from draft omits a moment and removes dangling preparation and travel links. It does not delete the original source timeline record or historical publication. Refresh from timeline can bring source moments back. Completed moments cannot be removed through this editor. A later publication also checks completion again on the server: reopening a moment in Live Mode is required before changing its published time or removing it from the next version.

Sections group the work into getting ready, ceremony, reception, or labels you choose. A moment’s private preparation checklist can track tasks such as confirming rings or checking microphones. These checks remain workspace planning data; they do not change shared Live Mode completion or appear on recipient schedules.

The See the day by role and location view shows parallel responsibilities. The scenario starters can select a ceremony delay, outdoor location changes, or additional buffers. Every starter is a deliberate scheduling operation, not an AI prediction. Preview changes and conflicts, apply them to the private draft, save, then Keep a scenario with a meaningful name. Use Draft history and alternatives to compare or restore it later.

Rehearse the coordination story

The interactive sample wedding demonstrates a twenty-minute ceremony delay using the same dependency engine. Switch among a photographer, caterer, DJ, and transport team, simulate delivery statuses, acknowledge one published version, and skip ahead five simulated minutes to see remaining follow-ups. This anonymous demonstration uses original fictional data. It makes no provider calls and sends no real SMS, email, or push notifications.

Ask the assistant for an alternate scenario

Save the current coordination draft, then use Rain alternative, Shorter celebration, or Protect the photographs. The assistant opens with that wedding and its coordination draft selected. Edit the request, add confirmed indoor location details or photography priorities when needed, and approve the displayed model-request charge. Without the shared model and usage configuration, the request remains unavailable; no unapproved overage is created.

The resulting Keep an alternate timeline proposal shows every before/after field difference, including dependent moments that move. Expand Edit the proposed adjustments to change proposed times, durations, buffers, or locations. Blank fields keep their source value. Save edited previews, review the exact proposal and source, then approve saving the scenario.

The assistant can adjust only existing moments. It retains source IDs, day links, dependency edges, assignment scope, fixed anchors, completed timing and timezone. A linked location must be another current reviewed location from this wedding; a written location must be grounded in the selected source or request. Missing room names, desired duration reductions, or photography priorities are questions to resolve. The source fingerprint includes draft revision, execution state and reviewed locations. Changes to them require a fresh review. Resource capacity and scheduling conflicts are checked again when the proposal is applied.

Approval creates a named alternate scenario in Draft history and alternatives. It does not replace the working draft, publish a schedule, reserve inventory, or notify anyone. Compare it there and deliberately restore it into the draft when ready; publication remains another reviewed action. The mobile assistant displays the scenario summary and links to the full web comparison for approval.

Each request uses the existing assistant source and cost limits: at most 100 explicit scenario adjustments, up to 25,000 characters per selected record and 65,000 characters across selected records. A truncated schedule that cannot be reconstructed is not silently accepted as a complete source. Narrow the source work or use the timeline editor. Model suggestions are bounded proposals; the assistant cannot promise that an unspecified rain room or photography requirement exists.