Approving an RSVP is the moment a reply becomes a chair, a meal and a favour you are paying for. Sign-ups that arrive through your invitation’s public page land in a queue and count for nothing until you approve them: not your totals, not your seating plan, not the numbers your caterer is waiting on. Here is what that gate protects, what to check before you approve, and how to clear a queue without letting it sit.
What approval actually protects
Three things, and they are all expensive. The first is your budget. Every approved head is a cover, a meal and a favour, and a reply form with no gate on it is a budget with the door left open. The second is your seating. Approved guests flow into the table planner, and someone you never checked should not be holding a chair at table four. The third is your catering numbers. The dietary answers you eventually hand over are totalled from approved guests only, so an unapproved vegetarian is invisible in the count your caterer reads.
Almost nobody in that queue is trying to get away with anything. One name arrives twice because the first submit did not visibly do anything, so the sender pressed it again an hour later. Another belongs to a work friend who was shown the link across a desk and read it as a general welcome. A third has put six in the party box after one very warm conversation at somebody’s birthday. None of that is bad faith. All of it turns into covers on an invoice if it goes into your totals unread.
Where the pending replies come from
Only sign-ups from the public page go through approval. A guest you added yourself and sent a personalised link to is already someone you invited, so their reply counts as soon as they send it. There is nothing there to moderate. The queue holds people who reached the invitation without a link of their own and filled in the form.
That distinction matters when you are deciding how to share your invitation. If you only ever send personal links, one guest at a time, you may barely see a pending reply. The queue fills when the invitation gets forwarded, or pasted into a family group where fifty people can see it.
What to check before you approve
Open the queue with your own guest list beside you. Four questions settle nearly every case.
- Are they already on your list? A household you have recorded once can easily arrive again through the public form, and then you are counting the same two people twice. Check the name, then check the partner’s name.
- Does the party size make sense? The number they entered is the number you will cater for. A guest who put down four when you had them as two is not necessarily wrong, but that is a conversation, not a tap.
- Were they invited at all? A public form does not know your list. Someone can be a thoroughly nice person and still not be a person you meant to invite.
- Has this reply changed? A submission that has been sent more than once is tagged as updated, and a reply from someone you rejected before is tagged as previously rejected. Both are worth reading properly before you decide.
When you are unsure, do not reject. Leave it pending and ask: the phone number they submitted sits on the row beside their answer, so a message is cheaper than a decision you regret. A reply left pending costs you nothing while you wait. A wrong approval costs a cover, and a wrong rejection costs an apology.
What changes the moment you approve
Approving is not filing. It moves a person into every count you use. From that moment they appear in your attending total and your head count, on your printed guest list and name tags, in the table planner as someone you can seat, in the table lookup guests use on the day, and in the planning tools that work off head counts. If the reply entered a larger party than you had recorded, approving raises the head count to match what they committed to, because that is the number you will be feeding.
Rejecting does the opposite, and it is not a deletion. The reply stays where you can find it, drops out of your totals, and any seat that person was holding is released, because a rejected guest should not keep a chair a real guest needs. If you reject someone by mistake, the row is still there to approve, and approving restores them to every count. The released seat is the one thing you have to give back yourself.
Clearing the queue without letting it sit
The failure here is almost never a bad decision. It is three weeks of not opening the queue, a venue asking for the final head count by the end of the week, and an evening spent trying to remember which of eleven names you actually know. Build the habit instead: when you sit down to look at replies, clear the pending ones first, before you read anything else. Deciding on a reply the day it arrives is far easier than reconstructing a whole queue in the last fortnight.
Caterers and venues tend to want the final count somewhere between a week and a fortnight out, and plenty ask earlier than that. Take the range as the shape most contracts happen to have, not as a number anyone has measured; your own contract is the only authority. Get the exact date from your caterer, mark it, and work backwards. Anything still pending a few days short of it needs a phone call, not another week of waiting.
Two things keep the queue small in the first place. Send personal links to everyone you genuinely intend to invite, so most replies never need reviewing at all. And be deliberate about where the public link travels, because the wider it goes, the more of your evening you spend deciding who is real. If you want the picture of how replies reach you in the first place, the RSVP overview covers that side.
What approval will not do for you
It settles whether a reply counts. It does not settle who someone is. There is no identity check behind the button. You are matching a name and a number against your own list and using your judgement, which is exactly as reliable as your list is.
It also does nothing about the guests who never go near the form. A queue can only moderate replies that were actually submitted, and the relatives who answer down the phone, or across the table at a family lunch, never appear in it. Somebody types those replies in by hand, and nothing reviews them afterwards. If a fair share of your list answers that way, the real work is the phone call and the pen, and the queue is a small corner of the job rather than the job.
And if your list is fifty people you all know personally, approval is a formality. Approve them as they arrive and put your attention into the seating, where it is needed.
Frequently asked questions
Do replies from a guest's own link need approving?
No. Guests you added yourself are already invited, so their reply counts as soon as they send it. Approval applies only to people who signed up through the public page without a link of their own.
What happens if I reject someone by mistake?
Nothing permanent. The reply is kept rather than deleted, and approving them afterwards restores them to your totals. Rejecting does release any table seat they were holding, so you may need to seat them again.
Someone replied twice with different numbers. Which one counts?
The latest one is what you see in the queue, tagged so you know it has been updated. Approving takes the party size on that most recent reply, so read it before you decide rather than approving from memory. Once someone is approved, a later edit from the same number updates their answer without returning to the queue.
Related: How RSVPs work