The Customer Says It Just Happens Randomly: Decision Tree

Why this matters

"Random" is the word a customer reaches for when a fault has a pattern they have not spotted yet. Take it at face value and you leave with "no fault found," run the meter for nothing, and get the same call back in two weeks. Truly random hardware failures exist, but they are the rare case. Most "random" faults fire on a condition the customer lives with every day and stopped noticing. Your job is to find the trigger they cannot see.

Start here: random means pattern-not-yet-found

Reset your own head first. A fault that "just happens" almost always happens under a condition, and that condition is hiding in a short list of buckets. Walk the buckets from most common to least and you convert "random" into "fails when X."

Before you probe anything, get the fault's fingerprint: what exactly fails (trips, shuts off, leaks, no-heat, no-cool), how long it lasts, and whether it clears on its own or needs a reset. Those three facts steer every branch below.

Branch 1: Is it tied to the clock or a routine?

The most common hidden trigger is time and habit.

• If it clusters at a time of day (early morning, evening, right after everyone gets home), suspect a load or routine that runs then. Electrical faults love the morning coffee-and-hairdryer surge; HVAC short-cycling shows up on the temperature swing at dawn or dusk.
• If it tracks an appliance or a person, something concurrent is the cause: the well pump kicks on, the dryer runs, someone showers, the pool pump starts its timed cycle.

Ask what is running or who is home when it fails. If they cannot say, that is your log-sheet assignment (see the companion Reference on turning random into a pattern).

Branch 2: Is it tied to weather or temperature?

• If it fails on hot afternoons or cold snaps, think thermal: a marginal capacitor that only fails hot, a control board with a cracked joint that opens as it expands, a condensate line that only overflows in humid weather, a pipe that only knocks when the water heater cycles.
• If it fails after rain or in high humidity, suspect water intrusion, a corroded connection that conducts when damp, a GFCI that only trips wet, or a pool bonding fault that surfaces after a storm.

Temperature and moisture are the classic "random," because the customer does not connect Tuesday's failure to Tuesday's weather.

Branch 3: Is it tied to a concurrent load?

Many faults only appear when demand stacks up.

• Electrical: a breaker that only trips when two big draws run together points to an overloaded circuit or a loose neutral, not a bad breaker.
• Plumbing: low pressure or no hot water "sometimes" often means simultaneous demand exceeding supply, or a mixing valve failing under load.
• HVAC or pool: equipment that faults only when another motor starts is a voltage-sag or shared-circuit problem.

Have them reproduce it by running the suspected loads together while you watch.

Branch 4: Is it cycle or startup related?

• If it fails on startup but runs fine once going, suspect a hard-starting motor, a weak capacitor, or a control that drops out on inrush.
• If it fails after running a while, think heat soak, a thermal cutout doing its job, or an airflow or flow restriction that only bites at temperature.

Branch 5: Only now is it truly intermittent

If none of the buckets land and the fault will not reproduce, you are in genuine intermittent territory: a hairline crack, a marginal connector, an aging part that fails on a threshold nothing external controls. This is the last branch, not the first. Here you leave instrumentation behind (a logging meter, a leak alarm, a camera) rather than guess-and-swap, because swapping parts on a hunch is how a small job turns into a string of failed callbacks.

Recap

1. Treat "random" as pattern-not-found; get the fault fingerprint first.
2. Walk clock and routine, then weather and temperature, then concurrent load, then cycle and startup.
3. Only call it truly intermittent after the buckets come up empty.
4. When you cannot reproduce it, log it or instrument it. Do not swap parts on a hunch.

References

• Trade-standard practice for intermittent-fault diagnosis
• OSHA and NFPA guidance on electrical load and connection integrity
• See related: Turning Random Into a Pattern With the Right Questions; The Trigger Is Something the Customer Changed Recently (decision tree)