For whoever is left holding the small list
Twenty-two people, a rehearsal time, a restaurant that wants a number by Friday, and four of them flying in that afternoon. One page with the address and a reply button handles all four without you answering in three chats.
Everyone treats the rehearsal dinner as the easy one. Fewer people, shorter evening, no seating plan. Then the practical reality arrives: it is the only event where you need exact numbers on a fixed deadline, the guests are travelling in on the same afternoon, and the timing depends on when the ceremony venue lets you in.
Small lists are less forgiving than big ones. On a wedding list of a hundred, four unanswered names are an inconvenience. On a list of twenty-two, they are the difference between a booked table and a group standing in a restaurant doorway.
Which is why the typed message in the family group fails here. The information is a chain, arrival to rehearsal to dinner, and a chain does not survive being re-told by five people in three chats. It needs one page that everyone in the sequence can look at.
Who needs to be where and when, in order. The people flying in need a note about how late they can land and still make the rehearsal; the rest need to know whether they are going to the venue first or straight to dinner.
Venue, address, room, start time, and whether it is a set menu or a booking where everyone chooses on the night.
Meal choices and allergies come back with each reply, which is the information the restaurant needs before you can confirm anything.
Hotel notes and directions, plus the one local number to call if a flight goes wrong. For out-of-town guests this is the most-read part of the page.
A small dinner often has a seating arrangement. Putting it on the page means nobody has to ask which side of the table they are on.
With a deadline you cannot move, the sequence is:
My Joyfullday has a separate dinner invitation product for formal dinners, and it is a genuinely different thing from a party page, with its own structure for seated events. Some hosts use it for the rehearsal dinner, particularly when the evening is a proper sit-down with printed places.
Most, though, keep the rehearsal as a small page alongside the wedding planning, because what they need from it is narrow: one address, one timing chain, one list of who is eating what. The reply form, the live guest list and reminders do that job, and the page can stay short.
Either way, keep it separate from the main wedding invitation. The rehearsal list and the wedding list are not the same set of people, and mixing their replies is how a restaurant booking ends up based on the wrong count.
Rehearsal is at the church at four on Friday, dinner after at the Oak Room, half seven. Times, address and the reply form are on this page, and we need the food answers by Wednesday at noon, the restaurant needs a number.
Page here for Friday: who needs to be at the rehearsal, what time dinner starts, and where we're all staying. If your flight lands after two, come straight to the restaurant and we'll tell you the rehearsal went fine without you.
How it works
In the web app, create the rehearsal as its own event. Different guest list, different deadline, and replies that do not overlap with the wedding count.
Flights and arrivals, the rehearsal time and place, then the dinner. Put them in order on the page so each group of guests can find their own line.
Enable meal choices and allergies in the reply form, cap extras to what the booking allows, and give a closing date that lands before the restaurant needs its number.
Publish, paste the link into the two or three chats that carry this list, and use reminders for the names still blank. Confirm from the guest list itself.
Questions
Its own page. The rehearsal dinner guest list is a subset with different timing, and keeping the replies separate means the number you give the restaurant comes from people actually invited to dinner rather than from the wedding count.
From the live guest list, once replies have closed. The names still blank get a reminder on WhatsApp or by email, which is usually enough for a small list, and you are left with a count you can hand over rather than an estimate assembled from messages.
Yes, and you should. Meal choices and allergies come back attached to each reply, so the restaurant gets the information it needs before the evening. On a list of twenty, that alone justifies the page over a group chat.
Sometimes. The guest list is small and deliberately excludes people who are invited to the ceremony but not to dinner. Password protection means the link cannot travel further than you sent it, which avoids the awkward explanation.
Whichever person or people are actually hosting, named on the page along with a contact number for the day. On a rehearsal dinner guests need to reach somebody who knows the timings, and that is rarely the couple.
Get Started
Give the smallest event of the weekend its own page with the timing chain and a reply button, and close the list before the restaurant asks. Start free.
