Wedding RSVP Tracker

A response-log example

A couple sends 92 invitations and records replies from cards, text messages and phone calls. After two weeks, 54 guests have accepted, 15 have declined and 23 still need a follow-up. Ten accepted guests chose a vegetarian meal and six have a named plus-one. Keeping those answers beside the invitation status gives the caterer one usable count later, while the couple can still see which households need a gentle reminder without exposing a public form or asking guests to create another account.

Treat the reply as a record, not a guess

When an answer arrives, record the date, attendance status and any meal or plus-one detail at the same time. A verbal yes that never reaches the list is what creates most last-minute confusion. Use a consistent status for each person rather than writing notes such as 'probably coming'. The tracker works best as the final record after you confirm an answer by card, text or call, not as a place to predict the guest count.

Keep households together before counting seats

A household can include two named adults, children or a permitted plus-one, and the invitation rule should be clear before you mark the response. Review the guest list entry when a reply changes the party size. That prevents an accepted household from becoming an inaccurate single seat in the catering count. If a guest asks about an unnamed plus-one, record the confirmed name only after the couple has decided the invitation allows it.

Use a clear CSV handoff

If you started with paper cards or a spreadsheet, use the guest-list template as the bridge. Import the completed CSV, keep the original as a dated backup, and export a fresh version when a caterer or planner asks for a count. A good handoff identifies confirmed seats, pending replies, dietary notes and the date it was exported. It does not pretend that the CSV is a public guest portal or a replacement for the couple’s communication.

Follow up without turning it into a campaign

A short, personal reminder is usually enough when the reply date approaches. Filter the pending names, decide who will contact each household, and record the reply as it comes in. Leave space for a guest who needs to decline or ask a practical question. The objective is a dependable headcount, not pressure. Once a venue’s final number is due, note that deadline in the timeline so the tracker has a visible stopping point.

Separate meal totals from final promises

Meal choices are valuable once your venue has confirmed how it wants them reported. Until then, treat the total as a working figure rather than an instruction to a caterer. Check that the accepted status and the meal answer belong to the same person, then compare the total with the guest count before exporting. This small review catches the common mismatch where a household responded but one member’s meal choice is missing.

Protect guest details in the handoff

Guest names, addresses and dietary information deserve a narrower audience than a general wedding update. Export only the columns a vendor needs, such as name, attendance and meal choice, and keep contact details with the couple or coordinator. Because this tracker is private to the device, sharing is an explicit action. That makes it easier to give a caterer a clean operational list without circulating a complete guest database in group chats.

How we make these planning assumptions: The response totals are direct counts from the statuses you enter. No attendance probability or automated outreach is applied, so confirm a guest’s answer before treating it as final.