Why data flow is the whole point
A suite of products is only as useful as the way its data moves. You can own software for facilities, finance, HR and maintenance and still be no better off than with a stack of point tools, if each one keeps its own copy of the data and you connect them by hand. What makes the Cohiva suite an integrated platform rather than a bundle is that the data flows structurally, through a shared data layer, rather than through exports and connectors.
The principle is simple. An event is recorded once. Every product that needs it reads the same record. There is no master copy to sync, no connector to maintain, and no reconciliation to chase. For the model behind this, see one platform, one data layer.
Following a single event
The clearest way to understand the flow is to follow one real event through the suite. Take a casual swim sold at the front desk this morning.
It starts in Complex
The sale is recorded in Complex, the product that runs aquatic and leisure facilities. Complex handles classes, memberships, point of sale, bookings and access control, so the casual entry sits against the member or visitor, the venue and the day. That single record is the operational truth of what happened.
It reaches finance through Crunch
Because transaction data flows natively from Complex into Crunch, the sale is already in the books. Crunch is the finance product, with real-time profit and loss, multi-entity consolidation and a 13-week cash forecast. Finance does not export a report from the front desk and key it into the ledger. The figure they work from is the figure that was recorded at the desk, current to today.
It connects to staffing through Culture
Across the week, that casual activity is part of the picture that informs the roster. Culture is the HRIS for shift-based teams, covering onboarding, rostering, leave, timesheets and payroll export. Staff records flow from Culture into Complex, so the people on the timetable are the people HR has onboarded and scheduled. The flow runs both ways in the sense that operations and HR share one source of truth about who works where.
The asset side of the flow
Not every flow starts at the front desk. Consider a pump at one of the venues. It is an asset that needs servicing and, in the accounts, an item that depreciates over time.
Control manages that asset, its work orders and its preventive maintenance schedule. Because Control posts fixed-asset depreciation straight to the ledger, the maintenance and financial views of the asset stay joined up. The service history that maintenance keeps and the depreciation that finance reports describe the same asset from the same data, rather than living in a spreadsheet and an accounting package that never meet. The mechanics of this are summarised in the glossary entries for CMMS and fixed-asset depreciation.
One identity underneath it all
The flows above only work because of one identity. A staff member onboarded in Culture, rostered against Complex and, where relevant, named on a governance record in Quorum is one person, not three accounts. A member exists once across the venues you operate. An asset exists once across maintenance and finance.
One identity is what lets the data layer be shared safely. Access reflects a person's role and the sites they work at, provisioning and deprovisioning happen in one place, and the same record is trusted everywhere because there is only one of it.
Flows beyond the front desk
Facility, finance, HR and maintenance are the busiest flows, but they are not the only ones. The same shared data layer carries records across the rest of the suite.
When an agreement needs signing, Sign keeps the signing inside the product workflow rather than in a separate tool, with a full audit trail attached to the record it belongs to. An enrolment agreement, a membership contract or a franchise disclosure document is signed against the same data the rest of the suite already holds, so the signed version and the operational record are one thing. The glossary entries for electronic signature and audit trail cover the mechanics.
For organisations that run a board or committee, Quorum manages meetings, agendas, minutes, resolutions and obligations on the same identity. A director is the same person across the platform, and a governance decision is recorded once. For marketing teams, Campaign keeps planning and approvals in one place, with the brand and compliance checks attached to the work rather than living in a separate review chain.
The pattern is consistent across every product. The data does not leave the platform to be processed somewhere else and come back. It stays in one place and is read by whichever product is doing the current job.
Why this is structural, not a feature
It is worth being precise about what makes these flows different from the integrations a stack of point tools relies on. An integration copies data from one system to another on a schedule or a trigger. There are two copies, a moment where they disagree, and a piece of software whose job is to keep them in step.
A shared data layer has one copy. The flow is not a copy operation at all. It is several products reading and writing the same records, with each product responsible for its own part of the operation. That is why the joins do not break: there is nothing to break, because nothing is being moved. This is the difference between integrated apps and an integrated platform, set out further in integrated suite vs point solutions.
What this removes
When the data flows structurally, a set of recurring costs simply disappear:
- No exporting and re-keying between systems.
- No connectors to build, monitor and repair.
- No duplicated, slightly stale copies of the same record.
- No reconciliation project standing between a head-office question and its answer.
That is the difference an integrated platform makes for a multi-site operator, and it is the case for choosing a suite over a set of point tools, as set out in integrated suite vs point solutions. To see the flow inside a working leisure business, read running a multi-site leisure operator on one platform, and for the criteria to apply when you evaluate, how to choose software for multi-site operations.
The suite is not a collection of products that happen to share a logo. It is one platform where an event is recorded once and read wherever it is needed, on one identity, one data layer and one bill.