When to Put Your Diagnosis in Writing and Stand Behind It

Why this matters

Most diagnoses live and die as a sentence spoken in a driveway. That is fine for routine work. Some calls, though, put your judgment on the line: a replace-don't-repair call on a costly unit, a red-tag, a fault another company or an insurance inspector will second-guess, or a comeback on your own shop's prior visit. On those, a verbal call evaporates the moment it is challenged. A written diagnosis, dated and specific, is the difference between "the tech said something about the compressor" and a finding you can defend a year later.

A finding is not a recommendation

A written diagnosis has two halves, and blurring them is what gets techs in trouble.

• The finding is what you observed and measured: "compressor drew locked-rotor amps on all three start attempts, no start." It is fact. You stand behind it fully.
• The recommendation is what you would do about it: "replace the compressor," or "replace the unit." It is judgment, and reasonable pros can differ.

Keep them in separate sentences. When someone challenges you later, you want to defend the finding like bedrock and discuss the recommendation like the professional opinion it is. A tech who writes only "needs a new unit" has committed to the opinion and thrown away the fact that supports it.

When a diagnosis earns a written record

Not every call. Reach for writing when any of these is true:

• The fix is expensive or destructive. A recommendation to replace rather than repair, or to open a wall or slab, needs the finding that justifies it on paper.
• A hazard is involved. Anything you red-tag, shut off, or refuse to leave running.
• Another party will grade your call. An insurance or warranty inspector, a home inspector, a second company. A three-way disagreement is far easier to hold your ground in when your finding was written before theirs.
• It is a comeback on your own prior visit. Your credibility is already spent once; the second diagnosis has to be airtight and on the record.
• You are referring out of your trade. When you diagnose up to the edge of your competence and hand off, write what you found and where your line is, so the next trade starts from your evidence, not a rumor.

How to write one that holds up

Aim for a paragraph a stranger could act on without you in the room:

1. Date, unit, and conditions. What you looked at, when, and the operating state (cold start, after an hour of run time, ambient conditions). Many faults only make sense with the conditions attached.
2. The observations and the numbers. Actual readings against the expected value, not "voltage was off." A pressure, a temperature split, a microfarad reading, a resistance.
3. The method. How you tested, so it can be repeated. "Isolated the circuit and read the winding" beats "checked the motor."
4. The finding, then the recommendation, in that order and clearly separated.

Hedge what you did not test, in the same breath

State the limits inside the diagnosis, not as a mental footnote. If you could not reach the far side of a coil, say it was inspected only where reachable. If a reading was taken once because the fault is intermittent, say so. A diagnosis that claims more certainty than you have is the one that burns you when a hidden second fault surfaces. "No fault found on the tested circuits; the intermittent trip was not present during the visit" is a strong, honest finding. "Unit is fine" is a trap.

Standing behind it when it is challenged

Write it as if the reader is skeptical, because sometimes they are.

• With the customer: the written finding turns "you're just trying to sell me" into "here is the reading, here is what it means."
• With an outside inspector: your dated observations and method are the currency. You are not arguing opinion against opinion; you are showing measurements. If the inspector's conclusion differs, the disagreement is now about interpreting shared facts, which is a professional conversation, not a shouting match.
• With your own comeback: resist the urge to soften the first miss. Document what is true now. Owning the corrected finding plainly rebuilds more trust than a defensive one.

The rule to bank: put the finding in writing whenever being wrong, or being doubted, would cost you real money or your name. Speak the routine ones; write the ones you would have to defend.

References

• Trade-standard practice for diagnostic documentation and reporting
• OSHA and NFPA guidance for tagging and documenting unsafe equipment
• See related: Reading Rust and Corrosion Patterns; The Jargon You Should Never Put in Writing
• See related: Second Opinion Requested - Validate vs Redo vs Defer