What swim schools should look for in scheduling software

Ask any swim school owner what generates the most phone calls and the answer is make-ups. Young kids miss lessons constantly — ear infections, colds, family trips — and every missed lesson becomes a parent who wants it back. If your software doesn't handle this, your staff does, one spreadsheet and one phone call at a time.

A make-up system worth paying for needs three things:

Credits issued automatically. When a parent reports an absence (or staff marks one), a make-up credit should appear on the account without anyone creating it manually. If issuing a credit is a staff task, it will be done inconsistently, and inconsistency is what makes parents angry.

Expiry windows you control. Open-ended make-ups become a liability that compounds — credits from last spring surfacing in December, redeemed by families who have since dropped. You want a configurable window (30, 60, 90 days) enforced by the system, not by an awkward conversation.

Parent self-booking with capacity checks. The end state you want: a parent opens the portal, sees one make-up credit, sees which classes at their child's level have an open seat this week, and books it. No call, no email thread, no risk of staff overbooking a full class. This is the feature that turns make-ups from a staffing cost into a self-service loop — ClassPulse's make-up credits work exactly this way, and it's worth demanding from any vendor.

Swim instruction is a progression business. Parents are paying to watch a kid move from blowing bubbles to swimming freestyle, and "how close is she to the next level?" is the second-most-common front desk question after make-ups.

Look for skill or level evaluations that instructors can record quickly on deck, and — the part many platforms skip — a parent portal view of that progress. When parents can see evaluations and skill checklists themselves, they stop asking, they trust the level placements more, and re-enrollment conversations get easier because the progress is visible. Certificates or level achievements parents can hold onto are a nice retention touch on top. Be realistic about one thing: no software decides when a child is ready to move up — your instructors do. The software's job is to make their evaluations visible and the level move painless.

Swim schools enroll families. Two or three swimmers per household is normal, and software that models each student as a separate account turns that household into three logins, three payment methods, and three separate bills. What you want is one family account: multiple children under it, one card on file, one combined statement, and sibling discounts applied automatically rather than remembered manually. This sounds basic. It is also the single structural thing that's hardest to retrofit, so check it first — everything from billing to communication inherits from how the platform models a family.

Popular time slots at a swim school — weekday evenings, Saturday mornings — run full with waitlists behind them. The question isn't whether software has a waitlist checkbox; nearly all of it does. The question is what happens when a spot opens. In weak systems, the answer is "a staff member notices, checks the list, and starts calling." Spots sit empty for days. In a good system, the opening triggers the waitlist automatically: the next family gets notified with a window to claim the spot, and if they pass, it rolls to the next. Empty seats fill themselves. Ask the vendor to demo the actual promotion flow, not just the waitlist sign-up.

At minimum, every class needs a hard cap that enrollment, make-up bookings, and waitlist promotions all respect — one number the whole system honors, so a class can never quietly end up with nine kids and one instructor. That per-class cap is table stakes and any serious platform, ClassPulse included, enforces it everywhere.

Beyond that, platforms genuinely differ: some model lane-by-lane assignments or instructor-to-student ratios as first-class concepts, others leave you to express ratios through class sizes and separate class listings per lane or instructor. Neither is automatically wrong for your school — but know which one you're buying, and if lane-level scheduling matters to your pool layout, ask to see it directly rather than assuming the word "capacity" on a feature list covers it.

Swim schools split between two models. Session-based enrollment (eight-week blocks, everyone re-registers) creates predictable revenue cliffs and a re-enrollment scramble four times a year. Perpetual enrollment (a swimmer holds a weekly slot until the family drops) smooths revenue and retention but demands software that can prorate a mid-month start, bill continuously, and handle level changes without a re-registration event. Many schools run perpetual for weekly lessons and sessions for camps and clinics. Whatever your mix, confirm the software supports both — a platform built only around sessions will fight you every day if you run perpetual, and vice versa.

Tuition should not be a monthly project. The checklist here is short: autopay on a card on file, proration for mid-cycle starts so front desk staff aren't doing arithmetic at the counter, and dunning — automatic retry and parent notification when a card declines, so failed payments chase themselves instead of landing on a call list. Declined cards are a fact of life at any volume; the difference between platforms is whether recovering them takes zero staff minutes or several hours a month.

Two capabilities matter most. First, absence reporting from the parent's side: a parent should be able to report "out sick today" from their phone, which both tells the instructor and kicks off the make-up credit flow. Second, SMS. Pool closures, fouling incidents, and weather calls are same-day, time-critical messages, and email is too slow for them — texts get seen in minutes. Email still has its place for newsletters and receipts, but if a platform can't text your families, same-day operations stay manual.

Vendors demo their best screens. These questions surface the workflows you'll actually live in:

1. When a parent reports an absence, what happens next — does a make-up credit get issued automatically, or does my staff create it by hand?
2. Can parents book their own make-up lessons, and does the system check class capacity when they do?
3. Do make-up credits expire, and can I set the window myself?
4. When a spot opens in a full class, what exactly happens to the waitlist — an automatic offer, a staff notification, or nothing?
5. Can parents see their child's level progress and evaluations without emailing us?
6. Walk me through a mid-month enrollment: how is the first charge prorated, and what happens when a card declines in month three?
7. How does a family with three swimmers, one card, and a sibling discount look in the system — one account or three?
8. What do families, students, and enrollments look like coming in from my current system, and what gets left behind?

Any vendor worth your tuition revenue can answer all eight concretely, on screen, without the phrase "that's on the roadmap." If you want to see how ClassPulse answers them, the free plan covers up to 50 students — enough to set up real classes and test the make-up and waitlist flows yourself before a single conversation with us.