Send the form before the meeting point. Keep the departure roster clear, so your guide can spend the first few minutes welcoming people and explaining the experience.
Unlimited waivers. From $9/month.Gather signatures before the meeting point, so your guide can focus on the people and the plan.
Email or text the people who need to sign, then review the pending names before departure.
Prepare the pre-trip messageKeep activity information and required fields together in a published template your team can recognize.
Match forms to toursPlease review the details before you sign.
A guardian can add minors and sign once, while the roster still identifies each person joining the tour.
Organize family groupsScan the confirmation, check the waiver status, and continue with the tour briefing and departure process.
Plan the arrival checkInteractive product examples with sample data. Try the form blocks, invitation filters, and check-in statuses.
At the meeting point, guests are trying to find the guide, check a bag, and make sure they are in the right group. Put the signing link in the pre-trip message so the form is familiar before that moment. Pair it with the exact meeting instructions and a contact method for a guest who is running late.
A group booking does not always include every participant’s contact information. Ask the organizer to pass the link to each person who needs to sign, or collect the roster for individual email or text invitations. Avoid asking one traveler to enter everyone’s details simply because they made the reservation.
Before departure, compare the signed names to the people actually attending. Review substitutions and additions explicitly. If the tour has a firm departure time, explain the paperwork deadline in advance and give staff a consistent process for a guest whose form is still incomplete.
Decide which guest questions belong in the form and who needs to review them. A request for assistance may require a conversation before arrival rather than a last-minute note on a roster. Use flag rules to surface answers your team has agreed to handle, and avoid collecting information that has no useful next step.
For families, keep each minor connected to the required guardian signer. For a corporate outing or school group, distinguish the organizer’s role from the signer’s role. A good roster explains who is coming and whose paperwork is ready without requiring the guide to interpret those relationships at the meeting point.
A signed waiver is not a decision about route conditions, readiness, or participation. The National Park Service’s trip-planning guidance emphasizes preparation and the environment you will encounter. Build your own briefing and departure checklist around the experience, with paperwork as a separate item.
See the ranch and outfitter guideUse the reviewed document for your actual tour, not a single vague agreement for every possible activity. Give the template a name that the reservations team can distinguish, especially when you offer several departure points or different experiences under one brand.
The builder supports rich text, questions, initials, signatures, minors, and photo or ID capture. Start with the fields your process needs, then check the mobile reading order. Activity details should be recognizable before a guest reaches the signature, rather than appearing as an unexplained title in a booking attachment.
Keep a separate, concise trip message for directions, timing, and practical preparation. When the route or experience changes, have the person responsible for the document decide whether the form needs revision. Publishing a new version preserves the version on earlier signed records; it does not decide whether earlier guests need to sign again.
| Field or section | Why include it |
|---|---|
| Participant name and contact | Identify the actual traveler rather than just the reservation owner. |
| Tour or experience | Present the reviewed information for that activity. |
| Guardian and minors | Connect younger participants with the required signer. |
| Relevant guest questions | Flag requests that need a team conversation before departure. |
| Signature and initials | Collect the approved acknowledgments in a readable flow. |
| Document version | Retain the wording associated with the signed record. |
At arrival, a confirmation QR code gives staff a way to retrieve waiver status. Match the participant’s name, resolve any mismatch, and move on to the briefing. Keep reservation payment, attendance, and waiver completion separate so one completed task is not silently standing in for another.
For departures with unreliable connectivity, ask guests to sign while they still have access and review completion before leaving the base. A draft saved after a dropped connection is useful for finishing the form later. It is not a completed signature or a guarantee that your check-in tools will operate offline.
Waiver.com retains signed versions, renders PDFs, and keeps an access log. Set up a consistent retrieval process for a particular person and departure. If you export participant lists or PDFs, decide who needs those files and where they belong rather than leaving them on a shared guide device.
Test a direct booking, a group organizer sharing a link, a late substitution, a guardian with a child, and a guest without their confirmation code. Use the same devices and meeting-point conditions your team will encounter. If an instruction only makes sense after a teammate explains it, revise the message before the next departure.
The REST API and webhooks offer a path to connect signed, voided, and checked-in events with other tools. Your integration should identify the participant and departure, account for duplicate notifications, and keep booking changes from producing a misleading status. Begin with the handoff the team needs, then automate the parts you can define clearly.
Explore the API and webhook previewNational Park Service: Trip Planning Guide ↗Background for advance preparation, location awareness, and keeping the trip plan separate from the signing task.
Choose the plan that fits your locations. Busy weekends and new participants do not add a per-waiver charge.
For one location, with room for every participant.
7-day free trial. Card required.
For businesses that need one plan across all their locations.
7-day free trial. Card required.
For organizations with requirements to work through together.
Your selected plan starts billing after the 7-day trial unless you cancel before it ends.
Text allowances renew every month. Starter includes 200 SMS and Growth includes 500 SMS each month, even when you pay annually. Extra messages are $0.02 each.
The details to work through before you introduce the new signing flow.
Yes. Add the public signing link to the confirmation or pre-trip message, or invite participants by email or text. Test the message on a phone and keep the link easy to find alongside the departure instructions.
Have the organizer distribute the link to each required signer, or send individual invitations from the participant roster. Reconcile names before departure. The reservation owner should not be treated as authorized to sign for all travelers simply because they booked the group.
Yes. Encourage guests to finish before traveling and review the roster while connectivity is available. A saved draft helps someone resume an interrupted signing flow, but it is not a completed waiver and does not promise offline check-in.
Check which document they signed and whether it applies to the new experience under your policy. Route changes, different activities, and revised wording may need review. Keep the old signed record rather than silently replacing its document with the latest template.
An integration needs to be implemented for your actual booking system and workflow. Waiver.com provides a REST API and relevant webhooks, but that is not the same as a prebuilt connection to every reservation platform. Confirm the participant and departure mapping before relying on automated status updates.