Build waivers, intake forms and applications
Write a waiver, an intake form or an application once in Forms. Bookings ask for it, people fill it in on your website, and you see who signed which version.
Open Forms and choose New form. Pick the kind: a waiver (the words people agree to and sign with their name), an intake form (questions you need before a first visit), a general form, or an application.
Add questions: a short or long answer, an email, a phone number, a date, a choice, a checkbox, or a file upload. Mark a file question private for things like a health record or an ID: only you and team members whose role sees sensitive details can open it.
Give a form a short name, like waiver, and your offerings can ask for it when people book. Saving changes makes a new version. People who signed the earlier one keep their bookings; their next booking asks them to sign again.
Required for booking shows what each booking asks for, like “Studio waiver: sign before booking” or “Unlimited members only”, and when. Tap one to change when: before booking, before paying, by a deadline, or at check-in.
Signed lists who signed or sent what, newest first, marked Older version when their next booking asks again, or Ran out for a record past its date. Tap a name to open their page. The roster for each session shows who’s still missing one.
We tell you when someone signs a form or sends a record for a booking. While an offering asks for a form or record, Forms stays on so the links people get keep working.
For agents
forms.save (tier 2) saves a form: key, kind (general, intake, waiver with waiverText, application with application settings), title, questions (id, label, type including file, required, options, sensitive for a file), sensitive, health with consentText. A file question needs a key (an application, or a form a booking asks for). forms.list and forms.get read forms. forms.requirements lists each admission’s requirements with productId and when each is checked; change timing with forms.attach. forms.results lists who signed or sent what (current is false for an older version, ranOut for a record past its date). The Forms page (/forms) opens a form’s editor at ?form=<formId> (?form=new-waiver for a new one), a requirement at ?require=<productId>~<key> and an application at ?application=<submissionId>; forms.requirements gives each requirement’s title in the owner’s words. business.useTool can’t turn forms off while an offering asks for form: or file:; offerings.save turns forms on when it’s off and an admission asks for one (formsTurnedOn).