All articles

Swim Lesson Roster Software: Tests Before You Switch

9 min read

The best way to evaluate swim lesson roster software is to make the vendor run your messy cases live, using fictional swimmers and a written expected outcome for each test. A demo that only shows a clean enrollment tells you nothing about what happens in week four, when a swimmer leaves, another changes class, and a substitute walks onto the deck.

This post is a pass/fail script you can use with any vendor, whether you are comparing Jackrabbit Swim, Amilia, Pike13, iClassPro, Swum, Swimphony or a purpose-built tool, or just deciding whether to leave Google Sheets and Excel. Five tests, five expected outcomes, one scorecard. It is different from a weekly reconciliation routine or a broad buying checklist. This is an acceptance test you run once, before you commit.

Why roster software demos hide the problems that matter

Roster software demos hide problems because vendors rehearse the happy path: one family, one class, one clean enrollment. The failures that hurt a small swim school show up later, in the edges.

Think about where rosters actually break. A swimmer withdraws and the instructor still sees them on the Thursday sheet. A transfer leaves a child on two rosters, or on none. A substitute gets either nothing or the entire family database. A swimmer changes level and the skill history stays behind with the old class.

The multi-location roster checklist names the cause: multiple live documents guarantee mismatched rosters. Software only fixes that if it holds up when the roster changes. So stop watching demos and give the vendor homework.

One rule for every test below: you drive, the vendor clicks. Hand them the fictional data in advance or read it out live. If they need to "prepare the environment," that is itself a result.

Set up the test: a fictional mini-program with five swimmers, two classes and one substitute

Build a tiny program that fits on an index card, and use names no real family could be confused with. Keep it identical across every vendor so your scores compare.

Swimmers: Test Swimmer Alpha, Beta, Gamma, Delta and Epsilon.

Classes: Tuesday 4:00 Level 2 (cap 6) and Thursday 5:00 Level 3 (cap 6), same rented pool.

People: one regular instructor per class, plus Test Substitute Sam, who has never used the system.

Seed the program so Gamma, Delta and Epsilon are already enrolled: Gamma and Delta in Level 2, Epsilon in Level 3. Alpha and Beta are the swimmers you will move through the tests. Print a one-line expected result for each test before the demo starts, so nobody grades on vibes afterward.

If the vendor offers a spreadsheet roster import, use it for your three seeded swimmers. Importing a roster from a spreadsheet is how a small school actually switches, and watching it work on your own columns is worth more than any slide.

Test 1: Registration, a family enrolls Test Swimmer Alpha and the roster shows it

Registration passes when a family completes enrollment on their own and the swimmer appears on the right class roster without anyone retyping anything.

Run it from the family's side. Open the school's public registration page as a parent, pick Tuesday 4:00 Level 2, enter Alpha's details, sign any waiver and pay. Then switch to the staff view.

Expected outcome: Alpha is on the Tuesday Level 2 roster, the roster count went from 2 to 3, the waiver and payment are recorded against the family, and the roster for the next class date already lists Alpha.

Fail signals: a staff member must add Alpha by hand; the count does not change; the family has to call to confirm; the roster export (ask for one) omits Alpha.

While you are here, test the edges. Enroll Beta into Level 2 as well so it reaches 4 of 6. Can the school see remaining capacity? Ask what a family sees if the class is full. Waitlists and a family portal are standard demo bullets, so ask the vendor to show what a full class does instead of describing it.

Test 2: Withdrawal, Test Swimmer Beta leaves mid-term and history stays intact

Withdrawal passes when Beta disappears from future rosters but every past attendance mark and skill record stays readable.

Before the test, record three attendance marks and two skill marks for Beta across the first sessions. Then withdraw Beta effective after week three.

Expected outcome: Beta is absent from the roster for week four onward. Weeks one to three still show Beta as present or absent exactly as marked. Skill marks remain visible in Beta's record. The Level 2 roster count drops by one, freeing a seat.

Fail signals: Beta vanishes from past rosters, which corrupts your attendance totals; deleting the swimmer is the only option; the freed seat does not show as open; there is no way to view a withdrawn swimmer's history at all.

The cleanest systems keep the attendance fact separate from the roster decision, an idea the pool-deck attendance guide lays out in detail. Your parent-facing wording matters too. See the withdrawal email guide for what to confirm in writing.

Test 3: Transfer, move a swimmer to another class and check both rosters

Transfer passes when the swimmer leaves one roster and joins the other on the effective date, with no duplicates and no gap.

Move Epsilon from Thursday Level 3 to Tuesday Level 2 starting week four. Now open both rosters for week three and week four.

Expected outcome: Week three, Epsilon is on Thursday Level 3 only. Week four, Epsilon is on Tuesday Level 2 only. Past Thursday attendance is untouched. Both class counts are correct: Thursday down one, Tuesday up one.

Fail signals: Epsilon appears on both rosters for any date; the move rewrites history so week-three attendance now sits under Tuesday; the transfer silently fails when the destination class is at capacity; the family has no visible confirmation of the move.

Push one more case: try to transfer a swimmer into a full class. A good system stops you or makes you consciously override. A bad one lets you overfill a rented pool without a word. For how to word the family notice, the mid-term class transfer email guide covers it.

Test 4: Substitute access, a cover instructor sees only what they need on deck

Substitute access passes when Test Substitute Sam can take attendance for one class without seeing the whole school's data.

Create Sam as a new instructor and assign Sam to the Tuesday 4:00 session for one date only. Log in as Sam on a phone, the way a real substitute would on a wet deck.

Expected outcome: Sam sees the Tuesday Level 2 roster for that date, can mark attendance, and can see the names and levels needed to teach. Sam does not see other classes' rosters, family billing details or payment records. After the date passes, Sam's access to that class does not linger as a standing assignment.

Fail signals: Sam needs a full admin login to do anything; Sam can browse every family's contact and payment data; the roster is only available as a printout the owner emails at 3:55; the regular instructor has to be removed from the class to add Sam.

Ask the vendor to explain exactly what an instructor role can and cannot see. Your answer should come from watching Sam's screen, not from a feature page. The instructor assessment calibration post is a useful companion if substitutes will also be judging skills.

Test 5: Skill continuity, progress survives a class change and a substitute

Skill continuity passes when a swimmer's progress record follows the swimmer, not the class, and a substitute's marks land in the same record as the regular instructor's.

Before the test, mark Gamma with two skills achieved in Level 2 by the regular instructor. Then have Sam, the substitute, mark one more skill for Gamma during a cover session. Finally, move Gamma up to Thursday Level 3.

Expected outcome: Gamma's record shows all three marks, with the instructor recorded for each. After the move to Level 3, the Level 2 marks are still there and Level 3 starts with its own skill list. A parent viewing Gamma's progress sees one continuous record.

Fail signals: the substitute's mark is stored in a separate note or lost; moving classes resets progress to zero; skill marks live only on a per-class sheet; the instructor cannot tell which skills carry over.

If you track skills on paper checklists today, ask whether the software mirrors that sheet, one list per level with a mark per skill, so instructors do not have to learn a new mental model. For how this fits a wider curriculum, read the learn-to-swim curriculum tracking checks.

Scoring the results and what to do with a failed test

Score each test pass, partial or fail, and treat Tests 2 and 3 as non-negotiable. A system that corrupts history on withdrawal or double-lists a transferred swimmer will cost you every term.

Use this simple scheme:

  • Pass: the expected outcome happened live, with no workaround.

  • Partial: it works, but only with a manual step you would forget by week six. Count it as half.

  • Fail: the vendor said "that's on the roadmap," fixed it with a spreadsheet, or could not do it at all.

TestWhat you are provingDealbreaker if failed?
1. RegistrationFamily self-enrolls, roster updatesYes
2. WithdrawalFuture rosters clean, history intactYes
3. TransferNo duplicates, no gapsYes
4. Substitute accessCover sees only what they needStrong concern
5. Skill continuityProgress follows the swimmerStrong concern

On a failed test, ask for a re-run after the vendor's explanation, not before. Vendors often have a feature that works but sits in a different menu. If the second attempt fails, believe it. Score every vendor on the same five-swimmer program, then compare totals.

If you want a broader frame around the decision, the swim school management software buying checklist covers criteria beyond rosters, and the migration checklist covers the switch itself.

Where Soljio fits when you run these tests

Soljio is swim school software that keeps programs, schedules, rosters, families and skill progress in one workspace, so the five tests above all run against a single system instead of several documents.

Here is what is verified against the script. Families enroll and pay on the school's own subdomain, which maps to Test 1. Instructors take attendance and mark skills from the deck, which maps to Tests 4 and 5. Rosters import from a spreadsheet, which is how you load your three seeded swimmers. Soljio is in private beta, shaped with a small number of swim schools.

Treat those as questions to put to Soljio, exactly as you would with any other vendor, and run the script yourself. If you are a small independent school, seasonal clinic or club learn-to-swim program under roughly 500 active students, bring the script to a call and ask which tests the current beta supports.

Run the five tests on Soljio before you commit to anything

Roster software earns its place in week four, not in the demo, so make every vendor pass registration, withdrawal, transfer, substitute access and skill continuity on your own fictional swimmers. Print the script, set your expected outcomes first, and score honestly. When you are ready to see how Soljio handles it, bring the five-swimmer program to a call at soljio.com and ask to run the tests live.