Deadhead miles cost a carrier fuel, wear, driver hours, and tolls while producing no revenue, so they dilute the effective rate on the loads that surround them. A dispatcher evaluating a load looks at the loaded rate and the deadhead required to start it together, not separately.
Some deadhead is unavoidable: freight does not always originate where the last delivery ended, and a truck has to reposition to stay in a lane with volume. The goal is not zero deadhead but keeping the empty percentage low enough that the loaded miles still clear the truck’s cost per mile with margin.
Deadhead is measured as a percentage of total miles — empty miles divided by loaded plus empty miles. Long-haul dry van operations commonly run in the low-to-mid teens; a number climbing toward 25–30% usually points to weak backhaul coverage or lanes chosen without a plan for the return.
Example
A truck delivers in Columbus, OH, and the next paying load picks up in Cincinnati, 110 miles away. Those 110 empty miles are deadhead. If the Cincinnati load pays $1,000 for 600 loaded miles, the carrier is really earning $1,000 for 710 miles of running — about $1.41 per mile, not $1.67.
Why it matters
Deadhead decides whether a load that looks profitable actually is. Dispatchers who price and accept loads on loaded miles alone routinely take work that loses money once the repositioning is counted.
How teams use this term
In a carrier operation, Deadhead belongs in the conversation about dispatch, planning, execution, and driver coordination. The useful question is not only what the term means, but which record or decision it changes. A dispatcher may see it while planning a load, a driver may create evidence for it in the field, and accounting may need the same context before a customer invoice or carrier settlement can be finalized. Keeping the term attached to the related workflow prevents a definition from becoming disconnected vocabulary.
When reviewing Deadhead, ask who owns the next action, what evidence supports the record, and what date or threshold makes the situation change. The answer can vary by equipment, lane, authority, customer routing guide, or contract. A small carrier should document the assumption it used rather than treating a general explanation as a universal rule. The related terms on this page are intended to help a team move from the definition to the operational decision.
A practical review starts with the example above, then compares it with the carrier's own settlement, dispatch, document, or compliance records. If the term affects a regulated filing, payment obligation, or customer requirement, verify the current primary source before acting. Trailflow can provide workflow context, but the carrier remains responsible for the policies, records, and professional advice that apply to its operation.
In Trailflow, this shows up in routing and mileage.