How to Track RSVPs Without Losing Count

Eighty-four invitations. Sixty-one yes, twelve no, eleven silent. The caterer wants a number by Friday and the number you give them is a bet, not a fact.

The mistake most people make isn’t losing track of replies — it’s treating “confirmed” as if it were the final figure, when the eleven non-repliers are where the risk actually lives.

Two numbers, not one

Confirmed is who has said yes. It’s a hard floor and it’s what you’d give a venue with a strict minimum.

Likely final is confirmed plus a realistic share of the outstanding replies. Most non-repliers eventually attend rather than decline — silence tends to mean “haven’t got round to it”, not “no”.

Give a caterer both numbers and ask when their final count is due. Most will accept an adjustment up to a few days before, and knowing that deadline changes how hard you chase.

Invitations, not people

Count invitations as units and record how many people each covers. An invitation to “Anil + 1” is one invitation and two people, and whether the plus-one exists is often unknown until the reply comes back.

This matters because tracking people directly means guessing at plus-ones, and tracking invitations without their party size means the headcount is wrong. Record both.

Capture dietary needs at the reply

Dietary requirements should be collected on the RSVP, not chased afterwards. Chasing a second time round is a much lower response rate — people who’ve already replied consider themselves done.

Ask on the invitation, record it against the guest, and note allergies separately from preferences. A caterer needs to treat a nut allergy differently from a vegetarian preference, and merging them into one “dietary” column loses that distinction.

Chasing without being a nuisance

Set a reply-by date on the invitation, roughly three weeks before for a large event.

One follow-up after that date is reasonable, and it works best as a direct message rather than a mass email — a personal message to eleven people gets a much better response than a group reminder.

After that, treat continued silence as a decline for planning, but keep a couple of places if the venue allows. People do turn up.

Common mistakes to avoid

• Giving the caterer only the confirmed figure and then adding people late at a premium.
• Recording “yes” without asking how many are coming.
• Collecting dietary needs as a separate exercise after the RSVPs.
• Chasing repeatedly, which annoys people without improving the count much after the first reminder.
• Keeping the list somewhere that isn’t backed up — export it before you need it.

How to do it with RSVP Tracker

The RSVP Tracker keeps confirmed and likely headcounts separate, in your browser.

1. Enter each invitation with the number of people it covers.
2. Update statuses as replies arrive, recording dietary needs at the same time.
3. Read the confirmed and likely final counts separately.
4. Give the caterer both, and ask when their final number is due.
5. Export the list — guest data stays in the page and isn’t saved between sessions.

Other event planning tools are in the tools directory.

Frequently asked questions

How many invitees typically don’t reply?

Expect around one in ten to need chasing, more for casual events. Building a chase date into the plan is more reliable than assuming silence means no.

What headcount should I give a caterer?

Confirmed attendance plus a realistic share of outstanding replies — and ask when their final number is due. Most accept a change up to a few days before.

Is guest data stored anywhere?

No. The list stays in the page and isn’t transmitted, which also means you should export it if you need it to survive closing the tab.

Final thought

Track invitations with party sizes, collect dietary needs at the reply, and give the caterer two numbers. That’s the whole system, and it prevents every version of the Friday-afternoon panic.

Try the free RSVP Tracker