A retreat is an offsite with travel, overnight stays and free time — which means three extra systems to run: lodging, movement, and unstructured hours that still need a plan.
Everything that goes wrong at a one-day offsite goes wrong at a retreat too, plus three things: people sleep somewhere (rooming), people move between places (transport), and people have gaps (activities and free time). Each is its own list, and each depends on the same attendee data.
Attendees will arrive across a full day and leave across another. Group them into waves rather than chasing individual flights — the shuttle calculator sizes the waves — and publish arrival instructions before anyone lands, including what to do if a flight slips.
Ask for flight numbers at registration, not just arrival times. Flight numbers let you check status yourself on the day instead of texting twelve people.
Rooming is the single most re-versioned document at any retreat. Collect share preferences at registration, build the list once, and send it in the hotel's format — template here. Keep accessibility requirements on a restricted sheet, not in the version circulated to the whole team.
Dietary requirements compound over a retreat: five meals means five chances to serve someone the wrong thing. Give the kitchen one sheet with severity marked — preference, intolerance, or allergy — and confirm allergies verbally with the chef on arrival day. Template here.
Two nights and three days is the most common shape and the easiest to justify: one travel day, one full working day, one half day. Three nights starts to need genuine downtime built in or people burn out.
Ask, do not assume. Room sharing saves real money at scale but is a significant imposition for some people, and a genuine accessibility or privacy issue for others. Make it opt-in at registration with single rooms available without explanation.
Roughly two to three hours of genuinely unscheduled time per full day, plus real breaks between sessions. Retreats fail more often from exhaustion than from insufficient content.
Mezze turns one attendee list into registration, dietary and travel tracking, rooming and shuttle manifests, breakout groups and an agenda that recalculates when a session runs long.
Join the offsites waitlistFree templates