How Degree Day Scheduling Works

If you have ever looked at a run sheet and thought, We should have hit that tank two days ago, you already understand why degree day scheduling matters. Knowing how degree day scheduling works gives fuel oil and propane dealers a better way to plan deliveries based on actual weather-driven usage instead of guesswork, fixed dates, or last-minute panic calls.

At its core, degree day scheduling is a method for estimating when a customer will need fuel by tying consumption to outdoor temperatures. The colder it gets, the faster heating fuel is burned. The milder it stays, the slower that tank drops. Instead of treating every account the same, degree day scheduling adjusts delivery timing around real heating demand.

That sounds simple, but the value is in the details. Done right, it helps reduce runouts, cuts unnecessary stops, and gives dispatch a cleaner picture of what needs attention today versus what can wait another few days. Done poorly, it can create a false sense of accuracy. The math is useful, but only if the account setup and daily temperature data are right.

How degree day scheduling works in the real world

A degree day is a measure of how much heating demand there was on a given day. In most heating fuel operations, the standard is based on a 65 degree balance point. If the average outdoor temperature for the day is 35 degrees, that day generates 30 heating degree days. If the average temperature is 50, that day generates 15 heating degree days.

Over time, those daily numbers add up. A delivery system tracks the total degree days since the last fill or delivery and uses that figure to estimate how much fuel the customer has burned.

To make that estimate useful, each account needs a usage factor, often called a K-factor or burn rate. That factor tells the system how many degree days it takes for the customer to consume one gallon of fuel, or in some setups, how much fuel they use per degree day. Once you know that relationship, the software can project the tank level based on the local weather history and the delivery history on that account.

For example, say a customer typically burns one gallon every 7 degree days. If that account has accumulated 210 degree days since the last delivery, the system estimates about 30 gallons have been used. If the customer was filled to 200 gallons usable capacity, the projected remaining volume would be around 170 gallons. As degree days continue to build, the estimated tank level keeps dropping until the account reaches its delivery trigger.

That trigger might be set at 30 percent, 25 percent, or another threshold based on your operating style. Some dealers are more conservative with older customers, hard-to-access locations, or accounts with a history of late payments and interrupted delivery patterns. Others run tighter for efficiency. There is no single correct setting for every account.

What has to be set up for it to work well

If you want accurate automatic scheduling, the first job is clean account data. Degree day scheduling depends on several pieces working together: tank size, usable capacity, delivery history, customer status, and the right degree day factor.

The burn rate matters most. If the K-factor is too aggressive, the system will think the customer is using less fuel than they really are, which increases runout risk. If it is too conservative, you will be scheduling stops too early and giving up efficiency.

New accounts usually need a starting estimate. That estimate can come from prior records, known equipment size, square footage, occupancy, or plain experience with similar homes in that area. But it is still an estimate. After a few deliveries, the account should be adjusted using actual usage patterns.

That is why experienced dealers do not treat degree day scheduling as a set-it-and-forget-it tool. They tune it. A family of five that is home all day will not burn like a weekend property. A house with a new boiler and insulation upgrades will not burn like it did five years ago. Propane adds even more variation when the same tank supports heat, hot water, cooking, pool heaters, or generators.

Daily temperature data also matters. If the weather readings feeding the schedule are outdated or too far from the customer base, your projections drift. Good scheduling systems pull in local temperature data automatically so dispatch is not relying on someone to key in weather numbers by hand.

Why dealers use degree day scheduling instead of calendar scheduling alone

Calendar scheduling is easy to understand. Deliver every 30 days, every 45 days, or on a fixed route pattern. In stable weather, that can work reasonably well. The problem is that heating demand is not stable.

A customer on a 30-day cycle in October may still have plenty of fuel left when a truck arrives. The same customer in January may be nearly empty before that 30th day shows up. Degree day scheduling fixes that by responding to actual cold weather instead of the calendar.

That usually means fewer unnecessary deliveries during warm spells and better protection during cold snaps. For a dealer trying to manage truck time, labor, and gallons delivered per stop, that is a real operational advantage.

Still, this is not an argument that calendar scheduling has no place. Some accounts are better handled by fixed timing, especially budget plans, difficult-access properties, or commercial accounts with more predictable usage patterns. In many operations, the best answer is a mix. Degree day scheduling handles weather-sensitive automatic delivery accounts, while dispatch uses calendar rules or manual review where they make more sense.

Where degree day scheduling can go wrong

Most scheduling problems are not caused by the concept. They come from bad data, poor follow-up, or special account conditions that were never flagged.

A tank that was partially filled but recorded as full will throw off future projections. A customer who starts using a wood stove, space heaters, or a secondary heat source may suddenly burn less than expected. A vacant property can look normal in the system until usage falls off. On the other side, a new baby in the house, an elderly resident keeping temperatures higher, or added propane appliances can push consumption up fast.

Deliveries that happen outside the normal workflow can also cause trouble. If a will-call order, emergency drop, or after-hours delivery is not entered correctly, the next projected tank level may be wrong from day one.

That is why the best dispatch teams still review exception accounts. Automation should narrow the list and speed up decision-making, not replace common sense.

How software makes degree day scheduling useful day to day

The theory behind degree day scheduling has been around a long time. The real improvement comes when software handles the repetitive work consistently.

A good system loads current temperature data, applies the right usage factor to each automatic account, updates estimated tank levels, and shows dispatch who is due based on your target thresholds. It should also make it easy to print tickets, organize routes, handle call-ins, and keep delivery records tied to the same customer file.

That matters because scheduling is not a stand-alone task. It affects routing, customer service, inventory planning, billing, and cash flow. When your schedule lives in one place and the rest of the operation lives somewhere else, office staff end up re-entering information, checking paper files, and making more judgment calls than they should have to.

That is where a fuel-specific platform earns its keep. Degree Days Online, for example, was built around how fuel dealers actually work, so degree day scheduling is part of the daily workflow instead of a separate feature that office staff have to work around.

How to get better results from degree day scheduling

The fastest way to improve performance is to treat account maintenance as part of dispatch discipline. Review K-factors regularly, especially after unusual weather, major usage changes, or customer complaints about delivery timing. Check that tank sizes and fill levels are accurate. Make sure emergency deliveries and will-call drops are posted right away.

It also helps to separate truly automatic accounts from borderline accounts that need more oversight. Not every customer belongs in the same scheduling bucket. Some accounts are clean, predictable, and easy to automate. Others need notes, custom minimums, or manual review before they are routed.

When the setup is right, degree day scheduling gives you a practical edge. You are not just sending trucks because the calendar says so. You are sending them because the weather, the history, and the account data say the fuel is being used.

That is the difference between reacting to deliveries and managing them. And in a business where margins are tight and winter mistakes are expensive, that difference shows up fast.