Swim School Management Software: Owner Buying Checklist

Most swim school owners can tell you exactly where their system lives. The waitlist is a tab in a spreadsheet. The level notes are in an instructor's head. The "which families are coming Thursday" answer is a group chat thread that scrolled away two weeks ago. It mostly works because one person remembers everything.

That is also why buying swim school management software is hard. Vendors show you feature lists, and every feature list looks fine. A feature list does not tell you what happens at 7:40 on a Tuesday morning when a spot opens in a Level 3 class and three families are waiting.

This checklist is written as questions you can ask any vendor, including Soljio, during a demo or trial. It skips prices, rankings and promises on purpose. It makes the software prove itself against the situations that actually eat your week. Bring a notebook, bring your real roster, and make every vendor show you, not tell you.

Before you demo anything: write down what your current system actually does

Do this first, before you book a single call. Open a blank document and list every job your current setup performs, including the ones nobody assigned. Not the official jobs. The real ones.

Start with the obvious: who is enrolled in what, who is on the waitlist, who paid. Then go further. Who remembers that a swimmer has a shoulder injury? Who knows two siblings must be in back-to-back slots because one parent drives alone? Who tells parents when the pool is closed, and how?

These hidden duties are where software purchases fail. A tool can handle enrollment beautifully and still leave you doing the other eight jobs by hand, because nobody told the vendor about them.

Write each duty as a sentence that starts with a verb. "Move the next waitlisted family into an opened spot." "Tell instructors a class moved lanes." "Record which skills a swimmer passed." You will end up with 15 to 30 lines. That list is your real requirements document, and it beats any vendor feature grid.

Then mark each line with who does it today and how long it takes. If the front-desk person spends 90 minutes a week reconciling payments against a sheet, that line matters more than a feature you would show off to a friend.

Take this list into every demo. When a vendor says "we handle scheduling," point at your line and say "show me this one." If you are planning an eventual switch, the software migration checklist pairs well with this exercise.

Programs, schedules and rosters: questions to ask about the core workspace

The core workspace is where you will spend most of your hours, so judge it first. A pretty parent page on top of a clumsy scheduler is a bad trade.

Ask the vendor to build a small real week while you watch. Not a pre-loaded demo school. Your week: a few group classes, a private, a parent-and-tot session, maybe a camp. See how many clicks it takes and whether the vendor has to look something up.

Then ask these questions:

• Can I see programs, schedules and rosters in one place, or do I jump between separate tools?

• Show me one class's roster. Where does a swimmer's level or skill history show up from that screen?

• How do I move a swimmer from one class to another, and what do I see afterward?

• How do I set up the next session without retyping every class?

That last one is a quiet time-saver. Rolling one term into the next is a recurring chore, and the term rollover checklist shows how much of it exists even before software enters the picture. If the tool makes you rebuild every class from scratch, you have traded one spreadsheet for another.

I'll take a position on this: one workspace beats several connected tools for a small school. Every extra tool is another place where the roster can disagree with itself. Soljio is built around that idea, with programs, schedules, rosters, families and progress kept in one workspace. Whichever vendor you evaluate, ask to see that claim demonstrated, not described.

Watch for any answer that begins "you could set that up by..." That phrase usually means a workaround, and workarounds are what you already have.

Families, enrollment and payment: what parents see on your school's own page

Your parents will judge your school by the enrollment experience before they ever touch the water. So ask to see it from their side, on a phone, because that is where most parents will do it.

The first question is where families land. Some tools send parents to a generic marketplace page full of other schools. Others give you a page that carries your name. With Soljio, families enroll and pay on the school's own subdomain, so the page is yours. Ask every vendor the same thing: what web address does a parent type, and whose brand is on it?

Next, run the parent journey yourself. Pretend you are a parent with two kids at different levels:

• How do I find the right class for each child?

• How many screens until I have enrolled and paid?

• What does the confirmation look like, and what do I receive afterward?

• What happens if I make a mistake and need to change something?

You are looking for friction. Count taps. Note anywhere you hesitated. A parent who hesitates at the payment step opens a different tab and forgets you.

Then flip the view. Ask what you see on your side the moment a family enrolls. Does the roster update by itself, or do you reconcile later? Reconciling later is the spreadsheet habit in disguise.

If your enrollment emails are a pain point, compare what the tool does against the templates in the enrollment confirmation email guide. Also check your registration link setup against the website registration link checklist, because a great enrollment page does nothing if parents cannot find the link.

Finally, ask who answers when a parent has a billing problem. Get a specific answer, not a general reassurance.

Deck work: attendance and skill progress your instructors will really record

Software only helps if instructors use it, and instructors use it only if it works while they are standing on a wet deck with eight kids and a whistle. This is the most overlooked section of any evaluation.

Don't let the vendor demo this on a laptop at a desk. Ask to see it on a phone or tablet, then try it yourself with a wet-ish hand and a tight time limit. Give yourself 30 seconds to mark attendance for a class of eight. If you cannot do it, your instructors will not either, and they will go back to paper.

Soljio is designed so instructors take attendance and mark skills from the deck. Whatever tool you test, hold it to the same standard:

• How many taps to mark a swimmer present or absent?

• How do I mark a skill as passed, and can I do it in the moment rather than at day's end?

• Where does a swimmer's skill history show up the next time they walk into a class?

• What does a substitute instructor see when they cover a class they have never taught?

That last question matters more than it sounds. Substitutes are where continuity breaks. A good system means the cover instructor opens the roster and sees where each swimmer stands, which is the same problem the instructor handover notes template tries to solve on paper.

My stance: simple beats thorough on deck. A skill tracker with 60 fields that nobody fills in is worse than one with five that everybody does. For ideas on what good notes look like, see these progress note examples and the guide to attendance tracking on pool decks.

Ask your two most skeptical instructors to try it. Their reaction is your real data.

Test with your real scenarios: a waitlist opening and a pool closure

Here is where you stop listening and start testing. Pick two scenarios from your own week and make every vendor walk through them live. The two best ones are a waitlist spot opening and a pool closure.

Scenario one: a spot opens. A family cancels from a Level 3 Tuesday class. Three families are waiting. Ask the vendor to show, step by step, what you do and what the software does. Where do you see the waitlist? How do you decide who gets the spot? What does the offered family receive, and what happens if they say no? How do you know the roster is correct afterward?

Don't accept "it notifies the next family" as an answer unless you watch it happen. Ask what you personally still have to do. If the honest answer is "quite a bit," you have learned something useful. The waitlist management guide and the waitlist offer email templates show the manual version, so you know what good looks like and what you would be replacing.

Scenario two: the pool closes. The heater fails on a Friday and Saturday classes are off. Ask the vendor to show how you find every affected class, how you reschedule or credit families, and how you tell parents. Be precise about what the tool does itself and what stays your job. Ask directly: does it send the notice, or do I write and send it myself? Treat any vague answer as a no.

For a sense of how the message itself should read, compare against this pool closure notice template and the makeup class policy guide.

Both scenarios prove the same thing. A demo of the happy path proves nothing. A demo of your worst Tuesday proves everything.

Getting your data in: roster import and what to ask about support

Switching fear is the quiet reason many owners stay on spreadsheets. You have years of rosters in a file, and the idea of retyping 300 swimmers is enough to end the evaluation. So ask exactly what comes across and what does not.

Be literal about the question. "Can I import my data?" gets a cheerful yes from everyone. Ask this instead: "Which fields from my spreadsheet come in, and which ones do I still enter by hand?" Hand them a real export, with your messy column names and the swimmer who has three spellings, and ask them to import it in front of you.

Soljio supports importing rosters from a spreadsheet. That is the verified scope, so treat it as just that: a roster import. Don't assume it carries over everything else you track. If you keep family notes, payment history or past schedules in separate places, ask each vendor, one item at a time, whether it comes across. Write down the answers. Anything not clearly confirmed, plan to handle yourself.

Then ask about the humans:

• When I get stuck during setup, who do I contact and how?

• Is that a person or a ticket queue?

• What does the first week look like for a school my size?

Plan the switch around your calendar, not the vendor's. The safest time to move is between sessions, when rosters are stable and parents are not mid-term. If your enrollment data currently lives in a spreadsheet you have outgrown, the guide on replacing a registration spreadsheet safely walks through the sequencing.

A vendor who is honest about what imports and what does not is giving you the most useful information of the whole evaluation.

Questions for any vendor about stage, support and fit, and what to do after you choose

The last set of questions is about the company, not the product. Software is a relationship you will live with for years, and small-school owners often skip this part.

Ask every vendor how long they have been selling, how many schools like yours use the product, and who you will talk to when something breaks. Ask what is shipped today versus what is planned. This one matters: roadmap features are not features. If a vendor describes an assistant or an automation that is still in development, price your decision on what exists now.

I'll be candid about our own stage, since you are reading this on Soljio's blog. Soljio is in private beta with a small number of swim schools, and it is run by a solo founder. You get a direct line to the person building it, and you also get a younger product than some alternatives. Weigh both honestly. Beta partners shape what gets built, which suits an owner who wants a say and is comfortable with a product still maturing. It suits less an owner who needs a long track record. Neither is wrong. Know which you are.

Size fits matter too. Ask each vendor what size of school the product is designed for, and whether your active student count sits comfortably inside it.

After you choose, do three things. Run a pilot with one program before moving the whole school. Get your instructors on the deck workflow in week one. And keep your old spreadsheet read-only for a full session as a safety net.

Then measure against the list you wrote at the start. Did the 90-minute weekly reconciliation shrink? That is your answer.

Conclusion

Your buying decision comes down to the two scenarios you test live: a waitlist spot opening and a pool closure. Run them in every demo, with your real roster, and let the software show you what it does instead of what it claims.

If your school is on spreadsheets and a group chat, put Soljio through the same checklist. Book a short call or write to hello@soljio.com, bring your list of real duties from section one, and ask to see enrollment on your school's own page, attendance and skills marked from the deck, and a roster imported from your spreadsheet. Soljio is in private beta, so you will be talking to the person building it. If it handles your worst Tuesday, you have your answer. If not, you will have learned that in 30 minutes instead of 30 days.