A liability waiver lets you require clients to confirm important information before booking (e.g., health status, informed consent, liability acknowledgment). This article walks you through the entire process — from creating a template to handling situations where a client hasn't signed the current waiver.
What is a liability waiver and when is it used
A liability waiver is a standalone declaration tied to a booking.
It can be required for online bookings as well as bookings created from the admin panel.
If a client hasn't signed the current version, their booking may be blocked.
Setting up a waiver template
Create a template: name, content, and form fields.
Add all required fields that should be filled out before signing.
Use the preview to verify that both the text and the fields make sense from the client's perspective.
After saving, test the flow with an actual booking.
Tip: Keep your waiver concise and easy to understand. A long or unclear text increases the number of abandoned bookings.
Waiver versions and why the change reason matters
When you edit an existing template, a new version is created. Clients who previously signed an older version may be asked to sign the current one.
When editing, provide a reason for the change (for internal change tracking).
Communicate significant changes to your clients ahead of time.
After publishing a new version, check the public booking form.
Signing the waiver during booking
If a waiver is active, the client confirms their consent and fills in the required data, including their signature, during the booking process.
Client has a current signature
The booking continues normally without any block.
Client does not have a current signature
The system asks them to complete and sign the waiver. The booking cannot be finished until this is done.
Override in the admin panel — creating a booking on behalf of a client
When creating a booking from the admin panel, you may encounter a situation where the client hasn't signed the current waiver. In that case, you can confirm an override and proceed.
When to use an override
Exceptional operational situations (e.g., a last-minute phone booking).
The client has already given consent through another channel and the signature will be added later.
When not to use an override
As a routine shortcut instead of getting the actual signature.
If you're unsure about the legal or operational implications.
Important: Using an override means you are knowingly proceeding with the booking without a current waiver signature.
Common problems and solutions
"The booking won't complete"
Check whether the client has signed the current version of the waiver and whether all required fields are filled in.
"The client signed before, but the system is asking for a signature again"
A new version of the template was likely published. A signature on an older version does not count as a signature on the current one.
Related articles