(Idle time, speed, and fuel behavior are the real margin drivers)
Fuel is already expensive and likely heading higher over time—but the real cost drivers in your fleet aren’t prices. They’re idle time, speed between jobs, and using premium fuel when your trucks don’t require it. Most contractors still look at fuel like it’s a pricing problem. It isn’t. It’s a behavior problem that shows up on a fuel receipt.
When fuel spikes, it feels external. Gas goes up. Nothing you can do. That’s just the market. And to be fair, fuel is influenced by market conditions. But focusing only on price is like blaming grocery inflation while ignoring what’s in your cart. In most contractor fleets, the real cost drivers are internal and fully controllable.
Idle time is one of the clearest examples. It isn’t really a fuel problem. It’s a labor visibility problem. A running truck usually means someone is sitting in it, work is not being produced, and a crew is being paid without output. In many cases, that “someone” is the foreman. And that creates a second-order issue. If the foreman is sitting in the truck, they are not supervising the crew. So idle time isn’t just inefficiency. It’s lost coordination at the job site.
I used to run a simple Monday morning report showing total idle time across the fleet. The rule was straightforward: one hour per day per truck was the maximum acceptable threshold. That allowed for warm-ups, traffic, and extreme weather conditions. Anything above that triggered a message to operations. It wasn’t aggressive—just a standard note that idle time had exceeded the threshold and should be reviewed with the crew.
What happened next was predictable. Behavior improved for a few weeks. Idle time dropped. Then it slowly drifted back to normal. No discipline ever occurred. No structural changes were made. It was simply reporting and social pressure. And that’s the key insight: visibility alone improves behavior temporarily, but it doesn’t sustain it.
Speed is the other half of the inefficiency problem, and it’s often overlooked. According to the U.S. Department of Energy, fuel economy drops 7%–14% when driving just 5–10 mph over 50 mph, and can be nearly 30% worse at 75–80 mph compared to 55 mph. That matters because excessive speed between jobs does not increase job output. In most cases, faster driving doesn’t complete more work, it just costs more per mile. The result is higher fuel spend, higher maintenance exposure, and no measurable gain in production.
Another quiet inefficiency is fuel grade misuse. In mixed fleets, it is common to see regular vehicles fueled with premium gas, often as a “just in case” habit or due to unclear guidance. Unless a vehicle specifically requires premium fuel, there is typically no performance benefit or efficiency gain. There is only a higher cost per gallon. And across a fleet, that becomes a slow, invisible margin leak.
Most contractors already use fleet management systems such as Samsara, Verizon Connect, or Geotab. These tools track idle time, speed, fuel usage, and routes. The data exists. But data does not automatically become accountability that can save money.
The gap is what happens after the data is collected. In many contractor operations, idle time is reported but not assigned to jobs. Speed is monitored but not tied to job performance. Fuel is tracked but not connected to labor productivity. Fleet reports exist, but they remain operational rather than financial. So instead of seeing “Job A lost $300 due to idle inefficiency,” the business sees only “fuel costs are up again this month.” It is the same data, but a completely different level of insight.
The real issue is that most systems measure activity, not profitability behavior. Fuel is simply the output. The underlying drivers are idle time, which represents paid labor without production; speed, which represents inefficiency per mile; and fuel grade misuse, which represents unnecessary cost per gallon. Individually, they appear small. Together, they quietly erode margin across every job.
That Monday idle report system also revealed something important about operations management. Reporting creates awareness. Awareness creates temporary behavior change. But without structural accountability, behavior inevitably reverts. That is why so many efficiency initiatives in construction fade after a few weeks. They are built on visibility, not reinforcement.
Better systems approach this differently. Instead of treating fleet data as reporting, they connect it to job performance. Idle time is allocated per job. Speed behavior is reviewed alongside production output. Fuel usage is tied to job costing. Foreman accountability is linked to crew productivity. Once fleet behavior appears in job costing, it stops being an operations metric and becomes a profit metric.
Fuel prices will rise and fall beyond our control. Idle time, speed habits, and fuel decisions do not. The real question is not whether you can see them. It is whether you have built a system where seeing them actually changes outcomes.
I would love to hear your feedback on this topic. Are you just tracking idle time and speed, or have you actually tied it to job costing and performance?