A waiver template builder with room for the details

Your form is a conversation with someone who may be standing in a lobby, holding a bag and watching a child. Good field order makes that conversation easier. The template builder lets you arrange the document and the information you need without making the guest work through an unrelated questionnaire.

Build around an approved document

Start with the wording your organization has approved for the activity. Add rich text for the document, then the participant information required to identify the signer and support your workflow. Signature and initials blocks serve different purposes, so decide where each belongs rather than adding both everywhere. A required field should have an operational reason. When staff cannot explain why an answer is needed or who uses it, reconsider whether it belongs on the signing form at all.

Choose blocks for specific jobs

Use questions to collect answers the team can act on. Guardian and minor fields should reflect the relationship between the adult signing and the children covered by that submission. Photo or identity capture deserves particular care: consider whether it is necessary, how guests will complete it on a phone, and who will be allowed to view the result. A field that technically fits in the builder can still create unnecessary friction or collect information your operation does not need.

Review the experience before publishing

Read the form in the order a guest will encounter it. Check headings, explanatory text, required controls and the placement of the signature. Try ordinary answers and incomplete answers. If questions use flag rules, confirm what triggers a flag and how the desk will review it. Then have another person attempt the form without coaching. Their hesitation usually reveals more than your own preview because you already know what each label was intended to mean.

Treat publishing as a controlled change

Editing a draft and publishing a version are separate decisions. Assign a person who can approve the final form, especially when the document wording or required information changes. Existing signed waivers retain their associated version, so do not describe a newly published form as rewriting earlier records. After publishing, test the link guests actually use and confirm that it opens the intended version. A correct draft is not enough if a website or printed sign still sends people to a different template.

Keep a short change note outside the guest form: what changed, who approved it, when it was published and whether staff need new instructions. That record is useful when a colleague asks why two participants saw different questions.