Government fleets should not use one universal mileage threshold to decide whether a vehicle is underutilized. A defensible utilization standard combines mileage with reservation activity, days in use, vehicle availability, mission requirements, operating cost, location, and demand for comparable vehicles.
For federal, state, and local government fleets, the goal is not to force every vehicle above an arbitrary number. It is to establish consistent thresholds that identify which assets deserve closer review while protecting the vehicles agencies genuinely need to deliver public services.
Key Takeaways
A fleet utilization threshold is a predefined level of activity used to identify vehicles that may require additional review.
Examples might include:
The threshold is not necessarily the final decision.
It is a screening tool.
For example:
A government fleet might flag passenger sedans that travel fewer than 4,000 miles annually.
That does not mean every sedan below 4,000 miles should automatically be removed.
It means those vehicles deserve a closer look.
The fleet manager should then ask:
This distinction is critical.
A threshold should help fleet managers find questions.
It should not answer them automatically.
Mileage is attractive because it is simple.
Most fleets can obtain odometer readings, and annual mileage is easy to compare across vehicles.
Mileage can help identify:
But mileage measures distance.
It does not measure the full operational value of a vehicle.
Consider two county vehicles that each travel 3,000 miles per year.
Vehicle A:
Vehicle B:
The mileage is identical.
The utilization story is not.
Agile Fleet’s Fleet Utilization Benchmarking Guide specifically notes that mileage alone should never determine whether a vehicle remains in the fleet and recommends evaluating it alongside operational demand, reservation frequency, and mission requirements.
Government fleet decisions often affect more stakeholders than private fleet decisions.
A right-sizing recommendation may need to be explained to:
A statement such as:
“This vehicle only drove 3,000 miles last year.”
may be true.
But it does not necessarily demonstrate that the vehicle is unnecessary.
A stronger government fleet recommendation might say:
“This vehicle completed 18 trips last year, was used on 14% of available business days, costs $8,200 annually, has no specialized mission, and has three comparable vehicles at the same site with available capacity.”
That is much harder to challenge.
The purpose of a utilization threshold is therefore not just to identify low-use vehicles.
It is to create a consistent, documented process that supports defensible decisions.
1. Mileage
Mileage should remain part of the analysis.
Track:
Useful questions include:
Low mileage is most meaningful when other utilization measures are low as well.
Trip frequency helps distinguish an active low-mileage vehicle from one that rarely leaves the parking lot.
Track:
For example:
A city inspection vehicle may accumulate limited mileage because nearly all trips occur within a compact service area.
If it is used four days per week, calling it underutilized based only on mileage would be misleading.
Reservation activity provides the missing context.
Read How to Benchmark Fleet Utilization: 10 Metrics Every Fleet Manager Should Track for a broader utilization measurement framework.
A vehicle cannot be evaluated fairly if it was not actually available.
Consider:
Suppose Vehicle A was used on 70 of 200 available workdays.
Vehicle B was used on 70 days but was available for only 110 because of extended repairs.
Their annual trip counts are identical.
Their effective utilization is very different.
Government fleets should therefore distinguish between:
calendar time
and
available time.
This becomes especially important when older vehicles are being evaluated for replacement or retirement.
A vehicle with modest utilization but very low cost may not require urgent action.
A vehicle with equally modest utilization and rapidly increasing maintenance costs deserves much closer attention.
Review:
The most compelling right-sizing candidates often combine:
low utilization + high operating cost.
Agile Fleet’s benchmarking guidance identifies that combination as a strong signal for reassignment, retirement, or replacement and recommends pairing utilization with operating cost when presenting recommendations to leadership.
A single threshold should rarely apply to every asset.
Government fleets may include:
A general-purpose sedan can often be compared with other sedans.
A specialized inspection truck should not necessarily be compared with the sedan pool.
Set thresholds within appropriate groups.
For example:
General-purpose shared sedans
may have relatively high expected utilization.
Specialized response vehicles
may have lower utilization but strong mission justification.
The purpose of segmentation is to compare vehicles serving reasonably similar functions.
Fleet-wide averages can hide local imbalances.
One county facility may have vehicles sitting idle while another struggles to meet demand.
Track:
A vehicle below the utilization threshold at Location A may be unnecessary there but extremely useful at Location B.
That makes reassignment a better decision than disposal.
Agile Fleet’s benchmarking framework specifically recommends comparing department and location activity because one site may have excess capacity while another experiences shortages.
Finally, document what the vehicle actually supports.
Questions include:
Low utilization can be acceptable when the consequence of nonavailability is high.
Government fleets should be able to explain that exception.
A specialized vehicle retained for a documented mission is very different from a lightly used sedan retained simply because a department has historically had one.
Consider a policy that states:
Any vehicle traveling fewer than 5,000 miles annually is underutilized.
That sounds objective.
But it could incorrectly flag:
At the same time, it could fail to flag:
Mileage is therefore better used as a screening measure than as a universal rule.
Instead of relying on one metric, create a multi-factor review.
For example:
Flag a general-purpose vehicle when one or more conditions occur:
This creates the review list.
For flagged vehicles, evaluate:
Review:
Determine whether demand could be met through:
Classify the asset:
This approach preserves consistency without letting one arbitrary number determine the outcome.
Government fleets do not need perfect benchmarks before getting started.
Use your own fleet history.
Create peer groups by:
Longer history is even better when demand is seasonal.
Include:
Look for obvious differences among similar vehicles.
Ask:
Rather than borrowing an arbitrary national target, determine what normal performance looks like inside your organization.
For example:
If most comparable vehicles are used on 100 to 150 days annually, assets used on fewer than 40 may deserve review.
The exact numbers will depend on your fleet.
Apply the proposed standard to your vehicle inventory.
Review the vehicles it flags.
If many clearly necessary assets appear, the threshold may be too blunt.
If it flags only obviously low-use assets, it may be useful.
Define legitimate reasons a vehicle may remain below the threshold.
Examples include:
Require the reason to be documented rather than assumed.
Fleet demand changes.
Revisit standards as:
Utilization benchmarking should be an ongoing management process rather than a once-a-year exercise.
Use a Review Range Instead of a Hard Cutoff.
The vehicle performs within the expected range for its peer group.
No action is required beyond ongoing monitoring.
Utilization is meaningfully below the peer-group norm.
Investigate:
The vehicle shows several concerning signals, such as:
This approach is often more useful than declaring:
“Anything under 5,000 miles must go.”
It acknowledges that fleet decisions involve degrees of evidence.
Utilization thresholds help identify potentially excess capacity.
Reservation denials help identify the opposite problem.
Before removing several low-use vehicles, look at:
If denial rates are already increasing, aggressive reductions may create service problems.
If low-use vehicles coexist with very low denial rates and abundant alternatives, the right-sizing case becomes stronger.
Read How to Use Reservation Denials to Decide Whether Your Fleet Needs More Vehicles for the complete framework.
A government fleet may have dozens or hundreds of assets below its utilization threshold.
Fleet teams may not have time to investigate all of them immediately.
Cost can help prioritize.
Start with vehicles showing:
low utilization + high annual cost
Then review:
These assets often present the clearest financial opportunity.
A low-use vehicle approaching replacement is particularly important.
The question becomes:
Should we spend public funds to replace this capacity for another lifecycle?
For a financial comparison framework, read How to Calculate Cost Per Reservation in a Shared Fleet.
Utilization thresholds can become contentious when departments believe fleet is trying to take away their vehicles.
The strongest response is transparency.
Show:
Avoid presenting the threshold as a punishment.
The message should be:
We are using the same process to evaluate comparable vehicles across the organization.
That helps shift the conversation from ownership to transportation need.
If a department has a legitimate mission exception, document it.
If not, the discussion can focus on how shared fleet capacity will continue serving its employees.
Manual mileage reports can identify vehicles that move very little.
A broader fleet management system can add context.
Useful information includes:
Instead of seeing:
Vehicle 214: 3,200 annual miles
the fleet manager can see:
Vehicle 214: 3,200 miles, 142 completed trips, used on 118 business days, low maintenance cost, and frequent department demand.
That tells a very different story.
Another vehicle might show:
Vehicle 389: 4,800 miles, 17 trips, used on 14 days, $9,100 annual cost, and several comparable vehicles available nearby.
The mileage threshold alone would make the vehicles look relatively similar.
Connected operational data reveals which one deserves attention.
Forsyth County, North Carolina, demonstrates why government right-sizing works better when decisions are supported by several months of operational evidence rather than a single vehicle metric.
The county used FleetCommander utilization reporting to identify underused vehicles, reassign capacity, and reduce unnecessary fleet growth. The result contributed to more than $800,000 in savings while maintaining transportation availability for employees.
The important lesson is not that Forsyth County found one magic utilization percentage.
It used operational data to determine whether individual vehicles were earning their place in the fleet.
That allowed leadership to evaluate right-sizing decisions based on documented demand rather than anecdotal claims.
Read Part 1: Forsyth County, NC's Fleet Success for more on how the county approached fleet modernization and cost reduction.
For each peer group, document:
Example:
General-purpose sedans
Example:
Flag vehicles with:
Before recommending action, review:
Record:
That creates consistency and an audit trail around the right-sizing process.
Mileage measures distance, not complete operational demand.
Different vehicle classes and missions require different expectations.
Vehicles that spend significant time in maintenance cannot be evaluated as though they were continuously available.
Government fleet demand may fluctuate with seasons, projects, weather, and program schedules.
Two equally underused vehicles may create very different financial consequences.
A threshold should initiate analysis.
An appropriate benchmark today may no longer fit the fleet several years from now.
Government fleets should not use one mileage number or universal utilization percentage to decide whether vehicles stay or leave the fleet.
A more defensible utilization threshold combines:
The threshold should identify vehicles that need review.
It should not make the decision automatically.
For public-sector fleets, this approach provides two advantages.
It helps identify genuine opportunities to reduce unnecessary vehicle costs.
And it gives fleet managers the documented evidence needed to explain why a vehicle should be retained, reassigned, pooled, replaced, or removed.
The best utilization benchmark is therefore not the strictest number.
It is the standard that consistently separates necessary fleet capacity from capacity the organization can serve more efficiently another way.
Start with one high-volume vehicle class, such as general-purpose sedans, SUVs, or pickups.
Review at least 12 months of:
Identify the normal range within your own fleet.
Then establish a review threshold that flags meaningful outliers rather than automatically removing vehicles.
For every flagged asset, add mission, location, demand, and alternative-capacity information before recommending action.
FleetCommander helps government fleets connect utilization, reservations, vehicle availability, department demand, maintenance information, and reporting so right-sizing decisions can be supported with consistent operational evidence.
Explore FleetCommander for Government Fleets to see how better utilization data can support defensible right-sizing, stronger budget decisions, and lower long-term fleet costs.