Wedding Day Assistant: Weighing a Catering Decision

Demonstration scenario · 2:42

Watch on YouTube

Nadia and Theo use the Wedding Day Assistant to compare catering options against their guest counts, the caterer’s staffing terms and their remaining budget. The Assistant lays out the tradeoffs; it doesn’t change a meal or contact anyone, and the couple makes the decision.

Demonstration scenario

Sample wedding with fictional guests and fictional data.

Narration voice is AI-generated.

The catering situation is a realistic scenario our team put together. The couple supplied the guest counts to the Assistant. The response shown is its actual answer to those supplied counts, and it has not been edited. No real guests were contacted and no records were changed.

Transcript

Plan in whichever planning platform or tools you prefer. When you're ready, bring your timeline and guest list into EventSync Day-Of to run the wedding day.

You can import a timeline from a readable PDF, a CSV export or pasted text, and bring in a guest list as a CSV. Review the information before saving it. If you've already collected RSVPs and meal choices elsewhere, they can come in with your guest list.

Planning in Workspace keeps your guest list, RSVPs and meal choices connected. The Wedding Day Assistant can help you reason through the details available to your role, together with the constraints you tell it. That matters when there isn't one obvious answer.

Let's follow Nadia and Theo through a realistic catering decision our team put together.

Six days before the catering deadline, 124 guests have accepted and six haven't answered. The couple offered beef, salmon and risotto. Now they need to reconcile that menu with the caterer's staffing terms and their remaining budget.

The caterer has confirmed that seven servers can handle three entrée choices for 112 guests, or two choices for 140. Another server costs $260 and raises the three-choice limit to 128. Nadia and Theo have $300 left, including the $220 they hoped to spend on late-night snacks.

They share the counts from their Guest List and the supplier terms with the Assistant, and ask it to compare the choices. Nothing is being changed.

Fifty-two accepted guests chose beef, 41 chose salmon and 31 chose risotto. Nineteen guests noted a vegetarian preference, and all of them chose risotto, which the caterer lists as its vegetarian dish. Meal names alone don't establish dietary suitability.

Keeping all three choices preserves everyone's selection. But the extra server leaves only $40, so the snacks no longer fit. And if five or six pending guests accept, even that extra server isn't enough.

Keeping two choices covers all 130 possible guests with the existing staff. Keeping risotto keeps the dish the caterer lists as vegetarian. Dropping salmon would mean asking 41 people to choose again; dropping beef would affect 52. Fewer follow-ups isn't the only priority, but now the tradeoff is visible.

They choose beef and risotto, subject to confirming the arrangement with their caterer and getting fresh choices from the affected guests. The six guests who haven't answered will be offered only beef or risotto. The Assistant hasn't changed a meal or contacted anyone; Nadia and Theo do that themselves.

That's the point of the Wedding Day Assistant: bringing the constraints into view so you can make a considered choice. Its advice doesn't change your wedding. You decide what happens next.

EventSync Day-Of. Your plan, your decisions, with help seeing how the pieces fit.

Cards shown in the video