Waivers
Digital waivers everyone signs, even when wifi does not.
A tablet you hand across the counter, a link on your booking page, or a call from the system you already use. The queue does not stop because the connection did.
Offline, and honest about it
Plenty of products claim offline signing. The question nobody answers is what time ends up on the certificate.
What we record
The moment we received it — because that is the part we can attest to — and, beside it, what the device says happened, marked as a claim. The clock difference is computed by us rather than sent by the device.
Why it matters
Letting a device set the time makes the timestamp a claim by whoever holds the tablet. Ignoring the gap puts a time on a certificate nobody was in the room for. Both are recorded and only one is ours.
Initials, per child, by name
A template can require initials, a checkbox, a date or a photo, and the requirement freezes when the template is published — because what you were asked to initial is part of what you agreed to.
A guardian initialling once for three children is not the same act as initialling three times. So a per-child requirement becomes one line per child, naming them — and a court asked which child a release covered is not told "the template said per child".
Where the refusal lives
A signature is refused while anything required is unsupplied, and that refusal is in the database rather than in the form. Your step form checking first is a courtesy that stops somebody being bounced at a counter. It is not the guarantee, because a second interface, a kiosk or an API caller would each have to remember.
Ready when the next guest is.
Free for the first 25 agreements a month. No card to start.