HVAC equipment history that survives the next service call.

Look up a rooftop model’s manufacturer reference in the equipment library.

The site alone isn’t enough.

“Worked on rooftop unit” might close a ticket, but it tells the next tech nothing. A commercial property can have several similar units with inconsistent labels. Each unit needs a fixed identity plus the details a tech uses to find it: site, building area, floor or roof position, the customer’s label, equipment type, make, model and serial number.

Two buildings can both have an RTU-1.

Say one customer has a north office and a south warehouse, each with an RTU-1 on the roof. The tag alone can’t tell the tech which one had the compressor replaced.

• North office / RTU-1: match the nameplate serial, roof location and reference photo. Its March report records a compressor replacement.
• South warehouse / RTU-1: a different serial and location. Its April report has a belt finding waiting on approval.

Open the unit from the scheduled stop. The last report, its photos and the open repair should all be on that exact unit. When a unit is replaced, keep the old unit’s history and mark the new one clearly so the two don’t blur together.

Then try the same lookup with no signal and see what was already saved on the phone. The no-signal buying test walks through it.

History should answer the next tech’s questions.

• Has this fault happened before?
• What parts were changed, and when?
• Which readings were abnormal?
• Are there photos of the nameplate, wiring or earlier damage?
• Was a repair recommended, quoted, approved, declined or completed?
• What maintenance tasks are due on this visit?

If the answers are buried in job PDFs, nobody will dig for them. The unit page should pull the facts together, with the original reports and photos behind them.

Open findings belong on the unit.

A finding isn’t done when it shows up in a report. It may still need office review, a price, customer approval, a booking and the repair itself. When its status stays with the equipment, the next tech doesn’t rediscover the same problem and the office has a list of what still needs doing.

PM agreements spell out what you owe.

A planned maintenance agreement sets the covered equipment, how often you visit and the tasks each visit includes. The software should keep that work apart from reactive calls and quoted repairs, so the tech knows what this visit covers and the office can see whether every promised visit and task got done.

The worked PM agreement shows how an overdue return stays separate from the next seasonal visit.

Build the record without a data-entry project.

Most shops already have equipment details spread across spreadsheets, old jobs, photos, PDFs and techs’ memories. A good system imports what you trust, keeps track of where it came from, and lets you review the uncertain matches. After that, ordinary field work fills in the rest: nameplate photos fill identity gaps, spoken notes add history, and completed quotes close findings.

Test it on one real unit.

Pick a unit from a customer with several locations and ask the vendor to open its history in the field: the last report and photos, the open repair, the PM tasks and the paperwork the customer gets.

For a small example, try the service-report builder or the worked report example. To compare vendors fairly, see how to compare commercial HVAC software.

How BoltWright connects it.

BoltWright keeps customers, sites, equipment, agreements, service history and findings in the same records. Techs see the history in the field, and the office sees what needs review or follow-up. See the equipment and PM workflow or read the commercial HVAC software guide.