• Multi-event
  • Guest list

Per-event invitations on a multi-day wedding

Link Invitation6 min read
Two stacks of envelopes of different heights side by side

Not everyone is invited to everything, and one invitation that lists all your events tells the people you left off exactly what they are missing. The way round it is to invite by event rather than by wedding: each guest is assigned the events that are actually theirs, and the link they open shows those and nothing else. This is about who is invited to what. Who replies to what is a separate setting, and worth keeping straight in your head from the start.

The card that names the party you are not going to

Picture a colleague opening your invitation. Church at ten in the morning. Reception at seven that evening. Homecoming lunch on the Sunday. They were only ever meant to come to the reception, and now they have read the whole weekend. Nothing on the page is untrue. It simply says more than you meant it to say, to somebody you did not mean to say it to.

Paper solved this with tiers of insert cards. The reception card went into some envelopes and not others, and the whole scheme depended on the right card going into the right envelope, by hand, late at night, by somebody who has done ninety of them already. It half worked. The other half was the guest who compared notes with a cousin and found out anyway.

Inviting by event instead of by wedding

The ticks sit beside the names on your guest list, not in the editor where you choose fonts and photographs, which is right: this is a decision about people, not about a page. You add your events once, then decide guest by guest which of them each person is invited to. A guest with nothing ticked is invited to everything, so you are not obliged to go through two hundred names to change the arrangements for eleven of them. As soon as you tick even one event for a guest, that guest is limited to exactly what you ticked.

What they open follows the same list. The schedule shows their events and no others. If they are replying, they see reply rows only for the events they are actually invited to. If every event they can see happens at one place, that is the place their invitation maps and gives directions to, so a reception-only guest is not sent to the address of a morning ceremony nobody expects them at.

Seats sit in the same place, because who comes and how many of them come is one thought with two halves. A household can carry six seats on the reception row and two on the homecoming row, those two being the parents without the children. Treat that number as an allowance and nothing more: a guest who is not meant to be at an event is handled by leaving the event unticked, never by whittling their seats down to nobody.

Drawing the lines so they hold

The mechanism is the easy part. Deciding who goes where is the part that takes an evening and one difficult phone call. Five habits tend to hold up once the family starts asking questions.

  • Work outwards from the smallest event. The twelve people at the family lunch are a list you can write exactly. The reception is everybody else, and that is a much easier sentence to finish.
  • Make the rule sayable in one line. “Both families and anyone staying over” survives a fortnight of questions. A rule with four exceptions in it does not, because you will not remember the exceptions when your mother rings.
  • Decide by household rather than by name. Inviting one half of a couple to the homecoming and not the other starts a conversation nobody wants to have.
  • Keep a group on one tier. Three of the eight people from one office at the family lunch is back around that office by Tuesday.
  • Draw the lines before you send. Adding somebody to an event later costs nothing. Taking an event away from a guest who has already seen it on their invitation is a different kind of task.

Wording it so nobody feels sorted

The invitation should never explain the tier. A guest who is invited to the reception does not need to be told there is a morning ceremony they are not part of. Write each event as though it were the whole invitation for the person reading it, with its own time, its own place and its own line of detail.

The trap is the copy that is the same for everybody. Your welcome lines and your story are written once for the whole invitation, so every guest reads them whatever they were invited to. The WhatsApp message works the same way with one exception: its placeholders fill themselves in per guest, naming only the events that guest is on and linking only their own card, but any sentence you type yourself goes out word for word to all of them. Mention Sunday lunch in either place and everybody has been told about Sunday lunch, and the careful ticking on the guest list counts for nothing. Keep shared wording about the wedding in general, and put event detail in the event’s own description.

Then decide who answers the question when it comes, because it will. Somebody will ask whether they should come to the morning as well. The kind answer is short, warm and the same from everyone in your family: the morning is a small family ceremony, and we would love to see you at the reception. Agree that sentence once and pass it round.

When to leave everybody on everything

Most weddings, honestly. If your whole list is invited to all of it, tick nothing and let every guest see the full schedule. There are three cases where per-event invitations are the wrong tool rather than an unused one.

If the small event is eight people at a dinner, that is not a tier, it is a second occasion. Burying it inside an invitation built for the whole list, even where nobody else can see it, gives a dinner the machinery of a wedding. Ring those eight, or write to them, the way you would for a dinner that had no wedding attached to it. If the second event is hosted by another family for their own circle, two invitations usually read better than one, because a homecoming run by the other side is its own occasion, not an appendix to yours. And if a real share of your guests will not open a link at all, no amount of structure fixes that. Print cards for those few, keep the links for the rest, and accept that you are running the guest list twice for one wedding.

Frequently asked questions

Can a guest tell they were left off an event?

Not from their own invitation. It shows the events they are invited to and nothing else, so there is no greyed-out row and no guest list to read. It is not a sealed envelope, though. Links get forwarded, and two guests who compare invitations will see two different schedules. Draw the lines so they hold up when they are discussed, because sooner or later they will be.

Can I change who is invited to an event after I have sent the links?

Yes. The personal link does not change, so there is nothing to resend. The next time that guest opens theirs, the schedule matches what you have set. Adding an event to somebody is painless. Taking one away from a guest who has already read it is the one to think about beforehand.

Do I have to set this for every guest on my list?

No, and you should not. A guest with nothing ticked is invited to every event on the invitation, which is the right answer for most of a list. Tick only the people whose invitation needs to be narrower than that.

Related: All features · Guest list

If your wedding runs to more than one event, invite each guest to the parts that are theirs. Start a draft, add your events and read the whole thing on a phone first; paying comes when you are ready to publish and send the links.
Start your invitation free