Chase a Comfort Complaint Further or Explain the Limits: Decision Tree
Why this matters
Every no-fault comfort call reaches a fork: keep spending time hunting for a cause, or stop and explain that the system is at its honest limit. Guess wrong in one direction and you eat hours chasing a fault that was never there. Guess wrong in the other and you drive off from a real, intermittent fault you gave up on too early. This tree is about spending your diagnostic effort where it will actually pay.
Start here: rule out the free wins first
Before you decide whether to chase, make sure you are not about to quit on something cheap or something dangerous.
- If the complaint could be a hazard (a smell near combustion, a tingle, warmth at electrical, symptoms that ease when they leave): that is not a comfort limit. Make it safe (ventilate and shut down, or de-energize and verify dead) and diagnose the hazard regardless of cost.
- If a within-spec adjustment or a quick education might resolve it: do that first. It is faster than either chasing or explaining.
The two signals that say "chase further"
Keep digging when the evidence says a real fault is hiding:
- There is a pattern in time or load. Intermittent, weather-linked, or peak-demand complaints usually have a physical cause you have not caught yet. A pattern is worth the return trip.
- The complaint changed. "It never used to do this" means something shifted. A system that degraded from acceptable to not has a cause worth finding.
The two signals that say "explain the limits"
Stop chasing when the evidence says the system is simply at its ceiling:
- Every reading is in spec at every point and time you have checked, and the complaint has no correlate. There is nothing left to measure.
- The gap is a known design limit for this equipment and this space (a run too long, a stage too coarse, capacity sized to the floor of the load). More diagnosis will not change physics.
Chase vs explain
| Factor | Lean toward chasing | Lean toward explaining |
|---|---|---|
| Pattern in time or load | Present | Absent |
| Complaint history | Recently changed | Always been this way |
| Readings | Deviate somewhere or sometime | In spec everywhere, every time |
| Likely cause | A findable fault | A design or physics limit |
| Cost of being wrong | A missed intermittent fault | Hours spent proving a negative |
Make the call out loud
Whichever way you go, say it to the customer as a decision, not a shrug.
- If you chase: tell them what pattern you are chasing and what a return visit under the trigger conditions will take in time, so it is their informed choice.
- If you explain: walk them through what you checked, that it is in spec, and what the real options are (live with it, change habits, upgrade the design). Put it in writing so the next visit starts from your conclusion, not from zero.
Recap
- Handle any hazard first, cost aside.
- Try the cheap within-spec fix or education before deciding.
- Chase when there is a pattern or a change.
- Explain when readings hold everywhere and the gap is a known limit.
- Whichever you pick, make it an explicit, documented decision with the customer.
References
- Trade-standard practice on diagnostic scope and performance verification
- Manufacturer documentation on design limits and rated capacity
- See related: Everything Tests Fine but the Customer Isn't Satisfied (decision tree); Setting Honest Expectations When the System Is Working as Designed