One system for the entire operational day.

The booking is the starting point. RidgeHQ connects it to sessions, participants, staff, resources, payments, changes, and reporting.

Activity-aware resource coordination

The operational day combines time, capacity, staff, locations, equipment, fleet, accommodation, and changing conditions. RidgeHQ checks the things that most often go wrong: an instructor assigned to two overlapping sessions is refused, a pilot can’t be put on two overlapping trips, gear availability is matched by unit and size, and equipment out for service drops out of availability the moment it’s logged.

Gear and fleet view showing each unit's bookings so nothing is double-committed
Staff list showing each instructor's role, planner visibility, and upcoming sessions

Move when the day changes

Reschedule a session and its participants and instructors move with it; cancel one and the people booked on it are notified. Weather and tide for the session’s spot sit beside the plan, against thresholds you set per activity, so the decision to move a group is made with the conditions in view rather than rebuilt from scratch.

How the pieces connect

Most activity businesses run on a booking widget, a spreadsheet, a whiteboard, a payment terminal, and a group chat — and the owner becomes the integration layer between them. In RidgeHQ a booking is one record that every other part of the day reads from:

  • It lands on the session it was made for, so the planner shows real occupancy and the roster shows who is coming, with their level.
  • Its participants carry their waiver requirements, sizes, and gear needs from their customer profile.
  • Its payment, deposit, and any later credit note sit on the same order, feeding the daily close and revenue-by-origin reports.
  • Instructors assigned to its session have their hours and fees calculated from that assignment.
  • The AI Copilot and any connected AI assistant read the same records, inside the same permissions.

Frequently asked questions

One connected platform. Bookings, scheduling, staff, gear and fleet, customer profiles, and payments share the same records, so each capability page describes a part of the same system rather than a separate app to integrate.

It refuses an instructor assignment that overlaps that person's other sessions and a pilot assignment that overlaps another trip, checks gear availability by unit and size, and removes gear that is out for service from availability. Online and front-desk sales draw from the same session capacity.

Yes. Reschedule the session and its participants and instructors move with it; cancel it and the people booked are notified. You can also email everyone on a session or trip from the planner.

Some honest gaps: there's no staff availability or time-off calendar, instructor-to-participant ratios aren't calculated or enforced automatically, and a direct export to accounting software is planned rather than built.

Customers can be imported from a CSV file. Design partners get founder-led onboarding and help with migration.

Ready to connect your operation?

Join the operators using RidgeHQ to manage their day from one unified platform.