If a guest submits a waiver with bad info — gibberish answers, the wrong name, an obviously invalid date of birth — admins can now formally reject the waiver and prompt the guest to re-sign. Previously, your only workaround was to manually send a fresh waiver link, which created a separate signature record that didn't always attach properly to the booking.
How to reject a waiver
On any signed waiver in a booking, you'll now see a Reject action. Clicking it will:
Mark the waiver as rejected (technically, it moves to a VOIDED state)
Free up the booking spot the guest was holding (so they can re-sign cleanly)
Automatically email the guest, prompting them to submit a new waiver
Record the rejection in the audit log (admin name, timestamp, reason)
The original submission isn't permanently deleted — it's preserved in the rejection history for record-keeping.
Resending a pre-filled waiver
When you resend a waiver invite to a guest, the form now pre-fills with their name and email from the booking — so they don't have to retype it. You can also change the destination email before resending if the original email was wrong. The previous invite link is invalidated when the new one is sent, so old links can't be reused.
What about post-trip rejections?
If you reject a waiver after the trip has already happened, the rejection is still recorded in the audit log, but the booking spot isn't released (since the trip is complete).
Where you'll find the actions
From the booking detail page, look at the Waivers section. For each guest:
Signed waivers show a Reject action
Pending waivers show Resend and Edit Email actions