Use the native runbook when reception drops

The native runbook is implemented for iOS and Android. Account and provider activation, device testing and distribution are separate release steps; this guide describes the implemented workflow rather than an app-store availability claim.

Download before leaving reception

Choose the intended workspace, open the wedding, and visit the tasks, live plan, photo lists or guest list you will need. Each view shows its download time. Protected copies expire after 48 hours. A large list may remain available online without fitting in the local cache; read the storage notice before relying on it offline.

Save a task or mark a photograph captured while offline. The app keeps a pending change with its original request identifier and record revision. Saved changes shows what still needs to sync. A local message approval is not confirmation that the message reached anyone.

Reconnect and resolve

Sync checks workspace access before submitting changes. A record changed elsewhere stays in an explicit conflict; the app does not guess which person's edit should win. Discard the local changes for that record, refresh its current version, and make the decision again.

A timing update can publish a coordination revision and notify affected vendors according to the workspace settings. Review the timing confirmation before queueing it. Published times remain visible until the server resolves dependencies and fixed moments.

Protect the handoff

Gallery originals upload in verified parts. To resume after a restart, select the same original file. The app checks completed parts before reuse; a different file needs a new upload.

Sign-out removes the account's protected copies and pending work after warning you. Server-confirmed session revocation or workspace access changes remove affected local data. Do not sign out to fix an ordinary connection problem if you still need unsynced changes.

Keep a separately reviewed contingency handoff for a device that loses power. Read the offline event plan before the wedding day.

Named day-of work

Preview and accept your named invitation in Invitations, or accept it on the web, then open Shared → Day-of Desk. Your accepted assignment determines the available schedule, photography list, catering packet or transport manifest. Coordination assignments can acknowledge the current revision, record readiness and arrival, complete assigned moments, report incidents and respond to handoffs. Catering and transport acknowledgments retain the exact packet or manifest version you reviewed.

Pending named updates retain their original request identifier, revision and snapshot fingerprint. If another person changes that record, resolve the conflict after refreshing; the app does not silently move your approval to a newer version. Losing a known assignment removes its local data and pending commands when access is checked online. Authorized Ably subscriptions refresh foreground views when their source changes; PostgreSQL remains authoritative. Refresh or sync after reconnecting.

Lead views support reviewed stage moves, and conversations can retain a private device reply draft before separate send approval. Guest views include meal totals and RSVP/dietary filters. CRM creation and edits, reviewed guest changes, invitation claiming, assistant source comparisons and editable proposed changes are available in the native app. Complex floor-plan and album design use the responsive web editors. A notification with a project destination checks current server authority before opening that project; notifications without a project use the workspace or shared-work destination. Physical-device, provider and distribution checks remain part of coordinated activation.

Shared voice notes

A named business operator with posting and attachment access can record, listen, upload a private draft, and select it for an approved shared message. The transcript and selected notification recipients are visible before posting. Native recordings use M4A; the server verifies and converts the original into a protected playback copy. Capture stops in the background, and unuploaded audio is cleared when you leave the conversation. See private voice notes for spending approval, processing and access rules.