Wedding Headcount: How to Get a Number Your Caterer Can Cook To

An accurate wedding headcount is not the number of RSVP replies you've received — it's the number of people each reply actually represents, tracked as heads rather than responses, locked in on a set date before the wedding, and adjusted with a small buffer for the guests who say yes and don't show and the ones who never replied and do.

Last updated: August 2026

Here is the mistake that costs the most money at a wedding: counting replies instead of people. One reply from a family of eight is eight seats and eight meals, not one. A caterer priced off "how many people responded" instead of "how many people are actually coming" is a caterer short by a table — and that table is usually the one with your favorite aunt and her four kids standing behind it.

How do I get an accurate wedding headcount?

Getting from "guest list" to "a number the caterer can cook to" is a five-step process, not a single tally on the morning of the deadline.

1. Ask for party size on the RSVP, not just a yes or no. Every reply should record how many people are actually attending under that name — a couple, a family of five, a "plus one" who's actually a plus three. A form that only captures "attending: yes" throws this information away before you ever see it.
2. Track heads and replies as two separate numbers. Your running total should show both "42 replies received" and "163 people confirmed" side by side. If your tracker only shows the first number, you are planning blind.
3. Set a real reply deadline, then chase what's left by name. Two to three weeks before you need to give the caterer a number, send a direct reminder to everyone still unanswered — by email, not a general re-post of the invitation.
4. Lock the final number 5–10 days before the wedding. This is the window most venues and caterers actually ask for, and it's late enough that most stragglers have replied, but early enough for the kitchen to shop and prep.
5. Build in a buffer, in both directions. Some of your confirmed "yes" replies won't walk through the door, and a few uninvited-but-expected relatives sometimes will. A small buffer absorbs both without you finding out the hard way.

Why isn't "who RSVP'd yes" the same as my headcount?

Because a reply is a household, not a person, and a "yes" on the day it's given isn't a guarantee of a seat filled on the night. The gap between replies and heads shows up twice: once when a single reply hides a party of six, and again when a small share of confirmed guests simply don't attend. The second gap is the one couples forget: a share of the guests who confirmed will not walk in — illness, a clashing obligation, a long drive that stopped being appealing. On a list of three hundred, a handful of no-shows among the confirmed is normal rather than exceptional. Neither gap is a rounding error once your list runs into the hundreds.

This is the reason a headcount built from "party size × replies" is a different, more reliable number than a headcount built from counting rows in an inbox.

How many guests will actually come to my wedding?

There's no fixed percentage that applies to every wedding — travel distance, the season, and how well you know your guests all move the number — but a decline rate somewhere in the range of one guest in five to one guest in four for a typical local wedding is a reasonable planning assumption, with steeper declines when a meaningful share of the list has to travel. Treat that as a starting assumption for your invite list size, not as a substitute for an actual RSVP count — the only number your caterer should ever cook to is the one built from real replies plus a small buffer, not a guess applied to your invitation list.

When should I give the caterer my final number?

Give it 5–10 days before the wedding, which is the window most caterers and venues request and the latest point that still leaves the kitchen time to shop and prep. Set your own RSVP deadline two to three weeks out so there's a real gap to chase down late replies before that final number is due. If your venue asks for a number earlier than that, use your confirmed heads plus your usual buffer rather than waiting for every last reply — a caterer needs a decision, not a moving target.

How do I count children and plus-ones in my headcount?

Count every name a guest lists on their reply, not just the household. If your RSVP form asks for party size and names, a "family of five" reply already gives you five heads, ages if you asked, and, if you're tracking meals, five meal choices — not one line item you have to chase for details later. This is exactly why party-size fields matter more than a plain yes/no button: a plus-one who turns into "plus three" without warning is a gap in your count you find out about on the RSVP form, not at the buffet.

What if guests show up who never RSVP'd?

It happens on almost every guest list, which is exactly why the buffer in step five matters — a handful of extra place settings costs far less than running short mid-service. The better fix is closing the gap before the wedding: keep your own invited list next to your RSVP replies so you can see exactly who's still silent, and send a direct reminder to those names specifically rather than a general repost that the people who already replied will see again for no reason. On the night itself, an entry check at the door — scanning each guest in as they arrive — turns your estimate into a fact instead of a guess, and shows you immediately if someone unexpected is standing in line.

Heads, not replies: how MumenLabs gets you a real number

This is the whole idea behind the RSVP built into a wedding invitation with online RSVP: the form asks for party size and, per event, who's actually attending — not a single yes/no button — so a reply from a family of eight is recorded as eight people from the moment it lands, not discovered later. The dashboard totals heads separately from replies, so you always know both "how many families responded" and "how many people are actually coming," and you can export that as a CSV for your caterer whenever you need it. You can also keep your own invited list alongside the RSVP replies and send a reminder email to anyone who hasn't answered yet, instead of guessing who's still silent.

And on the night itself, the gap between "said yes" and "walked in" closes for good: everyone who RSVP's gets their own QR entry pass, and a phone-based scanner at the door checks each guest in as they arrive. Your first 50 passes are included in the one-time $99 that publishes the whole invitation — the painted card, unlimited RSVP replies, and 18 months online, with no subscription and nothing recurring. A longer guest list adds passes by the hundred (+150 for $75, +400 for $180, +1,000 for $400, each size added once and stacking as your list grows), which is how 200 guests comes to $174 all in, 450 guests to $279, and 800 guests to $499 — the invitation, the link and every RSVP reply never cost more however long your list runs. Designing and previewing your invitation is free; a free account lets you save your draft, and you only pay when you publish. Guests never need an app or an account of their own, whether they're replying to the RSVP or scanning in at the door.

Frequently asked questions

What percentage of invited guests usually attend?

There's no single number that fits every wedding, but a decline rate of roughly one guest in five to one guest in four is a reasonable planning assumption for a typical local wedding, with a steeper decline when more of the list has to travel. Use that only to size your invitation list — the number you actually cook to should come from real RSVP replies, not an assumed percentage.

When should I give the caterer a final number?

Give your caterer the final headcount 5–10 days before the wedding — late enough that most guests have replied, early enough for the kitchen to shop and prep. Set your RSVP deadline two to three weeks earlier so there's real time to chase down the guests who haven't answered.

How do I count children and plus-ones?

Count every name a guest's reply actually lists, not just the household. An RSVP form that asks for party size — not just a yes/no — records a family of five as five heads and, if you're tracking meals, five separate meal choices, so nothing gets discovered late.

What if people turn up who never replied?

Keep a small buffer in your final number for exactly this — a few extra place settings cost far less than running short. Close the gap ahead of time by keeping your own invited list next to your RSVP replies and reminding the names still missing, then use a door check-in on the night to confirm exactly who actually walked in.

The number that matters is heads, not replies

A guest list is not a headcount, and a stack of RSVP replies is not a headcount either — the real number is party size added up, locked in on a set date, adjusted with a small buffer, and confirmed at the door. Build your wedding invitation with online RSVP and QR entry passes so every reply already counts heads instead of households, and hand your caterer a number they can actually cook to.

For the guests who won't reply at all, see what to do when wedding guests don't RSVP. To turn your final headcount into an actual door count on the night, read about QR entry passes and check-in for wedding guests. And if the list itself is the problem before you even get to counting replies, start with how to cut down your wedding guest list.