Eliminating the Easy Stuff First
Why this matters
A huge share of "broken equipment" calls are not broken equipment at all. They are a tripped switch, a closed valve, a clogged filter, a dead battery, a setting bumped by a customer, or power that never reached the unit. The tech who checks those first looks like a genius and is back in the truck in minutes. The tech who tears into the control side first wastes an hour, sometimes a part, and still has to come back to the simple thing they skipped. Checking the easy stuff first is not beginner behavior. It is what experienced people do because they have been burned by skipping it.
The easy stuff is the high-probability stuff
"Easy" does not mean unlikely. It means fast to check and common to fail. These two facts together make the cheap checks the highest-value moves you can make. A clogged filter is trivial to inspect and is one of the single most common reasons a system underperforms. Skipping it to chase something exotic is backwards on both probability and cost.
Order your checks by time to verify divided by likelihood. Whatever is fastest to rule out and most likely to be the cause goes first.
The universal easy-stuff checklist
Before you open a panel, run the basics. These cross every trade:
- Is it getting power? Breaker on, disconnect closed, plug seated, fuse intact, supply present at the unit. A surprising number of "dead" units are simply not energized.
- Is it turned on and set correctly? Switch, mode, setpoint, schedule, a control left in the wrong position by the customer or the last tech.
- Is the path open? Valves open, dampers not stuck, vents not blocked, drains clear, lines not kinked.
- Is it clogged or dirty? Filters, screens, strainers, traps, coils, intakes. Restriction mimics dozens of "real" faults.
- Is the battery or backup alive? Thermostats, sensors, controls, and remotes die quietly on dead cells.
- Did something obvious change? A recent storm, a power event, a remodel, a part someone else touched last week.
Restriction and missing power masquerade as everything
Two failure modes deserve special mention because they imitate so many others. A restriction (clogged filter, blocked drain, closed valve, fouled coil) makes a healthy system behave like it has a failed component: it short-cycles, overheats, loses capacity, or shuts down on a safety. Missing or low power does the same from the other direction: the unit chatters, fails to start, or behaves erratically.
If you chase the symptom without first clearing restriction and confirming clean power, you will diagnose a part that is innocent.
Why people skip the basics and why it costs them
The basics get skipped because they feel beneath a skilled tech, and because the exotic cause is more interesting. Both are traps. The customer does not pay for interesting. They pay for fixed. Skipping a five-minute check to spend an hour on a control board, then discovering it was a closed valve all along, is the most expensive kind of pride.
Make it a reflex, not a decision
The fix is to make the easy-stuff pass automatic, the first thing you do on every call before you have an opinion about the cause. When the basics are a reflex, you do not have to remember to do them under pressure. You will catch the dead battery and the closed valve every time, and you will only ever open the panel when the simple causes are genuinely ruled out.
When to skip ahead
There is one fair exception. If the symptom flatly rules out a basic cause (the unit is clearly running, so power is present), you can pass over that specific check. But rule it out with evidence, not assumption. "It must have power" is not the same as "I confirmed power at the terminals."
References
- Trade-standard service practice emphasizing basic checks before component-level diagnosis.
- Manufacturer service literature, which routinely lists power, settings, and restriction checks as first steps.
- See related: The Diagnostic Flowchart Mindset; Confirming the Complaint Before You Start; It Runs but Doesn't Do Its Job Decision Tree.