Operational packets / BEOs
An operational packet—often called a BEO—is a day-of document for planners, venues, and delivery teams. Wedding Computer builds it from the wedding workspace, then lets the managing vendor add service and logistics notes, print it, or share a revocable link.
Open a wedding and choose Operational packet from the command centre.
Who can manage it
Section titled “Who can manage it”Only a signed-in wedding member with Can manage permission can open, edit, print, or control sharing for the packet. In practice this is normally the managing planner or venue. Other vendors and the couple do not gain editing access merely because they belong to the workspace.
There is one operational packet per wedding. Every authorised manager works on that same packet.
What the packet contains
Section titled “What the packet contains”Wedding Computer assembles the current:
- event date, location, status, and guest-count source;
- non-private timeline rows, including their times, descriptions, and locations;
- RSVP totals, age groups, meal choices, allergy notes, and dietary notes;
- wedding team and roles;
- primary seating plan and connected room layout;
- filenames and descriptions from wedding-visible documents; and
- a floor-plan link, when one has been entered.
You can add a title, draft/final label, guest-count override, and notes for service, meals, beverages, staffing, setup, accessibility, and general operations. The guest count uses an explicit override first, then attending RSVPs, then the wedding’s recorded count, then the guest-list total.
The preview is a living view: changes to the shared wedding data appear when the packet is opened again. Saving the packet’s own fields creates a new revision. Draft and Final are presentation labels; changing the label does not change permissions or turn sharing on or off.
Print or save a PDF
Section titled “Print or save a PDF”Choose Print for a clean print view. Use your browser’s print dialog to print it or save it as a PDF. The printed content reflects the current packet view.
Share-link security
Section titled “Share-link security”Sharing is off until a manager enables it. The generated URL is a signed bearer link: no Wedding Computer login is required, so anyone who has the complete link can read the packet. It does not expire automatically.
The shared page is marked noindex and served with private, no-store caching, but those controls do not replace access control. Review the packet before sharing. In particular, it can contain vendor-only timeline rows, guest and dietary information, names in a seating layout, team names, wedding-document filenames, and an external floor-plan link. Private timeline rows are excluded, and the document list does not expose private files or provide their contents.
Use Rotate link if a URL may have been forwarded too widely; the old URL stops working immediately. Use Disable sharing when the recipient no longer needs access. Do not paste the link into a public website or an unrestricted group chat.
Plan availability
Section titled “Plan availability”Operational packets have no separate Pro gate. The normal free-plan allowance of 12 active weddings applies to weddings the vendor created.
See also
Section titled “See also”- Run sheets & timeline — maintain the schedule that feeds the packet
- Wedding workspaces & collaboration — assign the managing-vendor permission and understand timeline visibility
- Couple guest planning — manage RSVPs, meals, seating, and room layout