What goes in an HVAC service report

Who the report is really for

A service report gets written once and read three times, usually by three different people who each want something different from it.

• The customer, today. They want to know what was wrong, what you did, what it cost them, and whether anything still needs attention. They are not going to look up what "22 °F superheat" means.
• The next technician, later. Possibly you, eighteen months from now, standing at the same unit with no memory of this visit. They want the model and serial, the readings you took, and what you already replaced.
• Whoever settles a dispute. A landlord, a home warranty company, a buyer's inspector, a new owner. They want dated, specific facts and a signature.

Almost every problem with field paperwork comes from writing for only the first reader. "Serviced unit, system operating normally" satisfies nobody twice.

The eight sections

1. Identification

Your business name, license number and contact details; the customer's name and the service address — which is frequently not the billing address; the date, the arrival and departure times, and the technician's name. Give the report a number you can search on later.

2. Equipment

Manufacturer, model, serial, equipment type, placement (attic, closet, roof, north side of house), and where practical the voltage, phase and capacity. This is the single section most often left thin, and the one the next visit depends on most. Photograph the nameplate rather than copying it by hand — a transposed digit in a serial number is invisible until the day someone needs the warranty.

3. Customer complaint

What the customer actually said, in their words, before you touched anything. "The upstairs system was not cooling." Not "low charge" — that is your finding, not their complaint. Keeping the two apart is what makes the rest of the report defensible, because it shows what you were called out for versus what you concluded.

4. Technician findings

What you observed and measured, with the numbers attached. "Dual run capacitor rated 35/5 µF, measured 24.7 and 4.8 µF." "Condenser coil heavily loaded with cottonwood." Findings are observations. Resist writing conclusions here that the measurements don't support.

5. Work performed

What you actually did, in order, with the parts you used and their quantities. "Replaced dual run capacitor. Cleaned condenser coil." If a part came off the truck, name it. If the customer supplied it, say so.

6. Measurements and readings

The numeric record of the visit — see the next section for what to capture. Pair each reading with when it was taken: a supply-air temperature before the repair and one after tell a story that a single number does not.

7. Recommendations

What you did not do, and why it matters. Deferred repairs, aging components, airflow restrictions, a maintenance interval. Two things make a recommendation useful: it is specific ("replace pitted contactor at next maintenance visit", not "unit is old"), and it is dated, so a failure six months later lands against a documented warning rather than a surprise.

8. Acknowledgment

A signature or a typed acknowledgment from whoever was on site, captured before you leave. A signature collected on the spot is worth more than a form emailed the next day and never returned. If nobody was home, record that too.

Which measurements to record

What is worth capturing depends on the equipment and the call, but on a typical residential or light-commercial visit these are the readings that turn out to matter later:

Record the value, the unit, and what it was measured on. A page of bare numbers with no unit attached is worse than no numbers, because it looks authoritative and cannot be checked.

On record-keeping rules: requirements for refrigerant records vary by refrigerant, charge size, equipment type and jurisdiction, and they change. Nothing here is a compliance determination — check the current requirements that apply to your work with the relevant authority.

Five mistakes that cause disputes

1. Writing the report at home that night. Detail decays fast. The model number you were sure you'd remember becomes "Carrier heat pump," and the reading you took at 2pm becomes "pressures were fine."
2. Merging the complaint into the finding. Once the customer's words and your diagnosis are the same sentence, you have lost the ability to show what you were called for and what you concluded.
3. Recommendations with no date and no specifics. "Unit is getting old" protects nobody. "Contactor pitted, recommend replacement at next maintenance visit, 2 August 2026" does.
4. No photograph of the nameplate. The one artifact that makes every future visit cheaper, skipped because it was raining.
5. No signature. The customer agreed to the work at the truck and remembers it differently in November. An acknowledgment captured on site ends that conversation before it starts.

How to do it in two minutes

Every item above is worth writing down, and that is exactly the problem: written by hand at the end of a six-call day, most of it doesn't get written. The way through is not a shorter report — it is a faster way to produce a complete one.

That is what HVAC Field Report does. You talk through the visit the way you'd explain it to the customer, standing at the truck, and it sorts what you said into complaint, findings, work performed and recommendations. It pulls the pressures, temperatures, superheat, subcooling and capacitor readings out of your own sentences and leaves every one of them unticked until you confirm it — nothing reaches the report on its own, and no number is ever invented by a language model. You photograph the nameplate instead of copying it, collect a signature on the glass, and hand over a printable PDF before you leave.

It runs entirely on your iPhone or iPad, with no account and no signal required, because the attic is exactly where you need it to work.

This page is general guidance for working technicians, not legal, regulatory or engineering advice. Diagnosis, system sizing and any judgment about whether equipment is operating correctly remain the technician's professional responsibility.