Diagnosing Your Own Install Years Later

Why this matters

Going back to a system your own shop put in years ago feels like a home advantage, and it can be. You know the design intent, the layout, and why you made the calls you made. But that same familiarity is a trap. The system has aged, the building has changed, and other hands have almost certainly touched it since you left. The tech who diagnoses the install he remembers, instead of the install in front of him, walks into an avoidable callback and a bruised reputation on his own workmanship.

Two things changed: the system and your memory

When you last saw this job it was new, clean, and exactly the way you configured it. Two clocks have run since.

• The system aged and drifted. Parts wear, settings creep, seals dry out, connections loosen with thermal cycling. A perfect install still degrades on a normal curve.
• Your memory froze. What you carry in your head is a snapshot from commissioning day. It is accurate about that day and silent about everything after it. Treat it as a starting reference, not a current fact.

The failure mode is assuming the second clock never ran: "I put a good breaker there, so the breaker is fine," or "I sized that pump right, so flow is fine." Both may be true. Verify anyway.

Re-baseline before you diagnose

Walk the whole system as if you had never seen it, then overlay what you remember. You are looking for the gap between the two.

• Confirm the core numbers still read where you set them: pressure, voltage, temperature split, flow, refrigerant charge, chemical balance, whatever the trade demands.
• Note anything physically different from your original scope: added loads, a swapped component, new tie-ins, a relocated unit, a bypassed control.
• Check whether the operating conditions changed around the equipment: a finished basement over a once-open crawl, a new addition on the same panel, a bigger pool heater on the old plumbing.

Only after you know the current state do you compare it to the state you remember. The difference is your first suspect.

Fight the ownership bias two ways

Your name is on this job, and that cuts in two directions you have to manage.

• Do not defend your past work into a blind spot. The instinct to prove your original install was fine can steer you away from a real fault you created. Diagnose the fault honestly first, assign it second.
• Do not over-own a fault someone else introduced. The opposite instinct, taking the blame because it "used to be mine," costs you money and teaches the customer the wrong lesson. If a later change caused this, that is the finding.

The professional posture is neutral: the system is the system, regardless of whose hands built which part of it.

When later hands have clearly been in it

Most old installs show evidence that someone worked on them after you. Mismatched fittings, a wire nut where you used a lug, a different brand of part, fresh cuts in old material. That evidence is diagnostic gold, not an insult. See related: Separating Your Original Work From Later Changes, and Reading What Changed Since You Left the Job.

If the modification is unsafe (a defeated safety device, an undersized conductor, a missing bond, a bypassed pressure relief), lead with the safety action: make it safe or shut it down before you continue diagnosing, then document what you found.

Say what you find plainly

Because it is your old work, the customer may wonder whether you are covering for yourself or drumming up work. Earn the trust by showing your reasoning: what you measured, what changed since the install, and what the evidence points to. Being able to say "my original install is doing its job; this failure started when this was added" is only credible if you were equally willing to say the reverse. See related: The Credibility of Diagnosing Your Own Past Install.

The judgment to bank: your history with a job is a reference point, never a substitute for measuring the system as it stands today.

References

• Trade-standard practice for system commissioning and re-verification
• Manufacturer documentation on service intervals and acceptable operating ranges
• See related: Reading What Changed Since You Left the Job; The Credibility of Diagnosing Your Own Past Install; Using Your Own Install Notes to Diagnose Faster