How to Set Up Separate RSVPs for Ceremony and Reception
Running different guest lists for your ceremony and reception? Here's how to set up separate RSVP links for each event without juggling two platforms.

Planning an event?
Invyt handles your RSVPs so you can focus on the celebration — not the spreadsheet.
Try Invyt free →Aunt Linda called the morning of your wedding. She was confused — she'd gotten your RSVP link, confirmed her attendance, and shown up to the church at 11am. For the ceremony. That she was never supposed to attend.
This exact scenario plays out at weddings every year. Not because couples are careless, but because most RSVP tools aren't built for separate guest lists. They give you one link and one guest list and leave you to figure out the rest with color-coded spreadsheets and increasingly desperate group texts.
The good news: you don't need two platforms. You need one that's actually designed for this.
Why Ceremony and Reception Guest Lists Are Often Different
Not every wedding has separate lists. But when they do, the gap is usually significant.
The most common scenario is a smaller, more intimate ceremony (immediate family, closest friends) followed by a larger reception open to extended family, colleagues, and acquaintances. According to The Knot's 2025 Real Weddings Study, the average US wedding now has around 115 guests, but ceremony attendance is often 30-40% smaller than the reception headcount.
Other situations that create separate lists:
- A religious or civil ceremony that only immediate family attends, followed by a restaurant reception for 80+
- A destination ceremony (just the wedding party) with a local celebration afterward for everyone who couldn't travel
- A second event: rehearsal dinner for the wedding party and parents, reception for the broader guest list
- Cultural weddings with distinct ceremonies (a nikah, a civil ceremony, a reception), each with different guest compositions
The problem isn't the separate lists. The problem is communicating the right invitation to the right people without accidentally inviting Aunt Linda to both.
What Happens When You Use One Link for Everyone
This is where things go wrong.
You create one RSVP event. You share the link. Some guests should be attending the ceremony and reception. Others should only come to the reception. But the link is identical: the same form, the same event details, the same "attending/not attending" question.
Now you're managing the distinction manually. You're cross-referencing your spreadsheet against your RSVP list to figure out which respondents were ceremony guests. You're fielding questions from reception-only guests who saw "ceremony starts at 11am" in the event details and are asking if they should arrive then too. And yes, you're occasionally dealing with an Aunt Linda situation.
WeddingWire's community forums are full of couples working around this with elaborate workarounds: duplicate Google Forms, two separate Evite events in different accounts, or paper invitations for one group and digital for another. All functional. All more work than necessary.
The cleaner solution is a single tool that treats each event as its own unit.
How Invyt's Wedding Hub Handles This
Invyt uses a structure called the Wedding Hub: one parent event (your wedding) containing multiple sub-events. Each sub-event has its own dedicated RSVP link, its own guest list, and its own response tracking. The ceremony and reception don't share a list. They're separate events that happen to belong to the same wedding.
Here's what that looks like in practice:
| Setup | Single-link approach | Wedding Hub sub-events |
|---|---|---|
| Guest lists | One shared list | Separate list per event |
| RSVP links | One URL for everyone | Unique URL per sub-event |
| Guest confusion | High (all see all event details) | None (each guest sees only their invite) |
| Tracking | Manual cross-referencing | Automatic per-event dashboards |
| Ceremony crashers | Possible | Not possible |
You can have up to four sub-events under a single wedding: ceremony, reception, rehearsal dinner, and after-party. Each one is independent.
Step-by-Step: Setting Up Separate RSVPs in Invyt
This takes about 10 minutes once you have your guest lists ready.
Step 1: Create your account
Go to invyt.app/signup and create a free account. No credit card required.
Step 2: Start a new Wedding Hub
From your dashboard, select "New Event" and choose the Wedding type. This creates the parent wedding and unlocks the sub-event structure.
Step 3: Add your ceremony as a sub-event
Fill in the ceremony details: date, time, venue, and any notes for guests. Set the ceremony guest list (add only the people invited to this event). Invyt generates a unique RSVP link for the ceremony automatically.
Step 4: Add your reception as a second sub-event
Repeat the process for the reception. Different date/time (or same day, different time), different venue if applicable, and a separate guest list. Your reception link is completely distinct from the ceremony link.
Step 5: Add any additional sub-events
If you have a rehearsal dinner or after-party, create those as additional sub-events. Each gets its own link and list.
Step 6: Share the right links with the right people
This is where the setup pays off. Send your ceremony link to ceremony guests only. Send your reception link to reception guests. Anyone invited to both gets both links. Because each event is separate, there's no risk of a reception-only guest accidentally seeing ceremony details.
Step 7: Track responses per event
Your dashboard shows RSVP counts for each sub-event independently. You can see who's confirmed for the ceremony, who's confirmed for the reception, and who hasn't responded yet. No spreadsheet required.
For a deeper look at how digital RSVP pages work in general, the complete guide to online wedding RSVPs covers the fundamentals.
What to Write in Each RSVP Invitation
The wording matters more than most couples realize. When guests receive a reception-only invite, you want them to understand immediately why they're getting that version, not a ceremony invite.
For ceremony guests, keep it straightforward:
"We're so excited to have you join us at our ceremony and celebration. Please use the link below to let us know you'll be there."
For reception-only guests, a brief note prevents confusion:
"We're having an intimate ceremony with immediate family, then celebrating with everyone we love at the reception. We can't wait to see you there."
Zola's guide to reception-only invitations covers the etiquette thoroughly. The short version: brief acknowledgment that the ceremony is private, sincere enthusiasm about the reception.
More RSVP wording options for different event types are in this collection of wedding RSVP wording examples.
Managing the Rehearsal Dinner Separately
The rehearsal dinner is the event most often forgotten in multi-event RSVP planning. It's smaller than both the ceremony and reception (usually just the wedding party, immediate family, and out-of-town guests), and it typically happens the night before.
Setting it up as a third sub-event in the same Wedding Hub keeps everything in one place. You're not logging into a separate platform or maintaining a third spreadsheet. The guest list is independent. Add the rehearsal dinner attendees, share that specific link in your wedding party group chat, and track responses alongside your ceremony and reception counts.
This is particularly useful for destination weddings, where the rehearsal dinner guest list often spans multiple cities and time zones.
A Note on Etiquette
One rule holds across all of this: everyone invited to the ceremony must also be invited to the reception. The reverse isn't required. You can absolutely invite people to just the reception, but you cannot invite someone to witness the marriage and then exclude them from the celebration.
This isn't just etiquette. Practically speaking, if a ceremony guest notices that the reception link wasn't sent to them, that's a conversation you don't want to have the week before your wedding.
Keep your ceremony list as a subset of (or at least fully included in) your reception list. Setting up a wedding RSVP website walks through related invitation planning decisions in more detail.
If You're Already Managing This in Spreadsheets
Migrating mid-planning is worth it. The manual cross-referencing that feels manageable at the start ("I have two tabs, it's fine") gets significantly harder at 80+ guests, and nearly impossible when you're also tracking dietary restrictions, plus-ones, and late responses.
Importing an existing guest list into Invyt takes a few minutes. After that, the sub-event assignment (which guests go to which events) is the main time investment. For most weddings, that's under an hour.
The comparison of free online RSVP tools includes a breakdown of which platforms support multi-event structures if you want to evaluate your options before committing.
Getting Started
Separate RSVPs for your ceremony and reception are not complicated to set up. The complexity came from using a tool that wasn't designed for it. With sub-events, you have one login, one dashboard, and the right link for every guest.
Create your free wedding hub on Invyt. The ceremony, reception, and rehearsal dinner can all be live in under 15 minutes.