A delivery ticket is more than a piece of paper handed to a driver. It is the record that tells the office what was delivered, tells the customer what they received, and tells accounting what can be billed. This guide to delivery ticket workflows is built for fuel oil and propane dealers who want that record to move cleanly from dispatch to the truck to the office without piles of paperwork, missing details, or rekeying the same information twice.
When ticket handling breaks down, the damage is usually not dramatic at first. A driver returns with an unreadable ticket. A delivery is posted to the wrong account. A price change never reaches billing. Then the office spends the afternoon sorting through exceptions while tomorrow’s route still needs to be built. A good workflow prevents that kind of cleanup work before it starts.
Start With a Ticket That Matches the Actual Delivery
The workflow begins before a truck leaves the yard. Dispatch needs a ticket that gives the driver the information needed to make the stop correctly: customer name, address, account number, product, planned quantity when applicable, special instructions, and pricing or delivery notes that belong on the ticket.
For automatic customers, the ticket should be tied to the delivery schedule and current account information. That matters because automatic delivery is not just about estimating gallons. The dispatcher also needs to know whether the account is on hold, whether there is a delivery restriction, whether the customer has a locked gate, or whether a new tank location has been added.
For will-call customers, the ticket should begin with the order taken by the office. The person entering the order needs a clear way to record the requested product, desired delivery date, any promised price, and instructions such as “call before delivery.” If those notes live on a sticky note or in someone’s memory, they are likely to disappear when the route is printed.
A practical rule is simple: enter customer and order information once, where dispatch, drivers, billing, and customer service can all work from the same record. That reduces double entry and gives everyone a better chance of seeing the same facts.
Build Routes Before You Print Tickets
Printing tickets too early creates avoidable problems. A driver may receive a stack of stops that no longer reflects the day’s route, while dispatch has to handwrite additions, cross out customers, or issue replacement tickets. That is workable on a quiet day. It is not a dependable process during a cold snap when phones are ringing and trucks are already rolling.
Finish the route as far as possible before ticket printing. Review the delivery list for geography, truck capacity, product type, priority customers, and special access requirements. For propane dealers, make sure the route reflects the right cylinder or bulk-delivery needs. For heating oil dealers, verify that degree day or calendar day scheduling has not pulled in a customer who was recently delivered or placed on hold.
There will always be late call-ins and emergency no-heat stops. The goal is not to pretend the route will never change. The goal is to make changes in one place, clearly, so the office can see what was added and the driver has a usable ticket for every delivery.
Use a clear cutoff for routine route changes
Most companies benefit from setting a practical daily cutoff for ordinary additions and changes. After that point, the dispatcher can still add an urgent stop, but the change should be handled as an exception rather than quietly altering a completed route.
This gives the office time to check the new order, print or send the correct ticket, and make sure the delivery will be billed properly. It also gives drivers a better chance of loading the right product and carrying enough gallons to complete their assigned work.
Give Drivers a Simple, Consistent Delivery Process
The driver should not have to guess what information the office expects back. Whether your operation uses printed tickets, mobile devices, or a mix of both, establish the same basic delivery steps for every route.
At the stop, the driver confirms the account and location, delivers the product, records the actual gallons, captures any required signature or delivery acknowledgment, and notes anything that needs office attention. A tank concern, blocked fill, access issue, or customer request should come back as a clear note attached to that delivery, not as a vague verbal message at the end of the day.
The actual quantity delivered is especially important. The office may have planned 150 gallons, but billing should reflect what went through the meter. If the driver could not make the delivery or delivered a partial due to tank conditions, that exception needs to be obvious. Do not let a planned quantity become an assumed delivered quantity.
A good ticket workflow also protects drivers. Clear tickets reduce disputes over the address, product, price, and instructions. If a customer questions a delivery later, the company has a usable record instead of trying to reconstruct what happened from memory.
Bring Completed Tickets Back Into the System Promptly
The day is not finished when the truck returns. Tickets need to be reviewed, posted, and turned into invoices while the delivery details are still current. Waiting several days may feel easier during a busy season, but it creates a backlog that makes mistakes harder to catch.
The office should compare each completed ticket against the original delivery record. Look for actual gallons, no-delivery codes, price overrides, signature requirements, tax status, and driver notes. If something does not match, resolve it before the ticket is posted to billing.
This review is where many preventable revenue leaks are found. A no-delivery ticket that gets billed by mistake creates a customer service problem. A delivery that is completed but never posted delays cash flow. A handwritten price note that is missed can leave the company arguing with a customer after the invoice has already gone out.
For companies using paper, organize returned tickets by route and date so nothing gets separated from the rest of the day’s work. For companies using delivery management software, completed delivery information should flow back to the customer record and billing process without requiring staff to type every gallon and note a second time.
Connect Tickets, Billing, and Payments
A ticket workflow is only complete when the delivery can be billed accurately and the customer balance is current. That connection is where disconnected systems cause the most office work. Dispatch may have one list, accounting may have another, and the person answering the phone may not know whether a delivery has been posted yet.
The right process lets the office review completed deliveries, create invoices, and keep customer records current from the same operational information used to dispatch the truck. If your company uses QuickBooks Online, the accounting handoff should be planned carefully. Decide which system owns the customer record, how invoices are transferred, and who handles corrections when an invoice needs to be changed.
It depends on the size of the operation and how much accounting detail is needed, but the principle stays the same: avoid creating one delivery record for dispatch and another for accounting. Every extra handoff is another chance for a mismatch.
Payment collection should also be visible to the people handling orders. If an account has an overdue balance, a credit limit issue, or a required payment before delivery, the dispatcher needs to see that before the ticket is printed. That does not mean every driver needs to handle collections. It means the office has enough control to avoid sending a truck to an account that should be reviewed first.
Set Up Exceptions Instead of Hiding Them
No workflow eliminates exceptions. Customers run out early. Driveways are blocked. Tanks cannot be filled. A driver may find that the account information is wrong. The difference between a controlled operation and a chaotic one is how those exceptions are recorded and followed up.
Create clear statuses for common outcomes, such as delivered, partial delivery, no delivery, wrong address, unable to access, or customer canceled. Require a short note when a ticket is not completed as planned. Then give one person in the office responsibility for reviewing those exceptions before the next day’s routes are built.
This step matters for automatic delivery customers. A failed delivery can change the customer’s risk level quickly, especially during severe weather. If the exception is buried in a stack of tickets, the scheduling system may assume the customer has product they never received.
Make the Workflow Easy Enough to Follow on a Busy Day
The best delivery ticket workflow is not the one with the most rules. It is the one your dispatchers, drivers, and office staff can follow when the temperature drops and the phones do not stop.
Degree Days Online was built from the day-to-day realities of a fuel delivery business, with tools for scheduling, ticket printing, delivery history, customer records, payment handling, and accounting workflows in one practical system. The point is not to add another layer of software. It is to replace paper chases and duplicate entry with a process that gives the office control of the day.
Start by looking at where tickets stall now. Maybe it is route changes after printing. Maybe it is returned tickets waiting to be entered. Maybe it is billing that does not match what the driver delivered. Fix the point where information gets lost first. A cleaner ticket process gives your team more time to serve customers and fewer reasons to stay late sorting out work that should have been right the first time.