When wedding RSVPs are still arriving, the safest way to manage catering is to keep confirmed attendance separate from estimates, track each guest’s meal details independently, and send one reconciled final count according to the agreement. That gives you a useful working picture without letting a planning guess turn into an order. A simple roster and a few clearly labeled scenarios can make the in-between period manageable.
Separate confirmed attendance from estimates
Start with three attendance groups: accepted invitations, declined invitations, and invitations still awaiting a response. Only the first group represents confirmed attendance. An unanswered invitation may eventually become a yes, but it is not yet a confirmed meal. Keeping those categories visible prevents the total from quietly blending known replies with expectations.
It can still be useful to maintain a provisional number for early conversations or room planning. Label it plainly as an estimate, record how it was calculated, and avoid presenting it as the final catering order. For example, a couple might note that 82 guests have accepted, 9 invitations are unanswered, and their current planning estimate is 86. The figures answer different questions: 82 is the confirmed count, while 86 is a working assumption. Neither should be confused with a later commitment under the catering agreement.
Give the roster one owner or a clear process for updates. When a response changes, update the original guest entry rather than adding a second line. This keeps the running total understandable and makes it easier to trace why it changed.
Track meals and guest details separately
Attendance, meal selection, and dietary requests are related but distinct information. Use separate fields for each rather than folding them into a single note or count. The attendance total answers how many people are coming; meal counts answer how many selections of each planned option are recorded; a request field preserves details that may need individual handling. Mixing these data can make a correct headcount look inconsistent with the menu totals.
Connect each response to a named guest or household entry. If someone changes an RSVP or selection, revise that entry and then refresh the relevant totals. Do not add a new meal to the tally while leaving the old selection in place. A spreadsheet can work, but the important feature is a consistent record—not a particular app. Restrict the working copy to the people who need it, especially when it contains personal dietary information.
Keep a short note for anything that is not yet settled, such as a guest who has accepted but has not chosen between the offered meals. That lets you distinguish a missing selection from a missing RSVP. It also makes the eventual handoff more useful than a bare number because the caterer can see how the guest count relates to the meal breakdown and relevant requests.
Use scenarios for unanswered RSVPs
When decisions must be made before every invitation is answered, create a small set of provisional scenarios rather than disguising uncertainty as precision. A low scenario can use confirmed acceptances. An expected scenario can add a stated assumption about the unanswered invitations, and a high scenario can show the upper planning case if more of those guests attend. The assumptions matter more than the labels: another person should be able to see which replies are confirmed and which numbers are hypothetical.
For instance, if 82 people have accepted and 9 have not replied, a planning sheet could show 82 as the confirmed floor and 91 as the maximum if every outstanding invitation became a yes. A separate expected estimate may be useful, but it should be identified as a planning judgment, not reported as a reply count. Use scenarios to think through the event’s likely scale or prepare a preliminary conversation; replace them with actual responses as they arrive. The highest scenario is not automatically the right order quantity. The agreement and the caterer’s stated process determine what number is binding.
Make the final handoff consistent
Before sending the final count, find the deadline and change terms in the catering agreement and identify who will submit the numbers. The deadline matters because an internal roster can keep changing even after the point when the caterer needs a committed figure. If a late RSVP or change arrives, its effect depends on the terms in place, so do not assume that every update can be accommodated in the same way.
Reconcile the attendance total against the guest-level roster, then check that meal selections and relevant requests use the same version of that roster. Send one clear summary through the agreed channel, with the final total, meal breakdown, and necessary notes distinguished from any remaining estimate. Save a dated copy of what was sent. If a later question arises, both sides can refer to the same handoff instead of comparing an old spreadsheet with a newer message.
Food For Thought’s directory page is available for readers comparing local options: view Food For Thought. Whatever caterer you choose, the core method is the same: preserve the difference between replies and assumptions, keep food selections attached to the right guests, and make the final catering commitment from a reconciled roster under the terms you agreed to.