How to track RSVPs without losing count

Spreadsheet or app?

A spreadsheet is fine for a party of 20 where you collect every answer yourself. It costs nothing, you already know how to use it, and you can sort and total it. Its weakness is that it only knows what you type into it, so every reply has to pass through you, and every text you forget to copy across is a wrong number.

An RSVP app reverses that: guests answer on a form and the tracker fills itself. That matters more as the list grows, when guests bring partners and children, and when anyone else (a co-host, a partner) needs to see the same count. Whichever you pick, pick one. Two lists drift apart within a week.

What to track for each guest

Track households, not individuals, because that is how people reply. Then record enough about each household that you never have to message them again to plan the food.

• Status: invited, coming, maybe, can't make it, or not answered.
• Party size, with names. "Sam + 2" tells you nothing at the door; "Sam, Priya, Leo" does.
• Children, counted separately. Many venues and caterers price children differently, and a kids' table needs its own count.
• Dietary needs per person: vegetarian, vegan, gluten-free, nut allergy, and anything else in their words.
• Date replied and how you reached them, so you know who to chase and where.

Set up an RSVP tracker in five steps

Do this before the invitation goes out, not after the first replies arrive.

1. List every household you are inviting, one row each, with how to reach them.
2. Choose the reply-by date: a week before your caterer, baker or venue needs a final number.
3. Put the reply-by date on the invitation itself, as a date.
4. Decide where answers count, and tell anyone helping you: replies are recorded there and nowhere else.
5. Add a totals row for adults, children and each dietary need, and check it every few days instead of recounting from memory.

Chasing people who have not answered

Expect a share of guests not to answer by the deadline, and do not take it personally: most meant to and forgot. Two reminders are enough. The first, about three days before the reply-by date, is light: "Hoping you can make it, let us know by Saturday." The second, the day after the deadline, is direct and gives a reason: "Ordering food on Monday, are you coming?"

After that, stop. A third reminder rarely gets an answer that two did not, and it starts to feel like pressure. Count a non-responder as a no for the food order and a yes for the chairs; it is cheaper to have a spare seat than a guest with nowhere to sit.

Send reminders the same way the invitation went out, and send them individually where you can. A group message that says "some of you haven't replied" is answered by the people who already did.

From replies to a final headcount

The final headcount is the number of people who said yes, adults and children counted separately, plus a judgement on the maybes. Caterers usually want it 7 to 14 days ahead, bakers about a week ahead, and venues whatever their contract says, so read it before you set your reply-by date.

Count about half of your maybes as coming unless you know better. Then give the caterer the adult and child numbers and the dietary list together, written down, in one message. A headcount without the dietary split leads to a second round of questions in the busiest week.

How PartyPal keeps the count

In PartyPal guests reply on the invitation link, so every answer lands in one list without passing through you. The number of who is coming is worked out once, on the server, and Home and the Invite tab both show that same number, split into adults and children, with the dietary needs of everyone who said yes. Two guests with the same name stay two guests.

If the app cannot reach the server, it keeps the last numbers and says it could not refresh; it never shows zero because a connection dropped. For the guests who have not answered, the assistant can offer to draft a reminder, and nothing goes out until you approve it.

Common questions