Tours

Run a departure, not a spreadsheet.

Shuttle groups, guide assignment, capacity and viability, all held together. RideLoop tells you a tour will not make its numbers while there is still time to act.

Departure lifecycle

What happens between a booking and a departure, automatically.

Five stages, every one of them real — not a diagram of how it should work, but what actually runs on every scheduled date.

  1. 1

    A departure exists the moment the first booking does

    No separate step to "open" a date. The first booking against a tour and a day creates the real departure record everything else hangs off.

  2. 2

    Headcount is watched for you

    Against the minimum you set, with escalating alerts before your own decision deadline — not a surprise on the morning of.

  3. 3

    You decide, not a formula

    Short of the minimum, you choose: run it anyway, offer every booked guest a free reschedule, or cancel with automatic refunds. Nothing happens on its own.

  4. 4

    Crewed with conflicts checked

    Guides, vans and shuttle groups assigned with skill level and capacity validated automatically — the same guide can’t be double-booked across two departures on one day.

  5. 5

    Run, then reconciled

    Guide pay, van costs and logged expenses come off the departure afterward, so you see what it actually made — not gross revenue dressed up as profit.

Per-departure profit

Gross revenue tells you nothing about a tour.

Guide pay, van costs and expenses logged on the day come off the departure, so you can see which routes are worth running and which only look busy.

Cross-sell

A tour booking is also a bike rental waiting to happen.

A guest booking a tour or holiday can rent one of your own bikes in the same checkout — drawn from the same fleet-availability pool as a standalone rental, checked out and back in through Scan Station like any other hire. A second revenue line on every departure, with no extra admin.

  • Same fleet pool
  • One checkout
  • Waitlist auto-offer
  • bring-your-own stays the default

Put next season’s departures on one calendar.

Capacity, guides and viability in one place — and every booking path reading the same availability.