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
- In the sidebar, click Waivers.
- Click the waiver you want to inspect. The waiver list shows a quick summary including submission count and status:
| Status label | Meaning |
|---|---|
| Not used | Zero submissions. The waiver has never been signed. |
| Low usage | Fewer than 10 submissions. |
| Active | 10 or more submissions. |
- 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
- Open the booking detail page for the reservation you want to check.
- Navigate to the Waivers tab.
- 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.
Submission data
Each submission record contains:
| Field | Description |
|---|---|
| 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. |
| Customer | The 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." |
| Submitted | The date and time the waiver was signed, formatted in your locale. |
| Waiver | A reference to which waiver template was signed (visible in the booking view, where submissions from multiple waivers may appear). |
| Booking | The 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.
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:
- 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.
- 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".
- 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.