Swim-school administration needs to connect each swimmer with the right teaching group, instructor and pool location. Families need a simple way to understand the arrangement, while the school needs separate attendance and service records for every child. Start with the teaching structure before building the timetable.
A general booking calendar can show that a place exists without explaining whether the lesson suits the swimmer’s level. That suitability decision is central to enrolment and should remain clear throughout the process.
Define levels and groups before collecting bookings
Agree how the school describes levels and assigns swimmers to groups. Use terms that instructors can apply consistently and parents can understand. When a swimmer needs assessment, make the next step clear instead of treating an enquiry as a confirmed lesson.
Keep the teaching group distinct from the venue and the individual session. A group can continue its history even if a lesson moves to a different pool or an instructor changes for one date.
Build the schedule around real resources
Identify the pool locations and the resources used for teaching, then assign instructors and capacity. Check how the recurring timetable becomes individual dated lessons. Staff need to handle a single cancellation without losing the regular schedule.
Review capacity according to the school’s teaching arrangements. A software limit records an operational rule; the organisation remains responsible for deciding what that rule should be. Do not assume the system can determine an appropriate teaching ratio for you.
Give parents one account and children separate records
A guardian may have two children at different levels, on different days or at different pools. Keep each swimmer’s group, service, attendance and progress separate while connecting the family relationship.
When reception receives a question, confirm the child concerned before making a change. A clear participant context helps staff avoid applying one sibling’s arrangement to another.
Make lesson changes and make-up policies explicit
Agree the school’s cancellation and make-up policy before configuring the workflow. Ask how a proposed replacement lesson will be represented, what capacity checks apply and what the parent sees. Verify the required behaviour rather than assuming every booking system offers the same make-up mechanism.
For an unexpected pool closure or instructor absence, update the affected sessions and contact the relevant families. Include the specific date, location and next step so parents do not have to infer which lesson is affected.
Use attendance and progress for different questions
Attendance shows participation in the lesson. Progress records can support an instructor’s view of development. Neither should automatically decide every level change. Keep the school’s assessment criteria and instructor judgement central to progression.
Review incomplete registers and recurring family questions early. They can reveal a configuration or communication problem before the team creates separate spreadsheets to work around it.
Klunivo’s swimming-school workflow brings these operational records together. Use the family-account guide to prepare a realistic parent journey for your demo.
FAQ
Questions worth answering
Is available lesson capacity enough to confirm enrolment?
No. The lesson should also suit the swimmer’s level and the school’s teaching arrangements.
Can siblings have separate lessons under one guardian account?
A connected family model can keep separate swimmer records while the guardian manages the appropriate child context.
Should software decide when a swimmer changes level?
The school’s criteria and instructor assessment should determine the decision. Records can provide supporting history.
