A studio owner using a general-purpose scheduler usually discovers the mismatch in the same week: someone books a 6pm class that's already full, a member's class pack doesn't decrement, and a person who cancelled fifteen minutes before start keeps their credit while the spot sits empty.
The key thing to understand before you shop: class booking is a fundamentally different model from appointment booking, not a version of it with more seats. An appointment is one customer and one provider on a slot. A class is a recurring schedule with fixed capacity, a queue behind it, and a wallet — memberships, class packs, credits — that has to be checked at booking time and adjusted at cancellation time. Software built for the appointment model will do the first part and quietly fail at the rest.
This guide covers what to insist on, in the order the problems actually bite.
The five things a class model needs that appointments don't
1. Capacity that's enforced at the moment of booking. Not a note in the description, an actual count that closes the class when it's full and reopens it when someone drops. If a system lets two people take the last spot in the same minute, you'll be issuing apologies.
2. A recurring schedule, edited as a series. Your timetable repeats weekly. You need to publish a term or a season in one action, then change a single Tuesday for a public holiday without unpicking the series or breaking the bookings already in it.
3. A wallet the booking checks against. Members book against an entitlement — an open-access membership, a ten-class pack, a monthly credit allowance. The booking flow has to read the customer's balance, refuse or upsell when it's empty, and decrement on booking rather than on attendance (or on attendance, if that's your policy — but you should get to choose).
4. A waitlist that promotes automatically. In class businesses, cancellations are constant and last-minute. A waitlist that requires you to notice a drop and phone someone is not a waitlist. What you want is automatic promotion with a response window, so the spot moves down the list on its own. The mechanics of that — the offer window, the fallback, the cutoff before start — are the same ones covered in our guide to building a waitlist that fills cancelled slots automatically.
5. Cancellation rules with teeth. A late-cancel policy is only real if the software enforces it: a cutoff time, an automatic consequence (credit forfeited, fee charged, or nothing, by your choice), and a clear message to the customer at the point they cancel. Enforced by a human, the policy becomes a negotiation every single time.
If a system can't do these five, everything else on its feature list is decoration for your use case.
Capacity is more complicated than a number
For a yoga class, capacity is one number. For a lot of studios, it isn't:
- Assigned spots. Spin bikes, reformer beds, rowing machines, lane swimming — customers pick a specific position, and some positions are more desirable. You need a bookable floor map, not a headcount.
- Equipment as a separate constraint. Two classes may fit the room but compete for the same equipment set or the same instructor.
- Different limits per class type on the same timetable — a small-group session and an open class in the same room on the same day.
Ask to see this in a demo with your own timetable rather than trusting a feature-grid checkmark. "Capacity limits" on a comparison page tells you nothing about whether assigned spots exist.
Memberships, packs, and credits: the part that decides your revenue
This is where fitness software separates from generic scheduling. Work through your own product list and check each one can be modelled:
Recurring memberships. Monthly or annual billing on a stored card, with the states you actually use: active, paused, past due, cancelled. Pausing is not optional in this industry — people travel and get injured, and if the system can't freeze a membership, staff will cancel and re-create it, wrecking your retention reporting.
Class packs with expiry. A ten-class pack that expires after three months is a different product from one that never expires, and the system needs to track and communicate the expiry date. Customers who discover an expiry at the door become complaints.
Credit values that differ by class. If a specialist workshop costs two credits and a standard class costs one, the wallet has to support that.
Drop-in payment for someone with no membership, ideally inside the same booking flow rather than a separate "buy first, then book" journey. Every extra step here costs you bookings.
Intro offers. A discounted first-timer pass, limited to genuinely new customers, that the system can restrict so it isn't bought repeatedly.
Failed payment handling. Cards expire constantly on recurring plans. Ask what happens: retry schedule, customer notification, whether booking access is suspended, and whether staff get a list to work through. This is quiet revenue leakage in nearly every studio that hasn't looked at it.
No-shows, late cancels, and attendance
In appointment businesses a no-show costs you the slot. In class businesses it costs you the spot someone on the waitlist would have taken — and with an open-access membership the customer often feels no cost at all, which is exactly why class no-show rates behave differently.
Three controls do most of the work:
- A cancellation cutoff (commonly a few hours before start, or the evening before for early classes) after which the credit is forfeited or a fee applies. Publish it at booking, repeat it in the reminder, and show it again on the cancel screen.
- Reminders timed to the decision. A reminder that arrives when there's still time to cancel and free the spot is worth more than one that arrives an hour before. The general reminder logic is in our guide to reducing no-shows.
- Check-in that produces data. Whether it's a front-desk tap, a kiosk, or a QR scan, you want attendance recorded so you can see which classes are actually attended versus merely booked. Booked-and-empty is the metric that tells you your late-cancel window is too generous.
Operational features owners forget to ask about
- Instructor substitution. Cover happens weekly. Can you swap the teacher on one occurrence, notify the booked customers automatically, and have it show correctly on the timetable?
- Staff permissions. Front desk should be able to book, check in, and take payment without seeing revenue reports or editing memberships.
- A booking page that works properly on a phone, since most class booking happens on mobile, often in the last hour before a class.
- Waiver and health-questionnaire capture at first booking, stored on the customer record.
- Family and minor accounts, if you run junior classes — an adult booking for a child.
- Door or gate access integration, if you have unstaffed hours.
- Reporting that answers real questions: class utilisation by time slot, attendance rate, membership churn, revenue by product. Utilisation by slot tells you which timetable changes to make.
- Data export. Customers, membership status, payment history, and attendance, in a standard format — your exit route and your leverage at renewal.
A requirements checklist to take into demos
Score each candidate against these before you look at price:
- Enforced capacity, with assigned spots if you need them
- Recurring timetable, editable as a series and per occurrence
- Memberships with pause, past-due, and cancellation states
- Class packs with expiry, and variable credit costs per class
- Drop-in purchase inside the booking flow
- Automatic waitlist promotion with a response window
- Enforced late-cancel cutoff with a configurable consequence
- Reminders you can time and word yourself
- Check-in and attendance records
- Instructor substitution with automatic notification
- Staff roles and permissions
- Utilisation, attendance, and churn reporting
- Failed-payment retry and notification
- Full data export
Mark each as must-have or nice-to-have first, then score. That ordering — criteria before candidates — is the whole method in our booking software buyer's guide, and it matters more here than in most categories because class software is expensive to leave once memberships are billing through it.
FAQ
Can I run a studio on a generic scheduling tool?
You can start there, particularly if you sell mostly one-to-one sessions with a couple of classes a week. It stops working once you're selling memberships or packs, because a generic scheduler has no wallet to check against and no waitlist logic. The usual sign it's time to move is staff keeping a parallel spreadsheet of who has classes left.
Should credits be deducted at booking or at attendance?
Deducting at booking is the more common default and it's what makes a late-cancel policy meaningful — the credit is already committed. Deducting at attendance is friendlier but removes the cost of booking a spot and not turning up. Whichever you choose, make sure the software supports it explicitly rather than being worked around.
How long should the cancellation window be?
Long enough that the waitlist can realistically fill the spot. If your waitlist promotion gives people an hour to respond, a cancellation cutoff shorter than that leaves spots empty by design. Studios commonly land somewhere between four and twelve hours before class; pick a number, publish it, and let the software enforce it.
What happens to my bookings and memberships if I switch systems?
That depends entirely on the export you can get and the import the new system accepts. Before signing anywhere, confirm you can export customers, membership status and billing dates, remaining pack balances, and attendance history. Migrating recurring billing is the hard part — plan it around a billing date, not mid-cycle.
Compare class and membership booking systems
Class booking has a short list of make-or-break requirements: enforced capacity, a wallet the booking checks, a self-promoting waitlist, and a cancellation rule the software applies without you. Score candidates on those before price, and the shortlist gets manageable fast.
Compare the best fitness and class booking software on BookForMe →
