Wedding admin is mostly the same fifteen questions, asked one at a time, by ninety people, over eight months. What time does it start. Can I bring someone. Where do I park. What do I wear. Is there food. Can I stay nearby.
You cannot stop guests asking. You can make sure the answer already exists somewhere you can point to, which turns each question into a link rather than a conversation.
The order information is actually needed
Guests need different things at different moments, and sending everything at once means the important parts arrive eight months before they matter and are forgotten.
| When | What they need |
|---|---|
| Save the date | The date, the city, and whether it is a whole weekend. Nothing else. This exists to protect the date, not to inform. |
| Invitation | Ceremony time and place, reception if different, dress code, how to reply, and the reply deadline. |
| After they reply | Travel, parking, accommodation, the running order of the day, and anything about children or plus-ones. |
| Month before | Final timings, anything that has changed, and what to do on arrival. |
| Week before and the morning of | Only what has changed, and only if it affects them. Weather, a room change, a shuttle time. |
Say less on the save the date, not more
The commonest mistake is treating a save the date as a small invitation. It is not: it is a claim on a date, and every extra detail on it is a detail you cannot change later without confusing someone.
Names, date, city, and the fact that an invitation follows. If it is a destination or a weekend, say that too, because it changes what people are agreeing to. Everything else is better said on the invitation, by which point it is settled. There is more on this in what to put on a save the date.
Put the long answers somewhere, not in a message
Travel, parking, accommodation and the schedule are the questions that generate the most back-and-forth, and they are all badly suited to being sent. A message is read once, on a phone, months early, and then lost in a thread.
This is the entire argument for a wedding website: it is not a nicety, it is the place the long answers live so you can send a link instead of retyping them. Guests check it far more than couples expect, and they check it late — the night before, looking for a start time and an address.
When something changes
Something will. A venue changes a room, a shuttle time moves, the weather turns and the ceremony comes indoors. The rule is to tell only the people it affects, and to match the channel to the urgency.
Weeks out, an email is right: it can carry detail, people can find it again, and nobody needs it in the next hour. In the final day or two, email is the wrong tool, because it is not read in time. That is what a text is for, and it should be short enough to read on a lock screen without opening anything.
Doing this by hand across ninety guests is where couples lose an evening and miss someone. Scheduled email and SMS broadcasts that draw the recipients from your RSVP list mean the group is always current — the people attending, or the people who have not replied — rather than a list you built in March.
One thing to avoid: a group chat. It seems efficient and it is a trap. Every reply goes to everyone, the useful message is buried within an hour, and guests added later cannot see what came before.
What not to send
- Gift or registry information in the invitation itself — put it on the website, where guests can find it if they look
- A running order so detailed that guests feel scheduled
- Anything you are not certain of yet, because a correction costs more attention than the original
- Repeated reminders to people who have already replied, which is the fastest way to have your messages ignored
The morning of
One message, if anything has changed. Otherwise none. Guests who need the details will look them up, and the couple should not be sending anything at all that morning.
Make sure someone other than the two of you is the contact for the day, and that their number is somewhere guests can find it. It is the single most useful thing you can publish and the one most often forgotten.