How to plan a wedding weekend

Couples planning a wedding weekend are typically well organised about the wedding itself and much less so about everything around it. The welcome drinks, the morning-after brunch, the Friday arrivals, the shuttle times and the question of what is optional all exist clearly in the couple's heads and nowhere else.

From a guest's side the experience is a slow accumulation of unanswered questions. Is Friday night a thing I am invited to or a thing the wedding party is doing? Should I book Sunday night too? Is there transport from the hotel or am I driving? Is brunch included or do I pay? Each question is small, and each one ends up asked individually — usually of the couple, usually in the final week, usually by text.

The whole job here is publishing one clear source of truth early enough to be useful.

Write out every distinct thing happening, and for each one record five facts. Missing any one of them generates questions:

• What it is — "Welcome drinks", not "Friday".
• When — a start time and an end time. An end time is what tells people whether it is a drink or an evening.
• Where — the full address, not the venue's name.
• Who is invited — everyone, or a subset. Say it plainly.
• Whether it costs anything — and if so, how much and how to pay.

A typical weekend has more of these than couples expect: Friday arrivals and welcome drinks, Saturday morning for early risers, the ceremony, the reception, the after-party, Sunday brunch, and Sunday departures. Seven events, each needing five facts.

This is the highest-value sentence in the entire plan and it is almost always missing.

Guests cannot tell the difference between "there will be brunch on Sunday if you are around" and "brunch on Sunday is part of the wedding and you are expected". So they guess. Some rearrange flights to attend something that was never compulsory; others skip something the couple genuinely wanted them at.

Label every event with one of three words:

• Everyone — the ceremony and reception. Attendance assumed.
• Open — welcome drinks, brunch. Come if you are around; no explanation needed if you are not.
• Invited — the rehearsal dinner, the family lunch. A named subset. Say who, so nobody is left wondering whether their invitation was lost.

A destination wedding weekend can easily cost a guest £700 once travel, two or three nights of accommodation, an outfit and a gift are counted. Guests will do this willingly, but they need to know the number early enough to plan for it — and to decline gracefully if they cannot.

Publish, as soon as you can:

• Which nights people realistically need. If the ceremony is at 2pm on Saturday and the nearest airport is two hours away, say "most people will want Friday and Saturday nights".
• Two or three accommodation options at different prices, with rough per-night costs. One recommended hotel means anyone for whom it is too expensive has to research alternatives themselves, in an unfamiliar place.
• What is paid for and what is not. Assume nothing is obvious. If the welcome drinks are hosted but dinner afterwards is not, say so.
• Any block-booking deadline — the date the held rooms are released, prominently.

Guests who know the number six months out can budget for it. Guests who discover it six weeks out either overstretch or drop out.

Transport is where wedding weekends most often break down in practice, and the pattern is consistent: the journey to the venue is well organised and the journey back is not.

• Publish shuttle times both ways, including the last one back. If the last shuttle is 11:30pm and the party runs to 1am, guests need to know that before they choose where to stay.
• Say what happens if people miss it. "Taxis take about 40 minutes to reach the venue, so book ahead" prevents a group of guests stranded in a rural car park.
• Collect arrival times in one place. Guests who land within an hour of each other will happily share a taxi if they know about each other. This is free money for your guests and costs you one shared page.
• Name a contact who is not the couple. On the day, the couple must be unreachable. Someone else's number needs to be on the plan.

All of the above is only useful if guests can find it. Details spread across a save-the-date, an invitation, two emails and a WhatsApp group will be re-asked individually, and the couple will answer each one.

One page. Linked from the invitation and from every message you send afterwards. Updated in place when things change, so the link is always right rather than superseded.

The single most useful property is that changes propagate. Wedding timings move — the ceremony shifts by thirty minutes, the shuttle time changes, the brunch venue is replaced. If the plan lives in an email, the correction is a second email that half the guests will not connect to the first. If it lives on a page, you change it once and everyone who looks sees the current version.

Afterwards, that same page is the natural place for the photos. Guests take hundreds and the couple sees a fraction; one shared album where everyone can add theirs is the closest thing to a guest-perspective record of the day, and it costs nothing to set up before the weekend.

By about eight weeks out, a guest should be able to answer all of these without asking anyone:

• Which events am I invited to, and which are optional?
• What time does each start and end, and where exactly?
• Which nights do I need accommodation, and what are my options?
• Roughly what will the weekend cost me?
• How do I get from where I am staying to each venue, and back?
• What is the dress code — for each event, not just the wedding?
• Who do I contact on the day if something goes wrong?
• Where do the photos go afterwards?

If a guest cannot answer one of these, that is the next thing to publish.

The guest sheet itself, with every event's five facts and the transport section as fill-in-the-blanks: the wedding weekend itinerary template.

Two nights suits most weddings: guests arrive Friday, the wedding is Saturday, and Sunday is a relaxed departure. Three nights is a real ask — it means most guests taking a day off work on top of travel — so it is best reserved for weddings where people are travelling a long way anyway.

Usually yes, and that is normal. What matters is publishing options at more than one price point early, along with any block-booking release date. Guests generally do not mind paying; they mind finding out late that the only suggested hotel is beyond their budget.

If everyone is travelling and staying overnight, inviting all of them is much simpler than managing a subset — anyone who is in town and not invited will know. Whichever you choose, label it explicitly as open to everyone or invitation-only, so nobody has to work out whether they were meant to be there.

Put it in writing early — six months out if you can — with a realistic per-guest range covering accommodation, travel and any events they pay for. It is not awkward; it is the information people need to say yes properly, and it lets anyone who cannot afford it decline early rather than dropping out late.