Send a liability waiver to every workshop registrant
Each workshop registration sends a DocuSign waiver to the attendee, signed and filed well before the event date.
New form submission on your workshop registration form
Send a DocuSign waiver envelope to the registrant for signature
One-directional. A submission triggers the action — nothing is written back into your form.
Anything hands-on — a pottery studio, a knife-skills class, a climbing introduction — needs a signed waiver, and the worst place to collect one is at the door on the morning. People arrive late, the clipboard goes missing, and someone ends up running the session unsigned.
Registering and waiving become one step here. The registration submission sends the waiver through DocuSign as it lands, so signed copies sit in your envelope list days ahead. On the day the organiser checks a completed list instead of a pile of paper.
Setting it up
- 1
Publish the workshop registration form and keep Workshop You're Registering For as a fixed option list, so each waiver can name a specific session rather than "the workshop".
- 2
Load your waiver into DocuSign as a template with one signer role, one required signature tab and a date-signed tab.
- 3
Add a text tab for the session name and another for accommodation notes your instructor should read before the session starts.
- 4
Build the Zap with formformform's New Submission trigger pointed at the registration form.
- 5
Add the DocuSign envelope-from-template action and map Full Name and Email Address to the single recipient.
- 6
Map Workshop You're Registering For into the session tab so the waiver states which class it covers.
- 7
Set an envelope expiry that falls before the workshop date, so unsigned waivers surface as expired rather than sitting open indefinitely.
- 8
Register yourself as a test attendee, sign the waiver, confirm the envelope completes, then enable the Zap.
What maps where
Using the Workshop Registration Form as the starting point. These are its real fields — swap in your own and the mapping works the same way.
| Form field | DocuSign |
|---|---|
| Full Name | Signer name on the waiver |
| Email Address | Recipient email for the waiver envelope |
| Phone Number | Contact tab on the signed waiver record |
| Workshop You're Registering For | Session name tab in the waiver text |
| Accessibility & Accommodations | Notes tab the instructor reads before the session |
Variations worth knowing
Add a filter on Workshop You're Registering For so waivers go out for hands-on classes and lecture-only registrants are skipped. Everyone still lands in the same responses list, so headcounts stay in one place.
Switch on reminders in the waiver template — every two days works well for a class booked a fortnight out. Unsigned registrants get nudged by DocuSign rather than by the organiser on the morning.
If something isn't arriving
Set the envelope's sender name to your studio rather than a personal account, and warn people on the registration confirmation to expect an email from DocuSign. Resending is one click from the envelope view.
The session tab is being fed a value your template does not recognise. Keep the option labels on Workshop You're Registering For identical to the session names in DocuSign; free-text answers cannot be matched reliably.
Frequently asked questions
Can the waiver be signed inside the form itself?
No. formformform has no e-signature field. The Materials Acknowledgment checkbox records that someone ticked a box, which is not an executed waiver — that is precisely the job the DocuSign step exists to do.
Do I need one DocuSign template per workshop?
Only if the wording differs. A single template covers every session when the risk language is the same, because the session name arrives as a mapped value. Separate templates are worth the upkeep only for genuinely different activities.
What about attendees under 18?
Use conditional logic on the registration form to reveal a guardian's name and email when the attendee is a minor, then map the guardian as the DocuSign recipient. The waiver reaches the person who can legally sign it.
Related automations
- Get the order spec signed before production starts
Every order builds a DocuSign purchase agreement with the exact spec, so the customer authorises it before anything is cut.
- Send an NDA before every demo call
Every demo request generates a DocuSign envelope carrying your mutual NDA, addressed to the person who asked for the call.
- Send lease disclosures to every rental applicant
Each rental application sends the required disclosures and lease document to the applicant for signature.
- Send the offer packet the day a candidate accepts
The acceptance submission fills your DocuSign offer template and sends the letter and tax forms as one envelope.
- Turn a project scope request into a signed contract
A scope request populates your services agreement template and goes out for signature without an account manager touching it.
- Append every support request to a running log
Every help desk submission appends a line to one shared Dropbox text file, so the team reads the day's requests in order.
Build the form first
The automation needs somewhere to fire from. Publish a form, connect it once, and every submission from then on runs this flow.
Start free