Agree the form before configuring it
Gather the approved wording, participant questions and signing requirements for each activity. Identify the people responsible for legal wording and operational checks. A digital form does not make generic waiver text appropriate for every activity or jurisdiction.
Map the participant journey
Decide who receives the link, how group members are represented and what happens for minors. Test the form on a guest’s phone, including a long name, a missing required field and a participant who returns later. Check the signed version and booking association in the record.
Prepare the arrival team
Show staff how to identify completed, incomplete and unmatched records. Agree who resolves each exception. Keep a documented fallback for unavailable devices or connectivity and verify the actual offline behaviour of the selected setup.
Pilot before widening the rollout
Use a limited set of departures and review guest questions, on-site signing time and record retrieval. Confirm exports and access before replacing an existing process. Keep the approved wording and version history under clear ownership as the operation changes.
A concrete example
Test a solo adult, a family group, a participant without a completed form and a changed booking. A form that works once on an office laptop has not yet passed the departure-day test.
Put it to work this week
Choose one activity for the pilot and give staff a written fallback before changing the live process.