How to Document a Diagnosis So the Next Tech Can Follow It

Why this matters

A diagnosis is reasoning, not a part number. When it is not on the record, the next tech who opens the ticket (or you, three weeks later) starts from zero, re-running every test you already paid for, in front of a customer who watches the shop rediscover its own work. This is the procedure for writing a diagnosis down so the logic carries forward and nobody redoes it. It is not the whole-job handoff; it is the reasoning trail behind the call you made.

Write for a tech who was not there

The reader knows nothing about this job. Assume that on every line. Everything obvious to you standing in front of the unit is invisible to someone reading a note in the truck a week later.

Capture readings with their context

A number alone is useless. "38 on the gauge" tells the next tech nothing. "38 suction at the service port, both stages running, hot day, twenty minutes in" is evidence. For every reading, record four things: what, where, under what condition, and when. A reading without its condition is a reading nobody can reuse.

Record what you ruled out and why

The ruled-out list is the most valuable and most-skipped part of a diagnostic note. For each suspect you cleared, name the evidence that cleared it: "capacitor within spec on the meter," "supply confirmed at the terminals under load," "filter new and clean." A suspect marked cleared with no evidence attached gets re-tested by the next tech on the clock.

State the working hypothesis and what would prove it

Write where you landed and how sure you are. "Suspect the reversing valve sticking when hot. Not confirmed, it would not fail on demand today. Confirm by reading it hot or forcing the condition." A hypothesis paired with its confirmation test hands the next visit a plan instead of a shrug.

Flag the dead ends

Name the things you tried that went nowhere. If you spent an hour on the control side and cleared it, say so, plainly, so nobody spends that same hour chasing the same ghost. A dead end documented is time you buy back for the shop.

Attach the evidence, not just the words

Photograph the readings, the nameplate, the wiring as you found it, the fault indicator lit. A photo of the meter on the terminals settles what a sentence cannot, and it protects your call if the diagnosis is ever questioned.

Lead with a one-glance summary

Put three lines at the top: the symptom as you confirmed it, where the diagnosis stands, and the single next action. A returning tech reads those three before they walk in and drops into the detail below only when they need it. The summary is what makes the record usable under a customer's eyes, not just complete.

References

• Trade-standard practice for diagnostic record-keeping and multi-visit continuity
• Manufacturer service documentation for recording readings against rated conditions
• See related: How to Hand Off an Unfinished Job to the Next Tech; How to Close Out a Work Order in the Field