Catering handoffs

A catering packet freezes one event’s published menu, current invitation replies, meal totals, guest dietary notes and seating. Open Catering handoff from the wedding and choose the event. Publish its reviewed menu first.

Review and issue

Choose the current seating chart or a saved floor-plan revision. A saved revision must match the current attending guests’ table assignments before it can be issued. Review the exact preview, including children, outstanding replies, missing meals and unassigned seats. These uncertainties remain visible in the retained packet.

Only active invitations count. A guest whose invitation was removed is excluded. Re-inviting them starts a new response generation; their old response remains in history but does not count until they reply again. Another event’s meal and dietary answers are excluded.

Issuing creates an immutable packet. Unpublished menu or floor-plan edits do not replace it. Publishing a different menu, changing current replies or the relevant seating makes the packet stale. Preview a replacement to compare affected source categories, counts and the complete previous packet, then explicitly issue it. Previous packets and acknowledgements remain in the owner’s paginated history. A replacement revokes earlier recipient links.

Invite the named caterer

An owning-workspace administrator enters the recipient’s name, verified account email and an expiry of up to 30 days. Copy the resulting link and share it privately. This action does not send an email or SMS.

The recipient signs in with the invited verified email and claims the invitation. Claiming binds it to that account. Forwarding the URL does not grant another account access. The recipient sees only the frozen culinary packet, not guest contacts, private questionnaire answers, emergency information, gifts or business finances.

The earlier menu approval link records a typed reviewer label. It does not prove that person’s identity. A catering acknowledgement is separately attributed to the verified account that claimed this packet.

Acknowledge, replace and revoke

The named recipient can review and print the retained packet, then acknowledge its exact contents with an optional note. The acknowledgement is permanent and cannot be edited into approval of a later packet. If the source changes after claiming, the recipient can see the old packet with a stale warning but cannot give it a new acknowledgement. Ask the coordinator for a reviewed replacement.

An administrator can revoke one invitation; an authorized menu editor can revoke the packet and all its invitations. Expired, revoked or replaced invitations no longer open. Losing the inviting administrator’s current workspace authority also disables their grants.

If a save’s result is unknown, use Check original request. The exact saved request is retried without duplicating the issue, invitation or acknowledgement. Do not change its details until the original outcome is known.

Keep printed guest information private. A printout cannot show later changes; refresh the current handoff before service. Guest dietary notes are reported information, not a food-safety certification. Confirm preparation and allergen arrangements through the coordinator.