A runout is not just an inconvenient service call. It can mean a cold house, a damaged customer relationship, overtime for your driver, a truck pulled off route, and an office scrambling to explain what happened. The best runout prevention methods are not complicated, but they do require clean customer information, dependable scheduling, and someone watching the exceptions before they become emergencies.
For heating fuel and propane dealers, prevention starts with accepting one simple fact: no delivery system can predict every customer perfectly. People add a space heater, leave for Florida, host family for a week, install a new boiler, or change the thermostat without calling the office. The goal is not to promise zero surprises. The goal is to build an operation that catches risk early, responds quickly, and does not depend on handwritten notes or one person’s memory.
Why customers run out in the first place
Most runouts come from a few repeat problems. An automatic customer may have the wrong tank size, an outdated K-factor, or a delivery history that was never reviewed after an equipment change. A will-call customer may wait too long to call. A route may be delayed by weather, staffing, or a truck problem. Sometimes the customer was scheduled correctly, but the delivery ticket never made it onto the truck.
The underlying issue is usually poor visibility. When customer records, tickets, degree day data, and call-in orders live in separate places, dispatchers have to piece together the real picture under pressure. That is where mistakes get expensive.
A practical prevention plan separates customers by delivery type, keeps the assumptions behind each schedule current, and gives the office a clear list of accounts needing attention. That sounds basic because it is. Basic controls, used consistently, prevent most avoidable runouts.
1. Keep automatic delivery customer records accurate
Automatic delivery works only as well as the data behind it. At a minimum, every automatic account should have the correct tank size, fuel type, usable tank capacity, delivery amount, heating equipment, and current K-factor or usage rate.
The K-factor deserves regular attention. It is not a permanent number assigned when the account is opened. A customer who replaces an old furnace, adds insulation, converts part of the home, or starts heating a garage may use fuel very differently than before. A customer who was reliably scheduled last winter can become a risk this winter if nobody updates the account.
Review delivery history before peak season and after any unusual delivery. If an account repeatedly takes much more or much less fuel than expected, find out why. It may be a simple data correction. It may also reveal an unreported equipment change, a leaking tank, or a customer using fuel for a new purpose.
2. Use degree days, but do not treat them as magic
Degree day scheduling gives fuel dealers a practical way to estimate consumption based on local weather. It is far better than guessing based on the calendar alone for many heating oil accounts. But a degree day model is an estimate, not a guarantee.
The right weather station matters. A customer near the coast, in higher elevation, or in a different microclimate may not consume fuel like an account located 20 miles away. Use local temperature data that fits the delivery area, then adjust accounts when their actual usage tells a different story.
Also build in a reasonable delivery cushion. Scheduling every account to arrive with only a few gallons remaining may look efficient on paper, but it leaves no room for a storm, a blocked driveway, or a sudden cold snap. The correct reserve depends on the tank, route frequency, customer location, and service capacity. A rural customer at the end of a long route generally needs more protection than an account in town that can be reached quickly.
3. Use calendar scheduling where it makes more sense
Not every account belongs on degree days. Some commercial accounts have steady, predictable usage. Some propane customers use gas primarily for cooking, water heating, or other non-heating loads. Others have enough history that a calendar interval is the simpler and more reliable choice.
Calendar day scheduling is also useful when temperature is only one part of the usage picture. A small business may have regular operating hours. A customer with a pool heater or generator may use propane in patterns that degree days alone will not capture.
The point is to match the method to the account. Dealers get into trouble when they force every customer into the same model because it is easier for the office. A good system supports degree day schedules, calendar schedules, and manual attention for accounts that do not fit neatly into either category.
4. Set up a daily exception review
The daily schedule should not be treated as a finished product the moment tickets are printed. Before trucks leave, someone needs to review accounts that fall outside the normal pattern.
Look for customers with projected low balances, overdue deliveries, unusually high estimated usage, incomplete addresses, credit holds, or notes about access issues. Review new automatic accounts separately until there is enough delivery history to trust the calculation. If a customer says they are low but does not appear on the route, that call should trigger a record check, not a guess.
This is where software earns its keep. When schedules, delivery history, local weather updates, and customer notes are in one place, the office can focus on exceptions instead of manually rebuilding the route every morning. Degree Days Online was built around that day-to-day reality: get the information in front of the dispatcher while there is still time to make a sensible delivery decision.
5. Treat will-call customers as a separate risk group
Will-call customers are not bad customers. Many prefer to manage their own deliveries, and some use very little fuel. But they need a different prevention process because the dealer does not control the delivery timing.
Make sure will-call accounts understand the lead time required during cold weather. When a customer calls at one-quarter tank in January, they may assume delivery is automatic or same-day. Clear communication at account setup, on statements, and during phone calls helps set realistic expectations.
The office can also use past delivery history to spot customers who normally call at a certain interval but have gone quiet. A courtesy reminder may prevent an emergency, especially for older customers or seasonal residents. Do not represent it as automatic delivery if it is not. Simply give the customer useful information before the tank gets low.
6. Make delivery tickets and driver feedback part of the system
A ticket is not just paperwork. It is the record that confirms what happened at the tank. Accurate tickets help the office compare estimated usage with actual gallons delivered and identify accounts that need an adjustment.
Drivers are also one of the best sources of field information. They notice new construction, locked gates, dogs, damaged fill pipes, empty tank signs, and customers who mention a new appliance. Give drivers an easy way to report those details, and make sure the office updates the account instead of leaving the note buried in a pile of papers.
If a delivery cannot be completed, the account should immediately become visible to dispatch. A no-access stop is not a finished stop. It is a potential runout waiting for follow-up. The customer may need a call, a new delivery date, or a service plan for access problems.
7. Build a clear response plan for real emergencies
Even disciplined operations get runout calls. What separates a manageable event from a bad customer experience is the response plan.
Your office should know who verifies the account, who checks prior deliveries and tank information, who dispatches the truck, and who handles a possible prime or service call. If the customer is on automatic delivery, review the reason for the miss as soon as the immediate problem is handled. Was the K-factor wrong? Did the route get delayed? Was there a delivery exception nobody followed up on? Did the customer make an unreported usage change?
Do not settle for “the customer ran out” as the final explanation. That describes the result, not the cause. A short review after every runout helps prevent the same mistake from happening again, and it identifies whether the issue is customer behavior, staff process, data quality, or scheduling capacity.
Runout prevention is an operating discipline
The strongest runout prevention methods combine sound scheduling with people who pay attention to the accounts that do not look normal. Clean records matter. Local weather data matters. Driver notes, ticket accuracy, route capacity, and prompt follow-up matter too.
No dealer can control the weather or every change inside a customer’s home. You can control whether your team has current information, a workable delivery plan, and enough warning to act before a low tank turns into an emergency call. That is what keeps trucks productive, customers warm, and the office from spending January putting out fires.