Documenting What You've Ruled Out

Why this matters

Diagnosis is as much about what you have eliminated as what you suspect. A tech who writes down only the suspected cause leaves the next person - often their future self - to re-test everything from scratch. On a tough intermittent fault that comes back next month, the notes that say "checked power good, filter clean, capacitor in spec, valve verified open" are worth more than gold. They turn a fresh diagnostic marathon into a short pickup right where you left off. Documenting what you ruled out is how a single visit's work compounds instead of evaporating.

A diagnosis is a shrinking list of suspects

Every test you run does one of two things: it confirms a cause or it eliminates one. Both are progress. But only the confirmations usually get written down, and the eliminations - which are most of your work - get lost. That is backwards. The eliminations are what define how far you got. A clear record of "these are ruled out, these remain" is a map of exactly where the next step should begin.

Write the negative results, not just the positive

For each meaningful test, record three things: what you tested, what you measured or observed, and what it means.

• "Supply voltage at unit: present and in range. Power ruled out."
• "Filter and coil: clean. Restriction ruled out."
• "Run capacitor: reads within nameplate tolerance. Capacitor ruled out."
• "Suspect: intermittent control output, fails only when warm. Not yet confirmed."

The "ruled out" tag on each line is the part that saves the next visit. Without it, all anyone sees is a reading and they have to re-derive the conclusion.

Record the conditions you tested under

An elimination is only valid under the conditions you tested. "Capacitor good" means good when you measured it, which may have been cold. If the fault is heat-related, that elimination has a caveat, and the caveat needs to be in the notes. Otherwise the next tech reads "capacitor good," skips it, and misses a part that only fails hot.

So note the state: cold start or warm, under load or idle, dry or wet, time of day if it matters. An elimination with its conditions is trustworthy. An elimination without them can mislead.

Separate confirmed, ruled-out, and unverified

Keep three buckets clear in the write-up:

• Confirmed faults: things you proved are bad.
• Ruled out: things you proved are good, with conditions.
• Unverified suspects: things you could not test, could not reproduce, or ran out of time on.

The unverified bucket is the to-do list for the next visit. Spelling it out ("could not reproduce the no-heat condition; recommend returning during a cold-start in the morning when the customer sees it") tells the next person exactly what to do instead of starting blind.

Good notes prevent the repeat-diagnosis callback

The expensive callback is not the one where you missed the fault. It is the one where the fault returns, a different tech shows up, and they spend the whole visit re-checking everything you already cleared because none of it was written down. Documentation breaks that cycle. The second visit picks up at the unverified suspects, not at square one. Across a season of intermittent calls, that difference is enormous.

Write for the tech who knows nothing about this call

Assume the reader has zero memory of the job, because often it is you, months later, and you will not remember. Plain language, specific readings, clear conclusions. Avoid shorthand only you understand. A note that says "looked at it, seems ok" helps no one. A note that says "verified power, restriction, and capacitor good cold; suspect heat-related control fault; could not reproduce on a warm unit" hands the next visit a running start.

Keep it in the record, not in your head

Whatever system the shop uses, the notes belong attached to the job, not in your memory or on a scrap that gets tossed. Memory fades and scraps disappear. The point of documenting eliminations is that the knowledge survives past this visit and reaches whoever needs it next.

References

• Trade-standard service documentation practice across the residential trades.
• Reliability and maintenance record-keeping principles applied to field diagnostics.
• See related: The One-Variable-at-a-Time Rule; Confirming the Complaint Before You Start; It Works Then Stops Then Works Decision Tree.