How a tour operator runs waivers with Waiver.com

A tour operator has no front desk. The meeting point is a harbour wall, a hotel lobby or a car park, the guide is the whole staff for the next few hours, and the guests are often visitors who booked through a third party and have never heard the company's name spoken aloud. This walkthrough shows how such an operator could run waivers with Waiver.com. It is illustrative, not a real customer's story, and it is deliberately built around the departure rather than around a building.

Setup

The operator runs a handful of guided experiences that differ in intensity. It builds one template from the tour and guided experience waiver template, with the approved document as rich text, traveler details, a question asking which experience the guest has booked, and a short set of guest questions that the guides actually use: whether the guest can swim for the water tour, and whether they have any mobility concern the guide should plan around. The mobility question is optional, explained on the form, and carries a flag rule so the guide sees the answer before the group sets off.

Because the audience includes families, guardian and minor fields are enabled, and the form is explicit about who signs for a child. An initials block sits beside the paragraph describing the physical demands of the walking tour. Everything else is kept short, because the guest is likely reading it on a small screen in a hotel room.

The operator serves guests in several languages, so it prepares translated signing instructions to sit alongside the link, following preparing translated signing instructions. The template is tested on a phone with a slow connection and a long name in a non-Latin script before the owner publishes the version and notes what changed. Signed records stay linked to their version, which matters at the end of a season when the document is revised.

Signing

The signing link travels with the booking. Direct bookings receive it in the confirmation email with a sentence naming the tour and saying every traveler, not only the booker, must complete it, following collecting waivers before arrival. For a departure with a fixed group, the operator creates an event named for the date, time and route, and invites the travelers on the booking so signing progress is visible in one place.

Partner bookings need more care. Each hotel concierge and reseller receives a short instruction sheet and the same public link to include in their own confirmation. The operator reviews the wording with each partner so the tour name on the form matches the name the guest was sold, using preparing waiver instructions for partner venues. Partners never get access to records.

On the guest's phone the form opens in a browser: the document, their details, the experience choice, the guest questions and a finger-drawn signature. The completion screen shows a confirmation code and tells the guest to take a screenshot, because data may be unavailable at the meeting point. The operator sends a reminder the evening before to invitations still showing as unsigned, checking first for a record under another email, and never sends the same reminder twice.

For a guest who reaches the meeting point unsigned, the guide's own phone is the fallback. The guide opens the public link and hands the phone over, or the guest scans a QR code on the guide's laminated card. The guide waits for the record before treating that guest as done.

Check-in

Before the meeting time, wherever there is signal, the guide opens the departure's event and looks at who has signed and who has not, and notes any flagged answers. That preparation is the whole difference between a calm departure and a scramble. At the meeting point, guests show their confirmation code and the guide scans it, or the guide searches by name or email for anyone whose screenshot is unreadable in the sun. Each guest is checked in and appears in the arrival log, which becomes the departure list.

Statuses are read plainly. Valid means the paperwork is complete. A guest whose record shows expired from an earlier trip completes the current form on the guide's phone. A flagged mobility answer changes the route plan or the pace, which is a guide decision separate from the waiver itself. A child whose guardian is not present follows the operator's written exception process, and a guide who is unsure calls the office rather than improvising.

Group bookings arriving together are reconciled against the roster after the head count, following reconciling an event roster after arrival, so that a name on the booking who never turned up is not mistaken for a guest who did.

Records

Each departure's event holds the roster, the records, the signed PDFs with their version and the check-in log. Searching by name, email or confirmation code handles the ordinary questions. Filtering by event answers the question of who was on a particular morning's departure, which is what the office needs when a guest writes in afterwards.

Guides have a role that lets them search, check in and read the day's answers, and nothing more. The office manager reviews and exports; the owner publishes and manages the team. Seasonal guides are added at the start of the season and removed at the end. Exports are specific: a single signed PDF for an authorized request, or a CSV of a season for reconciling against partner bookings, stored in the approved folder and removed from laptops afterwards.

Old signing links are retired each season when the template changes, and the partner instruction sheets are re-issued, so no hotel is still sending guests to last season's form. Records from earlier seasons remain intact and searchable under their own versions.

What to adapt

An operator with fixed departure points might install a tablet kiosk in a partner's lobby. One that sells mostly last-minute walk-ups would lean on the QR card more than the pre-arrival link. A larger operation running many guides could integrate through the API so that a signed waiver updates the booking system.

The constant is the sequence: sign before the meeting point, review before the meeting time, check in at the meeting point, reconcile afterwards. For the legal basis of a signature drawn on a phone, see whether online waivers are legally binding, and see pricing for plan details.