A Customer Blames a Storm for an Unrelated Fault: Decision Tree

Why this matters

A storm is a convenient explanation. It is dramatic, it is memorable, and for a lot of customers it is also the difference between paying out of pocket and filing an insurance claim. That means you will regularly be asked to confirm a storm caused a failure when the evidence says otherwise, and you need a way to handle that conversation honestly without either rubber-stamping a claim that will not hold up or flatly contradicting a customer who is genuinely trying to understand what happened.

Start here: is there an immediate safety concern

If the storm involved lightning, flooding, or wind damage near electrical or gas equipment, rule out an active hazard before you evaluate the storm-versus-coincidence question at all. Water intrusion near live electrical components, a compromised gas line, or storm-damaged wiring get a safety check first, root-cause conversation second.

Step 1: gather the facts before forming an opinion

Ask what happened and when, independent of the customer's theory:

• Exactly when did the fault start, relative to the storm (during it, right after, or "sometime that week")?
• What kind of storm event: lightning nearby, high wind, heavy rain, or a power flicker/outage?
• Did anything else in the building act up at the same time?

Step 2: check for a plausible physical link

Match the storm type to a mechanism that could actually cause the failure you are looking at:

• Lightning or a grid disturbance can plausibly cause electrical or electronic damage, especially to control boards and sensitive components. It does not plausibly cause a worn mechanical bearing to seize or a valve seat to erode; those are wear failures with their own separate timeline.
• Wind and flying debris can plausibly cause physical damage to exposed equipment (outdoor units, vents, exterior fixtures). It does not plausibly cause an indoor unwitnessed electrical failure with no physical damage present.
• Heavy rain and flooding can plausibly introduce moisture into equipment, causing corrosion or short circuits, but usually with a visible entry path and some sign of water. Blaming rain for a fault with no moisture evidence anywhere near the failure point is a weak link.

If the storm type does not plausibly connect to the failure you found, say so clearly and move to Step 4.

If the mechanism is plausible, continue to Step 3.

Step 3: check whether the failure signature actually matches storm damage

A genuine storm-caused failure usually looks different from ordinary wear-out:

• Storm damage often affects more than one device on the same circuit or exposure path; an isolated single-component failure with everything else fine is a weaker case.
• Storm damage from a surge often shows in protective devices tripping, or components with visible burn/heat damage, not a component that simply stopped working with no trace.
• Ordinary wear failure usually has some supporting evidence: age consistent with expected service life, gradual prior symptoms, or wear marks on the failed part itself.

If the failed part shows classic wear signs (corrosion buildup over time, mechanical wear, age well past typical service life) with no burn or surge signature, this is very likely coincidental timing, not storm damage, regardless of how close the storm was.

Step 4: have the conversation honestly

You do not need to win an argument, you need to give the customer accurate information they can use. A workable script: "I checked whether the storm connects to this, here's what I found: [state the evidence]. Based on that, I'd say this looks like [normal wear / a genuine storm-related failure], and here's why." Let the evidence carry the conclusion rather than your say-so alone.

Step 5: document for insurance purposes, either way

If a customer intends to file an insurance claim, your documentation matters regardless of which way it points. Write down what you observed, not just your conclusion: presence or absence of burn marks, moisture, physical damage, component age, and prior service history if you have it. An insurer's adjuster may make the final call, but a clear factual account protects you from being asked later why you signed off on a claim the evidence did not support, or why you talked a customer out of a legitimate one.

Recap

1. Rule out an active hazard first.
2. Gather timing and storm-type facts independent of the customer's theory.
3. Check whether the storm type plausibly connects to the failure at all.
4. Check whether the failure signature matches storm damage or ordinary wear.
5. Explain your finding with evidence, and document factually for any insurance claim.

References

• Insurance Information Institute, general guidance on storm-damage claim documentation
• See related: Distinguishing Coincidence from Causation in Fault Timing; The Fault Started Right After an Outage or Surge (decision tree)