Starting a Diagnosis Fresh Instead of Trusting Someone Else's Notes

Why this matters

Prior notes on a unit are useful and dangerous in exactly the same way: they can point you straight at a real cause, or they can anchor you on someone else's mistake so firmly that you stop looking anywhere else. A tech who reads "checked capacitor, tested good" and moves on without re-verifying it is trusting a stranger's measurement, taken under conditions you did not witness, with equipment you did not see calibrated. The skill is using history as a lead, never as a substitute for your own check.

Notes are a hypothesis generator, not a verdict

Treat every prior note as a starting point for your own test, not as a finding you inherit. A note that says a component "tested good" tells you what someone believed at the time, not necessarily what is true now or what was true then. Between then and now, that same component could have degraded, the reading could have been taken incorrectly, or the note could describe a test that does not actually rule out the failure mode you are now seeing.

This is not about assuming the prior tech was careless. It is about the basic limit of secondhand information: you cannot verify a measurement you did not take, on equipment you did not personally confirm was accurate, under conditions you did not personally observe.

When notes help the most

Good notes earn their keep on timing and pattern, not on individual test results. Use them for:

• What has already been replaced, so you do not waste time suspecting a part that is provably new.
• The sequence and timing of prior symptoms, which tells you whether this is a new fault or the same one recurring.
• Anything nonstandard about the install or a modification someone else already found, which you can verify quickly rather than discover from scratch.
• What the customer was told previously, so your explanation is consistent or you can clearly explain why your finding differs.

Notice that none of these require you to trust anyone's diagnostic conclusion. They are facts about history, not verdicts about cause.

Where notes actively mislead you

• A confident conclusion with no supporting numbers. "Checked and it's fine" gives you nothing to verify against and nothing to disprove; treat it as untested until you test it yourself.
• A conclusion that matches the most obvious, common cause. If the note reads like the first thing anyone would guess, be more skeptical, not less, especially if the symptom returned after this diagnosis was supposedly confirmed.
• Notes copied forward from visit to visit with minor edits. Occasionally a tech under time pressure writes a note that mostly repeats the last one. This looks like corroboration across multiple visits, but it may just be one uncritical conclusion propagating.

The re-verification habit

Re-test anything the notes claim was already ruled out, if that item is still plausibly connected to the current symptom, before you accept it as eliminated. This does not mean re-testing everything on every job; it means not skipping the test on an item just because a note says it was already checked. The time cost of re-verifying a genuinely fine component is small. The time cost of building an entire diagnosis on top of a single wrong prior reading is much larger, and it is exactly how a fault survives three visits in a row.

The mental model to keep

History tells you what happened and when. It does not tell you why, unless you personally confirm the why with your own measurement. Read the notes for the timeline. Build the diagnosis from your own readings.

References

• Trade-standard root-cause analysis practice, primary versus secondary evidence in diagnosis
• ISO 14224, equipment failure event data recording and verification principles
• See related: The Prior Tech's Notes Are Detailed But Maybe Wrong Decision Tree; Documenting Your Own Work So the Next Tech Doesn't Face the Same Problem