Undersized vs Failing: A Decision Tree

Why this matters

A system that underperforms has two very different root causes that look identical from the doorway: it was never big enough for the job (undersized by design), or it was big enough and a component is now degrading (failing). Tell these apart wrong and you waste real money. You replace a healthy compressor on an undersized system and the new one falls behind too. Or you keep upsizing a system that just needs a part. The whole job is separating "always was this way" from "used to be better."

Start here: the one question that splits the tree

Ask: did it ever perform adequately? This single fact does most of the work.

• If it never kept up since day one, you are almost certainly looking at undersizing or a design flaw. Components rarely ship dead, and a brand-new system that misses the target was misapplied, not broken.
• If it performed fine and then declined, you are looking at a developing fault. Something that worked got worse, and worse-over-time is the signature of failure, not size.
• If you cannot get a clear history, fall back on measurement (below). Numbers settle it when memory will not.

Branch 1: signs it was undersized

Undersizing has a consistent fingerprint.

• Steady, not worsening. The shortfall has been constant for as long as anyone remembers. A failing part gets worse month over month; an undersized system stays exactly as inadequate as it always was.
• Fails only at the extremes. It keeps up on mild days and falls behind only at peak load. That is classic undersizing: rated for typical conditions, short for design extremes.
• The math does not support it. A proper load calculation shows the demand exceeds the equipment's rated output. This is the decisive evidence. Capacity on the nameplate is simply less than the load the building or system actually imposes.
• Followed a load increase that was never matched. An addition, a remodel, more fixtures, more area, with the same old equipment. The system did not shrink; the load outgrew it.

Branch 2: signs it is failing

Degradation looks different.

• Worsening over time. Performance has been sliding. It used to recover, cool, clear, or heat faster than it does now. Trend matters more than any single reading.
• Measured output below nameplate. The system is producing less than its own rating says it should. Temperature split, recovery rate, flow, or amp draw comes in under spec. If a unit cannot make its rated output, it is failing, regardless of size.
• A specific component tests weak. A capacitor below its microfarad rating, low refrigerant charge, a fouled coil, a scaled exchanger, a slipping or restricted motor, a partially blocked line. There is a named, measurable defect.
• Accompanied by other failure signs. Noise, heat, odor, error codes, higher draw, intermittent operation. Undersizing is quiet; it just falls short. Failure usually brings symptoms along with it.

The deciding test: measure output against rating

When history is murky, restore proper flow and clean conditions, then measure what the system actually produces and compare it to its nameplate.

A system that hits its numbers and still cannot satisfy the load is undersized. A system that cannot hit its numbers is failing. That distinction, backed by a reading, ends the argument.

When it is both

It happens: a marginally sized system limps along until a component weakens, and the combined shortfall finally shows. Fix the failure first, restore the system to its full rated output, then re-judge against the load. Often the repair is enough. Sometimes it reveals that even healthy, the system was never sized for the job, and now you can say so with evidence rather than a hunch.

References

• See related: The System Can't Keep Up: A Decision Tree
• See related: The Oversized System Symptoms: A Decision Tree
• Trade-standard load calculation methods for matching capacity to actual load
• Manufacturer performance data for rated output and component specifications