A sold-out class is a good problem. A sold-out class with no overflow plan is a retention risk. A solid class capacity overflow SOP turns consistent demand into additional revenue instead of frustrated members who couldn't get a spot. Your fitness VA owns this process end to end, from the moment a class hits capacity to the follow-up message that brings waitlisted members back.
This SOP covers three scenarios: managing the waitlist itself, triggering an additional class when demand warrants it, and handling the rare case where you cannot open more capacity and need to apologize without losing the member.
Setting Up the Waitlist Correctly
Most booking platforms (MindBody, Mariana Tek, Glofox) have native waitlist functionality. The problem is that the defaults are often misconfigured. Your VA should audit the settings before the process goes live.
Check these four things:
Waitlist cap. Set a waitlist limit that reflects realistic conversion. If your class holds 20 people, a waitlist of 10 is reasonable. A waitlist of 40 creates false hope and mass disappointment.
Notification window. When a spot opens, the first person on the waitlist gets an automated notification. The default window (how long they have to claim the spot) is often 24 hours. That is too long for a class that runs tomorrow. Set it to 60 minutes for classes within 48 hours, 4 hours for classes further out.
Auto-promotion. Most platforms can automatically move the next person into the class when a spot opens and the notification window expires. Enable this. Manual promotion creates gaps and relies on someone monitoring the queue.
Waitlist messaging. The default platform copy is generic. Your VA should rewrite the confirmation message to include: the class name, date, time, their position number, and a clear statement of what happens next: "You're #3 on the waitlist for 6 AM HIIT on Thursday. We'll text you the moment a spot opens. You'll have 60 minutes to confirm before the next person is offered the spot."
Once the waitlist is configured, your VA should check it daily, not just when automations fire. Platforms glitch. Manual overrides happen. A daily audit at 8 AM takes two minutes and catches problems before they become complaints.
Triggering an Additional Class
When the same class consistently fills and builds a waitlist of five or more people over three or more consecutive weeks, that is a signal to add capacity. Your VA tracks this data in a simple spreadsheet or dashboard: class name, date, waitlist count at close, waitlist-to-open-spot conversions.
The trigger threshold is your decision as the owner, but a clear rule prevents the VA from making judgment calls they shouldn't own. A workable default: if a class fills and has five or more on the waitlist for three weeks in a row, the VA flags it for a capacity review. The owner or manager decides within 48 hours whether to add a second class, expand the room layout, or hold.
When the decision is to add a class, the VA handles the logistics:
- Confirm coach availability for the proposed time slot. Use the same availability template from your coach scheduling SOP. Do not assume a coach is available because they taught the original class.
- Create the new class in the booking platform with the correct capacity, pricing, and description.
- Send a direct notification to everyone on the waitlist for the original class. Subject line: "New class added, grab your spot." Body: one sentence on the new time, a direct booking link, a 48-hour deadline to claim priority access before it opens to the general member base.
- After 48 hours, open the class to all members.
- Log the action: date added, waitlist notified count, spots claimed within 48 hours, final enrollment.
This data tells you whether the additional class was worth running. A class that only fills 40% of capacity from a large waitlist tells you the demand was time-specific, not class-specific. Adjust accordingly.
The Apology Script for Persistent Sellouts
Sometimes you cannot add capacity. The room is physically full, no coach is available at alternative times, or the business decision is to keep the class exclusive. In that case, the VA needs a script that acknowledges the frustration, offers something concrete, and preserves the relationship.
The script has three parts:
Acknowledge. "We know [Class Name] is consistently full, and we're sorry you didn't get a spot." No excuses, no "due to overwhelming demand" corporate language. Just a direct acknowledgment.
Offer something. A comp class credit, priority access to the next available slot, or a spot on a pre-registration list that opens 72 hours before public booking. The offer should have real value. A newsletter signup is not a goodwill gesture.
Signal action. "We're actively looking at how to add more capacity. We'll update you by [specific date]." Give a date, not "soon." Then the VA puts a task in the calendar to send that update, whether the news is good or not.
Your VA sends this message to anyone who was on the waitlist and did not convert to an open spot within the last 30 days. It goes out via the platform's messaging tool or SMS, not email, where open rates are lower for time-sensitive operational messages.
Reporting and Continuous Improvement
The overflow SOP only improves if someone is tracking results. Your VA produces a short weekly report: classes that hit capacity, waitlist size at close, conversion rate from waitlist to class, and any new classes triggered. This report goes to the owner every Monday morning.
Over time, patterns emerge. Certain time slots fill first. Certain coaches drive disproportionate demand. Certain class formats consistently overflow. That data is the input for scheduling decisions, coach recognition, and programming choices. None of which the VA should make unilaterally, but all of which become clearer when the overflow SOP is running cleanly.
Frequently asked questions
How many people should be allowed on a waitlist?
Cap the waitlist at 30-50% of the class size. For a 20-person class, 6-10 waitlist spots is a reasonable range. A longer waitlist creates more disappointment than value unless you have a reliable additional-class trigger in place.
What platform handles waitlists and auto-promotion best?
MindBody and Mariana Tek both have solid native waitlist tools with configurable notification windows. Glofox handles it adequately. Pike13 and Zen Planner require more manual management. Whichever platform you use, the VA should test the full waitlist flow (join, notify, promote) before trusting the automation live.
Should the VA communicate with members directly, or use the platform's automated messages?
Both. Platform automations handle the transactional messages (waitlist confirmation, spot available notification, auto-promotion confirmation). The VA handles the human messages: the apology script, the priority invite to a new class, the follow-up for members who repeatedly miss out. Automations scale; personal messages retain.
What if a member on the waitlist no-shows after being promoted?
Treat it the same as any other no-show. If you have a no-show fee policy, apply it. If you charge for waitlist no-shows at a different rate, make that explicit in your booking terms before the member joins the waitlist. The VA should not invent policy on the fly. Enforce whatever the policy document says.
How often should the overflow SOP be reviewed?
Review it quarterly. Platform features change, class schedules evolve, and member behavior shifts seasonally. A 15-minute quarterly review with the owner keeps the SOP current without creating administrative overhead.