Managing HVAC Maintenance Across Multiple Sites

What is multi-site HVAC maintenance?

Multi-site HVAC maintenance is the work of keeping heating, ventilation, air conditioning and refrigeration equipment serviced and compliant across more than one location, along with the records that prove it.

For a contractor it usually works on two levels at once: many clients, and many of those clients running several sites of their own. That's a different job from maintaining an organisation's own estate, where the engineers and the assets belong to the same business. The contractor version adds a complication the in-house version never faces, which is that none of the estates belong to the people maintaining them. Our guide to running HVAC service operations sets out the wider picture this sits within.

How does multi-site HVAC maintenance differ for contractors?

Most of the difference comes down to control. An in-house team decides what gets installed and who can work on it. A contractor inherits those decisions and works around them. In practice that shows up as:

• Equipment changing between visits. Tenants and fit-out contractors add or move units without telling the maintenance contractor, so the register drifts out of date unless engineers are expected to correct it on site.
• Every client defining things differently. Response times vary by contract, and so does something as basic as what counts as a "site". All of it has to coexist in one schedule.
• Asset data arriving in whatever state it was left. A new contract often starts with a register built by someone else, or with no usable register at all.
• Duties and evidence sitting with different parties. The client usually carries the legal duty. The contractor usually holds the records that show it was met.
• Engineers shared across clients. A reactive spike on one account eats into planned visits on another, often in the same postcode.

How should a multi-site HVAC asset register be structured?

Structure the register around how obligations and contracts actually apply. For most commercial HVAC work that means a hierarchy of client, site, system and individual unit.

The system level is the one that tends to get skipped. F-Gas obligations attach to individual pieces of equipment, while contracts and client conversations usually happen at system or site level. A register that only records units against a site address struggles to answer questions at either level without someone going back through the paperwork.

At unit level, the fields that do most of the work are:

• Make, model and serial number, plus where the unit sits within the site
• Refrigerant type and charge, with the CO2 equivalent alongside it
• Effective rated output in kW, taken from the rating plate rather than estimated
• The system the unit belongs to, and who owns it
• The contract and SLA it falls under, since one site can hold units on different agreements

Rated output rarely drives the maintenance itself, but clients occasionally ask for it. In England and Wales, air conditioning units in one building can add up past the 12kW threshold for a TM44 energy inspection, which the building owner or occupier normally arranges with an accredited assessor. Having the figure already on record saves a site visit to read rating plates.

Clients will have their own asset references, and they're worth keeping as a field. They make a poor backbone for the register, though, because every client's convention is different and none of them line up with each other.

How do you keep F-Gas records intact across a client base?

Record everything against the individual unit and treat each client's estate as its own set of obligations. The duty to have equipment leak checked sits with the operator, which is usually the client, and both operator and servicing company have records to keep. Most of the evidence, though, comes from the contractor's visits. Across dozens of clients, a few things decide whether that evidence holds together.

Leak-check intervals vary unit by unit

Frequency is set by the CO2 equivalent of each unit's refrigerant charge, so one site can hold units on 12-month and 6-month cycles side by side. Scheduling leak checks per unit, and then grouping them into visits, keeps every unit on its own interval. Scheduling per site visit can pull everything onto the shortest or the most convenient cycle. The leak-check bands and recordkeeping duties are set out in our F-Gas guide.

Records have to outlast the contract

F-Gas records for qualifying equipment must be kept for five years, a period that can easily span more than one maintenance contract. The records belong to the equipment's history, so they need to be held against the unit in a form that can be handed to the client, or to the next contractor, without being rebuilt. The same applies in reverse. When you win a contract, ask for the existing records at mobilisation rather than at the first audit.

The operator's records also have to include the certification number of the company servicing their equipment. On a multi-site contract, that's an easy detail for the client to lose track of and a simple one for the contractor to supply.

Refrigerant exposure is a client-level number

Total CO2 equivalent across each client's estate shows where leak-check workload and refrigerant cost will concentrate. That matters more now that Defra's update on HFC phasedown reform confirms the quota step due on 1 January 2027 goes ahead as already set out in law. Contracts priced on refrigerant assumptions from a few years ago are worth checking against that figure.

How do you plan engineer coverage across client sites?

Plan by geography and capability first, and by client second. Grouping each client's sites into its own run feels tidy, but it can send an engineer past one client's building to reach another's on the same street. A few constraints shape the plan more than distance does:

• Certification. F-Gas work can only go to engineers holding the right category, which turns certification into a hard scheduling constraint on who can be sent where.
• Site access rules. Permits, inductions, escort requirements and restricted hours vary by client and by site. They need to sit on the site record, where the planner sees them before the engineer reaches the gate.
• Visit alignment. Where a statutory leak check falls due close to a planned service, doing both in one visit saves a trip. It's part of the cost case for planned maintenance on commercial estates.
• Seasonal headroom. The first hot spell of the year lands on every client at once. Leaving some engineer capacity unbooked in each region through the peak months stops reactive callouts from consuming the planned schedule.

Capacity is unlikely to loosen soon. The Institute of Refrigeration's skills report, published in February 2026, describes shortages in both the number and the competence of engineers, and expects them to intensify over the next two to five years without coordinated action.

What should multi-site HVAC reporting show?

Reporting has two audiences, and they want different cuts of the same data.

Clients usually want to see, site by site:

• PPM completion against the agreed schedule
• Response and fix times against the SLA
• F-Gas records for each unit, ready for an audit
• Open recommendations and quoted remedial work

The contractor needs the commercial view:

• Margin by contract and by site, so a loss-making building shows up inside a profitable account
• Refrigerant used per client, set against what each contract assumed
• Repeat visits by asset type, which point to problem equipment or a poor installation
• Engineer travel time between sites as a share of each contract's hours

Both views depend on the register being built the same way for every client. If one account records units against systems and another records them against a building address, no report can compare the two.

What should a survey of an inherited HVAC estate establish?

Before the first planned visit on a new contract, a survey should capture enough to plan from, and enough to protect the contractor if the records turn out to be incomplete:

• Every unit located, labelled and assigned to a system, including units the client didn't know about
• Refrigerant type and charge for each unit, so leak-check intervals are right from the first visit
• Rated output from the rating plates, recorded once while the engineer is there
• Whatever F-Gas history the client or outgoing contractor can provide, with any gaps noted in writing
• Who owns each unit, particularly where tenants have installed their own
• Access arrangements and permit requirements for every site

Recording gaps at handover matters as much as filling them. A missing leak-check history noted in writing at mobilisation belongs to whoever held the contract before. The same gap found at an audit two years later looks like yours.

Frequently asked questions

How often do F-Gas leak checks happen across a multi-site estate?

It depends on each piece of equipment rather than the site. Frequency is set by the CO2 equivalent of the refrigerant charge, so two units on the same site can be on different intervals.

What happens to F-Gas records when a client changes HVAC contractor?

The client, as operator, has to keep F-Gas records for five years, so the history should stay with the equipment rather than leave with the outgoing contractor, even though the contractor keeps records of its own. In practice the incoming contractor should request the records at mobilisation and note any gaps in writing before the first visit.

Is multi-site HVAC maintenance a field service or a CMMS job?

For a contractor maintaining equipment on client sites, it's field service work, because the engineers travel to assets their business doesn't own. Field service management software is built around that model. An organisation maintaining its own estate with its own engineers sits closer to CMMS territory, although teams travelling between their own sites end up borrowing some field service scheduling.

How does software support multi-site HVAC maintenance?

Most of what this guide describes depends on whether the asset record is structured well enough to answer questions across clients. Service Geeni builds its software for HVAC contractors around the asset, so each unit holds its own work and breakdown history and keeps it if the unit moves to another site. Parent and child relationships link related assets together, and custom fields on asset records can hold details such as rated output. Maintenance contracts, rate cards and SLAs sit in the same system, and the F-Gas module records refrigerant movements and leak checks against the system they relate to, with site CO2 tonnage reported across the client base.