Group and participant waivers
One booking. Eight guests. Three minors. One link.
Almost every booking in this business is one name and a card, and almost every trip is eight people. The gap between those two facts is where the morning goes.
What this document is
A set of waivers that belongs to a booking rather than to a person — each participant signing their own, each minor routed to a guardian, and one readiness answer for the whole group.
Also called: group waiver · party waiver · participant list · roster waiver · booking waiver
Where it goes wrong
Not a feature list. These are the three moments this exists for.
The booking has one name on it
Whoever paid. The other seven people exist only as a number in a field, and you will meet them for the first time at the moment you most need them to have already signed.
Somebody signs on behalf of everybody
It happens every day, on paper, because the form has one line and the queue is moving. It is also the first thing an insurer looks at and the first thing it throws out, because a release signed by somebody else releases nothing.
Seven of eight, and nobody knows which one
The count is easy. The name is the hard part, and the reminder you send to the whole group to be safe is the one that makes the six people who did sign think you have lost their paperwork.
What happens instead
The booker adds the party, once
Names, emails and phone numbers, or a paste from your reservation system through the API. Each person becomes their own signer rather than a line on somebody else's form.
Each person signs their own, and each minor gets a guardian
Adults get their own link on their own phone. A participant under age routes the consent to the guardian named for them, who signs from wherever they are — a separate document with a separate signature.
One answer for the whole booking
Ready, or not ready and the name of who is missing. On a phone, at a counter, or through the API into the screen your staff already look at.
We do not hold the booking
Reservations, payments, availability and the calendar stay in whatever runs them. What this holds is the document side: who has to sign what, who has, and what the group's readiness is right now. The API exists so the reservation system can ask that question and show the answer inside itself, which is where staff are already looking.
Who sends this one
The same document, sent by businesses that have nothing else in common.
Questions
Can one person sign for their whole family?
A guardian signs for each of their own minors, as a separate consent naming that child. An adult cannot sign for another adult, and the product will not pretend otherwise — that is the whole reason the group is modelled as people rather than as a count.
What if the party changes the night before?
Add or remove people and the links follow. Signatures already collected stay; a person added at ten at night gets their own link and can sign before breakfast.
How do walk-ups join a group that is already half signed?
A QR code at the counter adds them to the same booking. The readiness count includes them from the moment they scan it.
Can we see who has not signed without opening a list?
Yes — the count and the missing names come back from the API, so a reservation screen, a tablet at a counter or a text to the guide can carry them. The list is there too, for the person who wants to look.
Ready when the next guest is.
Free for the first 25 agreements a month. No card to start.