ResytechResytech Docs
Waivers

Track Waiver Submissions

How to view, search, and monitor signed waiver submissions from the dashboard, individual waivers, and booking detail pages.

Every time a customer signs a waiver, Resytech creates a submission record with a full audit trail. You can track submissions from three places: the waiver list page, an individual waiver's submissions view, and the booking detail page. Each submission captures the signer's identity, linked booking, timestamps, and a reference to the signed PDF stored in secure cloud storage.

Viewing submissions for a specific waiver

  1. In the sidebar, click Waivers.
  2. Click the waiver you want to inspect. The waiver list shows a quick summary including submission count and status:
Status labelMeaning
Not usedZero submissions. The waiver has never been signed.
Low usageFewer than 10 submissions.
Active10 or more submissions.
  1. On the waiver detail page, navigate to the Submissions section to see all submissions for this waiver, ordered by most recent first.

Viewing submissions for a specific booking

  1. Open the booking detail page for the reservation you want to check.
  2. Navigate to the Waivers tab.
  3. The table shows all waiver submissions linked to that booking.

This view is useful for front-desk staff verifying that every guest in a booking has signed the required waiver before check-in.

Live updates

The booking Waivers tab refreshes itself every 5 seconds while it is open, so you can watch signatures arrive without reloading the page. A green Auto-updating indicator above the list shows when it last checked, and the refresh icon next to it forces an immediate check.

Submissions that arrive while you are watching the tab are highlighted with a green New badge, making it easy to spot the guest who just finished signing at the kiosk. Refreshing pauses while the browser tab is in the background and resumes the moment you switch back to it.

Submission data

Each submission record contains:

FieldDescription
Signer(s)The legal name(s) captured from the Signer Identity component(s). If multiple signers are present (e.g., a parent and minor), the count is shown as a badge. The email address(es) entered on the form are shown underneath the names.
CustomerThe linked customer record name and email, if the signer was matched to an existing customer or a new customer was created via "Capture Signer as Customer."
SubmittedThe date and time the waiver was signed, formatted in your locale.
WaiverA reference to which waiver template was signed (visible in the booking view, where submissions from multiple waivers may appear).
BookingThe linked booking ID, if the customer looked up a reservation during signing.

Searching submissions

In the booking waiver tab, use the search bar to filter submissions by signer name, customer name, or customer email. The search is case-insensitive and matches partial strings.

On the waiver detail page the search also matches the email addresses entered on the form, so you can find a submission even when the signer was never linked to a customer record.

Exporting submissions and email addresses

To pull signer details collected by a waiver into a spreadsheet or a mailing tool:

  1. Open the waiver from Waivers in the sidebar.
  2. Optionally use the search bar and the date filter (All Time, Today, Last 7 Days, Last 30 Days) to narrow the list.
  3. Click Export in the page header.
  4. Tick the columns you want. The choice is remembered on this device for next time.
  5. If the list is filtered, pick Current filters to export only the rows currently shown, or All submissions to ignore the filters.
  6. Click Export. A CSV file downloads (on the mobile app it opens the share sheet).

The file has one row per submission. Columns you can choose from:

ColumnContents
Submission IDThe submission's unique ID, matching the ID column in the table.
StatusSubmitted, Pending Counter-Signature, Counter-Signed or Rejected.
Submitted AtSigning time in the location's time zone.
Signer NamesThe name(s) from the Signer Identity component(s).
Signer Emails / Signer PhonesEvery email address and phone number entered on the form, separated by ;.
Customer Name / Customer EmailThe linked customer record, if any (see How submissions are linked to customers).
Booking Confirmation / Booking DateThe linked booking, if any.
Covered GuestsGuests selected on a guest-selection field, or the guest the signer was matched to.
IP Address / User AgentWhere and with what the waiver was signed.
Counter-Signed At / Counter-Signed ByFilled for counter-signed waivers.
Rejected At / Rejected By / Rejection ReasonFilled for rejected submissions.

Only emails and phones that were typed into an Email Input or Phone Input component on the waiver are exported. If your waiver does not include one, add it in the waiver editor; submissions signed before that change will not have a value. Answers to other form fields (date of birth, address, and so on) live only in the signed PDF and are not exported.

The same person signing more than once appears once per submission. Most spreadsheet and email-marketing tools de-duplicate on import; otherwise remove duplicates on the Signer Emails column before importing.

How submissions are linked to customers

When a waiver is submitted, the system attempts to match the signer to an existing customer record by email address:

  1. If an Email Input field is present on the waiver and the customer enters an email that matches an existing customer in your location, the submission is linked to that customer.
  2. If no matching customer exists and Capture Signer as Customer is enabled on the waiver, a new customer record is created automatically with:
    • Name from the Signer Identity field.
    • Email from the Email Input field.
    • Phone from the Phone Input field (if present).
    • Source set to "waiver".
  3. If no email is provided or no match is found and auto-capture is off, the submission is stored without a customer link.

Submission security and audit trail

Every submission includes tamper-evidence and forensic data:

  • Data Hash (SHA-512) -- A cryptographic hash of the submitted form data, computed identically on both client and server. If the hashes do not match, the submission is rejected.
  • File Hash -- A hash of the generated PDF bytes, stored alongside the submission.
  • Metadata Hash -- A hash of the full metadata JSON (browser fingerprint, IP, user agent, audit log).
  • IP Address -- The signer's IP address at the time of submission.
  • User Agent -- The signer's browser and device information.
  • Browser Fingerprint -- A client-side fingerprint for additional signer identification.
  • Audit Log -- A timestamped record of when the document was opened, when consent was checked, when each field was interacted with, and when the form was submitted. The server validates that all required fields have interaction events and that timestamps are chronologically consistent.

Rate limiting

To prevent abuse, submissions are rate-limited:

  • With a booking linked: Maximum 25 submissions per IP address per booking, and 100 total submissions per booking.
  • Without a booking: Maximum 25 submissions per IP address per day.

Submissions that pass CAPTCHA verification (Cloudflare Turnstile) bypass IP-based rate limits.

Tips

  • Check the Waivers tab before check-in. Use the booking detail page to quickly verify all guests have signed.
  • Use the submission count on the waiver list as a quick health check. If a waiver shows "Not used" but should be active, double-check that the URL is being distributed correctly.
  • Submissions are immutable. Once signed and stored, a submission cannot be edited or deleted. This preserves the legal integrity of the document.
  • Customer linking is automatic. As long as your waiver includes an Email Input field, the system handles matching. Enable "Capture Signer as Customer" if you want walk-in signers added to your CRM.

On this page