At 15 trucks, dispatch runs on memory and a whiteboard. At 50, memory fails and the whiteboard becomes a liability. The fleets that hold margins past the 50-truck mark treat dispatch as a planning problem with numbers attached, not a daily guess.
There is a threshold in oilfield trucking where the informal system stops working. It sits somewhere around 40 to 60 trucks, depending on how spread out the work is. Below it, the dispatch lead knows the drivers, the wells and the current jobs well enough to route by feel. Above it, trucks start waiting at location, deadheading across the basin and burning fuel while the morning meeting argues about who is where.
What changes at 50 trucks
- Geography stops being local. Jobs spread across counties, and return-to-base routing collapses.
- Multi-job days become the norm. One truck may touch three locations, and every handoff is a chance to misroute.
- Maintenance windows collide with dispatch. Trucks come out of service at the worst moment unless the plan accounts for it.
- Driver knowledge stops scaling. The 50th driver does not know the shortcuts the first 15 knew.
- Tickets stop aligning with trucks. When dispatch and billing run on different records, the day's work gets reconstructed after the fact.
None of this shows up on the rig count or the revenue line. It shows up in utilization, fuel and the ticket-to-truck match at the end of the day.
Deadhead and idle are the two leaks
Fleet benchmarks put the industry-average deadhead rate at 15 to 22 percent of total miles, with dedicated contract carriers holding 10 to 15 percent and well-run operations targeting under 10. On a 100,000-mile truck, a 20 percent deadhead rate is 20,000 empty miles a year, paid at the same fuel, maintenance and driver rate as loaded miles.
Fleet benchmarks; dedicated contract carriers hold 10 to 15%, and well-run fleets target under 10%.
Idle is the quieter leak. A heavy truck burns about 0.8 gallons per hour idling, and the average truck idles roughly 1,800 hours a year. That is around 1,400 gallons of fuel per truck per year consumed without moving an inch of freight. Telematics data typically cuts idle time 15 to 20 percent on its own, and 30 to 35 percent when paired with driver coaching.
Per-truck idle fuel equals roughly 1,400 gallons a year; telematics plus coaching cuts it by a third.
Plan the day, then let dispatch adjust it
The fleets that optimize at scale do not dispatch reactively. They build a plan the night before: jobs batched by region, trucks assigned to minimize empty miles, maintenance windows pre-blocked, and a small float of spare capacity for breakdowns and blowouts. The morning call then adjusts the plan instead of inventing it.
Batching matters more than routing software. Three jobs in the same county run by one truck beat three trucks running from base. Consolidating loads and sequencing stops is where most deadhead reduction actually comes from; the software is what makes the sequencing repeatable when the dispatch lead is not the one who built the plan.
The plan also sets the day's exceptions in advance. If a truck goes down at 9 a.m., the dispatcher already knows which jobs can flex, which client window is hard, and which driver can cover the gap. That pre-answer is what separates a fleet that absorbs a breakdown in twenty minutes from one that loses the afternoon.
Technology alone; 30 to 35% when combined with structured driver coaching.
Dispatch and tickets are the same system
Here is the part that trips up service companies specifically. The truck's day is the ticket's content. Hours, location, standby time and out-of-scope work all originate in dispatch decisions. If dispatch runs on the lead's memory, the ticket gets reconstructed from memory too, and that is where rate disputes and missing charges start. Every field operations lead we talk to says the same thing: the accurate ticket is the one written against the plan, not against the recollection.
The Q2 2026 operations benchmark has the sector-level numbers on cycle times and ticket accuracy. We have also written separately on the cost of paper field tickets and on cutting days to invoice, because dispatch and billing are two halves of the same day.
On the tooling side, the plan is only as good as the schedule it runs on. A dispatch and scheduling platform that holds the day's plan, fleet positions and maintenance windows in one view turns the morning scramble into an exception list, and the scheduling layer is built for exactly that. The field ticket capture side then records the day as scheduled, so the invoice matches the plan instead of the argument.
Start at the truck level. Pick the five trucks with the worst deadhead and idle numbers and fix their days first, then widen the plan to the fleet. The 50-truck fleet that plans the night before is not working harder; it is running the same miles in the right order, and the tickets come out cleaner because the day happened as scheduled.