Getting an accurate headcount: RSVPs and final numbers

Ask a venue where they lose money on functions and eventually someone says numbers. Not the price — the count. Catering for 120 when 96 turn up is a direct loss, and it happens because the number the kitchen worked from was a guess dressed up as a confirmation.

The underlying problem is that the guest count is collected by the client, from their guests, and lands with you last. You are third in a chain you don't control. What you can control is when you ask, what you ask for, and what happens when the answer doesn't arrive.

Where the number actually comes from

A guest count moves through three states, and venues get into trouble by treating them as one:

• Estimated — the number on the enquiry. Useful for quoting and room allocation, useless for ordering food.
• Indicative — the client's count once invitations have gone out and replies are coming in. Directionally right, still moving.
• Confirmed — the number you cater and charge to, locked at an agreed date.

If your paperwork has one field called "guests", staff will read whichever number is in it as confirmed. Keeping the estimate and the confirmed count visibly separate is most of the fix.

Where to put the cut-off

Seven days out is the common answer and usually the right one for plated service. Earlier than that and the client hasn't heard from everyone, so you get a number that keeps changing after it was supposed to be final. Later, and your kitchen is ordering under pressure and your staffing roster is already published.

Two rules make the cut-off hold:

• Numbers can go up after the cut-off, not down. Adding two guests is a catering problem you can usually solve. Removing twelve is a loss you can't recover.
• The cut-off is the same date as the balance. Tie the two together and the client has one deadline to remember, and the amount they are paying is the amount you are catering. Setting them on different dates guarantees the invoice and the kitchen disagree.

That second rule is the reason the cut-off belongs in your deposit policy rather than in an email — it is a payment term as much as an operational one.

Don't become the client's admin department

The moment a venue starts fielding "can I add my cousin" emails, it has taken on the client's job. Every one of those messages is a chance for the count in your system to drift from the count in theirs.

Two approaches work, and they suit different clients:

Give the client one channel and one deadline

For most functions this is enough. The organiser collects their own replies however they like, and sends you one number by the cut-off. Your job is to make the deadline unmissable — stated at booking, repeated in the reminder, and tied to the balance.

Collect the RSVPs yourself

For weddings and larger functions, taking the RSVP off the organiser is a genuine service. You send a link, guests respond directly, and the replies land against the booking. The organiser stops maintaining a spreadsheet, and you stop working from a number that has been transcribed twice.

This also solves the dietary problem. Asking each guest for their own requirements at RSVP time produces a far better list than asking the organiser to remember them all a week out — and it puts the allergy information on the booking, where the kitchen can see it.

What to ask each guest for

Keep it to what changes what you do on the night:

• Name — so the count reconciles to actual people, not a tally
• Attending or not
• Guest type — adult, child, supplier — because they are usually priced differently
• Meal choice, if the package offers one
• Dietary requirements and allergies, free text

Resist the urge to add song requests and seating preferences. Every extra field lowers the completion rate, and the count is the thing you actually need.

Chase before the deadline, not after

A reminder sent two days before the cut-off recovers numbers. One sent the day after it passes starts a negotiation. The cadence that works is unremarkable: confirm the deadline at booking, remind at two weeks, remind again two days before, then close it.

None of that should depend on someone remembering. It is the clearest case on the whole booking for automation — fixed dates, fixed message, no judgement required.

How this fits together

In ezybooked you can generate an RSVP link for a booking and let guests submit directly; the responses land against that booking rather than in an inbox, so the guest list, the dietaries and the count all sit with the event. Reminders send on schedule, and the confirmed count is the figure the invoice and the run sheet both read from.

That last part matters more than the RSVP collection itself. A count that lives in one place cannot disagree with itself — which is the same principle behind not double-booking the room. See the features page for RSVP, packages and automated reminders.

The short version