The operating reality for universities and tertiary providers
A university or tertiary provider is several operations under one roof. There are sport and recreation facilities to run, with memberships, bookings and casual entry. There is training and short-course delivery, which in many institutions includes vocational programs reported under national standards. There is a large campus estate of buildings and plant to maintain. And there is finance to account for across faculties, schools and related entities. Each of those tends to belong to a different department with its own software.
That departmental split is the source of most of the friction. Recreation activity is exported to finance by hand. The asset register sits apart from the maintenance team's records. Training delivery and its compliance reporting live in a separate system again. Building a picture across the institution means asking several departments for several exports, and the answer is always a few weeks behind.
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 large institution, four products carry the load.
- Complex runs campus aquatic and recreation facilities, including memberships, bookings and casual entry. See recreation facilities for universities.
- Campus delivers vocational training and produces AVETMISS reporting where the provider operates as an RTO. See it at campus.cohiva.app.
- Control manages campus assets, work orders and preventive maintenance, and posts fixed-asset depreciation to the ledger. See campus asset maintenance for universities.
- Crunch consolidates finance across faculties and entities with multi-entity consolidation. See it at crunch.cohiva.app.
How the shared data layer changes the work
Because the products share one identity and one data layer, the institution operates across recreation, training, maintenance and finance on one platform rather than a set of departmental islands.
A membership or booking taken in the recreation centre through Complex becomes activity Crunch can consolidate, so finance sees usage and income across facilities without a manual export. A building or plant item tracked in Control carries its maintenance history and its depreciation in the same place, so the estates team and the finance team read the same asset. Where the provider runs an RTO, training delivered through Campus carries the AVETMISS reporting that the institution must produce. One identity recognises staff, contractors and members across the products rather than setting each up separately per department.
A normal term across the institution
Picture a term at a multi-campus provider. At the recreation centre, students and staff renew memberships and book courts and lanes in Complex, and casual entry is taken at the door. That activity is captured as it happens and consolidates into the finance view in Crunch across both campuses, rather than waiting for an end-of-term reconciliation.
Across the same term, the estates team works through preventive maintenance in Control: pool plant, HVAC and lifts each carry a schedule and a work order history, and the depreciation on those assets posts to the ledger so finance and estates see one version of the asset. Where the institution delivers funded or fee-for-service vocational programs as an RTO, those enrolments and completions run through Campus, which produces the AVETMISS reporting required of the provider. Four operations, one data layer.
Why integration matters across faculties and campuses
Large institutions answer to budgets, to regulators and to their communities, and each of those is easier to serve when the underlying systems connect. A central question such as how a campus or a faculty is performing draws on recreation income, asset cost and training activity that, in most institutions, sit in separate systems. On one data layer, the consolidation in Crunch joins facility activity from Complex, asset cost from Control, and the training picture from Campus, so reporting across faculties and campuses comes from one source rather than a stack of departmental exports.
That shared layer also scales with the institution. Adding a campus or a faculty does not mean standing up another disconnected stack. The new entity joins the same identity and data layer, so recreation, maintenance, training and finance stay connected as the institution grows.
Built for multi-site institutions
Cohiva suits universities and tertiary providers that want recreation, training, maintenance and finance connected across many sites. As the institution grows, those operations stay on one data layer rather than fragmenting per department.
If you run a university or tertiary provider, start with the Complex overview for recreation facilities, then see how campus asset maintenance fits your estate. Public operators with similar facility and asset needs can also see the councils solution.