Wedding party readyLead planner · Garden suite
For planners and wedding-day teams
A wedding-day run sheet that stays ready when the venue network does not.
Everly keeps the current published run sheet, assigned work, approved floor plan, and authorized contacts with the wedding. A bounded encrypted event packet remains readable when service drops.
The iPhone companion is available to invited testers through TestFlight while public App Store review and release preparation continue. It requires an Everly account.
Juniper & RowanStaff run sheet · Pacific time
Revision 4Available offlineDownloaded today at 8:42 AM
Guest arrival beginsCoordination team · Courtyard
CeremonyAll teams · Birch lawn
Family portraitsPhoto team · Oak terrace
Reception doorsVenue and catering · Oak room
The run sheet should be a shared operating record, not a PDF someone forgot to resend.
Publication creates a specific revision. Staff acknowledgement shows who has reviewed that version. Later changes remain explicit instead of quietly replacing the plan people are already using.
Built around what can go wrong on the wedding day.
Venue connectivity, stale copies, missing context, and rushed handoffs are operational risks. Everly treats each one as a visible state instead of assuming the phone is always online and every team member has the latest document.
Know which revision the team is following.
The staff run sheet shows its publication revision and event-local times. A planner explicitly acknowledges the current version. Draft changes do not silently replace the published plan or send messages to vendors.
Lose the signal, not the event packet.
A planner chooses which authorized event packet to download. The encrypted local copy has a visible capture time and a seven-day retention ceiling. Staleness is disclosed, and losing workspace access or signing out clears protected offline planning data.
Capture the issue with the wedding it belongs to.
Private wedding-day issues keep a short operational note and an expressly selected photo with the authorized event. Uploads are verified server-side, files use short-lived download controls, and storage locations never appear in the mobile response.
A professional companion, not a second source of truth.
The Everly web workspace remains the system where studios configure weddings, publish timelines, manage permissions, and make dense planning decisions. The iPhone app reads and updates the same authorized Everly records through versioned APIs.
Subscription purchases remain on the web. The initial iPhone app requires an Everly account plus a TestFlight invitation until public release and does not contain a parallel in-app subscription system.
Day-of questions, answered plainly.
What remains available offline?
A selected event packet can include the current overview, published run sheet, assigned tasks, and bounded event-linked contact information. Sensitive guest, inbox, finance, and private vendor intelligence remain online-only.
Can an offline change overwrite newer work?
No. Supported queued changes use record versions and idempotency keys. A stale or conflicting operation must be surfaced for review instead of reporting a false success.
Does the app send messages to the wedding team?
The current run-sheet and event-packet flows do not autonomously send vendor or client messages. Contact methods use explicit, user-initiated handoffs.
When will the app be available in the App Store?
TestFlight testing is active. Privacy review, App Store submission, and public release are still in progress.
Keep the current plan with the people delivering it.
Start with the web workspace and one current wedding. The iPhone companion remains TestFlight-only until public App Store release.
Start a 14 day trial No card and no automatic paid plan.