How to plan a destination wedding weekend for 40 guests

At Friday check-in, two guests have brought partners nobody counted, and the braai has meat but no charcoal. A destination wedding weekend for 40 guests needs more than a venue booking: reserve suitable rooms, keep one shared itinerary, confirm transport and meal numbers, and give every job a named owner. The same approach works for a milestone birthday away.

Set the boundaries before taking deposits

Start with a short brief: dates, location, what the hosts will pay for and what guests must cover. Separate the wedding itself from optional extras. Friday’s welcome braai and Sunday’s breakfast can quietly turn a one-day invitation into three days of accommodation and meal costs.

Give guests an honest estimate covering rooms, transfers and any shared food contribution. Say when they must commit. If attendance depends on annual leave or a flight price, record that person as provisional rather than treating an enthusiastic WhatsApp reply as a booking.

Book accommodation blocks with an exit route

For 40 guests, count beds and room types, not just cottages. Couples, solo travellers and families need different arrangements. Check whether a “sleeps four” unit has two bedrooms or a sleeper couch in the lounge. Ask about minimum stays, accessible rooms, breakfast, check-in times and the distance between accommodation and the venue.

Ask properties to quote for a room block and explain the terms in writing. Can guests book and pay individually using a reference, or must one person guarantee the full amount? What deposit secures the rooms? When are unused rooms released, and what charges remain after that date?

A block is not automatically cheaper or refundable. Compare the total against ordinary bookings. Where possible, set your guest commitment deadline before the property’s cancellation or room-release deadline, leaving time to chase replies. Avoid personally guaranteeing rooms you cannot afford to carry.

Give everyone one source of truth

Use one mobile-friendly page or shared document for guest information. Put the dates, map pins, accommodation instructions, event times, transport bookings, clothing guidance and organiser contact there. Add a “last updated” date. A simple document that someone maintains is better than an elaborate wedding website abandoned after the invitations.

Use one announcement group to point people back to that page. If the shuttle time changes, update the page first, then send the alert. Do not leave essential details buried in five chats. Keep individual payments and dietary information in a separate, access-controlled organiser file.

Plan transport beyond the ceremony

Map the actual journeys: airport to accommodation, accommodation to the welcome braai, wedding transfers and Sunday departures. Ask who is driving, who has spare seats and who needs a booked transfer. Confirm passenger numbers, luggage capacity and accessibility needs with the operator; a full vehicle may have little room for suitcases.

For a rural venue, do not assume an app-based taxi will be available at midnight. Get the collection point, departure times, waiting charges and final return trip in writing. Offer an earlier return if children or older guests need it, and assign someone to account for passengers before departure.

A designated driver must agree beforehand and remain alcohol-free. Do not allocate that role casually over dinner. Keep the transport operator’s number available offline, especially where mobile coverage is patchy.

Count people by meal, not by invitation

Your master register needs a status for every person and a separate attendance field for each meal. Forty invited guests means 42 with the couple, before agreed supplier meals. Children, late arrivals, partners and photographers can all affect catering numbers, but they do not necessarily attend every event.

Ask about allergies, dietary requirements and children’s meals before the caterer’s deadline. Pass the requirements on clearly and confirm what the kitchen can safely provide. “Vegetarian option available” does not resolve a severe nut allergy. Ask the caterer to confirm whether separate preparation and service are possible.

Set a final meal-count deadline in line with the catering contract. After that, additions need explicit approval and a confirmed cost. Do not promise that the kitchen can simply stretch the food.

Make the welcome braai an assigned job

“Everyone bring something” works poorly when half the guests are flying. Decide whether the hosts are catering or local guests are contributing agreed items. Allocate quantities against confirmed attendance, and include charcoal or gas, firelighters, utensils, ice, drinking water, serving dishes and rubbish bags, not just meat and salads.

Each job needs one owner, a delivery time and a fallback. Someone must check the braai facilities and venue fire rules, receive groceries, keep perishables cold and handle clean-up. The person bringing charcoal should not also be the person whose flight lands after supper.

A realistic six-month planning timeline

Six months is a useful working window, not a guarantee of availability. Popular wedding dates and holiday weekends may need booking much earlier.

• Six months out: Agree the budget and guest boundaries. Check venue availability, accommodation capacity and travel costs. Read deposit, cancellation and refund terms before paying.
• Four months out: Issue invitations with cost expectations and commitment dates. Open the shared information page and request provisional transport needs.
• Three months out: Reconcile guest replies with room bookings. Release unnecessary rooms where terms allow. Book transport and assign food, equipment and event-day jobs.
• Six weeks out: Chase outstanding replies, dietary requirements and balances. Check supplier deadlines and agree who can approve extra spending.
• Two weeks out: Confirm meals and passenger lists against the relevant contract deadlines. Send the final itinerary and verify every job owner has accepted.
• The day before: Reconfirm drivers, collection points, keys, groceries and weather arrangements. Download the essential contacts and itinerary for offline use.

Watch headcount drift and unclaimed jobs

Headcount drift happens one apparently harmless change at a time: a partner joins, a child stays elsewhere, someone skips Friday but arrives for Saturday lunch. Give one organiser authority to update the register. No supplier should receive competing numbers from different relatives.

Unclaimed jobs hide behind phrases such as “we’ll sort the ice”. Replace “we” with a name and ask for confirmation. Keep a simple task register showing the owner, deadline and completion status. On the wedding day, appoint a duty contact other than the couple, with clear spending limits. Forty guests is manageable when the plan does not depend on the hosts answering every call.