Linked equipment groups: why we built the HVAC feature no one else has.

That problem — figuring out which condenser goes with which evaporator on a property you haven't visited in a year — is the entire reason we built linked equipment groups. It's not a compliance feature. It's not a flashy demo feature. It's a quiet productivity feature that solves a daily friction point HVAC techs and dispatchers have been swallowing for years because the software they use was never designed for the way HVAC equipment actually works.

Where the idea came from

The Finished Touch Limited — the largest HVAC contractor in St. Kitts and Nevis, ten years in business, running TuffOps in production — is one of our joint development partners. Their book is primarily commercial with a residential side, and at island scale they're touching enough properties on a regular basis that they have the institutional memory most contractors never get the chance to develop. The problems most shops never even notice as problems — because they just adapt around them — show up clearly.

They kept flagging this as a real, observed cost. Not a feature request in a wishlist. A daily friction point that showed up in three places:

• In the field: Techs lost five-to-ten minutes per visit on multi-unit properties just figuring out which equipment belonged to which system.
• In dispatch: When a customer called about a problem with "the upstairs unit," the office had to triangulate from old work orders, install dates, and customer descriptions to figure out which physical unit they meant.
• In quoting: When a condenser failed and the matched evaporator was within warranty, nobody knew without manually cross-referencing serial numbers and dates.

None of these are catastrophic on their own. None of them generate a support ticket. But across hundreds of properties and thousands of visits a year, they add up to a meaningful tax on the operation.

So we built linked equipment groups.

How it works

In TuffOps, you can link any number of equipment records into a single system:

• A residential split system: one condenser + one evaporator
• A 4-zone mini-split: one condenser + four indoor heads
• A commercial rooftop unit and its remote economizer
• A refrigeration rack with one condensing unit and N evaporator cases
• Any other combination that makes operational sense for your shop

Open any member of a group and you see a chip in the UI showing the system size — for a matched split, the chip reads "2" next to a chain icon, telling the tech at a glance that this evaporator is paired with one other unit. One click on the chip jumps you straight to the partner. Service history, photos, notes, and refrigerant events are unified across the group, so when a tech opens the upstairs evaporator, they see every visit ever made to any unit on the same system. Warranty records stay aligned, so a matched-pair warranty has one expiration date the office actually trusts.

The hard part: breaking links cleanly

Equipment doesn't last forever. The condenser fails after 12 years; the matched evaporator might still be good. You replace just the condenser. Now what?

This is the lifecycle problem that, more than anything else, is why other HVAC software vendors haven't tried to model linked equipment in the first place. Linking units forever is easy. Letting them link, unlink, re-link, and retire — without losing the historical record at any step — is hard.

In TuffOps, when a unit is decommissioned:

• You break the link from the active system without deleting the unit's record.
• The decommissioned unit retains its full service history — you can still see what was in service when, where it lived, and what work was done on it. Useful for warranty disputes, compliance audits, or just answering a customer's question two years later.
• The remaining members of the system continue forward, and the new replacement unit gets linked in.
• Refrigerant tracking, leak rate calculations, and warranty records all reflect the current system membership without losing the audit trail of what came before.

This is what makes linked equipment groups actually usable, instead of a model that breaks down the first time you do a partial replacement.

Want to see this live? Book a 30-minute demo and we'll walk through linking a real split system, doing a partial replacement, and showing how the historical record stays intact.

What this gets you, day-to-day

Why no one else has built this

Housecall Pro, Jobber, ServiceTitan, FieldEdge — all of them grew up serving general field-service trades. Plumbing, electrical, lawn care, pest control, handyman work, and HVAC, all under one umbrella. In a generic property profile, every "thing" is a thing: a water heater, a dishwasher, a furnace, an A/C. They don't relate to each other. The flat list works fine for plumbing.

HVAC is different. The defining characteristic of an HVAC system is that pieces of equipment are connected to each other by refrigerant lines, electrical interlocks, and shared controls. Modeling them as independent records is a category error — but it's the one every general field-service tool makes, because they were never designed with HVAC as the primary trade.

We built TuffOps with HVAC contractors as our joint development partners, not as one of many trades on a feature roadmap. So when the matched-pair pain showed up in production, we built the right model for it instead of telling the customer to use a naming convention and hope for the best.

Linked equipment groups isn't the only feature that came out of these conversations. The QR-code service-request flow — where an end customer scans a sticker on the unit to start a service request without ever picking up the phone — came from the same TFTL conversation about how much of their work was still arriving by phone call, and how much office time that was eating. The way checklists are bound to the equipment rather than to the work order is the same pattern, applied to procedure-of-record. Same theme: HVAC-specific friction, named, fixed in the product instead of papered over with a workaround.

Available where

Linked equipment groups are available on TuffOps Pro and Enterprise plans, alongside the rest of our HVAC-specific equipment tooling — QR-coded units, refrigerant tracking with the Comply module, and full work-order-to-invoice integration.

The bottom line

If you've ever had a tech radio the office to ask which condenser is paired with which evaporator on a property they haven't been to in a year — or if you've ever discovered three months too late that a warranty claim got missed because the matched coil's record lived in a different row of a spreadsheet — you've felt the cost of equipment that isn't linked.

We built linked equipment groups because that cost is real, recurring, and entirely fixable. The fact that it also makes EPA compliance dramatically easier is a happy side effect. The reason it exists is the day-to-day work.

← Back to all posts