What to keep after an HVAC maintenance visit

The trouble starts when the paper trail is thin

Most owners think the headache starts with the callback itself. It usually started a week earlier when the maintenance visit ended with a scribbled note, a wet invoice, and a tech saying, “I checked it all.” Then the customer calls back and says the condenser coil was never cleaned, the filter was never changed, or nobody told them the contactor was pitted half to death.

That is where job evidence matters. Not big fancy paperwork. Real proof from the visit. Who showed up. When they got there. What they checked. What they found. What they left behind. If you run HVAC trucks, that record is your shield when a customer says the story changed after the fact.

And it is not only about defending yourself. Good records let you see patterns. If one tech keeps writing “all good” while the next guy keeps finding dirty evaporator coils and weak capacitors, you know where the training gap is.

What a real maintenance record should capture

For an HVAC maintenance visit, I want the record to tell me the job happened and what shape the equipment was in. Not a novel. Just the stuff that matters when the next issue pops up.

A solid job record should include:

• GPS check in and check out time
• Tech name
• Equipment location and unit type
• Model and serial number if the tag is readable
• Filter size and whether it was changed
• Coil condition
• Refrigerant pressures if they were checked
• Supply and return temperatures
• Amp draw on the compressor and blower if relevant
• Capacitor reading if the tech tested it
• Static pressure if that is part of your routine
• Photos of the unit before and after service
• Notes on any dirty burners, loose wiring, rust, or water in the pan

That is the kind of evidence that holds up in a customer conversation. If the condenser was packed with cottonwood and the tech took a before photo, you do not have to guess later about what was found. If the suction pressure was low and the superheat was off, you have the numbers, not a shrug.

SodaDesk records the check in time with GPS. It tags the tech. It keeps the photos and checklist together for that visit. That matters because a job record without time and place is just a note.

The after photo is worth more than people admit

A lot of shop owners treat photos like a nice extra. I don’t. A good after photo saves arguments.

Say your tech cleans a rooftop unit and changes a filter in a ceiling return. A week later the customer says the unit still looks filthy and nobody touched the filter cabinet. If you have a clear after photo of the coil face, the clean drain pan, and the installed filter with the date on the visit record, the conversation changes. It stops being a memory fight.

The photo needs to show something useful. Not the sky. Not the side of the tech truck. Get the evaporator coil before and after. Get the condenser coil with the cabinet open. Get the old capacitor with the reading written in the checklist if it was out of range. Get the rusty flue connector if the unit has one and it needs attention next time. Those pictures tell the story better than a checkbox that says “completed.”

And if your tech finds something borderline, the photo proves why the recommendation was made. A swollen contactor, a leaking Schrader cap, a drain line full of sludge. That is the stuff customers forget five minutes after you leave.

Checklist notes beat vague language

The problem with lazy notes is that they sound fine until you need them. “Unit checked.” “All good.” “No issues found.” Those phrases do nothing when the same system fails again.

I want specifics. If the tech measured 410 microfarads on a 40/5 capacitor that should have been replaced, write that down. If suction pressure was 118 psi on R-410A and head pressure was 315 psi at 92 F ambient, that tells me more than “pressures normal.” If the supply air was 18 degrees cooler than return, note it. If the condensate drain was flushed and a pan tablet was left, say so.

The checklist should also note the parts of the visit that get missed when the shop gets busy:

• Thermostat operation verified
• Blower compartment cleaned
• Electrical connections inspected and tightened
• Drain line cleared
• Outdoor coil rinsed
• Air filter checked or replaced
• Belt condition checked on belt-drive units
• Rust, oil stain, or vibration noted

That kind of record is useful for the next maintenance call, too. You do not want a tech walking into the same air handler blind because nobody wrote down that the blower wheel was packed last time.

Recurring service visits need a paper trail of their own

If you run maintenance agreements, the real value shows up over time. One visit is one visit. A record across the season tells the story.

Say a commercial tenant has a package unit that keeps chewing through capacitors every summer. If each maintenance stop has a photo, a capacitor reading, ambient temp, line voltage, and note about airflow, you can spot the pattern. Maybe the unit is running hot because the condenser coil is loading up faster than expected. Maybe the condenser fan is drawing too much. Maybe the disconnect is loose and the voltage is bouncing.

Without good visit records, that pattern gets buried in a truck box or a tech’s memory. With them, you can show the customer what changed and when it changed. That is the difference between a one-off complaint and a record of repeated trouble.

SodaDesk keeps those recurring visit records tied to the same equipment history. So when the same rooftop unit gets serviced again, the tech sees what was last found. No guessing. No “I think we changed that already.”

What to do when a customer challenges the work

This is the moment every owner knows. The customer calls and says the system was never serviced, or the problem was there before your tech showed up, or the unit is still in the same condition.

You do not want to start digging through text messages and half-finished notes.

You want the visit record.

Pull up the GPS check in. Show the time on site. Show the checklist. Show the photos. Show the tech name. If there was a second visit, show that too. If the tech found a clogged drain line and took a photo of the slime in the pan, that is your answer. If the capacitor was already weak and the reading was logged, that matters. If the customer signed off on the completed visit, even better.

This is not about picking a fight. It is about having the facts lined up. Most customers calm down when you can show them what was actually found on the roof or in the mechanical room. They may still be unhappy. Fine. But now you are talking about the same job.

Train the techs on what proof looks like

Good evidence does not happen by accident. Your techs need to know what to capture before they climb down the ladder.

I tell guys to think like this. If you had to explain this maintenance visit to another tech tomorrow, what would he need to know?

That means a clean before photo, a clear after photo, the readings that matter, and a note that says what was touched. If the tech swapped a filter, note the size and condition. If he found a bad capacitor but did not have the part on the truck, note the reading and the symptom. If he cleaned the coil, note whether it was a light rinse or a full degrease. If he checked the drain, note whether it flowed freely or needed a flush.

You do not need every visit to look like a textbook. You need it to be honest and useful. That is what keeps you from eating a callback that should have been easy to explain.

The owner’s real job is knowing what got done

This is the part a lot of us learn the hard way. You are not trying to turn every HVAC maintenance stop into a paperwork contest. You are trying to know the job got done right without driving to every site yourself.

That means time on site. It means the right tech was there. It means the unit was actually touched. It means there is a record of the readings, the pictures, and the checklist. If a rooftop unit gets serviced in July and the condenser coil photo, amp draw, and temp split are all in the file, you are not operating on hope. You have job evidence.

And when a customer asks what your crew did for the money, you can answer with specifics instead of a vague promise.