A template is the long-lived form identity. Its draft is editable working content. Publishing creates a version that can be used for signing. Keeping these states separate prevents an unfinished edit from becoming the document shown to a guest.
Create before publishing
Create a template with its name, then save its draft. Creating the template alone does not make a complete published signing form. A template that has never been published reports a null active version.
Build the draft from supported blocks. The block IDs matter because submitted values are keyed by those IDs. Keep a record of the exact structure your custom signing interface renders rather than assuming a label uniquely identifies a question.
Review the whole form
Before publishing, inspect the text, required fields, guardian flow and signature behavior. A technically valid form can still be confusing at the desk. Test a representative guest journey on a phone and make sure the resulting record can be found.
Have the document's wording approved through your organization's review process. The API publishes the content you supply; a successful publish response is not a legal review of that wording.
Respect version boundaries
Existing signed waivers keep the version they were signed against. Editing and publishing a new version should not be presented as changing what a previous participant agreed to. When reviewing a record, retrieve its version information rather than assuming today's active content was shown at signing.
A custom interface should account for a template changing between loading and submission. Read the submission response and handle validation or state failures clearly. Do not silently delete answers that no longer match the form.
Archive deliberately
Archive a template when it should leave the active workflow, and restore it when appropriate. Archiving a template is separate from voiding a signed waiver. Use the operation that matches the object you intend to change.
For a hosted booking flow, consider prefill links. For a custom form, continue with submitting a waiver.