Copy it, replace every bracketed placeholder, and put it somewhere guests can find from the invitation. When something changes, change it here rather than sending a second message half of them will not connect to the first.
1The weekend at a glance
- Dates: [Fri DD – Sun DD Month]
- Nearest airport / station: [name], about [N] minutes from the venue
- Most guests will want: [Friday and Saturday] nights
- Dress code: [ceremony] / [welcome drinks] / [brunch]
- On-the-day contact (not the couple): [name, number]
2Friday — welcome drinks
- Who: [Everyone / Invited: names]
- When: [start] – [end]
- Where: [full address]
- Cost: [hosted / pay your own]
- Optional: [yes — come if you are around]
3Saturday — the wedding
- Ceremony: [time], [full address], arrive by [time]
- Reception: [time] – [time], [address if different]
- After-party: [time] – [time], [venue]; [open to everyone / invited]
- Cost: [hosted]
- Optional: [no — this is the wedding]
4Sunday — brunch and departures
- Who: [Everyone / Open]
- When: [start] – [end]
- Where: [full address]
- Cost: [hosted / pay your own]
- Optional: [yes]
- Checkout at most hotels: [time]
5Where to stay
- Option A: [hotel], about [£] per night, [walking distance / N min by taxi] — block booking code [code] until [date]
- Option B: [hotel or rental], about [£] per night
- Option C: [budget option], about [£] per night
- Block-booking release date: [date] — prominently
6Getting around — both directions
- Shuttle to the venue: [times], from [pick-up point]
- Last shuttle back: [time] — after this, taxis take about [N] minutes; book ahead
- Taxi numbers: [two local firms]
- Parking at the venue: [yes / no / limited]
- Arrival times sheet: [link] — share a taxi with whoever lands near you
7Afterwards
- Photos: [link to the shared album] — add yours, especially the ones we were not in
Worth knowing
- Label every event Everyone / Open / Invited. Guests cannot tell "brunch if you are around" from "brunch, attendance expected".
- Publish costs and accommodation options six months out. Guests who know the number early can plan for it; guests who learn it late overstretch or drop out.
- The journey back is where wedding weekends break. Publish the last shuttle time before people choose where to stay.
- Name a contact who is not the couple. On the day, the couple must be unreachable.
Common questions.
What should a wedding weekend itinerary include?
For every event: what it is, when it starts and ends, the full address, who is invited (everyone, open, or a named subset), and whether it costs anything. Plus accommodation options at more than one price, transport in both directions including the last shuttle, the dress code per event, and an on-the-day contact who is not the couple.
How early should guests get the itinerary?
Costs, dates and accommodation options about six months out, so people can budget and book. The full timed itinerary by six to eight weeks out. Put it on one page linked from the invitation and update it in place, so the link is always current.
Should the itinerary say what is optional?
Explicitly, for every event. It is the highest-value line on the page and almost always missing: guests rearrange flights for things that were never compulsory, and skip things the couple genuinely wanted them at, because nobody said.
Can I copy this template?
Yes — the Copy button gives you the whole sheet as markdown with the placeholders in brackets. Replace them, paste it wherever guests will see it. Free, no account.
The other checklists.
A checklist that fills itself in.
Kinora keeps this list live for the whole group — every job shows who owns it, the date poll closes the date, the budget tracks who has paid. Free while the beta runs.