The operating reality for swim schools
A swim school is a scheduling business with a duty of care. There are class timetables to build across pools and terms, enrolments to take and manage as families join and leave, attendance to mark for safety and progression, billing to run on a recurring cycle, and instructors to roster against every class. Most operators do this across more than one location, which multiplies the coordination.
Run on separate tools, this becomes double entry. The booking system does not know who is rostered. The billing run does not know who signed the enrolment agreement. Instructor hours are re-keyed into payroll. Each gap is manual work and a place where a family or a class falls through.
The Cohiva products that fit
Cohiva is an integrated operating platform of purpose-built products that share one identity and one data layer. For a swim school, four products do the work.
- Complex handles class scheduling, enrolments, attendance, bookings, billing and point of sale. It is the core of the swim school operation. See it at complex.cohiva.app.
- Culture manages instructor rostering, leave and timesheets, connected to the classes in Complex. See instructor rostering and HR for swim schools.
- Sign handles enrolment agreements as legally binding e-signatures with a full audit trail, embedded in the enrolment workflow. See enrolment agreements for swim schools.
- Crunch consolidates finance across locations and reports profit and loss from the billing captured in Complex.
How the data layer changes the work
Because the products share one data layer, a new enrolment connects the class, the payment, the roster and the signed agreement in one flow.
A family enrols in Complex, signs the enrolment agreement through Sign without leaving the workflow, and is billed on the recurring cycle. The class they join is staffed from rosters built in Culture, and the instructor's hours flow to payroll without re-keying. The billing run becomes revenue Crunch can see and consolidate across locations. One identity means a family or a staff member is set up once and recognised across the products.
Enrolments and agreements in one flow
The enrolment is where a swim school either runs smoothly or creates work. A parent wants to enrol a child, pick a class time, sign the agreement and pay, and they want it to take a few minutes. Behind the scenes, the school needs the class place reserved, the recurring billing set up, the signed agreement on file, and the right instructor rostered.
With the suite, that is one flow. The enrolment is taken in Complex, the agreement is signed through Sign without leaving the workflow, and billing is set on the recurring cycle. The class the child joins is staffed from rosters built in Culture. Nothing is re-entered between steps, and nothing depends on a parent printing, signing and scanning a form. The audit trail on the signed agreement is kept by Sign, so the school can show what was agreed.
Why the integration matters across terms
Swim schools run on terms, and terms create churn: families finish levels, move up, take breaks and return. Tracking that across separate systems means reconciling who is enrolled, who has paid and who has signed every term. On one data layer, those facts live together, so a child's place, payment, attendance and agreement are one record that moves with them across terms and locations.
This is the integrated operating platform thesis for learn-to-swim: one identity, one data layer, and scheduling, billing, staffing and agreements connected.
Attendance, progression and the duty of care
A swim school carries a duty of care that an ordinary booking business does not. Marking attendance is more than admin. It is the record of who was in the water, which underpins ratios, progression and the conversation with parents about a child's level. Complex records attendance against classes and enrolments, so the mark taken at the poolside is the same data the office and the parent see. When a child is ready to move up, the enrolment, the new class place and the billing change follow in the same product rather than across three.
Because attendance and enrolment sit on one data layer with billing and rostering, a teacher's view of their class, the office's view of payments, and a parent's view of their child's progress all draw on one source. That consistency is what keeps a growing swim school from spending its evenings reconciling spreadsheets.
Built for multiple locations
Cohiva targets multi-location swim school operators who want classes, staff, agreements and finance connected. As you add pools and terms, the shared data layer keeps scheduling, billing and rostering aligned across sites rather than in separate systems per location.
If you run a swim school, start with the Complex overview, then see how instructor rostering and enrolment agreements fit your operation. Operators running pools alongside classes can also see the aquatic centres solution.