Rafting Waivers: Every Participant Signed Before the Put-In

RidgeHQ Team•November 15, 2026•3 min read

A rafting trip is booked by one person and run with eight. The waiver has to cover all eight before the bus leaves for the put-in, not just the name on the payment.

Groups Book as One, Paddle as Many

Rafting and canyoning sell in groups: a stag party online, a school group through the desk, a hotel's guests through an agent. On paper, that becomes one clipboard per group and a guide counting signatures in the car park. Somebody always arrives late, somebody signed for a friend, and the form for the canyoning trip got mixed up with the morning raft.

In RidgeHQ, waivers are built in, not a paid add-on, and every channel writes to the same trips. A group sold by an agent and a group booked on your website end up on the same roster with the same waiver rules.

One Waiver per Participant, Not per Booking

Waiver requirements attach to products. When a rafting or canyoning trip requires a waiver, every participant on the booking completes it with a typed e-signature before checkout can be submitted. A group of eight produces eight signed records, each stored with the exact text that person agreed to and their answers, so a later template edit never changes what an earlier guest signed. Records are protected by database-level row-level security like the rest of your data.

Teen groups and families raise the question of minors. There is no dedicated guardian-signature flow today. You can add questions to the template for a parent or guardian to complete, but RidgeHQ does not verify the signer's relationship to the child.

Questions for the River, Not a Generic Form

A first-timer on a family float and a returning paddler on a grade IV section should not answer the same questions. Waiver templates support conditional questions: a follow-up appears only when an earlier answer calls for it, such as a swimming-confidence question when a guest says they are not a confident swimmer. Products can also require a minimum experience level, asked only where the trip needs it.

The same template can carry a medical questionnaire. Medical answers need a separate health-data consent, are visible only to senior roles, and every read is audited. Guides see that the form was signed, not what it says.

On the Day: Roster, Then the Bus

The trip roster shows every participant and their waiver status, so the lead guide can see who is unsigned before anyone is loaded on the shuttle. A guest who missed checkout can sign with staff at the desk, or staff can email a single-use renewal link that expires after seven days.

Check-in runs from the same roster. Staff check guests in from the session roster in the Event Planner, and guests can check in everyone on their confirmed booking by scanning a per-booking QR code. The QR code is for check-in only (QR waiver signing is not built); waivers are signed at checkout, by renewal link, or with staff at the desk. RidgeHQ records the arrival time and whether staff or the guest checked in, so the guide knows who has actually turned up.

Key takeaways

  • Waivers are built into RidgeHQ and enforced per participant with a typed e-signature before checkout, whichever channel sold the trip.
  • Conditional questions, experience requirements and a restricted, audited medical questionnaire fit the form to the river and the guest.
  • There is no dedicated guardian-signature flow; guardian questions can be added to the template.
  • The trip roster shows waiver status. Staff and guest QR check-in are live.

Learn more


Book a demo to see a group trip, its waivers and its roster on one booking.

See how this looks running on RidgeHQ

Explore the platform capability this post describes, or book a demo when you're ready to see your own operation.