Weddings · Updated 2026-10-19
Wedding weekend itinerary for guests: what to include (with wording examples)
When a wedding stretches across more than one day (welcome drinks on Friday, ceremony on Saturday, farewell brunch on Sunday) guests need more than a single invitation. A wedding weekend itinerary (sometimes called a schedule card or timeline insert) tells everyone where to be, when, what to wear and how to get there. This guide is for broad-market multi-event and destination weddings in the US, UK, EU and Australia: what belongs on the itinerary, when a separate travel-and-stay card helps, copy-ready wording for common events, invite-only extras, printed vs phone versions, mistakes to avoid, a sample timeline and FAQ. For the main invitations, see wedding ceremony and reception invitation wording; if you're still wording pre-wedding invites, our Haldi, Mehndi and Sangeet invitation wording; for reply cards, wedding RSVP card wording; after the day, wedding thank you card wording may help too.
What a guest itinerary is (and when you need one)
A guest itinerary is a short schedule of the events guests are invited to: day, time, venue, dress code and any practical notes. It sits alongside the main invitation; it does not replace it. Think of the invitation as the formal ask, and the itinerary as the weekend map.
You usually need a dedicated itinerary when:
- There are two or more events on different days, or different venues on the same day.
- Guests are travelling in: a destination wedding, a hometown celebration for out-of-town family, or a guest list spread across countries.
- Dress codes or start times differ enough that one line on the invite would be confusing.
- You are running a shuttle, a room block, or staggered arrival times that people must plan around.
For a single-venue Saturday afternoon ceremony and evening reception, a clear line on the invitation ("ceremony 3pm · reception to follow") is often enough. Add a dedicated itinerary when the weekend has moving parts. If you already have a wedding website, the card still helps: many guests screenshot a phone version or tuck a printed card into a bag, and older relatives often prefer paper over clicking through menus.
When to send it
Most couples include the itinerary with the invitation suite, or send it shortly after RSVPs close once hotels and shuttle times are locked. Digital guests often get a PDF or phone-story version by email or WhatsApp a week or two before travel. Exact timing varies by family and how far people are flying; the useful test is: would a guest booking flights next week need this information? If yes, send the bones of the schedule earlier rather than later, then refresh shuttle or weather notes closer to the weekend.
A practical sequence many couples use:
- Save-the-date with city and wedding weekend dates (no minute-by-minute detail).
- Invitation with ceremony (and reception) essentials.
- Itinerary + travel card once venues, dress codes and hotel cut-offs are confirmed.
- Optional digital reminder a few days before arrival with any last changes.
What to include for each event
For every event on the card, aim for the same five fields. Guests skim; consistency helps more than clever wording.
- Day and date: "Friday 12 June" or "Sat 13 Jun" is clearer than "Day 2" or "Eve of wedding."
- Start time: and, if helpful, an arrival window ("doors 2:45 · ceremony 3:00").
- Venue name and short address: enough to drop into maps; full street details and parking can live on the travel card.
- Dress code: one short line guests can pack for.
- One practical note if needed: meal included, outdoor surface, kids welcome / adults only, shuttle pickup, end time.
Optional extras that reduce messages to the couple: transport between venues, whether a meal or drinks are provided, an end time for evening events (so babysitters can be booked), accessibility notes (stairs, gravel, quieter room), and an RSVP line if that event was not on the main invite.
| Field | Why it matters | Keep short |
|---|---|---|
| Day / time | Flights, childcare, work leave | One line per event |
| Venue | Maps and taxis | Name + neighbourhood or street |
| Dress code | Packing for travellers | Phrase, not a paragraph |
| Meals | Guests plan snacks and allergies | "Dinner provided" / "drinks & canapés" |
| Kids | Avoid awkward doorstep moments | "Adults only" or "children welcome" |
| Transport | Parking and late-night exits | Shuttle time or "taxis plentiful" |
The guest travel & stay card (separate from the schedule)
When many guests fly or take a train, a second card, travel and stay, keeps the itinerary readable. Crowding airport codes, booking codes and parking gates onto the schedule card makes both documents harder to use. Typical sections on a travel card:
- Venue address for the main ceremony site or the hotel hub where most people are staying.
- Airport and station with a rough transfer time (taxi / train / tram). Give a realistic range ("about 35 minutes by taxi") rather than a full timetable that goes stale when the operator changes schedules.
- Hotel room block: hotel name, the group booking name or code, how to book (phone / email / link), and the cut-off date when the held rooms are released. Cut-offs are set by each hotel; they often fall a few weeks to a couple of months before the wedding. Confirm the date in writing with the hotel and print that date. Do not invent one from a template.
- Parking: free / paid / gate letter / "limited on-site, use nearby garage." Note if Saturday traffic is heavy.
- Shuttles: pickup point, departure times, and who the shuttle is for (all guests vs hotel block only).
- Local tips: one or two lines (cards widely accepted, Sunday shop hours, evening weather layer). Skip a full city guide; link the wedding website if you want deeper recommendations.
Finish with a contact line for last-minute questions ("message us: we'll help you find your way") so guests are not stuck at arrivals with no number. If one partner's family is coordinating transport, name that person and a reachable channel.
Copy-ready wording examples
Adapt the names, dates and venues. Keep each event to a few short lines on the card; the samples below are meant to be trimmed to fit your layout.
Welcome drinks
Friday 11 June · 6:30 pm
The Conservatory Bar, Harbour Hotel
Smart casual · Drinks and light bites · Children welcome until 8 pm
Friday evening · from 7 pm
Rooftop of The Lane Hotel · City centre
Relaxed evening wear · Cash bar after the welcome toast
Rehearsal dinner (only if those guests are invited)
Friday 11 June · 7:00 pm
Olive & Vine · Private dining room
Semi-formal · Dinner provided
By invitation: see your separate card
Pre-wedding celebration (one example among several)
Many weekends include a cultural or community event before the ceremony: a rehearsal party, a welcome barbecue, an afternoon tea, a barn dance, or, in some families, a Mehndi or Sangeet evening. Whatever you call it, guests need the same basics: time, place, dress and whether food is served. Explain unfamiliar events in one plain sentence so nobody arrives under- or over-dressed.
Thursday 10 June · 4:00 pm
Garden Lounge, Riverside Hotel
Bright colours · Comfortable festive · Afternoon gathering with music and light food
Friday evening · 7:00 pm
Ballroom · Music, performances and dancing
Festive evening wear · Dinner provided
Ceremony
Saturday 12 June · 11:00 am
Grand Pavilion · Formal traditional or formal western
Please arrive by 10:45 · Unplugged ceremony (photos after the recessional)
Saturday 3:00 pm
St Mark's / garden lawn beside the hall
Garden formal · Heels may sink: block heels or flats welcome · Ceremony ~30 minutes
Reception
Saturday 12 June · 6:00 pm
Ballroom Terrace · Black-tie optional / elegant evening
Dinner, toasts and dancing · Adults only after 9 pm · Last shuttle 00:30
Reception to follow at The Orchard Barn
Cocktail attire · Dinner at 7:30 · Open dancing from 9 · Bar closes 12:30
Farewell brunch
Sunday 13 June · 10:30 am to 1:00 pm
Hotel courtyard · Casual daytime
Come as you are · Drop in anytime · Bags welcome before airport runs
Invite-only events: use a separate insert
Not every guest is invited to every piece of the weekend. Rehearsal dinners, family-only blessings, after-parties and some cultural ceremonies are often smaller. Putting those on the all-guest itinerary creates awkward explanations at the door and long message threads afterward.
- Keep the main itinerary to events open to the full guest list (or clearly marked cohorts: "wedding party only").
- Give invite-only guests a separate insert, card or message with that event's time, venue and dress code.
- On the main card, if you must acknowledge an exclusive event at all, use a quiet line such as "private family dinner: separate invitation" rather than listing a time that half the room cannot attend.
- Brief ushers or hosts so they know who is expected where; a schedule in your pocket is not enough if the door team has not seen it.
Printed cards vs digital / phone versions
Printed itinerary and travel cards in the invitation suite still feel special for formal weddings and for relatives who prefer paper. Phone-story or PDF versions (often 1080×1920 for Stories, WhatsApp and email) are practical for last-minute updates, international guests and anyone who already lives in group chats. Many couples do both: print with the suite, then send a digital copy a few days before travel with shuttle or weather notes refreshed.
If you print at home, use decent card stock (around 250-350 gsm) and one test copy first. Denser text, travel cards and full weekend timelines, usually reads more comfortably on A5 or 5×7 than on a compact A6. Check that times survive a phone screenshot: high contrast and a little extra line spacing help outdoors.
Working with a wedding website
Use the card for the essentials guests must have offline, and the website for maps, expanded hotel lists, gift registry links and long FAQ answers. On the itinerary, a single line such as "full details and maps at our wedding website" is enough; repeating every URL on every row clutters the design. Keep the website URL identical everywhere (invite, itinerary, travel card, email signature) so people are not hunting variants.
Dress codes that travellers can actually pack for
Out-of-town guests often bring one suitcase for the whole weekend. Ambiguous dress lines ("festive", "nice", "cocktail-ish") create stress and emergency shopping. Prefer concrete, short phrases:
- Smart casual: neat trousers or a dress; jacket optional; no trainers for evening.
- Garden formal / semi-formal: suits or dresses; note ground surface if heels will sink.
- Cocktail attire: short or midi dresses, suits; less formal than black tie.
- Black-tie optional: tuxedos welcome, dark suit equally fine; long or elegant evening wear.
- Adults only after 9 pm: pair with the dress line if the evening shifts tone.
If cultural dress is welcome or encouraged (colour themes, traditional outfits, or "wear what feels like you"), say so in one additional clause rather than assuming every guest already knows. A gentle footer that dress codes are a guide, not a test, helps anxious friends without undoing the packing advice.
Mistakes to avoid
- Vague venues: "the hotel bar" without a hotel name forces guesswork, especially in a city with three "Grand" hotels.
- Missing or inconsistent dress codes: travellers pack once; "festive" alone is not enough if Friday is casual and Saturday is black-tie optional.
- Stale hotel cut-off dates: always confirm with the hotel; do not invent a date from a blog template.
- Listing private events for everyone: see invite-only inserts above.
- Too much prose: an itinerary is a schedule, not a love letter. Save the story of how you met for the website or programme.
- No end times for late nights: parents and guests with early flights need them.
- Forgetting accessibility or weather notes: stairs, gravel paths, strong sun or evening chill deserve one short line.
- Different times on the invite vs the itinerary: proofread both against the same master spreadsheet before printing.
Who receives which card
Not every household needs the same packet. Local guests who already know the city may only need the itinerary. Guests flying in need itinerary plus travel and stay. Wedding-party members may need an extra private schedule for photos, hair and rehearsal timing that does not belong on the public card. Build two or three versions from the same master list rather than rewriting from scratch: it reduces the chance that Uncle David has a different ceremony time than the bridal party.
A simple checklist before you print or send
- Export one master list: event name, date, start, end, venue, dress, meals, kids, transport.
- Have both partners (and one detail-oriented friend) read the card aloud.
- Confirm hotel cut-off and shuttle times in writing the same week you finalise the PDF.
- Print one test page or send the phone PNG to your own device and read it outdoors.
- Align the wedding website and any WhatsApp group with the same numbers.
Sample timeline table
A compact weekend for a multi-event celebration might look like this on the card (swap events to match your plans):
| When | Event | Where | Dress |
|---|---|---|---|
| Fri 6:30 pm | Welcome drinks | Harbour Hotel bar | Smart casual |
| Sat 11:00 am | Ceremony | Grand Pavilion | Formal |
| Sat 1:00 pm | Lunch / photos break | Pavilion lawn | Same as ceremony |
| Sat 6:00 pm | Reception | Ballroom Terrace | Black-tie optional |
| Sun 10:30 am | Farewell brunch | Hotel courtyard | Casual |
If your weekend also includes a cultural pre-wedding evening, a rehearsal dinner or a recovery picnic, add a row in the same format, or keep that row on the invite-only insert so the public card stays honest.
Frequently asked questions
Do we need both an itinerary and a travel card?
If most guests live locally and there is only one venue, a short itinerary (or a clear line on the invite) is enough. Add a travel-and-stay card when people are flying or training in, or when hotel blocks, parking and airport transfers would clutter the schedule.
When should hotel room-block cut-off dates appear?
Print the cut-off date the hotel gave you in writing. Policies vary by property and season; some release held rooms weeks before the wedding, others closer to the date. Confirm before you send stationery, and remind guests once by message as the date approaches.
Should kids' events appear on the main itinerary?
Yes if children are welcome at that event. If an evening is adults-only, say so on that row so families can arrange childcare. For a separate kids' activity, a small note or a message to parents often works better than a full public listing.
Is a wedding website enough instead of a printed card?
A website is excellent for updates and maps. Many guests still appreciate a printed or phone-sized card they can screenshot or tuck into a purse, especially relatives who will not dig through email threads on the day. Using both is common.
How do we handle last-minute time changes?
Update the digital version and message the affected guests. Do not rely on people re-reading an old PDF. For printed cards already mailed, a clear group message or wedding-website banner is the practical fix.
What if dress codes differ a lot between events?
Put a dress line on every row. Travellers would rather pack two outfits than guess. A footer such as "Dress codes are a guide: come as you feel most yourself" softens strict wording without removing the guidance.
General planning suggestions only: hotel policies, transport and etiquette vary by place and family. Related reading: Ceremony & reception invitation wording · Haldi, Mehndi & Sangeet invitation wording · Wedding RSVP card wording · Wedding thank you card wording.