How to Get a Final Headcount for Your Wedding Caterer

Caterers bill per head, per event. Here is how to get a final headcount for your wedding caterer for every function, with dietary counts included.

By Mia · 2026-07-12

To get a final headcount for your wedding caterer, confirm attendance for each function separately instead of asking for one overall yes or no. Filter your guest list to a single event, count only the guests marked attending, add the dietary breakdown for that event, and export it. In Cordially Wed each guest RSVPs per event, so the Haldi lunch count and the reception dinner count are two different, live numbers you can hand over with confidence.

Why a single wedding total is useless to a caterer

Caterers do not cook for a wedding. They cook for a function, on a date, at a venue, for a number of plates. If Priya and Raj tell their caterer that 300 people are coming to the wedding, the caterer still cannot order a single crate of vegetables, because the Haldi lunch is close family and a few neighbors, the Sangeet is most of the invite list, and the reception is everyone plus plus-ones. Three functions, three numbers, and none of them is 300.

That gap is where money leaks. Quote for 300 at every meal and you pay for hundreds of plates nobody eats. Guess low and you have a room of hungry relatives at the event people will talk about for years. The fix is not a better spreadsheet formula. It is collecting attendance per event from the start, so the number you hand over is a count of real people who said yes to that specific function.

Confirm attendance one event at a time

Your working number for any function is simple: guests invited to that event, whose RSVP status for that event is attending, plus the seats their plus-ones and children represent. Everything else is noise while you are sizing that meal.

So work event by event. Open the guest list, filter to one function, filter to attending, and read the number. Then do it again for the next one. You will usually find something like this:

• Haldi: 62 confirmed, family and close friends only
• Sangeet: 184 confirmed
• Reception: 241 confirmed, including plus-ones

Count seats, not invitations. In many desi families one invitation quietly means four people, so make sure your yes count reflects heads at the table rather than households. If your RSVP asks how many are coming with each guest, this is already handled and you are just reading a total.

Give the kitchen dietary counts per category, per event

A headcount alone still leaves the kitchen guessing. What a caterer actually wants for each function is the total, then the split. Pure Veg, Jain, Halal, Kosher, vegan, gluten-free, and nut or other allergies, each with a number next to it.

Ask for this in structured options at RSVP, never as a free-text box. Free text gives you fifteen spellings of vegetarian and a note that says no onion garlic please tucked into a comment field, and someone ends up cleaning it by hand at midnight. Structured options give you a tally you can read in one glance.

The breakdown also shifts by event, which is why it has to be tied to the function and not to the guest alone. A Haldi lunch that is family heavy might run 48 Pure Veg out of 62. A reception with the couple's colleagues and college friends might run 70 Pure Veg out of 241, with 30 Halal and a handful of nut allergies that the kitchen needs flagged in writing, not mentioned in passing. Send both numbers, per function, and your caterer can actually plan a menu.

Export a clean CSV for each function

Caterers and venues do not want a login. They want a file, or a number in an email they can forward to their kitchen. So for each function, export a CSV of the confirmed guests for that event with the columns that matter: name, party size, dietary need, and any allergy note. Nothing else.

One file per function keeps everyone honest. If the reception venue and the Haldi caterer are different vendors, and they usually are, neither of them should be reading a spreadsheet full of guests who are not coming to their event. It also gives you a record. When a caterer says you told us 200, you can point at the file you sent, with the date on it.

Send the export with a short note that says which function it is for, the date, the venue, and the total. Keep the file naming boring and obvious, like reception-dinner-final-count. Boring files are the ones people find again in a hurry.

In the final week, chase only the stragglers for that event

Most caterers want a final number somewhere between three and seven days out, with a small buffer allowed on top. That last week is not the time to message all 300 guests again. It is the time to message the handful who are still pending for the one function you are locking.

Filter to the guests invited to that event whose status is still pending, and text only them. That is usually a dozen people, not a list. Keep it warm and short, name the event and the date, and give them a single link to tap. Anyone who has already answered hears nothing from you, which is exactly how it should be.

When the replies land, your count moves on its own. Then you send the caterer the final number with a note on your guaranteed minimum, and you stop touching it. If two cousins confirm on the day of, that is what the buffer is for.

How Cordially Wed gives you the number

This is the whole reason Cordially Wed tracks RSVPs per event rather than per wedding. Each guest is invited to the functions that apply to them, RSVPs to each one separately, and picks their dietary need from real options like Pure Veg, Jain, and Halal, with a field for allergies. You get a live per-event headcount that updates as replies come in, a dietary breakdown per category per event, and a CSV export per function to send your caterer. When it is time to chase, you filter to the guests still pending for that one event and message only them, by SMS or WhatsApp, with their replies landing in a single inbox.

Zola and The Knot handle a one-day Western wedding well, but they are built around one event, one RSVP, one headcount, so a Haldi lunch count and a reception dinner count are not something they can give you.

The guest list, per-event RSVPs, dietary tracking, seating chart, wallet passes, and your wedding website are all free. The only paid piece is unlimited guest texting: a one-time payment from $59, sized to how many unique guest phone numbers you are texting, with no subscription. You can send yourself a free test message first. Add your first guests and send your first invites at cordiallywed.com/invite.