When you invite two hundred guests to an event garden up north, the big question is not only how many will come but what each of them can actually eat. Without a tidy way to collect preferences, the wedding evening turns into a string of last-minute requests aimed at busy waiters. A digital RSVP solves it in one line: you ask everyone at once, and the answers gather themselves.

Why collect dietary needs through the RSVP

It used to be normal to phone guests one by one, or simply guess. Both options are expensive: you either burn hours, or you over-order plates and pay for food nobody touches. When the question sits inside the digital RSVP flow, every guest who confirms also marks what they eat, and the answer is stored next to their name.

  • You get a full picture in the first weeks, not the night before.
  • No separate spreadsheet to update by hand.
  • Guests answer comfortably from their phone, without feeling like a bother.

Which questions are actually worth asking

The temptation is to ask everything. In practice, a short list with a closed choice fills in faster and more accurately. The categories that cover most weddings in Israel:

  • Kosher (sometimes also meat versus dairy, if the hall serves both)
  • Vegetarian
  • Vegan
  • Gluten-free
  • Allergies, in a short open field (nuts, peanuts, shellfish)

Leave allergies as a free-text field rather than a single checkbox, because a severe nut allergy is nothing like a mild sensitivity. One open field gives the caterer exactly what they need without flooding the guest with twenty questions.

Inclusive wording that lifts the response rate

How you phrase the question changes how many people bother to answer. A cold prompt like “mark dietary restrictions” feels bureaucratic. Warm wording explains why it matters to you:

We want everyone to feel at home and enjoy every bite. If you have a dietary preference (kosher, vegetarian, vegan, gluten-free) or an allergy we should know about, just tell us here and we will arrange it in advance.

Notice that the text does not assume every guest has a restriction; it invites the ones who do. It also lowers the awkwardness for someone who avoids meat for health or faith reasons they would rather not explain.

How to hand the counts to the caterer

Once the big wave of replies passes, roughly seven to ten days before the event, you have a summary table: how many vegan plates, how many gluten-free, how many guests flagged an allergy. You pass this to your contact at the hall or event garden in a form they can work with.

  • Export the summary as a clean file or screenshot.
  • Flag severe allergies separately, since they require separation in the kitchen.
  • Leave a buffer of two or three spare plates per category for last-minute changes.

Coordinating these counts is part of the same job as managing the guest list: the single source that tells you how many are coming also tells you what they eat.

Common mistakes to avoid

  • Asking only “vegetarian, yes or no” and forgetting vegans, who get a completely different plate.
  • Relying on a relative’s memory instead of a written figure.
  • Closing the count too early, before half your guests have even replied.
  • Overloading the guest with a long survey; three or four options is plenty.

If you are building the invitation from scratch, read the full guide to digital wedding invitations first, which shows how this question sits alongside the RSVP, Waze navigation and add-to-calendar in the same single invite.

We would love to build you a digital invitation that gathers all of this gently, with a dietary question worded for your exact event. Pick the package that fits you, and we will carry on together over WhatsApp until everything is ready.