ZenotiHelp

Configure guest custom form requirements

ZTZenoti Docs Team Updated August 20, 2026 4 min readHow-to

Custom forms (waivers, health questionnaires, T&C acknowledgments, photo-release forms) can be made mandatory for guests at different lifecycle moments β€” first check-in, first class registration, before a specific class type, before an amenity booking. This article configures which custom forms apply to which guest categories at which moments.

Audience: Administrators who configure the legal and operational form requirements for guest entry and participation.


On this page


Before you begin

  • The custom forms themselves must already exist. See the forms category for authoring procedures.
  • You need administrator access to organization-level Configurations.
  • Coordinate with your legal team on which forms are mandatory vs. optional, and on minor-vs-adult differentiation.

Custom form requirement model

A form requirement consists of:

  • Form β€” Which custom form must be completed.
  • Guest category β€” Which guests must complete it (all, members, guests, minors, prospects).
  • Trigger event β€” When the requirement applies (first check-in, first class registration, before a specific class type, before an amenity booking, before a specific service).
  • Block behavior β€” What happens when the form is not completed (block the action, warn-only, log-only).
  • Re-prompt cadence β€” Whether and when the requirement re-fires (one-time, annually, before each high-risk class).

Configure a form requirement

  1. At the organization level, click the Configuration icon.
  2. Open Fitness > Forms > Requirements.
  3. Click + Add Requirement.
  4. Configure:
  • Form β€” Select the custom form.
  • Guest category β€” All / Members / Non-members / Minors.
  • Trigger β€” First check-in / First class registration / Before class type / Before amenity / Before service.
  • Block behavior β€” Block (the student cannot proceed without completing the form), Warn (a banner shows but allows proceed), Log (recorded silently).
  • Re-prompt cadence β€” One-time / Annual / Per-occurrence.
  1. Save.

The requirement applies on the next trigger event for matching guests.

Guest categories and exemptions

Common patterns:

  • Universal waiver β€” All guests must complete a general liability waiver before their first check-in. Block behavior: Block.
  • Minor-specific health form β€” Guests under 18 must have a parent/guardian-signed health form. Block behavior: Block. Re-prompt: Annually.
  • High-intensity class waiver β€” Specific class types (HIIT, hot yoga) require a separate intensity-acknowledgment form before first registration in that class type. Block behavior: Block.
  • Prospect intake β€” Non-member prospects must complete an intake form on their first visit. Block behavior: Warn.

Form lifecycle and re-prompts

  • One-time requirements never re-prompt after first completion.
  • Annual requirements re-prompt 365 days after the most recent completion.
  • Per-occurrence requirements re-prompt before every triggering event (typically used for emergency contact verification before a high-risk class).

When a re-prompt fires, the system surfaces the form requirement at the next trigger event for that guest. The Roster row, Kiosk welcome page, and Webstore checkout all display the form prompt.

  • Forms authoring. Form requirements depend on the underlying form definitions. Verify the form exists and is published before configuring a requirement.
  • Block behavior interacts with check-in alerts. A Block-level requirement appears as a red alert on the Visits page; staff must resolve it (have the guest complete the form on iPad / ZMA) before check-in succeeds.
  • Audit trail. Every requirement change and every form completion is logged.
  • Notifications. Configure notification templates to remind guests about pending forms (Email + Text) so they can complete forms before they arrive.

Impacts and considerations

  • Block behavior and operations. Block-level requirements halt the front desk if a form is not completed. Plan an iPad or ZMA station for in-center form completion to avoid backups during peak hours.
  • Legal review. Mandatory waivers and minor-specific forms typically require legal sign-off. Do not change Block behavior without legal review.
  • Form versioning. When a form is updated (for example, a new clause added), the system can re-prompt all guests to complete the new version. Configure this from the Forms authoring screen.
  • Cross-center handling. A form completed at center A may or may not count at center B, depending on your organization's policy. Configure the Center scope field on the requirement (Org-wide / Center-specific) to control this.

Troubleshooting

  • A guest completed the form but the system is still prompting. Verify the requirement's Center scope. A center-specific completion does not apply at other centers. Also confirm the form version was completed (a new version invalidates older completions).
  • The form appears for a guest who should be exempt. Verify the guest's category. Minors are categorized by date of birth; if the DOB is wrong on the profile, the system may treat the minor as an adult or vice versa.
  • The Block behavior is too aggressive at the front desk. Switch to Warn for non-critical forms; reserve Block for legally mandatory waivers.
  • The annual re-prompt does not fire on time. The re-prompt fires on the next trigger event after the 365-day window, not exactly on the 365-day anniversary. A guest who has not checked in for 18 months will be re-prompted on their next check-in.
Was this article helpful?
Your feedback helps us improve our documentation.