Liability waiver form
A liability waiver captures risk acknowledgement in writing so the form itself is the evidence, not a separate document attached afterward. This one separates the participant details from the emergency contact so staff can quickly reach family without reading the whole submission. The required checkbox makes acknowledgement explicit — a record that the participant saw the terms, not a loophole they later claim to have missed.
The form beside this text is live. Fill it in and submit it — it validates exactly as it would for a real respondent, and saves nothing.
Required fields prevent incomplete submissions
The participant name, email, activity name, date and acknowledgement checkbox are all required. A missing name or an unchecked box is rejected in the browser and never reaches your records, so every waiver you receive is complete.
Send waivers to Slack or a webhook as they arrive
Each signed waiver is posted to your Slack channel, sent to a webhook endpoint, or both, the moment the participant submits. Every waiver is also in the CSV export with a timestamp, so you can reconcile against that rather than a chat archive.
No card required.
Liability Waiver
Live previewHow to build this form
5 steps in the editor. Nothing here needs a paid plan.
- Add text and email fields for the participant, plus phone for contact on the day of the activity.
- Add a text field for the activity or event name so you know which waiver template was used.
- Add a date field for the activity date so you can match waivers to the right session.
- Add text and phone fields for emergency contact, marked optional, so staff can reach family in case of injury.
- Add a required checkbox with the full liability release text, then a required text field labelled "Typed legal name" — this is their acknowledgement, not a drawn signature pad.
Fields in this form
9 fields, using 5 of the 19 field types available.
| Question | Field type | Required |
|---|---|---|
| Participant name | Short text | Yes |
| Yes | ||
| Phone on activity day | Phone | Yes |
| Activity or event name | Short text | Yes |
| Date of activity | Date | Yes |
| Emergency contact name | Short text | Optional |
| Emergency contact phone | Phone | Optional |
| I have read and agree to release the organizer from liability for ordinary injury sustained during this activity. | Checkboxes | Yes |
| Typed legal name (acknowledgement) | Short text | Yes |
What goes wrong with this form
Specific to a liability waiver form, not general advice about forms.
Putting the liability text in instructions instead of the checkbox label
If the release terms live only in the form description, a participant can later claim they never saw them. Put the exact text you want acknowledged into the checkbox label itself — "I have read and agree to release the organizer from liability for ordinary injury" — so the submission proves they read and clicked it.
Calling a typed-name field a "signature"
A field labelled "Signature" implies a drawn or biometric mark, which this form does not collect. Label it "Typed legal name (acknowledgement)" so nobody mistakes what was actually captured.
Mixing participant and emergency-contact fields together
If emergency details sit in the middle of the participant section, staff have to read past unrelated fields to find a phone number during an incident. Keep the emergency contact fields grouped and clearly labelled at the end of the form.
Questions about this form
Is a typed name the same as an electronic signature?
A typed name is a typed acknowledgement that the participant read and agreed to the liability release — it is not a drawn signature, a biometric, or a legally binding e-signature. The form collects their name, email, emergency contact and a checkbox proving they read the terms. Have your own legal counsel review the release text you put in the checkbox label.
What is the activity date field for?
It is a separate required field so you can match each waiver to the correct session or class date. If you run the same activity weekly, the date tells you which week the participant signed up for — useful if a waiver is disputed after the event.
Do I have to collect emergency contact details?
No, mark the emergency contact fields optional if you prefer. The participant still has to check the acknowledgement box and submit their own details; the emergency contact is there for staff to use only if something goes wrong on the day.