How to Track Wedding Dietary Requirements for Guests: A Guide

A calm, practical way to collect, organize, and share guest dietary needs across a multi-day wedding, so the right plate reaches the right person every time.

By Mia · 2026-06-28

Tracking what your guests can and cannot eat sounds small until you are three days deep into a wedding, feeding a few hundred people across a Mehndi lunch, a Sangeet dinner, and a Reception, and someone at table 6 is staring at a plate they cannot touch. Dietary needs are not an afterthought at a desi wedding, they are a matter of respect, faith, and safety. The good news is that with a little structure early on, you can keep every requirement straight and hand the caterer a clean, confident list without chasing aunties on WhatsApp the night before.

Start with the categories that actually come up at desi weddings

Before you collect a single response, decide on the language you will use so answers stay consistent. A generic "any allergies?" box gets you mush. Build a short, clear set of options instead. For most South Asian weddings that means: Pure Veg, Jain (no onion, no garlic, no root vegetables), vegetarian, vegan, Halal, and a free-text line for allergies like nuts, dairy, gluten, or shellfish. Add a "no restrictions" option too, so a blank does not get mistaken for an unanswered guest. Keep faith-based and allergy-based needs in separate fields. A Jain guest and a guest with a nut allergy need different things from the kitchen, and collapsing them into one note loses information your caterer genuinely needs. Agreeing on these labels up front means every response maps cleanly to a kitchen instruction later.

Collect dietary info at RSVP, not by chasing people later

The single biggest time-saver is asking the question at the moment someone confirms they are coming. When a guest taps "yes, I'll be there," that is when they are thinking about the event and most willing to answer. Bolt a dietary question right onto your RSVP so it arrives with the headcount, not as a separate ask weeks later. Make the field optional but visible, with the preset categories above plus an "other" line. For a multi-day wedding, remember that attendance differs by event: a cousin may come only to the Reception while grandparents attend everything. Ideally you capture dietary once per guest, then carry it to whichever events they actually attend, rather than asking the same person five times. Collecting at RSVP also means you are gathering needs from confirmed guests only, so you are never counting plates for people who never replied.

Keep one source of truth, not five spreadsheets

The mess usually starts when dietary info lives in three places: a few WhatsApp replies, a Google Sheet your sister keeps, and notes scribbled during phone calls. Pick one list that holds everything, and make it the only place anyone updates. Each guest row should carry their name, which events they are attending, their table, and their dietary field. When your mother remembers that Uncle Raj went vegetarian last year, that change goes in the one list, immediately, so it never gets lost in a chat thread. A single source also lets you see patterns at a glance: how many Jain meals total, how many Halal, how many nut allergies. Those totals are exactly what your caterer will ask for, and pulling them from one clean list takes seconds instead of an evening of cross-referencing.

Filter and count by event so the caterer gets exact numbers

Caterers do not need a story, they need counts per meal. "Sangeet dinner: 142 guests, 18 Pure Veg, 9 Jain, 22 Halal, 3 nut allergies" is the format that prevents mistakes. To produce that, you need to be able to slice your guest list two ways at once: by event and by dietary need. If your list supports saved filters or segments, build one for each combination you care about, for example "attending Reception AND Jain," and let the count update itself as people RSVP. This matters most across a multi-day wedding where the same person eats at different events with you. Give each caterer or kitchen a per-event breakdown rather than one master list, and confirm the numbers a few days out once RSVPs settle. Flag severe allergies separately and in writing, since those are a safety issue, not a preference, and the kitchen needs to handle cross-contamination, not just swap a dish.

Put each guest's dietary need where the kitchen can see it

Knowing the totals is half the job. The other half is making sure the right plate reaches the right seat on the day, when you are in a lehenga and nowhere near the kitchen. Two things make this work. First, your seating chart and your dietary list should be linked, so the table layout you hand to catering shows which seat needs what. Second, give the guest something they carry themselves. A wallet pass on a guest's phone that shows their schedule, table, and dietary note means that if a server is unsure, the guest can simply show their screen. It also quietly reminds the guest of their own table and timing, which cuts down the day-of questions aimed at you. The goal is that no one has to find you to answer "which table, and what can they eat," because the answer is already in two places: the kitchen's printout and the guest's pocket.

Build in a final check before each event

Dietary needs drift. People change diets, plus-ones get added, and someone always forgets to mention a new allergy until the week of. Schedule one light review before each major event rather than trusting the list you froze a month ago. A simple rhythm works well: a few days before the Mehndi, the Sangeet, and the Reception, pull the dietary counts for that specific event and send them to whoever is cooking. If your guests can still update their own RSVP and dietary line up to that point, even better, because corrections flow in without you fielding calls. Keep a short "watch list" of the few guests with serious allergies and confirm their meals personally with the caterer, by name. Everything else can run on counts, but a nut allergy or a celiac guest deserves a named, double-checked plate.

How Cordially Wed keeps all of this in one calm place

All of the above lives together in Cordially Wed, a free guest-management platform built for multi-day desi weddings. You import your guest list once, and the dietary question rides along with your RSVPs by SMS or WhatsApp, with presets for Pure Veg, Jain, Halal, vegetarian, vegan, and a line for allergies. Every answer lands on one guest list you can filter and count by event, so you can hand each caterer an exact per-meal breakdown. Each guest's table and dietary note also appears on their Apple or Google Wallet pass and flows into your seating chart, so the right plate finds the right seat without anyone hunting you down. Everything is free except unlimited guest texting, which is a one-time $49 after your first 15 texts. If you would like to start by adding your guests and sending the first invites, you can do that at cordiallywed.com/invite whenever you are ready.