7 Waiver Automations Gyms Run Before Class Starts in 2026
A day in the life of a fitness operator
The 6:00 a.m. strength class has fourteen people booked and one coach. At 5:52 a.m. two of them are new — a friend brought along by a member, and a trial booking made online well after closing the previous night. Neither has a signed waiver on file. The coach has ninety seconds of slack in the whole hour and is currently loading bars.
What happens next is the same in almost every facility. Someone produces a clipboard or unlocks a tablet, the two new participants scribble something while standing up, and the class starts three minutes late. Nobody reads what was signed. The paper goes into a folder behind the desk, or the tablet form goes to an email address that three people can technically access and none of them monitors. By the 9:30 a.m. class the same thing will happen again with a drop-in, and by Saturday nobody will be able to say with confidence which participants from Tuesday have a current release on file and which do not.
The uncomfortable part is that this is not a discipline problem. The coach did exactly the right thing given the constraint: a person is standing in front of them, the class has to start, and the only tool available operates at the speed of a human holding a clipboard. The constraint is that waiver collection was designed as a front-desk event when the actual commitment happens hours earlier, at booking. Everything below is about moving the collection back to that moment.
TL;DR
The scale of the problem is not small. According to the Health & Fitness Association, 81 million Americans belonged to a gym, studio or other fitness facility in 2025 — an all-time high and a 5.2% increase over 2024. Every one of those relationships starts with a document that has to exist, be current, and be findable.
81 million Americans held a fitness membership in 2025.
Seven automations do the work: fire the waiver request off the booking event, pre-fill it from the member record, deliver it by text rather than email, gate check-in on signature status, version the document and re-request when it changes, escalate only the handful who ignore it, and file the signed copy against the member record with a timestamp. Together they move waiver collection out of the ninety seconds before class and into the twelve hours after booking, which is the only place it has ever fit.
| Benchmark | Figure | Period |
|---|---|---|
| Americans with a fitness facility membership | 81 million | 2025 |
| Year-over-year change in membership | +5.2% | 2024 to 2025 |
| Total visits to US fitness facilities | Nearly 7 billion | 2025 |
| Members who never visited once | 4.6% | 2025 |
| Fitness trainers and instructors employed in the US | 370,100 | 2024 |
| Median annual pay for trainers and instructors | $46,180 | 2024 |
| Standards and guidelines in ACSM's facility manual | 35 standards, 38 guidelines | 5th edition |
Sources: Health & Fitness Association (membership and visit data); US Bureau of Labor Statistics (employment and wage data); ACSM's Health/Fitness Facility Standards and Guidelines, fifth edition.
Volume is what turns a manageable exception into a systemic gap. According to the Health & Fitness Association, those members generated nearly 7 billion visits in 2025, with only 4.6% of members never visiting at all — an all-time low. Higher attendance means more first-time participants, more guest passes and more drop-ins arriving at the exact moment staff are least able to process paperwork.
Nearly 7 billion gym visits in 2025 each carried a liability question.
The workflow, mapped
A waiver workflow has four states, and most facilities only track one of them. The four are: not requested, requested and unsigned, signed and current, and signed but superseded (the member signed the 2024 version and you have since changed the document). A clipboard system can only really represent "we have a piece of paper somewhere," which collapses all four into one and makes the last state invisible.
Here are the seven automations, in build order:
| Automation | Fires on | Build effort (hours) | Share of gaps it closes |
|---|---|---|---|
| Waiver request at booking | Booking created | 5 | 55% |
| Pre-fill from the member record | Booking created | 3 | 10% |
| SMS delivery instead of email | Request sent | 2 | 12% |
| Check-in status gate | Check-in scan | 4 | 8% |
| Document versioning and re-request | Waiver version change | 6 | 9% |
| Exception escalation to staff | 2 hours pre-class | 3 | 4% |
| Timestamped filing to the member record | Signature completed | 4 | 2% |
Modelled build effort and gap attribution for a single-location studio with an existing booking platform. Treat the shares as a sequencing guide, not a measurement.
The first row carries more than half the value, which is the practical case for building it alone and stopping there for a month. Everything after it is an increasingly narrow class of exception.
A note on the check-in gate: the word "gate" scares operators, and it should be soft. A hard block that refuses entry to a paying member because a document is unsigned will cost you more in goodwill than it saves in risk. What works is a status flag visible to whoever is at the desk, plus a one-tap resend, so the conversation becomes "let me text that to you now" rather than "you can't come in."
Delivery channel matters more than most operators expect. According to EZ Texting's 2025 Consumer Texting Report, a survey of 1,074 consumers, 57% expect a business response within 15 minutes and 74% expect one within an hour. A document that arrives by email into a promotions folder is not participating in that timeframe.
74% of consumers expect a business reply within one hour.
Worked example
Consider a two-location studio group running Mindbody, with roughly 260 new participants a month across both sites. Mindbody's published webhook catalogue includes a classRosterBooking.created event, which fires the moment someone reserves a spot — the trigger this whole chain depends on. The workflow reads the booking, checks whether that member has a current signed release, and if not sends a pre-filled link by text within 60 seconds of the booking. In the group's own reconciliation, the median signature landed 14 minutes after the text, and the share of participants arriving unsigned fell from roughly 30% of new bookings to under 4%, leaving about 10 exceptions a month for a human to chase instead of 78. At the $22.20 hourly rate derived from the published median annual wage for trainers and instructors, the 15 hours a month of front-desk waiver handling that disappeared is worth about $333. Those figures are an illustrative sizing exercise on that group's volumes, not a benchmark — run the same arithmetic on your own numbers before committing.
What it costs to keep doing it manually
Cost the manual version honestly before pricing a replacement. According to the U.S. Bureau of Labor Statistics, 370,100 people worked as fitness trainers and instructors in the United States in 2024, with a median annual wage of $46,180 — about $22.20 an hour on a 2,080-hour year, which is the rate used throughout the tables below.
| Line item | Manual, per month | Automated, per month | Difference |
|---|---|---|---|
| New participants requiring a waiver | 260 | 260 | 0 |
| Front-desk minutes spent per waiver | 4.0 | 0.5 | 3.5 |
| Total front-desk hours on waivers | 17.3 | 2.2 | 15.1 |
| Cost of that time at $22.20/hour | $384 | $49 | $335 |
| Classes starting late on paperwork | 18 | 2 | 16 |
| Signed waivers that cannot be produced on request | 21 | 0 | 21 |
Modelled for a two-location studio group at 260 new participants a month, using the hourly rate derived from BLS median annual pay. Substitute your own volumes; the structure is what transfers.
The last row is the one that should hold your attention. A waiver you cannot produce on request is functionally equivalent to a waiver you never collected, and paper-and-folder systems fail this test constantly — not because staff are careless, but because retrieval was never designed into the process. Our write-up on chasing client documents in fitness covers the retrieval side of this in more depth.
There is also a standards dimension. According to ACSM's Health/Fitness Facility Standards and Guidelines, the fifth edition sets out 35 standards and 38 guidelines covering preparticipation screening, emergency planning, staffing and operating procedures, with template questionnaires and informed-consent forms included. Screening and consent are treated there as operating disciplines, not front-desk courtesies — which is a reasonable framing to hold your own process against.
ACSM publishes 35 standards and 38 guidelines for fitness facilities.
One caution before the tooling section: enforceability of pre-injury liability releases varies by state, and courts in some jurisdictions have declined to enforce them in particular circumstances. Nothing here is legal advice; the operational question this post answers is how to reliably collect and retrieve the document your own counsel has told you to use.
The tool comparison
You are assembling four layers. Buying a tool for a layer you did not need is the most common way these projects get expensive.
| Layer | What it must do for waivers | Representative tools | The question that decides it |
|---|---|---|---|
| Booking and membership platform | Owns the booking event and the member record | Mindbody, Glofox, Zen Planner, Wodify, Push Press | Does it emit an outbound webhook on booking, or must you poll? |
| Document and signature capture | Renders the waiver, captures a legally usable signature | Your platform's built-in waiver module, or a dedicated e-signature tool | Can it version documents and tell you who signed which version? |
| Messaging | Delivers the link and the reminders | The platform's native SMS, or a business messaging provider | Does a member's reply reach a person, or a dead number? |
| Orchestration | Reacts to events, checks status, escalates exceptions | A workflow layer spanning the three above | Can it act on an event, or only on a nightly schedule? |
The webhook question in the first row determines the shape of everything else. A platform that publishes booking events lets your waiver request go out in under a minute. A platform that does not means a scheduled sync with a lag measured in hours, which for a 6:00 a.m. class booked at 11:40 p.m. is the difference between a signed release and a clipboard.
At US Tech Automations this is the layer we build: the booking webhook triggers a status check, the check routes either a text request or nothing at all, and only the unsigned exceptions reach a staff queue two hours before class. Nothing in that chain makes a judgement call — it is triggers, conditions and a write-back, which is exactly why it holds up at 6:00 a.m.
If you are still choosing a booking platform, our comparison of alternatives for multi-location fitness studios covers the event-surface question directly, and our piece on contracts stuck unsigned in fitness treats the membership-agreement version of the same workflow. Platform pricing sits on the US Tech Automations pricing page.
Payback math
Build effort is the honest cost here, not software licences. Assume a 20-hour build for the first automation and the same $22.20 hourly rate.
| Scenario | New waivers per month | Hours saved per month | Monthly value at $22.20/hour | Build hours to full coverage |
|---|---|---|---|---|
| Single studio, one location | 60 | 3.5 | $78 | 20 |
| Growing studio, two locations | 180 | 10.5 | $233 | 26 |
| Multi-site operator, five locations | 520 | 30.3 | $673 | 40 |
| Franchise group, twelve locations | 1,300 | 75.8 | $1,683 | 70 |
Modelled from the four-minutes-per-waiver figure and the BLS-derived hourly rate. Build hours are planning estimates for a team with existing platform access.
Read that table sceptically. At a single studio the labour saving alone does not justify a 20-hour build — the case there rests entirely on the risk side, on being able to produce a current signed release for any participant on any date. By five locations the labour arithmetic stands on its own, and by twelve it is not close.
Operators are already leaning this way. According to Mindbody's 2025 State of the Industry Report, a survey of more than 1,400 fitness and wellness decision-makers, 72% were confident about their performance for the year, and businesses investing in technology reported higher optimism still at 81%.
Who this is for
This is written for studio and gym operators running class-based or appointment-based services where new participants arrive continuously — CrossFit boxes, boutique studios, martial arts schools, multi-location franchises. If you run a 24-hour access gym with a single onboarding path and no drop-ins, the booking-triggered request is still worth building, but the check-in gate and versioning layers are probably over-engineering for you.
It is also for the operator who has already automated onboarding and found that waivers are the one document still handled on paper. That is an extremely common pattern, and it usually persists because the waiver feels legally serious enough that nobody wants to touch it. Our guides to paper intake forms in fitness and messy client onboarding cover the adjacent documents.
US Tech Automations builds these waiver workflows on top of whichever booking platform you already run — the booking trigger, the status check, the SMS delivery and the two-hour escalation queue. If you want to test the idea cheaply, build the booking-triggered request by itself and measure how many participants still arrive unsigned after a month.
FAQs
Can a waiver signed on a phone before class hold up?
Electronic signatures are widely used for this purpose, but whether a specific release is enforceable depends on your state's law and on how the document is written, not on the delivery channel. Have your counsel review the document itself; the automation only changes when and how it reaches the member.
What happens when someone books a class ten minutes before it starts?
The workflow still fires, and most people sign in the car park. The realistic residual is a small number of same-minute bookings, which is exactly what the staff escalation queue is for — a named exception rather than a system-wide clipboard habit.
Do we need to re-collect waivers when we update the document?
Yes, and this is the state most manual systems cannot see. If you change the release, everyone signed against the previous version is technically covered by a superseded document. Versioning turns that from an unknowable question into a queryable one.
Should the check-in gate actually block entry?
We would not recommend a hard block. A visible status flag plus a one-tap resend gets the same result without turning your desk staff into enforcement. Reserve hard blocks for categories where your insurer or counsel specifically requires them.
How do guests and one-off drop-ins fit into this?
Treat a guest pass as a booking. If your platform creates a record for guests, the same trigger applies; if it does not, a short public form linked from a QR code at the desk covers the gap, with the signed copy filed against a guest record rather than a member one.
Is there any benefit beyond risk management?
Some. A member who signs before arriving has already had one successful interaction with you, and the same pre-arrival flow can carry a par-Q, an emergency contact and a first-class briefing. That said, the primary case is retrieval and currency, and any pitch that leads with retention benefits is stretching.
Key Takeaways
Waiver collection fails because it is scheduled for the ninety seconds before class. Move it to the booking event and most of the problem disappears.
Track four states, not one: not requested, requested and unsigned, signed and current, and signed but superseded.
Deliver by text, not email. The response-time expectations consumers now hold are measured in minutes, not days.
370,100 US fitness trainers earned a $46,180 median wage in 2024. That is the labour rate your manual process is spending.
A waiver you cannot retrieve on request is operationally equivalent to one you never collected.
Keep the check-in gate soft — a status flag and a resend, not a hard block on a paying member.
At one location the case is risk, not labour. At five or more, the labour arithmetic stands on its own.
Waivers are a good first automation precisely because they are unglamorous and bounded: one trigger, one status check, one message, one file. If you want a second pair of eyes on your own event surface before you build, start at ustechautomations.com and bring a screenshot of your booking platform's webhook or integration settings — it answers most of the design questions in the first five minutes.
About the Author

Helping businesses leverage automation for operational efficiency.
Related Articles
See how AI agents fit your team
US Tech Automations builds and runs the AI agents that handle this work end to end, so your team doesn't have to.
View pricing & plans