The Damage Is Older Than the Customer Claims: Decision Tree

Why this matters

The customer says it started last week. The wear says it has been going for a year. That gap is not a small thing to smooth over - it decides whether a warranty applies, whether a "pre-existing condition" clause kills a claim, and whether the damage was there before you ever touched the equipment. Getting this right protects the customer's honest claim and protects you from owning damage that predates your visit. This tree keeps you factual, not accusatory.

Start here: make it safe, then verify your own read

If the failed equipment is still a hazard, handle that first: de-energize and verify dead, relieve pressure, isolate water from live parts, let hot components cool. Then inspect.

Before you tell anyone the damage is old, prove it to yourself. The whole branch below collapses if your dating is wrong, so pressure-test it:

• Do you have at least two independent clues that agree (wear depth plus corrosion in the fracture, scale thickness plus an undisturbed dust bridge)?
• Could a harsh environment have aged it fast and fooled you? Very hard water, salt air, or constant heat lay down in weeks what a clean setting takes years to show.
• Are you dating the fault, or just the part? An old part can suffer a brand-new fault. See the next branch.

If your read does not survive this, you do not yet have "older than claimed." Keep gathering before you say it.

Branch 1: Is it old damage, or a recent fault on an old part

This is the most common trap, and it changes everything.

• Old damage: the fault itself is aged - corrosion inside the crack, a wear groove worn smooth, scale over the failed area. This genuinely predates the customer's story.
• Recent fault on an old part: the component is old, but the failure is fresh - a bright break, clean contamination, no corrosion in the fracture. The part's age is not the fault's age. An old capacitor that just let go, an old pipe that pinholed yesterday.

Do not let a gray-haired part trick you into calling a new failure old. Date the failure surface, not the component.

Branch 2: Why does the timeline matter here

The reason for the gap tells you how to handle it.

• If a warranty or claim hinges on it: the date is now evidence. Document it to a defensible standard and be precise about what you can prove. See related: The Timeline Matters for a Warranty or Insurance Claim (decision tree).
• If it is about your liability ("was this like this before you got here"): document that it predates your visit, ideally before you do any work. A photo of pre-existing damage taken on arrival is worth more than any argument later. See related: The Pre-Existing Damage You Need to Flag.
• If it is neither - just a customer who did not notice - there may be nothing to litigate. Note it and move on to the fix.

Branch 3: Is the gap innocent, or is something being hidden

Most gaps are innocent. Assume that first.

• Honest not-noticing (most cases): a slow fault runs silent until it crosses a threshold the customer finally feels or sees. They are dating when they noticed, not when it started. No conflict of intent, just a difference between onset and awareness.
• A misremembered or shifted story: people compress time and attach a failure to a recent memorable event. Benign. Correct the record gently if it matters to a claim.
• Concealment of misuse or a prior DIY attempt: occasionally the "it just started" is covering something - a bypassed safety, a self-repair that failed, a known-and-ignored leak. Read for it, but do not accuse. See related: The Evidence Contradicts the Customer's Story (decision tree).

Branch 4: Have the conversation without a fight

You do not need the customer to agree with your date. You need the record to be right.

1. Show the evidence, do not just assert it. Point to the corrosion in the crack or the scale depth.
2. Separate onset from awareness out loud: "This looks like it's been developing for a while - you probably only felt it recently when it got bad enough to notice."
3. State what you can defend and no more: a range, tied to your anchor.
4. Document it, especially if a claim or your liability rides on it.

Recap

• Make it safe, then verify your own dating with two agreeing clues.
• Separate old damage from a recent fault on an old part - date the failure, not the component.
• Match your handling to why the timeline matters: claim, liability, or nothing.
• Assume innocent not-noticing first; read for concealment without accusing.
• Show evidence, split onset from awareness, state a defensible range, document.

References

• Trade-standard failure-analysis and pre-existing-damage practice
• Manufacturer documentation on service life and warranty conditions
• See related: The Pre-Existing Damage You Need to Flag; The Evidence Contradicts the Customer's Story (decision tree); The Customer Who Misremembers the History (decision tree)