Travel together, be there for the wedding

Fit guest plans around the wedding

Copy confirmed guest information into the shared plan and note its source and latest update. If the invitation and a later message disagree, ask the hosts or their named contact before treating a change as confirmed. Leave realistic time for getting ready and travelling between the accommodation and the actual event address.

Your guest plan does not manage wedding suppliers, change ceremony rules or make bookings. Follow the hosts' instructions about dress, plus-ones, children, photos and attendance. Do not promise entry or arrange an extra guest without checking with them.

Give each arrival a workable route to check-in

Guests can arrive on different days and stay in different places. Check how each arrival group reaches its accommodation, whether reception will be open and what happens if a journey is delayed. A shared transfer needs a confirmed passenger list and a departure time; one late arrival should not leave everyone guessing.

Keep booking references, room assignments and access codes in a separate private conversation with the people who need them. Share only the meeting and timing details useful to the whole guest group. Do not imply the shared itinerary has a hidden view for each guest.

Agree the transfer and a fallback before the day

Confirm the actual pickup point, travel time and return arrangement with the provider or driver. Allow a realistic buffer before the hosts' requested arrival time. Guests leaving the reception early need their own checked way back; a late shared return may not suit everyone.

“Meet at [checked pickup point] by [time] for [confirmed transfer]. If we cannot reach each other, wait until [cutoff], then use [agreed alternative] and tell [named contact] when you can. Your return arrangement is [confirmed option].”

Replace the brackets with real arrangements and agree who pays for the alternative. Keep the essential instructions accessible without a connection. Check availability before relying on a taxi or another departure; do not assume the wedding hosts can solve every guest's travel delay.

A guest-weekend outline to adapt

1. Arrivals: guests follow their confirmed transfers and check-in arrangements.
2. Optional welcome: only invited guests join an official welcome event; a separate group meal has its own replies and cost rule.
3. Ceremony and reception: invited guests follow the official schedule, with checked travel and return arrangements.
4. Optional brunch: those who choose to join confirm a place separately, leaving time for checkout and departures.
5. Departures: each guest follows their own confirmed journey and accommodation checkout instructions.

This is an adaptable outline, not a booked package or a wedding invitation. Free time stays free: a guest can skip an optional outing without missing the official celebration.

Split guest costs by the people who agreed to them

Eight guests attend the wedding; six agree to share a fictional €180 transfer. If those six agree to split it equally, each owes €30. The other two stay outside that transfer split. Wedding attendance alone does not make someone part of a shared ride.

Say what the hosts cover before collecting money. Keep hosted wedding costs separate from guest accommodation, transfers, optional meals and voluntary gifts. Each expense needs an agreed payer, participants and repayment deadline. Equal division here is an example, not a default fairness rule; dropping out does not remove a deposit or cancellation commitment agreed before booking.

Keep one plan the group can check

Cairn's manual friends' weekend demo shows an itinerary, dinner attendance and an illustrative expense split among the people joining that meal. It is a fictional demonstration, not a created trip or a wedding guest package.