A customer can have a full tank on Monday and be calling for an emergency delivery by Friday if the weather turns hard. That is why learning how to manage heating degree days is not an office exercise. It is one of the practical controls that protects delivery margins, keeps trucks moving efficiently, and helps customers avoid runouts.
For a fuel oil or propane dealer, degree days turn changing weather into a usable delivery signal. Used correctly, they help you estimate consumption, schedule automatic deliveries, and spot accounts that do not fit the pattern. Used carelessly, they can create bad forecasts, unnecessary stops, and costly last-minute calls.
Start With the Right Meaning of Heating Degree Days
A heating degree day measures how much colder the average outdoor temperature was than a chosen base temperature. In most heating fuel operations, 65 degrees Fahrenheit is the standard base. If the day’s average temperature is 45 degrees, that day produces 20 heating degree days.
The number itself does not tell you how many gallons a customer will use. It gives you a way to measure the weather-driven part of their demand. When you combine degree days with an account’s past usage, tank size, and delivery history, it becomes a scheduling tool.
The basic calculation is simple:
Heating degree days = base temperature – average daily temperature
If the average temperature is above the base, the result is zero. A 68-degree day does not produce negative heating degree days. It simply produces no heating demand by this measure.
The calculation is simple. Managing it across hundreds or thousands of accounts is where discipline matters.
Use Local Weather Data, Not a Regional Guess
The quality of your scheduling starts with the temperature data you load. A weather station 40 or 50 miles away may look close enough on a map, but terrain, elevation, wind exposure, and lake effects can make its readings a poor match for your service area.
Assign the best practical weather source to each delivery area. Dealers serving several counties may need more than one weather location. A colder hill town, a coastal route, and a protected inland town can burn at noticeably different rates during the same week.
Consistency matters as much as location. Do not switch weather sources midseason without a reason and without checking how the new data compares with the old source. Your account history and degree-day factors were built from prior weather readings. A change can make good customers suddenly look like bad estimates.
There is also a timing issue. Temperature data needs to be loaded regularly. If dispatchers are working from readings that are several days old during a cold snap, the schedule is already behind. Daily updates give automatic delivery schedules a current view of what is happening outside.
Build a Degree-Day Factor From Actual Deliveries
Every automatic account needs a realistic usage factor. Often called a K-factor, this figure estimates how many degree days occur per gallon used. A customer with a 5.0 factor, for example, uses roughly one gallon for every five heating degree days.
The formula is:
K-factor = degree days since delivery / gallons delivered
Suppose an account received 150 gallons after 750 degree days. Its K-factor is 5.0. If the account has 500 gallons of usable fuel capacity and you normally schedule a delivery at about 30 percent remaining, you can estimate when weather consumption will bring it to that level.
Do not treat one calculation as permanent truth. A factor based on a single delivery can be distorted by several things: a partial fill, an inaccurate tank size, a customer who was away, a new addition to the house, a wood stove, or a service issue. Better factors come from several clean delivery records over time.
Review the accounts that keep producing surprises. A customer who is always early or always late is giving you useful information. Check the delivery amount, prior tank level, tank capacity, address weather assignment, and degree-day history before deciding that the factor is wrong.
Set Delivery Rules That Leave Room for Reality
Degree-day scheduling works best when it is paired with sensible delivery thresholds. The goal is not to run every tank as low as possible. The goal is to deliver efficiently while preserving enough reserve for weather changes, route delays, and normal forecasting error.
A large, easy-to-access tank with steady usage can carry a smaller reserve than a small tank, a difficult driveway, or an account in an exposed location. Propane accounts need the same practical judgment, with added attention to vaporization, winter access, and the customer’s actual appliances.
A delivery window should account for more than projected gallons. Consider the days until the truck will realistically be back in that area. If a route is only served once a week, an account needs more protection than one located near the terminal or on a daily route.
This is where calendar-day scheduling can still have a place. Some accounts have predictable non-heating loads, unusual occupancy, or a pattern that is better managed by time than temperature. Call-in customers also belong outside the automatic model unless they specifically enroll. Do not force every account into degree-day scheduling just because the feature is available.
Watch the Exceptions Before They Become Runouts
A good degree-day system does not replace dispatch judgment. It gives dispatchers a shorter, smarter list of accounts to review.
Pay attention to accounts with a sudden change in delivery pattern. If a long-time customer starts using far more fuel than expected, there may be a new household member, a thermostat change, a leak, a failed delivery record, or an incorrect tank size in the account. If usage drops sharply, the customer may have added another heat source, moved out, or stopped using the property.
Weather can also break the normal pattern. Windy conditions, prolonged cloud cover, and sharp overnight temperature drops can increase demand in ways that a daily average does not fully capture. The answer is not to abandon degree days. It is to use reserve levels and dispatcher review for the days when conditions are moving fast.
Keep clear notes on customer records. Notes such as “second home,” “wood stove used on weekends,” “tank is 275 gallons, not 330,” or “call before delivery” prevent the office from relearning the same lesson every winter.
Keep Tank and Delivery Data Clean
Bad account data will defeat good weather data. Tank size, usable capacity, product type, location, and prior delivery gallons all affect the schedule. One incorrect digit on a tank size can send a truck too early or too late for years.
Make a habit of verifying account details when a driver reports a discrepancy. If the driver finds a different tank, a changed fill pipe, a locked gate, or an estimated fill that does not make sense, update the customer record promptly. Waiting until the next delivery season turns a simple correction into a recurring dispatch problem.
Delivery tickets should also flow back into the account history without rekeying. When gallons, dates, and ticket details are delayed or entered twice, the degree-day schedule is working from incomplete information. That adds office work and weakens forecasting at the same time.
Manage Heating Degree Days With a Daily Dispatch Routine
The strongest operations make degree days part of a daily routine, not a report someone checks once a week. Load current local temperature readings, review the automatic delivery list, and look at accounts near their delivery threshold. Then group the needed deliveries into routes that make sense for truck capacity, geography, and driver time.
During a cold stretch, check the schedule more often. A weekend storm or a rapid temperature drop can pull forward accounts that looked safe two days earlier. During mild weather, resist the urge to send trucks simply because a route is nearby. Extra deliveries consume labor, fuel, and truck capacity that will be more valuable when winter tightens up.
This is also where software earns its keep. Degree Days Online can combine customer records, daily temperature updates, automatic scheduling, ticket printing, and delivery history in one operating system, so the office is not calculating schedules from paper tickets and separate spreadsheets.
Measure Results After the Season
At the end of the heating season, review more than total gallons sold. Look at runouts, emergency deliveries, average gallons per stop, out-of-route miles, and the accounts that required repeated manual adjustments. Those results tell you whether your reserve levels, K-factors, weather assignments, and route practices need work.
A lower number of runouts is good, but not if every delivery became a half-load. The best setup balances customer protection with productive truck loads and fewer wasted miles. That balance will vary by service territory, customer mix, and storage capacity.
Heating degree days are not a crystal ball. They are a practical way to make better decisions before the phone starts ringing. Keep the weather data current, keep account records honest, and give dispatchers enough room to apply the experience that no formula can replace.