Good Fleet Utilization Rate: How to Calculate Your Fleet’s Actual Ceiling in 2026

A good fleet utilization rate is whatever figure sits just below your fleet’s arithmetic ceiling, and that ceiling is set by your demand variability rather than by an industry average. A fleet that must serve peak demand is sized for peak, so its average utilization can never exceed the inverse of its peak-to-average ratio, before maintenance and mandated non-driving time are subtracted. For a stable urban operation that ceiling lands near 71%. For a typical last-mile fleet it is closer to 61%, and for a seasonal or service fleet nearer 48%. Fleet and logistics leaders use the calculation below to replace a borrowed benchmark with their own number, because targeting a generic 85% forces a fleet cut that fails at peak.

Why the utilization ceiling matters: the business case

Utilization is the metric most often used to justify fleet cuts, which makes getting the target wrong expensive in both directions. Set it too low and you carry vehicles you do not need. Set it too high and you cut into peak coverage, which shows up as missed windows rather than as a utilization problem, so the cause is rarely traced back.

The constraints that consume utilization are larger than most targets assume. Dwell is the biggest and the least controllable: ATRI’s driver detention research found detention of six hours or more occurring at 39.3% of stops, which is paid vehicle and driver time producing no delivery. Congestion adds variance that differs by market rather than nationally, with INRIX putting US congestion at 49 hours per driver in 2025, Chicago at 112 hours and New York at 102. Driver availability caps it further: the American Trucking Associations reported large truckload carrier turnover at an annualized 87% in recent quarterly data against a long-run average of 92.7%, and a vehicle without a qualified driver is unavailable regardless of how it is scheduled.

The cost consequence concentrates in the same leg. McKinsey puts the last mile at 60% to 70% of total parcel delivery cost, so utilization decisions in the final leg move more money than equivalent decisions upstream.

Locus data indicates how much recoverable capacity hides inside a fleet that looks fully committed. A Fortune 50 parcel and freight enterprise running 4,500 drivers across 51 sites uncovered more than $14M in unused contracted capacity, including $565K at a single site once the analysis was scaled across 25 more, while lifting weekly execution rate from 75% to 92%.

Also Read: What Is Fleet Utilization? Key Metrics and Importance in 2026

How to calculate your fleet’s utilization ceiling

The formula is:

Maximum sustainable utilization = (1 ÷ peak-to-average ratio) × (1 ? maintenance downtime share) × (1 ? mandated non-driving share)

Step 1: Measure your peak-to-average demand ratio

Take twelve months of delivery or trip volume at the granularity you actually plan on, usually weekly or daily. Divide your busiest period by your average period. A grocery operation with steady weekly demand may sit at 1.2. A parcel or retail last-mile fleet commonly runs 1.4. Seasonal retail reaches 1.8 and construction or field service can exceed 2.2.

Step 2: Invert it to get your sizing cap

Because the fleet must cover peak, peak defines the vehicle count. Average utilization is therefore capped at one divided by the ratio. At 1.4 that is 71%, and no scheduling improvement raises it while the fleet is sized for peak. This single step explains most of the gap between reported utilization and the benchmarks operators are measured against.

Step 3: Subtract planned maintenance downtime

Preventive maintenance, inspections and repair take vehicles out of service on a predictable cycle. Express it as a share of calendar availability, commonly around 5% for a well-maintained delivery fleet. At a 1.4 ratio the cap falls from 71% to about 68%.

Step 4: Subtract mandated and structural non-driving time

Federal hours-of-service rules require breaks and cap driving within a duty window, and pre-trip inspections, loading and depot time consume more. Counting roughly 10% of the shift as mandated or structural non-driving takes the ceiling from 68% to about 61%. That is the realistic maximum for a typical last-mile fleet.

Step 5: Repeat per vehicle class, not once for the fleet

Refrigerated units, box trucks, last-mile vans and linehaul tractors have different duty cycles, maintenance intervals and demand profiles, so each has its own ceiling. A blended fleet number averages a van at its ceiling with a specialist unit at half of its own, and hides both.

Utilization ceilings by operation type

Figures are computed from the stated inputs, assuming 5% maintenance downtime and 10% mandated non-driving time. Substitute your own values.

Two conclusions follow. The widely quoted 70% healthy figure is the derived ceiling for a low-variability operation, which is why it fits some fleets and misleads the rest. And a last-mile fleet reporting 60% utilization is not underperforming, it is at roughly 98% of its achievable maximum.

Also Read: AI-Powered Fleet Utilization Analytics 2026

Generic benchmark vs derived ceiling: key differences

What to look for in fleet management software

Peak-to-average reporting, not just averages. The system should show demand distribution by period and by vehicle class, since that distribution sets your ceiling. Ask to see a twelve-month peak-to-average ratio computed from your own volume.

Utilization by vehicle class as standard. Confirm the platform segments utilization by asset type rather than blending it, and that thresholds can be set per class.

Separation of the three utilization types. Time utilization, capacity utilization and distance utilization answer different questions and move independently. A platform reporting one composite number cannot tell you which is constraining you.

Idle and dwell attribution. Dwell at consignee sites is the largest single consumer of available hours in many fleets, and it needs to be attributed to the location and the client rather than absorbed into a route average.

Cross-fleet or cross-client pooling. Because pooling is the only lever that raises the ceiling, the platform must be able to plan one shared pool across regions, clients or business units while accounting for each separately.

Also Read: Fleet Utilization for 3PLs: How to Maximize Asset Performance Across a Multi-Client, Multi-Fleet Operation (2026)

Raising the ceiling: pooling is the only lever

Every operational improvement moves a fleet toward its ceiling. Only one thing moves the ceiling itself, which is reducing the peak-to-average ratio, and the practical way to do that is to pool demand whose peaks do not coincide.

Two last-mile operations each at a 1.4 ratio, with peaks falling on different days or in different regions, combine to a pooled ratio closer to 1.18. That lifts the achievable ceiling from 61% to about 72%, an eleven-point gain produced by nothing except shared capacity. The same mechanism explains why 3PLs running many client accounts on one fleet can sustain utilization that a single-client operation cannot, provided the accounts are genuinely counter-cyclical rather than all peaking at month end.

The corollary is that pooling clients with coincident peaks achieves nothing. Before consolidating fleets, check whether the peaks actually offset, because two operations that both peak in the last week of the month pool to almost the same ratio they started with.

Fleet utilization in action: real-world results

Fortune 50 parcel and freight, 4,500 drivers, 51 sites. Capacity was contracted and dispatch decided locally, so nobody could see whether committed capacity was being used. Centralizing execution on Locus lifted weekly execution rate from 75% to 92% and uncovered more than $14M in unused contracted capacity, including $565K at a single site once the analysis was scaled across 25 more, at 99.99% uptime. The unused capacity was not idle vehicles, it was contracted capacity nobody had measured against demand.

Global FMCG, 10 countries, 5,000+ riders. The operation spanned 1,000+ distributors with demand peaks varying by market, which is the pooling case at scale. On Locus it achieved 3X ROI with more than 12,000 trips saved per month across $4B+ in optimized orders, reaching 1.8M+ retail outlets. Trips saved is the utilization metric that matters here, because a saved trip is recovered capacity rather than a cheaper trip.

Also Read: Fleet Management and Utilization: AI Architecture Framework 2026

Common fleet utilization mistakes to avoid

Benchmarking to an unattributed industry figure. Most published utilization bands carry no derivation and no statement of the demand profile they assume. Using one as a target imports someone else’s demand variability into your fleet plan.

Cutting vehicles to hit an unreachable number. If the target sits above your ceiling, the only way to reach it is to remove capacity you need at peak. The resulting failures get diagnosed as dispatch or driver problems because the utilization number improved.

Reporting one blended fleet figure. A single percentage across mixed vehicle classes conceals both the specialist asset running at half its ceiling and the van running above sustainable load.

Pooling fleets without checking whether peaks offset. Consolidation is sold as a utilization gain, but pooling two operations that peak simultaneously leaves the ratio, and therefore the ceiling, almost unchanged.

Why Locus: raising the ceiling requires planning one pool, not many fleets

Most fleet software measures utilization. The harder problem is changing it, and the arithmetic above shows that requires planning across pooled demand rather than optimizing each fleet separately.

Locus, the world’s first Decision-Intelligent, Agentic TMS, is built for that. The Digital Supply Chain Officer (DiSCO) framework runs a Sense-Decide-Execute-Learn cycle across eight specialized agents, reasoning over 250+ real-world constraints, so one plan can span regions, clients and business units while each is still accounted for separately.

The Capacity Agent matches supply to forecast demand shape rather than to average demand, which is what allows a pooled fleet to be sized against a combined peak instead of the sum of individual peaks. The Dispatch Agent plans across the whole pool while respecting each account’s windows and constraints, and DispatchIQ applies that across hundreds of concurrent constraints, reaching 99.5% on-time delivery in multi-region deployments against the 80% to 90% typical of manual dispatch. The Carrier Agent extends the pool beyond owned assets to 1,000+ pre-integrated carriers through ShipFlex, so peak coverage can be bought rather than owned, which lowers the fleet size the peak requires and raises the ceiling again. The Orchestrator Agent normalizes utilization, cost and event data across fleets and carriers, which is the prerequisite for computing a peak-to-average ratio anyone trusts.

Across more than 1.5 billion deliveries for 360+ enterprise customers in 30+ countries at 99.99% uptime, Locus has produced over $320M in documented logistics cost savings and removed more than 800 million miles from the road. Locus has been recognized by Gartner for seven consecutive years, including the 2026 Gartner Hype Cycle for Supply Chain Execution and Logistics Technologies, is a Leader in Transportation Management Systems in the QKS Group SPARK Matrix, and ranked #1 in Route Planning on G2’s 2026 Best Software Awards.

In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently.

Request a Locus fleet utilization assessment to see your peak-to-average ratio and the ceiling it implies.

Also Read: Dispatch Performance Analytics: 8 KPIs Every Logistics Manager Should Track