Rehearsal Weekend RSVP Itinerary: One Page for Every Event

A rehearsal weekend RSVP itinerary lists every gathering—welcome drinks, rehearsal dinner, ceremony, and farewell brunch—and lets guests say yes to the ones they are actually invited to. One “I’ll be there for the wedding” text does not tell you who needs a Friday seat.

Keep the wedding reply on your wedding RSVP website, and treat side events as their own Yes/No lines. Our guides to a rehearsal dinner RSVP online and a wedding welcome party RSVP website cover single events; this page is the weekend view that ties them together.

Build the itinerary guests can scan

• Day and time in the guest’s local understanding (include time zone for destination weekends)

• Event name, venue, and who is invited (“wedding party and out-of-town family”)

• Attire if it differs from the ceremony

• Whether kids are included at that event

• A one-line note on food: heavy appetizers, seated dinner, or brunch

Order the list Friday to Sunday. Do not make guests reconstruct the weekend from five texts.

RSVP so each event has its own count

1. Ceremony and reception Yes/No (the main list)

2. Welcome party Yes/No, shown only to people invited

3. Rehearsal dinner Yes/No for the smaller list

4. Farewell brunch Yes/No if you are hosting one

5. Meal choice only where a plated meal exists

If the lists differ a lot, separate pages are fine—as long as each person gets the correct link. If most travelers are invited to everything, one page with clear toggles is easier to share.

Lodging sits next to the schedule

Out-of-town guests book nights based on which events they attend. Put the hotel block, code, and cutoff beside the itinerary, using the same approach as a wedding RSVP with hotel block info. Do not ask for flight numbers unless you are truly running a shuttle manifest.

Who sees which line

• Local ceremony guests do not need a rehearsal-dinner question

• Wedding-party partners need a clear yes on the dinner even if they skip the rehearsal itself

• Plus-ones follow the invitation, not the guest’s assumption

• Kids policy can change by event—say so on that line

Timeline for hosts

• When rooms open: publish the itinerary even if one menu is TBD

• With invitations: highlight reply-by dates per event if caterers differ

• One week before each vendor guarantee: chase only Pending guests for that event

• After close: export three counts, not one blended headcount

Common mistakes

• Assuming every wedding Yes is a welcome-party Yes

• Hiding Friday plans in a photo caption

• One meal question that actually applies only to Saturday dinner

• Changing the brunch time in a story and not on the RSVP page

• Sending a PDF itinerary that contradicts the live link

Quick checklist

• Each hosted event has its own Yes/No

• Invite scope is written on that event

• Times, venues, and time zone are visible on mobile

• Hotel block details match the nights guests need

• Exports split by event for each caterer

A rehearsal weekend itinerary on the RSVP page is how hosts stop treating Friday, Saturday, and Sunday as one blob. Guests see the plan, reply to their events, and you order food for the people who are actually walking in.