How to Track HVAC, Plumbing, and Building Equipment in a Condo (Asset Registry Guide)

Every condo building already has an inspection schedule, a warranty period, and a rough replacement cost for its major systems, that information exists somewhere, in an engineer's report, a vendor's invoice, or an installer's spec sheet. The problem most property managers run into isn't that the information doesn't exist. It's that it's scattered across years of emails, PDFs, and whoever happened to handle that vendor relationship, and reconstructing it under deadline (a reserve study intake, an insurance renewal, a board question about the roof) is what actually costs time.

An asset registry solves this by making the equipment itself, not the maintenance ticket, the unit of record. This guide walks through how to structure one for HVAC, plumbing, and the rest of a condo's mechanical, electrical, and life-safety systems.

Start with categories, not a spreadsheet of individual items

The temptation is to start listing individual pieces of equipment. Resist it until the categories are set. A condo asset registry works best when it's organized around the same structure a reserve fund study already uses to assess common elements:

• Mechanical: boilers, chillers, air handling units, pumps, cooling towers, domestic water booster pumps
• Vertical Transportation: elevators, escalators, lifts
• Envelope: roofing, cladding, windows, curtain wall, waterproofing, balcony resurfacing
• Life Safety: fire alarm panels, sprinklers and standpipes, emergency lighting, egress systems
• Electrical: switchgear, generators, automatic transfer switches, distribution panels
• Structural: foundation, slabs, load-bearing elements, parking garage structure

Organizing the registry this way from day one means it lines up with the report a board eventually has to approve, instead of requiring someone to manually reclassify years of scattered records into reserve-study categories every time a new study is due.

What each asset record needs

For every individual piece of equipment, five fields do most of the work:

1. Category and location. Which of the six categories it belongs to, and specifically where in the building, "rooftop AHU-2" is a record; "the HVAC unit" is not.
2. Install date. The single most consequential field, since useful-life and replacement-cost projections are calculated from it. If the true install date is unknown, that should be flagged explicitly rather than guessed at, since a wrong assumption compounds into every future funding projection.
3. Condition status. Not a paragraph of notes, a clear tier (something like Critical, Monitor, Good) that a board member can scan at a glance without needing to interpret engineering language.
4. Useful life and replacement cost. Even a rough estimate, tied to the install date, is more useful than nothing, and it's the number a reserve-study engineer will eventually verify or override.
5. Linked history. Every work order, invoice, and inspection tied to that specific asset, in one place, not scattered across a shared drive by date instead of by equipment.

Handle high-cardinality systems as pools, not one row per unit

Some systems don't fit a one-asset-one-record model cleanly. In-wall piping, wiring runs, and fire alarm devices are typically modeled in real reserve studies as an allowance pool, a per-unit cost over a replacement cycle, rather than an individual line item per fixture. A registry that tries to force every fire alarm pull station into its own row will be harder to maintain than one that tracks the system as a pool with a defined replacement interval, matching how the equipment is actually funded and replaced in practice.

Elevators are the opposite case: they're commonly modeled as several distinct line items (cab and doors, controls, and mechanical), because each component has a meaningfully different useful life, controls are typically replaced well before the mechanical drive system, and lumping them into one record obscures that.

Keep it current: log at the point of work, not after

The single biggest failure mode for an asset registry isn't the initial setup, it's drift. A registry that's accurate on day one and never updated again is just a more detailed version of the same stale PDF it replaced. The fix is structural, not procedural: make updating the registry part of how work gets logged, not a separate task someone has to remember to do afterward.

That means the vendor doing the work should be the one updating the record, at the time of the visit, from the job site, ideally without needing to create an account or learn a new system. Every extra step between "the work happened" and "the record reflects it" is a place where the update quietly doesn't happen.

How belo structures this

belo's registry is built around the same six categories described above, so setup doesn't require translating a building's actual systems into a generic taxonomy. Each asset carries install date, condition, and useful-life fields natively, and every work order, invoice, and vendor certificate of insurance attaches directly to the specific asset it applies to. Vendors update records through a no-login field link, which is what keeps a registry from going stale between reserve study cycles: updating it is part of closing out the job, not a follow-up task.

When the registry needs to feed a reserve fund study, it exports in the same category structure the engineer is already using, which is the difference covered in more detail in our guide to reserve fund study prep for property managers.

If you're setting up an asset registry for your property, or migrating one out of a shared drive, book a demo to see the six-category structure applied to your own building.