Heating and Cooling Degree Days: What Operators Need to Know

Every operator knows that utility bills spike in summer and winter. But when someone asks "how much of that increase is weather vs. waste?" most operators shrug. That's where degree days come in.

Heating degree days (HDD) and cooling degree days (CDD) are the standard way to quantify how much weather drives energy consumption. They're not complicated, they're free, and once you understand them, you'll never look at utility data the same way again.

What Are Degree Days?

Degree days measure how far the outdoor temperature deviates from a comfortable baseline — typically 65 degrees F. The further outside that comfort zone, the harder HVAC systems work, and the more energy a building uses.

Heating Degree Days (HDD): When the average daily temperature is below 65 degrees F, the difference is one day's HDD. If the average temperature on January 15th is 30 degrees F, that day has 35 HDD (65 minus 30).

Cooling Degree Days (CDD): When the average daily temperature is above 65 degrees F, the difference is one day's CDD. If the average temperature on July 20th is 90 degrees F, that day has 25 CDD (90 minus 65).

A month's total is the sum of each day's values. A January in Salt Lake City might accumulate 1,100 HDD. A July in Phoenix might hit 800 CDD. A mild April? Close to zero on both counts.

Why Operators Should Care

Degree days aren't an academic exercise. They solve four real problems that operators deal with constantly.

1. Bill Estimation When Actual Reads Aren't Available

When a meter fails and you need to estimate a bill, degree days give you a defensible method that accounts for seasonal variation.

Here's the problem with simple averaging: if a meter fails in January and you estimate based on the last 12 months' average, you'll underestimate. January consumption is driven by heating load, which is far higher than the annual average.

The degree-day method: Look at the ratio between this month's degree days and the historical month's degree days, then scale consumption proportionally.

Example:

• Last January's consumption: 1,200 kWh
• Last January's HDD: 1,050
• This January's HDD: 1,180 (colder than last year)
• Estimated consumption: 1,200 x (1,180 / 1,050) = 1,349 kWh

That's a much fairer estimate than a flat average — and if a resident challenges it, you have a methodology backed by NOAA weather data, not a guess.

2. Weather-Normalizing Consumption Data

Suppose you retrofitted a property's HVAC system in June and want to know if it's actually saving energy. You compare this November's consumption to last November's consumption and see... a 5% increase. Does that mean the retrofit failed?

Not necessarily. If this November had 15% more HDD than last November — meaning it was significantly colder — a 5% consumption increase actually represents a 10% improvement in efficiency. Without weather normalization, you'd draw the wrong conclusion.

Weather-normalized consumption = Actual consumption x (Baseline period degree days / Current period degree days)

This is how utility analytics platforms separate weather effects from operational changes. It's the only honest way to evaluate energy projects, compare properties, or track efficiency over time.

3. Seasonal Budgeting

Property budgets that use flat monthly utility projections are wrong by definition. Utility costs are seasonal, and degree days are how you model that seasonality.

The approach:

1. Pull 3-5 years of monthly utility consumption and costs for each property
2. Pull the corresponding monthly degree days from NOAA for the nearest weather station
3. Calculate the cost-per-degree-day for heating months and cooling months separately
4. Apply those rates to long-term average degree days for each month to build a weather-adjusted budget

This gives you a budget that expects January to cost more than April. It also lets you set variance thresholds — if actual costs exceed the weather-adjusted budget by more than 10%, something changed operationally and warrants investigation.

4. Fair Property-to-Property Comparisons

If you manage properties in different climate zones, raw consumption numbers are meaningless for comparison. A property in Minneapolis will always use more heating energy than an identical property in Dallas. That doesn't make the Minneapolis property less efficient.

Energy Use Intensity (EUI) normalized by degree days lets you compare apples to apples. Two properties with the same kWh-per-HDD are performing equally, regardless of where they're located.

This is how portfolio operators identify their best and worst performers — not by total consumption, but by consumption relative to weather demand.

Where to Get Degree Day Data

The National Oceanic and Atmospheric Administration (NOAA) publishes daily HDD and CDD data for thousands of weather stations across the United States. It's free, it's authoritative, and it's updated daily.

How to access it:

• NOAA Climate Data Online: Search by weather station or ZIP code for historical daily, monthly, and annual degree day data
• Degree Days.net: A third-party tool that lets you pull degree day data for any location with custom base temperatures — useful if your buildings use a base other than 65 degrees F
• Your utility billing platform: Most modern platforms, including VITALITY, can pull degree day data automatically and apply it to consumption analysis and estimation workflows

Putting It Into Practice

You don't need a data science degree to start using degree days. Here's a practical starting point:

Once you see how tightly consumption correlates with degree days, you'll spot the anomalies faster — the building that's using more energy than weather explains, the month where costs spiked without a corresponding weather event, the property that's outperforming its climate peers.

Those anomalies are where the opportunities hide. Understanding rate schedules alongside degree day data gives you the full picture — not just how much energy you're using, but how much you're paying per unit of weather-driven demand.

For a broader look at how historical consumption data powers smarter utility decisions, check out our guide to historical spend analysis.

Turn weather data into billing intelligence

VITALITY integrates degree day data directly into estimation, analytics, and budgeting workflows — so weather-normalization happens automatically.

Talk to the Team

The Bottom Line

Degree days are one of the simplest, most powerful tools in a utility operator's toolkit. They cost nothing, they're available for every location in the country, and they turn vague seasonal patterns into precise, actionable data.

If you're estimating bills without degree days, you're guessing. If you're comparing year-over-year consumption without normalizing for weather, you're drawing false conclusions. And if you're budgeting utilities with flat monthly projections, you're setting yourself up for variance surprises every quarter.

The weather is going to do what it does. Your job is to account for it — and degree days are how.

Related Articles

Apr 5, 2026

What Is an Energy Management System? A Guide for Property Operators

An energy management system turns raw utility data into actionable insights. Here's what an EMS does, why it matters for property operators, and how it connects to utility billing.

Read more

Mar 13, 2026

Heating and Cooling Degree Days: What Operators Need to Know

Degree days are the missing link between weather and utility consumption. Here's how operators use HDD and CDD for bill estimation, weather-normalization, seasonal budgeting, and fairer comparisons across properties.

Read more

Apr 3, 2026

Your Utility Data Is Telling You Something — Are You Listening?

12-24 months of historical utility spend data reveals patterns most operators miss. Seasonal swings, rate changes, billing anomalies — it's all there if you know where to look.

Read more