Food preference tracking for mixed veg, non-veg and Jain guests

At my cousin's engagement lunch two years ago, I watched my chachi walk the length of a beautiful buffet — paneer, dal makhani, three kinds of sabzi, a live chaat counter — and come back to her seat with a plate of plain rice and curd. She's a strict Jain; no onion, no garlic, nothing from below the ground. Everything on that table had been cooked with the very things she doesn't eat. The hosts had spent lakhs on the food. For one of their most respected elders, none of it was edible. Nobody had asked, and she was far too gracious to say a word.

That plate of plain rice has stayed with me longer than any decor I've seen. Because the failure wasn't the caterer's — it was a tracking failure. Somewhere between the guest list and the kitchen, the single most important thing about a chunk of the guests — what they can actually eat — never got written down. This guide is the fix: how to collect food preferences without turning your invite into a form, how to hold them in one place, and how to hand your caterer numbers instead of a shrug. It's the piece I wish someone had given the hosts of that lunch.

Preference is not one axis — it's four

The mistake most of us make is treating food as a veg / non-veg toggle. In an Indian mixed gathering, that's nowhere near enough. On any real guest list you're quietly juggling at least four different things, and they don't stack neatly:

• Pure vegetarian — no meat, egg, fish. The default assumption for many families, but never safe to assume.
• Non-vegetarian — but with sub-rules that matter: some eat chicken and mutton but no beef or pork, some are fish-only, some eat egg but not meat (the "eggetarian" you'll meet at every function).
• Jain / no onion-garlic (satvik) — no onion, no garlic, nothing from below the ground (potato, carrot, radish, ginger for the strict). This is a whole separate cuisine, not a subtraction from the veg menu.
• Allergies and medical — the nut allergy, the lactose intolerance, the diabetic elder who needs the sweet counted separately. Rare, but the one you cannot get wrong.

These overlap in awkward ways. A guest can be non-veg and have a nut allergy. A family of six can be four veg, one Jain grandmother, one eggetarian teenager. If your tracking has one column, you've already lost that grandmother's plate. Capture the axis that actually applies, per person — not per family, per person.

Ask once, ask early, ask specifically

Here's the trap I fell into at my own first big function: I put "please let us know any dietary requirements" at the bottom of the invite and felt thorough. Almost nobody replied to it. Not because they didn't have preferences — a vague open-ended line reads as optional, and people skip optional.

Preferences come out when you ask a specific, closed question at the same moment you ask people to RSVP. When someone is already telling you "haan, 4 log aa rahe hain," that is the exact moment to ask "veg ya non-veg, aur koi Jain ya no-onion-garlic?" You'll get an answer, because they're already in the replying frame of mind. Ask two weeks later, separately, and you're chasing people twice.

A few rules that make the answers usable:

1. Ask for the split within a group, not one label for the whole family. "Aap log veg ho?" gets you "haan mostly" — useless. "Kitne veg, kitne non-veg, koi Jain?" gets you "3 veg, 1 Jain."
2. Name the categories you actually cater. If you're not doing a Jain counter, it's kinder to know that a Jain guest is coming so you can arrange one specific dish, than to discover it at the buffet.
3. Make no-onion-garlic its own option. A lot of guests won't call themselves "Jain" but genuinely don't eat onion-garlic on festival days or for religious reasons. Offer it explicitly and they'll tick it.

A tracking table you can start tonight

Whatever holds this — a notebook, a shared sheet, a wall of sticky notes — the columns matter more than the tool. This is the structure I use now, and it survives contact with a real guest list:

Guest / family	Total heads	Veg	Non-veg	Jain / no onion-garlic	Notes (allergy, medical)
Sharma family	4	3	1	0	—
Chachi & chacha	2	0	0	2	Strict Jain, no potato
Rohan (cousin)	1	0	1	0	Fish only, no chicken
Mehta family	5	2	2	1	1 nut allergy (child)
Dadi	1	1	0	0	Diabetic — no-sugar sweet

The power isn't the rows, it's the column totals. Sum them and you don't have "around 60 log" — you have "38 veg, 14 non-veg, 6 Jain, 1 nut allergy, 1 diabetic." That is a sentence your caterer can actually cook to. The difference between that and a headcount is the difference between my chachi eating and my chachi not eating.

Notice this sits right on top of your regular headcount work. If you're already tracking who's coming and how many — and if you've read caterer count tiers, you know why that number is money — the preference columns are just three more fields on the same row. Don't build two systems.

WhatsApp scripts that get you the split

Copy these, swap the names, send. The goal every time is a number per category, not a vibe.

Template 1 — asking at RSVP time (Hinglish)

Namaste 🙏 Neha di ki engagement 24th ko hai, aur main khaana finalise kar raha hoon. Aap batayenge — kitne log aa rahe hain, aur usme kitne veg, kitne non-veg, aur koi Jain ya no onion-garlic? Bas ek line: jaise "4 log, 3 veg 1 Jain". Isse kisi ki bhi plate miss nahi hogi 🙏

Template 2 — the specific Jain / satvik check

Ek chhoti si baat — kya aap ya ghar mein koi Jain khaana ya bina pyaaz-lehsun ka khaate hain? Agar haan, toh main alag se arrange kar dunga, aap bilkul chinta mat karna. Bas bata dijiye kitne log.

Template 3 — allergy and medical, asked gently

Aur agar kisi ko koi food allergy ho (jaise nuts) ya sugar/BP ka dhyaan rakhna ho, toh please bata dijiye. Hum uske hisaab se ek-do cheezein alag rakh lenge. Better hai pehle se pata ho.

Template 4 — the group reminder, 48 hours before the count locks

Sab log 🙏 caterer ko count Wednesday shaam tak dena hai. Jinhone abhi tak nahi bataya — please bas itna reply karo: kitne log, kitne veg / non-veg / Jain. Aapki ek line se poora khaana set ho jaata hai, aur kisi ke saath plain-rice wali situation nahi hoti 😅

That last emoji line does real work — it names the fear (a guest stuck with nothing to eat) lightly, and people respond to it. If the silent repliers are your problem, the psychology of the non-answer is its own subject — I've written about why guests don't RSVP and how to convert a "dekhte hain" into a real number, and every bit of it applies double when you also need a food preference.

Turning preferences into a caterer brief

Collecting the data is half the job. The other half is handing it over in a form the kitchen can execute. When I call my caterer now, I don't say "make some Jain food also." I give three things:

• The category counts. "38 veg, 14 non-veg, 6 Jain — cook Jain as a separate batch, no onion-garlic, no potato."
• The non-negotiables, flagged loudly. The nut allergy and the diabetic aren't quantities, they're rules. "One child with a serious nut allergy — please keep the desserts nut-free or clearly separated." A good caterer will thank you for this; a careless one will forget, which is why you say it twice.
• Labels at the buffet. Ask for small cards — "Jain", "No onion-garlic", "Contains egg" — propped by the relevant trays. This is the cheapest, highest-impact thing you can do. It lets guests self-serve safely and spares your Jain grandmother from interrogating a waiter mid-function.

One honest caterer truth: a proper Jain preparation is usually a separate deg and separate labour, so caterers often price it per portion or set a minimum. That's fair — it's a different kitchen discipline, and exactly why the count matters. "6 Jain plates" is a number they can quote and cook. "Kuch Jain log bhi aayenge" is a number they'll guess at, and guessing is how you end up with plain rice.

A pre-count checklist for mixed preferences

Run this the day before you commit numbers to the caterer:

• Every family row has a per-person split, not one label for the group.
• Jain / no-onion-garlic is a separate column, not folded into "veg".
• Non-veg sub-rules noted where they matter (egg-only, fish-only, no beef/pork).
• Every allergy and medical note is flagged in the notes column, in writing.
• Column totals are summed into category counts I can read aloud to the caterer.
• I've confirmed whether Jain food is a separate batch and how it's priced.
• I've asked for buffet labels on the trays.
• The dessert / sweet is checked separately for nut and sugar issues.

Ten minutes with this list is the difference between a guest who eats and a guest who smiles politely over an empty plate.

When you're overthinking it

Not every gathering needs this apparatus. If you're having twelve people over for a Sunday lunch and you already know your family — you know Bhabhi is Jain and Rahul won't touch mutton — write it on the back of an envelope and move on. Building a tracking table for a dozen people you know by heart is effort spent where there's nothing to gain. A notebook, or just your memory, is genuinely the right tool.

The structure earns its keep when the list crosses maybe forty guests across families you don't all know intimately — the wedding side you've met twice, the office group, the neighbours. That's where preferences hide, where a family of six has one Jain member you'd never guess, and where a live per-person count across scattered WhatsApp threads becomes genuinely hard to hold in your head. That's the exact spot we built Inyeet for — each guest replies to their own invite link, their headcount and food preference land as structured fields on one dashboard instead of thirty "haan aa rahe hain" messages, and the category totals add up on their own. If you're hosting something that size, you can join the early access list. If you're not, the table above and one firm deadline will carry you just fine.

The one thing to take away

Food preference is not a footnote on the invite — for the people it affects, it's the whole event. Ask specifically, ask at RSVP time, and hold the answers per person in columns you can total. Do that, and you'll never watch a respected guest walk a buffet twice and come back with plain rice. The food you paid for will actually reach the people you invited — which, when you think about it, was the entire point of feeding them.