Fleet fuel management

Fleet fuel management for trucking carriers.

Fleet fuel management is the work of deciding where your trucks fuel, making sure the decision reaches the driver in time, and proving afterwards that it happened. The three parts depend on each other: a good decision only pays if it reaches the driver, and you only know it did if you check afterwards.

The five jobs a fuel program has to do

A fuel program is not a report and it is not a discount card. It is five jobs that have to happen in order, every day, for every truck. A program that does four of them leaks through the fifth.

  • Decide where the truck should fuel

    Not the nearest station and not the cheapest sign on the interstate — the stop that is best once your contracted price, the detour off the lane, the driver's remaining hours and the fuel already in the tank are all taken together. This is a routing decision with a price attached, and it changes hour by hour as the truck moves.

  • Get that decision to the driver before the tank forces it

    A correct stop that arrives after the driver has already pulled off is worth nothing. The decision has a deadline, and the deadline is set by the fuel gauge, not by the office. That is the failure to design against: the analysis is right, and it arrives late.

  • Confirm the fill actually happened

    A driver can be sent to a stop and not take it — hours ran out, the lane changed, the station was full. Without a confirmation step the program cannot tell a driver who ignored the assignment from one who was rerouted by dispatch an hour earlier.

  • Reconcile against the fuel-card statement

    The fuel card is the only complete record of every fill, including the ones nobody planned. Matching card transactions back to assigned stops turns the program's claims into arithmetic: this stop was assigned, this transaction is the same fill, this is the difference against the alternative.

  • Coach the fleet on what the reconciliation shows

    Compliance is not necessarily even across the fleet: off-network fills can cluster around particular drivers or lanes, and the reason behind a cluster can only be fixed once somebody knows it. Without per-driver and per-lane numbers, coaching is a fleet-wide email that changes nothing.

Where fuel money leaks

Where a carrier with a negotiated discount network loses money, the loss is not in the contract. It is in the gap between the contract and the pump.

A driver at an exit with a quarter tank does not know which of the two stations in front of them is in-network, and has no way to find out that does not involve stopping and looking it up. The default is the nearest one. Repeated across a fleet and a month, the aggregate of those defaults is the leak — and because it shows up as ordinary fuel spend rather than as a line item, nothing in the accounting flags it.

The second leak is timing. A truck that runs the tank down too far loses the choice entirely; whatever is at the next exit is the stop. The third is the reverse, a truck topping off in small amounts at convenient stations, which keeps the tank comfortable and the discount unused.

None of these is a driver problem. They are all information problems, and they are solvable at the point where the decision gets made.

How this work gets done today

Before comparing anyone's offer, it is worth being honest about the four ways this already happens, because every carrier is doing one of them whether or not they have named it.

The first is that nobody does it. The card contract is signed, the discount sits in it, and the choice of station is made by whoever is driving, at the exit, with the information on the sign. Nothing is broken, nothing is reported, and the gap only shows up as a number that is lower than it should be.

The second is that a dispatcher does it alongside dispatching. This works, and it works well, right up to the point where load coverage and fuel planning want the same half hour. Fuel loses that contest, because a truck without a load is a problem today and a truck that fuelled in the wrong place is a problem next month.

The third is software that reports it. A report tells you where the money went and leaves the two hard parts — making the call on each truck, and getting it to the driver before the tank decides — with the person who already did not have time for them. That is not a criticism of the software; it is a description of where the line is drawn.

The fourth is that somebody outside the company runs it as a service, which is what this is. The work moves rather than disappears, and the question to ask of it is the same one you would ask of a dispatcher: what does it decide, how does the driver hear about it, and what proof arrives afterwards.

How DispatchFuel.ai runs it

We take the decision on for the fleet rather than handing it back as a dashboard. That is the difference between this and fuel software: nobody at the carrier has to log in for the program to work.

  • We watch the tank, not the calendar

    Position and fuel level come from your telematics. When a truck is coming up on a fill, that is when the stop is worked out — against the lane ahead, your pricing and the driver's hours.

  • The driver gets one message

    A Telegram message with the stop, the exit and the reason, answered with one tap. Where a fleet already runs its driver group on Telegram, there is no app to install and no training day.

  • The fill is confirmed at the pump

    The driver confirms and keeps rolling. That confirmation is what separates a stop that was taken from a stop that was only sent.

  • The card transaction closes the loop

    When the fuel-card transaction arrives it is matched back to the coordinated stop, so the savings line is recorded history rather than a projection. Actual and estimated savings are labelled separately and never blended into one number.

  • Exceptions come to a person

    Stale telematics, unmatched transactions, a stop that was sent and not taken — these surface as exceptions for an ops desk to work, rather than quietly degrading the numbers.

What it connects to

Telematics for position and fuel level. Your fuel-card transaction feed for reconciliation. Your discount network pricing, in whatever form you hold it today. Telegram for driver communication. Google Sheets for import and export.

Named providers are confirmed with each carrier during the pilot rather than advertised here, because an integration list on a marketing page is a promise about somebody else's API.

What the term also covers, and what we do not do

"Fleet fuel management" is a wide phrase, and most of what it covers is not this. Bulk and on-site fueling, tank level monitoring and delivery scheduling are a different operation with different equipment. Idle-time and miles-per-gallon coaching is about how the truck is driven, not where it stops. Card fraud controls, purchase limits and policy enforcement sit with the card provider. IFTA fuel-tax reporting is an accounting obligation that happens after the fact.

This service does none of those. It covers one question and the three jobs hanging off it: where a truck should fill on the road, how that decision reaches the driver in time to be acted on, and what the card statement says about it afterwards. If what you need is tank telemetry at a yard or a fuel-tax filing, this is the wrong tool and you should not hear otherwise from us.

Who this fits, and who it does not

It fits carriers running roughly 10 to 500 trucks that already hold a fuel-card contract with negotiated pricing, and that have nobody whose full-time job is making sure drivers use it. That combination — a good contract and no one minding it — is where the gap is widest. Larger and multi-terminal fleets are in scope too; the pilot is sized to one division so the rollout stays controlled.

Below roughly ten trucks the economics get thin, and we would rather say so on a call than after you have signed something. If you have no discount network at all, there is nothing yet for the program to route against; that contract comes first.

Questions

Does this replace our dispatcher?
No. The decision about where a truck fills is made and sent, and your dispatcher reviews each one for as long as you want that review to continue. The work moves; the authority does not.
What happens when a driver does not take the stop?
It shows up in the monthly match as an assignment with no matching transaction. That is either a coaching conversation or a legitimate reroute nobody told the office about, and the match on its own does not say which — so it gets asked about rather than assumed.
Do you need write access to our systems?
No. The setup pass is read access to your telematics, your fuel-card transaction feed and your discount network pricing. Nothing is written back into your systems, and no driver personal data is needed beyond what dispatch already holds.
Can we see why a particular stop was chosen?
Yes. The message the driver receives carries the stop, the exit and the reason, and the confirmation that comes back records the time and location. The same reasoning is what the monthly reconciliation is checked against.

See it on your own fleet.

Apply for the pilot to run it on a slice of your trucks with your data, or join the waitlist for launch access.