A rising summer bill is the weakest evidence a homeowner can bring to an equipment decision. It climbs when utility rates climb, when July runs hot, when a household adds a person, and none of that says anything about the condenser sitting in the side yard. Recorded compressor runtime is different, and when runtime rises while the weather holds roughly steady, the sensible next move is a hvac repair louisville ky diagnostic rather than a replacement quote. The argument here is narrow. Measured runtime, normalized against weather data, is the one piece of household evidence that separates a system quietly losing capacity from a system that is simply working through a hotter season.
Bills Move For Reasons Beyond Your Equipment
Judging a cooling system by its utility bill is like judging a restaurant kitchen by its monthly grocery invoice. The invoice swells in a busy month and shrinks in a slow one, and neither movement tells the owner whether the line cooks are wasting food. Cost per plate served answers that question, because it divides the spending by the work actually done. Runtime per unit of cooling load is the household version of cost per plate, and almost nobody looks at it, since the bill arrives on its own while the runtime has to be pulled.
Runtime Hours Isolate The Real Variable
Most connected thermostats already keep this record. They log how many hours the compressor ran each day, and the file exports by month or by whole season, which is why a homeowner searching hvac repair louisville ky with two seasons of logs in hand asks sharper questions than one holding a stack of bills. Weather data supplies the other half of the calculation, since cooling degree days count how much heat the outdoor air actually pushed at the house. Divide hours by degree days and the weather is accounted for. What usually turns up is not a dead system but a slow one, still cooling, just taking longer to get there. The log keeps score even when nobody is looking.
Two Cooling Seasons Compared Degree Day By Degree Day
Take a 2,400-square-foot house in Prospect, tracked across two cooling seasons by an owner who exported the thermostat log every October. Season one recorded 612 compressor hours against 1,050 cooling degree days. Season two ran warmer at 1,120 degree days, and the compressor logged 793 hours. The electric bill for that second summer landed about nine percent higher, which is the sort of number most households shrug at and forget by November.
The bill rose nine percent. Runtime per degree day rose twenty-one.
The Worked Example On Lost Capacity
Before the arithmetic, it helps to know where the replacement side of this decision actually sits. Manufacturer literature is blunt about it. As of May 2026, Bryant’s furnace replacement guidance put a typical gas furnace at 15 to 20 years of service and treated a unit past 15 with a repair bill over $1,000 as replacement territory. That is a heating benchmark rather than a cooling one, and it matters here because the furnace and the air handler usually share a cabinet, an install date and a service history.
Run the Prospect numbers. Season one gives 612 hours over 1,050 degree days, or 0.583 hours of compressor time per degree day. Apply that same rate to season two’s 1,120 degree days and a healthy system should have logged roughly 653 hours. It logged 793, so 140 hours of runtime carry no weather explanation. At a measured draw of 3.4 kilowatts, those 140 hours burn 476 kilowatt-hours, and at $0.128 per kilowatt-hour the excess comes to $60.93 across the season. Call it sixty-one dollars of electricity buying nothing at all.
Sixty-one dollars is not really the argument. The argument is what twenty-one percent more runtime per degree day implies about capacity, because a compressor working an extra fifth of the time to hold the same setpoint has lost something measurable, and the usual causes are a low refrigerant charge, a fouled condenser coil, a weakening capacitor, or duct leakage that opened up after attic work. Against an illustrative replacement quote in the eight-thousand-dollar range, paying well under a hundred dollars to learn which one it is stays the cheaper move by a wide margin.
Where Data Stops And A Technician Starts
A log proves that something changed. It cannot say what changed. The next measurements need gauges on the refrigerant circuit, a manometer reading duct static pressure, and a clamp meter on the compressor windings, and refrigerant handling is federally certified work, not a homeowner task. A technician who reads the runtime data instead of waving it off turns a vague service call into a specific one, which is usually the difference between a same-day fix and a return visit.
Measure First Then Spend Once
Two numbers, pulled twice a year, change the whole conversation with a contractor. Export the thermostat runtime at the end of each cooling season, pull the degree days for the same window from the local weather record, and keep the ratio somewhere you will find it again. When that ratio drifts upward by a fifth while the house itself sits unchanged, that is the moment to buy a diagnostic, not the moment to sign for new equipment. Age eventually settles the replacement question on its own, and capacity loss inside a system’s service life is usually a repair that the log already pointed at.