Create the date and the places
Set the start and end date, location, capacity, room options and package inclusions. Reuse the experience structure when you add the next departure to your season.
Manage scheduled camps, retreats and tours with separate capacity, guest lists, payment dates and hosts for every departure. Reuse the trip structure across the season.
A guest chooses a specific departure with a defined start, end and number of places. The trip description and preparation may be shared, but every date has its own accommodation, participants, hosts and payment deadlines. Marnie keeps that distinction clear.
A full June departure and a half-filled July departure need different action. A season overview should lead directly to the relevant guest list, outstanding balances and preparation for each date.
Explore the connected platformThe business sells the same surf week on 14, 21 and 28 June. Each date carries its own rooms and capacity; the booking and reminder sequence follows the departure the guest selected.
14, 21 and 28 June · Own capacity + assigned hosts
Room + package + selected extras · Deposit and balance for that date
Forms + waivers + arrival details · Reminders before 21 June
Guest list + rooming + payments · Itinerary + host handover
Set the start and end date, location, capacity, room options and package inclusions. Reuse the experience structure when you add the next departure to your season.
Each reservation connects the party, stay, extras and payment schedule to that date. Review applications or waitlist requests alongside the actual available space.
Check guest information, documents and balances, then share the itinerary and host briefing. Timing for reminders and joining instructions follows the departure.
Dates · location · room and bed capacity · inclusions
Payments · forms · waivers · travel details
Guest list · rooming · itinerary · responsibilities
Configure messages around confirmation, payment due dates and arrival. Your team can focus on the guests and tasks that still need attention.
Confirm the selected date and send the guest preparation link.
Schedule preparation and joining messages relative to that date.
Follow the booking’s deposit and balance schedule.
Guests book a specific experience on a specific date and receive the preparation and itinerary for that group.
Your team can move from the season overview into one departure’s guests, capacity, payment status and remaining tasks.
Yes. Each departure retains its own inventory, bookings, preparation and assigned team.
Yes. Use days before arrival and the booking’s payment due dates to organise the communication sequence.
Each departure has its own booking and operational records. Reuse the experience structure while keeping the date, guests, inventory and team assignments specific.
Yes. Use a branded booking link, an embedded journey or an agreed custom integration. We map your booking model, configure the trips, payments, forms and messages, and help connect your website during free setup.
We’ll show you how Marnie brings your bookings,
guests and team together.