A day in a multi-site leisure operation
Picture an operator running several aquatic centres and a swim school brand. On any given morning the front desk is selling casual entries and retail, the learn-to-swim program is running classes, members are checking in through the gates, instructors are starting shifts, a pump needs a service, and head office wants to know how the network is tracking against budget.
Every one of those is a data event, and every one touches more than one function. A casual entry is operational activity, money in the accounts and, across the week, a reason the roster needed an extra lifeguard. A class enrolment is a program record, a payment and an attendance mark. A pump service is a maintenance job and a cost against an asset.
In a stack of separate tools, those connections are invisible to the software. The booking system knows about the class, the payroll system knows about the shift, the accounting package knows about the money, and none of them know about each other. The connections live in spreadsheets and in the heads of the people who do the reconciling.
What changes on one platform
On one platform, those same events are recorded once and read by every function that needs them. The casual entry sold this morning is venue activity in Complex, a line in the books in Crunch, and part of the staffing picture that informed the roster in Culture, all from the same record. Nobody exports it, reformats it or keys it in twice.
That is the practical meaning of one identity and one data layer. The member is a member of the organisation, not of a single pool. The instructor is one person across the platform, onboarded once and rostered against the venues they work at. The pump is one asset, maintained in Control and depreciated in the ledger from the same place.
The four functions, joined
Facility management
Complex is the anchor. It runs classes and programs, memberships, point of sale, bookings and access control across venues, with reporting that rolls up to head office and drills down to a single site. For the full picture of how a pool operator uses it, see solutions for aquatic centres, and for the swim school case, solutions for swim schools.
HR and rostering
Culture handles onboarding, rostering, leave, timesheets and payroll export for a shift-based workforce. Because staff records flow into Complex, the people on the timetable are the people HR has scheduled. The matrix page on instructor rostering and payroll for swim schools covers this for a learn-to-swim operator.
Finance
Crunch is the finance product, with real-time profit and loss, multi-entity consolidation and a 13-week cash forecast. Transaction data flows from Complex into Crunch, so the books reflect what happened at the desk today rather than last month. For an operator running several entities, accounting and finance software for aquatic centres shows the consolidation angle.
Maintenance
Control manages assets, work orders and preventive maintenance across the network, and posts fixed-asset depreciation to the ledger. Plant fails when it is not serviced, and unserviced plant closes pools, so keeping maintenance and finance joined matters. See maintenance management software for aquatic centres.
What head office sees
The payoff of joining these four functions is most obvious at head office. In a stack of separate tools, a regional manager asking how the network performed last month sets off a small project: pull a report from the booking system, a report from the accounting package, a roster summary from payroll, and a maintenance log from a spreadsheet, then stitch them together and hope the dates and definitions line up.
On one platform, the same question is a query against one set of records. Revenue by venue, program enrolments by site, labour cost against takings, and the cost of unplanned maintenance all read from the same data, current to today. The manager can compare venues on a like-for-like basis because the numbers come from one definition rather than four. Reporting rolls up across the network and drills down to a single pool, so the conversation moves from assembling the figures to acting on them.
That shift, from reconciling to deciding, is the practical reason multi-site leisure operators move to one platform. The reconciliation never created value. It only made the network legible, and the platform makes it legible for free.
A note on growth
Leisure operators rarely stand still. A council takes on another centre, a swim school brand opens new venues, a health club chain acquires a competitor. In a stack of point tools, each addition multiplies the joins you maintain, because the new site has to be wired into every system and every manual process.
On one platform, growth is mostly configuration. A new venue is added to Complex, its staff are onboarded in Culture, its finances roll into Crunch, and its assets are tracked in Control, all on the data layer that already exists. The marginal effort of the next site falls rather than rises, which is the opposite of what most operators experience with a disconnected stack.
Adopting it gradually
No operator switches everything at once, and they do not have to. The common path is to start with facility management in Complex, which immediately gives finance a live feed into Crunch, then add HR in Culture and maintenance in Control as the data flow earns its place. Each product joins the existing data layer rather than adding another integration to maintain, and the whole thing runs on one identity and one bill.
The result is an operation that is recorded once and read by everyone who needs it. The reconciliation work that used to fill a week shrinks, head-office questions have direct answers, and the team spends its time running pools rather than keeping software in step.
For the model behind this, read one platform, one data layer; for the data mechanics, how data flows across the Cohiva suite; and for the build-or-buy trade-off, integrated suite vs point solutions.