Please wait while we prepare your content.

Please wait while we prepare your content.
Give guests a waiver before departure, handle individual and family signatures, and check completed records before the activity briefing.
Build a handover between the person sending trip instructions and the guide checking participants at departure.
01
Include your published waiver link in the pre-trip instructions you send through your existing communication process. Tell guests which activity the form covers and when to complete it. Sending the link is separate from confirming a signed waiver.
02
Ask each adult to complete their own waiver. Use the family / guardian flow for an authorised adult signing for minors. A tour organiser’s booking does not stand in for every participant’s signature; plan how families will receive the link.
03
Check completed records against the participants who arrive, and give anyone unfinished a way to sign before the briefing. Plan for connectivity at your actual departure site. Do not assume an ordinary browser link will work without a connection.
04
Retrieve a completed waiver and PDF copy when the team needs to review it. Keep your booking manifest and activity records in their appropriate systems; the waiver dashboard is not a tour scheduling or group-booking service.
Configure your activity wording and participant questions in template management. Collect only information your team needs and has a process to review. A form response is not an equipment check or medical clearance.
Video briefings with checkpoint questions are an optional module. They complement, rather than replace, the guide’s briefing and practical checks. Explore digital safety briefings.
For a remote site, review kiosk preparation and test your chosen device and recovery procedure before using it with guests. Agree a fallback for an unavailable connection.
This is operational guidance, not legal advice. Have a qualified adviser review the terms for your activity and location. No insurance acceptance or legal outcome is promised.
API access and webhooks support custom integration work. Do not assume a ready-made booking connector is included.
Read the Wall Walkers operational case study for a bouldering example, not evidence of a tour deployment.