How a trampoline park runs waivers with Waiver.com

A birthday party at a trampoline park is a single reservation with a long list of participants, most of them children, most of them arriving with an adult who is not their guardian. The host has paid, the parents have dropped off, and the desk has a few minutes to work out whose paperwork is done. This walkthrough describes how a park could handle that with Waiver.com. It is illustrative, not an account of a real customer, and it starts where the park's problem starts: with the party booking, well before the party.

Setup

The park treats every party as an event. Before that can work, it needs a form built for a roster. It starts from the event participation waiver template, which already expects an event context and guardian details, and replaces the sample with the park's approved wording. The guardian and minor fields are enabled so that an adult can add each child they are responsible for and sign for the submission.

Questions are kept to a minimum because a parent is completing this on a phone in the school car park. There is a required acknowledgment above the signature and an optional question that lets the guardian note anything the court staff should know; that question carries a flag rule so any answer is routed to a supervisor rather than lost in a list. The form states plainly, near the top and again beside the signature, who the park requires to sign for a child. That wording came out of a conversation with the park's adviser, and the guide to liability waivers for minors framed the questions they asked.

A separate general admission template handles walk-in jumpers, so the party form never has to serve both purposes. The manager tests the party form with one child, then with several children whose surnames differ from the guardian's, and checks how each child appears on the resulting record. Publishing is a deliberate step taken by the manager after that review, and a change note is kept outside the form.

Signing

When a party is booked, the office creates an event named for the date, time and host so staff can tell it apart from the other parties that afternoon, attaches the party template, and adds the host as the first invitation. The host does not sign for the guests. Instead the host receives a message, prepared using preparing a party organizer message, that explains the guardian requirement and gives a link to forward to each household.

Households that the host adds to the roster receive their own invitation by email or SMS, naming the park, the party and who should sign. On the guardian's phone the form opens in a browser: the document, the guardian's details, an add-child section, the optional note question and a finger-drawn signature. The completion screen shows a confirmation code and suggests arriving early enough for check-in.

The park reviews the roster's signing progress in the days before the party and sends a single reminder to households still unsigned. Staff check for an existing record under a different contact detail before re-sending, because a guardian who signed through the public link on the park's website will not show as signed against their invitation until the desk matches them. On the day, a bank of tablet kiosks at the entrance runs the kiosk workflow for anyone who has not finished, with the screens angled so one family's answers are not visible to the next.

Check-in

Parties arrive in a burst. The desk opens the event, which gives a view of the roster with who has signed, and then works through the arriving children. A host standing at the counter naming children is a starting point; the check itself is done by finding each child's record and reading the minor details, not by matching an adult's name. A child whose guardian signed shows valid and is checked in, and the arrival appears in the event's log.

A child without a record goes to a defined waiting spot with a staff member while the accompanying adult is asked whether they are the guardian. If they are, they sign on a kiosk. If they are not, the park's written exception process applies, and the supervisor, not the receptionist, handles it. Late additions, handled as described in handling late additions to an event, are added to the roster so the party's progress view stays truthful.

Flagged notes from the optional question appear on the record at check-in and are passed to the court monitor for that party's session. A signed status never stands in for the safety briefing, which happens at the court regardless. Walk-in jumpers on the general admission form use the main entrance QR code and are checked in against that template, so the party roster is not cluttered with strangers.

Records

After the party, the event holds everything: the roster, each guardian's record with the children on it, the signed PDFs with their version, and the arrival log. When a parent calls the following week asking whether their child's form was completed, staff search by the child's name and confirm using the guardian's contact detail. The handling group waivers routine covers the harder cases, such as a child who attended several parties in the same month.

Access follows roles. Party hosts see nothing inside the workspace; they only ever receive messages. Receptionists search and check in. Supervisors review flags. The general manager publishes templates, manages members and exports. Exports are used for a defined purpose, such as reconciling a month of parties against bookings in a CSV, and the file is stored in the approved folder rather than emailed.

Expiry rules mean a guardian who signed for a party in an earlier season sees expired when the family returns for open jump, and the desk explains the renewal and sends the current general admission link. The earlier party record remains intact with its own version and date.

What to adapt

A park with several entrances can run signing at each, following running signing at multiple entrances, while keeping one event per party. A park that also hosts school visits would add a school template and lean on the coordinator to distribute links, with the same rule that the coordinator does not sign for the children. A park group with more than one site adds each as a location and decides which templates are genuinely shared.

The part that does not change is the separation between the person who booked and the people who must sign. For plan and SMS allowance details, see pricing.