How to review a waiver template before publication

Treat publication as the end of a review, not the moment to discover whether the form works. Separate content approval from the practical guest test so a technically valid form is also understandable and usable.

Confirm the approved content

Identify who approves the document wording and which activity it covers. Check that the draft contains the intended text, not an earlier copy pasted during setup. Resolve any unclear scope before publishing.

Software validation is not a review of legal wording. Keep that approval in your organization's established process, and record which draft was reviewed so a last-minute edit does not bypass it.

Walk through every required path

Complete the form as an adult, then as a guardian if the form supports minors. Leave a required field empty to inspect the correction message. Test typed and drawn signatures only where the relevant settings allow them.

Read long text blocks on a phone. Check that headings, labels and buttons remain understandable without zooming. Use mobile testing to catch issues hidden by a large desktop screen.

Follow the record beyond the final button

Confirm that the signed sample reaches the intended workspace and can be found by the desk. Inspect the participant details and the document version. Allow time for the PDF to be prepared rather than treating a pending file as a failed signature.

Then check every public link that will introduce the new version. Tell staff what changed, who the form applies to and where to raise an exception. Keep the earlier signed records intact rather than trying to update their historical content.

Before you call it ready

• The content owner approved the intended draft.
• Adult and guardian paths were tested where applicable.
• Required-field errors are understandable on a phone.
• The completed record and version can be found.