In development. This is on the roadmap and not available yet. The guide is here so it is ready the day it ships.
Event Management

Collecting a signed waiver during checkout

Have attendees read and accept your liability waiver as they buy, with the acceptance kept on the ticket.

3 min readUpdated 2026-07-29

Anything physical—a breathwork intensive, an ice bath, a trail race, an aerial class—usually needs a waiver, and collecting them on paper at the door is the slowest part of the morning. Attendees arrive in a rush, someone forgot a pen, the line backs up, and you're asking people to sign something they haven't had time to actually read.

A digital waiver on BrightStar moves that step earlier, into checkout, where there's no line and no rush. The attendee reads your agreement text and has to accept it before the purchase completes — the order simply won't go through otherwise. That acceptance is then stored against their ticket, not on a piece of paper that has to be filed, scanned, or hunted for later if a question comes up.

You supply the wording yourself. BrightStar's job is to present it at the right moment and record who agreed to it and when.

One waiver per attendee, not per order

A waiver is a statement made by a person, so BrightStar collects it per attendee rather than once for the whole basket. If someone buys four tickets — say, for a group heading into an ice bath session together — they're asked for four separate acceptances, each tied to one of the four named attendees, rather than one signature covering everyone else in the order.

That matters because the purchaser isn't necessarily the person taking the physical risk. The person doing the trail race or the aerial class is the one whose agreement you actually need on file, and BrightStar asks for it directly from them rather than assuming the buyer can speak for a friend.

Because the record sits on the ticket itself, it travels with it. When you look up an attendee before the doors open, whether they accepted the waiver is part of what you see, so you know in advance who still needs handling rather than finding out at the front of the line.

Keep the waiver text you paste in as the exact wording you want to rely on. What gets stored is the attendee's acceptance of what was shown to them at that moment — not a general idea of a waiver, but that specific text. If you change the wording partway through your sales window, earlier attendees will have accepted an older version, which is why it's worth treating the text as final before you open sales rather than editing it once people have already started buying.

Why the acceptance stays with the ticket after checkout

Because the acceptance is stored against the ticket rather than in a separate document, it stays available to you well past the moment someone buys. At a check-in table for a breathwork intensive, a staff member pulling up an attendee's record sees the waiver status right alongside their name — there's nothing extra to dig for, and nothing on paper that could be left at home, smudged, or misplaced overnight.

That same record is still there after the event ends, for as long as you need to refer back to who agreed to what. Because it's tied to the specific text you showed at checkout, it also tells you exactly what version of the wording that attendee saw, which is the whole point of keeping the wording locked before you sell.

What happens if someone doesn't accept it

The acceptance isn't optional once you've set the waiver up: the order can't be completed until the attendee accepts it. That's what makes this different from a paper form someone can skip past in a hurry at the door — the purchase itself is the checkpoint, so there's no way to end up with a ticket holder who never actually saw or agreed to your wording.

That also means you don't need a fallback plan for what happens if someone shows up having never encountered the waiver at all. If they have a ticket for a session that requires it, the acceptance already exists, because it was a condition of getting that ticket in the first place.

How the waiver appears at checkout

The sequence is the same for every attendee on a ticket type that requires a waiver:

  1. 1You paste your final waiver wording into the event setup, as one of the attendee questions attached to the relevant ticket types.
  2. 2At checkout, the attendee buying that ticket type sees the waiver text presented directly to them.
  3. 3They have to accept it before the purchase can go through — the order won't complete otherwise.
  4. 4Their acceptance, along with who agreed and when, is stored against their ticket.

Common questions

Where does the attendee sign the waiver?

During checkout on BrightStar. The waiver text is presented as part of the purchase flow and has to be accepted before the order can be completed, so there is nothing to collect on paper at the door.

Read more

This is what removes the door bottleneck entirely: instead of a table, a clipboard, and a line of people signing something they haven't read, the acceptance happens at the moment of purchase, when the attendee actually has time to read the text. By the time they arrive, that step is already finished.

Is the waiver collected once per order or once per attendee?

Once per attendee. A waiver is a statement made by a specific person, so on BrightStar someone buying several tickets is asked to record an acceptance for each attendee rather than agreeing on their behalf.

Read more

Picture one person buying tickets for three friends to a trail race. Each of those three friends is asked to accept the waiver themselves, tied to their own name, rather than the purchaser signing away liability for people who aren't even present at checkout. It keeps the record honest about who actually agreed.

Where is the signed waiver kept?

The acceptance is stored against the attendee's ticket in BrightStar, so it appears when you look that attendee up and stays available to you after the event rather than living in a stack of paper.

Read more

Because it's attached to the ticket record rather than a separate file, it doesn't get lost, left in a car, or rained on at an outdoor check-in. It also stays tied to the exact wording that was shown at the time, so the record tells you not just that someone agreed, but to what.

Can I require a waiver on some ticket types but not others?

Yes. The waiver is set up as one of your event's attendee questions on BrightStar, so you can apply it to the ticket types that need it — the participants — and leave it off ones that do not, such as spectator or volunteer tickets.

Read more

This matters because not everyone at a physical event is taking the same risk. A spectator watching a trail race or a volunteer helping run an ice bath session isn't doing the activity itself, so tying the waiver to specific ticket types lets you ask for it only from the people actually stepping into the risk.

What happens if I change the waiver wording after people have already bought tickets?

Attendees who already accepted the waiver keep the acceptance they gave for the wording they saw at that time; it doesn't retroactively update to match new text. That's why the source recommends finalizing your wording before you start selling.

Read more

In practice this means your event could end up with two groups of attendees who technically agreed to slightly different versions of the same waiver, depending on when they bought. That's not a problem if the change is minor, but it's worth knowing about before you edit live wording rather than discovering it afterward.

Ready to get started?

Create your first event on EveryEvent Rio de Janeiro — it’s free.