Documentation
The service report is a safety document, a legal record, and the next tech's inheritance. What to write, how to write it, and why the boring admin task matters as much as the wrench work.
What you'll take away
- ▸ Understand why documentation is a safety and legal requirement, not just paperwork
- ▸ Write a service report that future techs can use
- ▸ Record readings, part numbers, and recommendations so the record stands alone
- ▸ Know what MUST be documented after any safety-relevant finding
A service report is four things at once: a record of what you did so the customer can see their money was spent on something, a reference for the next tech who visits this equipment, a safety document that demonstrates you communicated hazards clearly, and a legal record that can be subpoenaed if something goes wrong. For all four purposes, what matters is the same: specific, accurate, complete writing, produced the same day the work was done — not reconstructed from memory three weeks later when the callback arrives.
Most techs think of documentation as paperwork. That’s wrong. It’s part of the work itself, as much as the voltage drop test or the combustion analysis. A service report that omits critical findings is a liability; one that includes them protects everyone.
What a good service report contains
Service report contents
reference| Equipment identification | Make, model, serial, age if known | Future parts lookups depend on this |
| Customer complaint | In their words | What brought you out |
| Tests performed | Voltages, pressures, readings | With specific numbers |
| Findings | What was wrong, specifically | Not 'bad contactor' — 'contactor coil open, 0 Ω across coil terminals' |
| Parts replaced | Part numbers, not descriptions | For warranty, returns, future reference |
| Post-repair verification | Readings after the fix | Proof it's resolved |
| Recommendations | What should be addressed next | With reasoning |
| Safety findings | Explicit section if any | HX cracks, CO, gas leaks — always |
| Customer signature | Acknowledgment of work performed | Legal record |
Specific vs. vague writing
The difference between a report the next tech can work from and one they can’t is specificity.
Vague:
“Furnace not firing. Found bad part. Replaced. Now works.”
Specific:
“Customer call: Bryant 90% furnace (model 925SAN060A, s/n 4812A123) won’t light. Arrived to find 24V present at R-C (25.8 VAC), thermostat calling, inducer running, pressure switch closing at 0.68” WC (spec 0.65”). Ignition trial: HSI glowed, module commanded gas valve (24 VAC at MV terminals during trial), gas valve did not open. Meter on MV coil showed 85 Ω (in spec) but valve mechanically stuck. Replaced gas valve (White-Rodgers 36G22-253) with matching replacement. Leak-checked fittings with bubble solution. Verified manifold pressure 3.5” WC on firing (NG spec). System cycled normally through three cycles. Combustion analysis: CO 22 ppm, O2 7.8%, efficiency 82.4%. Recommended: standard annual maintenance, next scheduled fall 2026.”
The specific version lets the next tech who visits this furnace know exactly what was done and what the baseline readings were. If this furnace acts up in 18 months, the next tech can compare new readings against the old ones.
Safety findings get their own section
A service report that mentions a safety finding casually in the middle of other text is a legal document waiting to hurt you. Safety findings — cracked heat exchanger, elevated CO, gas leak, flame rollout, water leak into electrical, missing cover panels, improper venting — get their own explicit section, in plain language the customer can understand:
This section, on its own, accomplishes: the tech documented what they found, documented that the customer was informed, created a legal record that can’t be misconstrued, and protected the shop from liability. If the customer ignores the recommendation and turns the system back on, the documented warning protects the shop. If a fire or CO incident occurs, the documented warning limits the shop’s exposure. If the customer calls in six months saying “you didn’t tell me,” the document exists.
Readings become baselines
The most underused feature of service documentation is creating a baseline of readings. Every service call should capture:
- Voltage at the transformer secondary (no-call, with-call)
- Current draw on major motors (blower, inducer, compressor, condenser fan)
- Gas pressures during firing (inlet and manifold)
- Combustion numbers (CO, CO2/O2, efficiency, stack temp)
- Static pressure across coils and filter (if measured)
- Approach temperature / delta-T
- Refrigerant pressures (if EPA-certified)
These readings take 5–10 minutes at the end of a service call. A year later, when a complaint comes in, having last year’s numbers lets you see what’s changed. Blower amp draw crept up 0.8 A — bearings are going. Manifold pressure is 0.3” WC lower — regulator drift or gas supply change. CO jumped from 18 ppm to 88 ppm — combustion problem developing.
Without baselines, you’re guessing. With baselines, you’re tracking.
Parts: numbers, not descriptions
“Replaced gas valve” is useless documentation. “Replaced gas valve, White-Rodgers 36G22-253, under mfr warranty” is useful. The part number lets the next tech look up the part quickly, order an identical replacement, or investigate compatibility with the equipment model.
A running list of parts used is also useful for your own records — if you’re seeing the same part fail repeatedly across a fleet of equipment, that’s a pattern worth flagging to the shop or the manufacturer.
Documentation habits
Documentation practices that work
reference| Document during the call | Not at the end of the day | Memory decays fast |
| Photograph complex panels | Before and after wiring work | Your phone is a tool |
| Photograph nameplates | Before you close the panel | Saves callbacks for serial numbers |
| Save combustion test printouts | Upload or photograph | The analyzer's record is authoritative |
| Customer signature | Get one for every call | Especially safety findings |
| Use your shop's template | Consistency aids legal review | Don't freelance formats |
| Copy to customer email | Reduces 'you never told me' | Paper trail |
The habit that pays off
Good documentation is an investment. The first six months of careful reporting feel slow and overly formal. Then a year later, you get a call back to equipment you serviced, you pull up your own notes, and you immediately know what you did and why and how the system was behaving. That’s when the investment starts paying.
Three years later, documentation becomes one of the things that separates experienced techs from new ones — the experienced tech walks into a call knowing exactly what was done last visit, and the customer experiences continuity and competence. The new tech who’s starting fresh on every visit is walking the same diagnostic tree every time, for the same equipment, for no reason.
Check your understanding
0 / 301After a service call, you find a cracked heat exchanger and have shut the system down. What's the correct documentation approach?
02Why include specific readings (voltages, amp draws, combustion numbers) in a service report when the problem is already fixed?
03Which of these documents a replaced part most usefully?