The Wedding RSVP Checklist: What to Do at 30 Days, 7 Days, and 1 Day Before

The difference between a smooth wedding and a chaotic one is not luck -- it is what you did at 30 days, 7 days, and 1 day before.

For weddings of 200 or more guests, the guest management process is not a single task. It is a sequence of coordinated decisions, each one building on the last. Miss a step at the 30-day mark and you will feel it on the wedding day when your caterer is short by 40 covers and three guests with nut allergies never flagged their dietary needs.

This checklist is designed for both couples managing their own guest list and Wedding Organizers running the coordination layer. Each task is assigned to a responsible party -- the couple, the WO, or the venue -- so nothing falls through the gaps.

The Manual Reality vs. The Digital Reality

Before the checklist, it is worth naming the environment you are working in, because it changes everything.

Manual process: RSVP confirmations arrive across WhatsApp, phone calls, and paper cards. The WO or couple manually reconciles them into a spreadsheet that is out of date the moment someone replies at 11pm. Dietary notes live in someone's camera roll. The final headcount is a best guess.

Digital process: Every RSVP is captured in a centralized dashboard the moment a guest responds. Dietary and accessibility data is structured and filterable. Automated reminders go out without anyone pressing send. The headcount is live, accurate, and exportable to the caterer in one click.

Every task below assumes you are building toward the digital workflow. If you are still working manually, use this checklist to understand exactly where the manual process will cost you the most time.

30 Days Before: Set Up the System

This is the foundation. Everything at 7 days and 1 day depends on decisions made here.

Couple's responsibilities:

• Finalize the guest list with full names, contact numbers, and email addresses. No duplicates, no 'plus one TBD' entries left unresolved.
• Define RSVP deadline: set it 21 days out from the wedding, not 7. You need buffer time for follow-up.
• Confirm which dietary categories you are tracking: vegetarian, vegan, halal, kosher, nut-free, gluten-free, shellfish-free, and a free-text 'other' field.
• Confirm accessibility needs: mobility assistance, hearing loops, seating proximity to exits.

WO's responsibilities:

• Deploy the digital invitation with RSVP form live by day 30. Every day of delay compresses your follow-up window.
• Set up the RSVP tracking dashboard with real-time response rates visible. Target metric: 60% response rate by day 21.
• Configure automated reminder triggers: send a first reminder at day 24 (6 days after initial send), second reminder at day 21 (RSVP deadline day).
• Collect the vendor headcount requirements from caterer, furniture hire, and AV team. Know the minimum numbers each vendor needs and by when.

Venue's responsibilities:

• Confirm the venue's operational headcount ceiling (this is different from the invitation count -- factor in staff, vendors, and wedding party).
• Provide the dietary accommodation process: who receives the dietary list, in what format, and by what date.

Data to track at 30 days:

• Total invited count
• RSVP response rate (live)
• Dietary restriction breakdown
• Accessibility requests logged

7 Days Before: Confirm and Lock

At this point, the RSVP window is closed. You are no longer collecting -- you are confirming, reconciling, and submitting.

Couple's responsibilities:

• Review the non-responder list and make personal contact (call, not message) for any guests whose attendance significantly affects seating, table count, or catering. Prioritize VIP and family tables first.
• Make final decisions on any 'pending' RSVPs. A non-response at 7 days is a no.
• Approve the seating chart draft based on confirmed numbers.

WO's responsibilities:

• Export the confirmed headcount from the dashboard and submit to the caterer by day 7. Most caterers require final numbers between 5 and 7 days out.
• Submit dietary and accessibility data to the venue catering manager in a clean, structured format -- not a screenshot of a spreadsheet.
• Share the confirmed seating plan with the venue event coordinator and the day-of floor manager.
• Build the emergency contact sheet: one document with names, roles, and direct mobile numbers for the couple, both sets of parents (if relevant), the venue coordinator, the caterer's lead, the AV operator, and the transport coordinator.

Venue's responsibilities:

• Confirm receipt of final headcount and dietary list.
• Walk through the room layout with the WO based on final numbers. Adjust table count if the confirmed guest count shifted more than 5% from the estimate.

Data to track at 7 days:

• Final confirmed attendance count
• Final dietary breakdown (submitted to caterer)
• Seating chart version number and approval status
• Vendor submission timestamps (proof of delivery)

1 Day Before: Lock, Brief, and Prepare for the Unexpected

Nothing new gets added to the system after this point. The goal today is clarity and calm.

Couple's responsibilities:

• Freeze the guest list. No more additions. Any last-minute walk-ins are managed at the door by the WO, not added to the seating plan.
• Confirm that all immediate family members know their arrival time, parking instructions, and holding room location.

WO's responsibilities:

• Print one physical backup of the final guest list with table assignments. Technology fails; the backup does not.
• Brief the check-in team: each person should know their assigned entrance zone, how to handle name-not-on-list situations (escalate to WO, never turn away at the door), and where to direct accessibility guests.
• Activate the day-of check-in mode on the digital guest management system: switch from RSVP tracking to arrival tracking. Each check-in should update the live count.
• Distribute the emergency contact sheet to every vendor lead. This is not optional.
• Set a last-minute changes protocol: any amendment after 6am on the wedding day goes through the WO only. Not the couple. Not the parents.

Venue's responsibilities:

• Confirm the dietary meal tagging system is in place (place cards, colored stickers, or digital plate flags).
• Brief the front-of-house team on the check-in flow and the location of the accessibility seating sections.

Data to track on the day:

• Live arrival count vs. confirmed count
• No-show rate (useful for your post-event vendor reconciliation)
• Any last-minute dietary changes flagged at the door

The 80% Rule for Catering Submissions

If your confirmed RSVP count is 220 and your invited count was 280, do not submit 220 to the caterer. Submit 220 plus a 5% buffer (approximately 231 covers). Last-minute arrivals, plus-ones who were never formally confirmed, and vendor meal adjustments consistently push final attendance above the confirmed RSVP number by 3 to 8 percent at large weddings.

Discuss this buffer with your caterer in advance. Most are happy to accommodate it when given enough notice.

A checklist like this is only as useful as the system behind it. When the RSVP data is scattered across WhatsApp and paper cards, executing every step above requires manual effort that compounds across hundreds of guests. When it is centralized -- one digital invitation, one live dashboard, one exportable data set -- each milestone becomes a checkpoint, not a rescue operation.

Wedwebs builds the digital infrastructure that makes this checklist effortless to run. If you are planning a wedding of 200 or more guests and want to see what a properly structured guest management system looks like in practice, we would be glad to walk you through it.