Wedding DeskIn beta · early access by invitation

Understand module readiness

Wedding Desk is currently in beta. These guides describe the workflows that are available now. Some articles are still being expanded with fuller instructions, screenshots and video.

What this article covers

Module readiness shows which parts of a project may need attention before the wedding day.

What readiness is

Readiness is a practical signal. It looks at whether important areas contain enough useful information to support the plan.

It is not a legal status, not a guarantee and not a replacement for your final professional review.

What can feed readiness

Readiness can use signals from:

Examples of useful readiness signals

A project may need attention when:

  • the wedding date or location is missing
  • the timeline has too few planned moments
  • important timeline moments do not have times
  • the shot list has no must-have shots or family groups
  • key vendors do not have contact details
  • gear has critical items still open
  • delivery preparation has not started after the wedding

Steps

  1. Open the project overview.
  2. Review Wedding day readiness.
  3. Look for areas marked Needs work or listed under Sections that need attention.
  4. Open the linked workspace.
  5. Update the source data there.
  6. Return to the overview if you want to check readiness again.

How to interpret readiness

Readiness is most useful when it points to a concrete next action. If readiness says Vendors need attention, open Vendors and check missing names, roles, phone numbers or timeline links. If timeline readiness is weak, open the timeline and review missing time, location and structure.

Tips & suggestions

  • Use readiness as a checklist starter, not as your final approval.
  • Fix gaps in the workspace that owns the detail.
  • Do a manual final check before sharing, printing or using On The Day.

Updated Jun 30, 2026

Was this article helpful?