HVAC equipment history that survives the next service call.

Check a rooftop model and find its manufacturer reference in the equipment library.

The site is not specific enough.

“Worked on rooftop unit” may close a ticket, but it does not build a useful history. A commercial property can have several similar units and inconsistent labels. The record needs a stable equipment identity plus the practical details a technician uses to find it: site, building area, floor or roof position, customer label, equipment type, make, model, and serial number.

Two buildings can both have an RTU-1.

In this fictional example, one customer has a north office and a south warehouse. Each roof has an RTU-1. A unit tag alone cannot tell the tech which compressor was 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 awaiting approval.

Open the unit from the scheduled stop. The previous report, supporting photos and open repair should belong to that exact record. If a unit is replaced, preserve the old unit's history and clearly identify the replacement rather than blending the two.

Then repeat the lookup without reception. Check which history and attachments were saved on the phone first. Use the no-signal buying test; a searchable office record does not by itself prove field availability.

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 prior 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-level PDFs, the history exists but is difficult to use. The unit page should bring the relevant facts together without erasing the original report and evidence.

Open deficiencies need a lifecycle.

A finding is not finished when it appears in a report. It may need evidence, office review, pricing, customer approval, scheduling, and completion. Keeping that status attached to the equipment prevents the same issue from being rediscovered on every visit and gives the office a clear list of work that still needs action.

PM agreements describe obligations.

A planned maintenance agreement connects covered equipment, visit frequency, and required tasks. The software should distinguish work that is due under the agreement from reactive service work and additional quoted repairs. That makes the next visit clear for the tech and helps the office see whether every promised visit and task has been delivered.

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

Building the record without a data-entry project.

Most shops already have equipment information scattered across spreadsheets, job history, photos, PDFs, and technicians' memory. A practical system should import what is trustworthy, preserve the source, and make uncertain matches reviewable. After that, ordinary field work should improve the record as a byproduct: nameplate photos fill identity gaps, spoken notes add history, and completed quotes close deficiencies.

Test a unit record, not a demo dashboard.

Use one representative asset from a customer with multiple locations. Ask the vendor to open its history in the field, locate the last report and photos, show the outstanding repair, then show the PM obligation and the customer-facing paperwork. A list of jobs is not the same thing as a useful unit record.

For a small fictional example, try the service-report builder or read the worked report example. For a fair buying script, see how to compare commercial HVAC software.

How BoltWright connects it.

BoltWright keeps customers, sites, equipment, agreements, service history, and findings in one operating record. The field sees the history; the office sees what needs review or follow-up. Explore the equipment and PM workflow or read the commercial HVAC software guide.