DO Adventure
Log inTry the demo

Module 1 of 17

Operations

Departure day, built and controlled end to end.

All modules

What it looks like

Departures by status, with passengers, meeting point and what is missing
Departures by status, with passengers, meeting point and what is missing
Guides, drivers and gear assigned, with gaps and overlaps in plain sight
Guides, drivers and gear assigned, with gaps and overlaps in plain sight
The month as an activity-by-day grid: blue with departures, red when something is missing, dashed when a recurring one is not created yet
The month as an activity-by-day grid: blue with departures, red when something is missing, dashed when a recurring one is not created yet
Upcoming services: hover a cell to see the service, the passengers with their flag and the assigned resources
Upcoming services: hover a cell to see the service, the passengers with their flag and the assigned resources

What it solves

Everything between the sale and the group getting back — and the part almost no system in this industry actually solves. Most of them sell bookings and call it management: they tell you who paid, not whether you have a certified guide, whether the van is free, or whether the kayaks came back. Here you build the departure, assign people, fleet and gear against their real constraints, and follow the operation while it runs instead of reconstructing it afterwards.

  • Departures built from what was sold, with capacity, time and meeting point
  • Guides and drivers assigned by current certification, not from memory
  • Fleet and gear with double-booking checks and return tracking
  • Real cost adding up during the departure, not estimated at month-end
1place where the whole departure lives
0double-booked guides or vehicles

What you can do

  • Build the departure from what has already been sold
  • Assign guides and drivers, checking their certification is current
  • Book vehicles and gear, with a warning when they are already committed
  • Spin up a regular departure from its template
  • Plan the month on the upcoming services grid, with each departure's details on hover
  • Follow the day's departures on one board, by status
  • Post the real cost while the departure is running
  • Log operational transfers separately from excursions

A real case

Three-day trek to Fitz Roy

The situation

14 passengers, two guides, one van and camping gear that has to come back and be checked.

  1. 01

    The departure is built from the 14 seats sold and calls for two guides with current high-mountain certification.

  2. 02

    You assign the van; the system flags that it is already committed on day 2 and lets you fix it before it becomes a problem.

  3. 03

    Tents, sleeping bags and stoves go out assigned to that departure, so on the way back you know what to check and what is missing.

  4. 04

    For three days the departure stays in progress with its real cost adding up: fuel, per diems and the mountain hut.

What you end up with

You finish the departure knowing what it actually cost, with the gear checked back into the store and without a single call to confirm who was going.

How you get it

Included in the plan.

See pricing

Load one of your own departures and see how it looks.

No video, no guided tour: it is your account, with every module open, so you can try it on data you recognise.

15 days · no card · closes itself if you stop there