These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Swimming Pool Management
- Implementation and migration
How a Swimming Pool Management rollout works
Start with one pool and one week of sessions the front desk and manager can reconcile.
Agree the operating boundary
The scope is pool operations: services, sessions, members, plans, bookings, lanes, check-in, payments and water checks. Payments, online booking, messaging and chemistry controllers remain connected. The pool decides its booking, refund and closure policies and water thresholds; Proto prepares configuration for review.
Map the source data
Bring the service list, the timetable, members with plans, lane limits and the water testing schedule.
Configure a bounded pilot
Pilot one pool for one week. Confirm bookings, allocate lanes, check swimmers in and record water checks.
Rehearse the exceptions
Confirm a booking for a member without an entitlement. Overfill a session. Book a lane past the session end. Record a Close result and cancel sessions. Approve a refund.
Reconcile and release
Compare members, plans, places and payments with the source. Obtain the Aquatics Manager's acceptance before adding pools.
What the customer provides
- Services with durations, capacities and prices.
- Membership plans with allowance and validity.
- Members with numbers and current plans.
- The timetable with instructors and lane limits.
- Water testing schedule and thresholds.
Changing it afterwards
Use Proto to prepare changes on a branch. Review changed fields, permissions and reports with the Aquatics Manager. Replay the pilot’s exception cases before release.
Set up Swimming Pool Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.