Baseline vs Faulty: The Comparison Diagnosis Method
Why this matters
Half of all diagnostic dead-ends come from guessing whether a reading is "normal." A number means nothing on its own. The fastest way to find a fault is to compare what you have against what it should be, side by side. Get good at the comparison method and you stop chasing parts and start finding faults.
What a baseline is
A baseline is the known-good value, state, or behavior you measure the suspect against. It tells you what "right" looks like so a wrong reading jumps out. Baselines come from four places, ranked by how much you should trust them:
- The nameplate or spec sheet. The manufacturer's stamped rating: voltage, amp draw, pressure, microfarad, flow, RPM. This is the gold standard because it is the design intent.
- A matching known-good unit. A second identical component, or the same component on a system you know works. Two pumps on one job, two circuits off one panel, two doors of the same model.
- Your own recorded readings. Numbers you wrote down when the system was healthy (a commissioning sheet, a prior service ticket).
- Experience and trade norms. What you have seen a hundred times. Useful, but the weakest baseline because memory drifts.
Always reach for the strongest baseline available. If the nameplate is legible, use it before you trust a hazy memory.
The method, step by step
- Define what you are testing. One component, one circuit, one measurable thing at a time.
- Establish the baseline first. Read the spec, or measure the known-good twin, before you touch the suspect. Write it down.
- Measure the suspect the same way. Same probe points, same conditions, same units. An apples-to-oranges comparison is worthless.
- Compare and quantify the gap. Not just "high" or "low" - how far off, and in which direction.
- Decide if the gap is meaningful. A reading inside normal tolerance is not your fault. A reading well outside it is a strong suspect.
Same conditions, or the comparison lies
The single most common comparison error is measuring under different conditions. A motor's amp draw is different cold than hot, light-loaded than fully loaded. A pressure reading is different at startup than at steady state. If your baseline came from one condition and your suspect reading from another, the gap you see may be the condition, not a fault.
Control for the variables you can: same temperature, same load, same point in the cycle, same input supply. When you cannot match conditions exactly, note the difference and weigh it before you condemn the part.
Reading the gap
A meaningful difference between baseline and suspect points you toward a fault, but the direction matters:
- Suspect reads far too low. Often a weak, worn, or partially failed component, a restriction, or a supply that is itself low. Check the supply feeding it before you blame the component.
- Suspect reads far too high. Often a short, a binding mechanical load, a blockage downstream, or a sensor lying about the real condition.
- Suspect reads near zero or open. Often a complete failure, a broken connection, or a blown protective device upstream.
- Suspect reads exactly the baseline. The component is fine. Move on - do not replace good parts because you ran out of other ideas.
Where the method shines and where it stalls
Comparison is strongest on a system with a built-in twin: paired devices, repeated circuits, identical fixtures. It is weakest on a one-off with no spec and no twin, where you fall back to trade-norm baselines and must reason harder.
When you have no baseline at all, build one. Measure a similar healthy system on your next visit and record it. A shop that keeps commissioning readings on file turns every future callback into a fast comparison instead of a fresh investigation.
References
- Manufacturer nameplate and specification data (the primary baseline source)
- Trade-standard commissioning and acceptance-test practice
- See related: Testing a Component In vs Out of Circuit
- See related: Two Symptoms, Which Is the Cause