How Government Fleets Should Set Vehicle Utilization Thresholds Without Relying on Mileage Alone

16 minute read

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

Mileage is useful, but it should not be the sole basis for a government fleet right-sizing decision.
Utilization thresholds should vary by vehicle class, mission, location, and operating requirements.
A threshold should trigger review rather than automatic vehicle removal.
Reservation frequency, availability, cost, downtime, and unmet demand provide important context.
Government fleets should establish internal benchmarks using historical data and review them regularly rather than copying a universal industry percentage.
Fleet management software can make utilization standards more defensible by connecting reservations, actual use, departments, vehicle status, and cost data.

What Is a Fleet Utilization Threshold?

A fleet utilization threshold is a predefined level of activity used to identify vehicles that may require additional review.

Examples might include:

Annual mileage below a certain amount
Fewer than a certain number of trips
Low percentage of available days used
Long periods of inactivity
High cost per utilized vehicle
Low reservation frequency

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:

How often is the vehicle used?
Are the trips short but frequent?
Does it serve a specialized purpose?
Is another vehicle available?
How much does it cost?
Is demand increasing or decreasing?
What happens if the vehicle is removed?

This distinction is critical.

A threshold should help fleet managers find questions.

It should not answer them automatically.

Why Mileage Became the Default Fleet Benchmark

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:

Vehicles that barely move
Assets accumulating unusually high use
Imbalances among similar vehicles
Replacement timing
Maintenance needs

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:

Completes several short trips every week
Supports inspections within a small geographic area
Is reserved regularly
Has little downtime

Vehicle B:

Completes a few long-distance trips
Sits unused for weeks at a time
Has similar vehicles available nearby

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.

Why Government Fleets Need More Defensible Utilization Standards

Government fleet decisions often affect more stakeholders than private fleet decisions.

A right-sizing recommendation may need to be explained to:

Department leaders
Finance
Procurement
Agency executives
Elected officials
Auditors
Employees who rely on the vehicles

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.

Seven Measures to Use When Setting Government Fleet Utilization Thresholds

1. Mileage

Mileage should remain part of the analysis.

Track:

Annual mileage
Monthly mileage
Mileage trends over time
Mileage compared with similar vehicles
Mileage by department
Mileage by location

Useful questions include:

Is the vehicle consistently below similar assets?
Is mileage declining?
Is high mileage concentrated among only a few vehicles?
Does mileage align with reservation activity?

Low mileage is most meaningful when other utilization measures are low as well.

2. Reservation or Trip Frequency

Trip frequency helps distinguish an active low-mileage vehicle from one that rarely leaves the parking lot.

Track:

Reservations per month
Completed trips
Days used
Repeat users
Seasonal activity

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.

3. Percentage of Available Time Used

A vehicle cannot be evaluated fairly if it was not actually available.

Consider:

Maintenance
Repairs
Recalls
Accident damage
Inspections
Operational holds

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.

4. Operating Cost

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:

Fuel
Maintenance
Repairs
Insurance
Registration
Depreciation
Administrative expense where available

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.

5. Vehicle Class

A single threshold should rarely apply to every asset.

Government fleets may include:

Sedans
SUVs
Pickup trucks
Passenger vans
Cargo vans
Specialty equipment
Emergency-response vehicles
Accessible vehicles

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.

6. Location and Department Demand

Fleet-wide averages can hide local imbalances.

One county facility may have vehicles sitting idle while another struggles to meet demand.

Track:

Utilization by location
Utilization by department
Reservation denials
Available substitute vehicles
Driver demand

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.

7. Mission Requirement

Finally, document what the vehicle actually supports.

Questions include:

Is the vehicle tied to a specific public service?
Does it carry specialized equipment?
Is immediate access required?
Does it provide emergency backup?
Is another vehicle realistically available?
What happens operationally if it is removed?

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.

Why One Universal Mileage Standard Can Produce Bad Decisions

Consider a policy that states:

Any vehicle traveling fewer than 5,000 miles annually is underutilized.

That sounds objective.

But it could incorrectly flag:

Frequent short-trip vehicles
Seasonal vehicles
Remote vehicles
Specialized vehicles
Backup units
Assets unavailable for significant maintenance periods

At the same time, it could fail to flag:

A vehicle making a few long trips but sitting idle most of the year
A costly asset with poor reservation activity
A vehicle at an overcapacity location
A high-mileage vehicle performing trips that another fleet resource could absorb

Mileage is therefore better used as a screening measure than as a universal rule.

A Better Government Fleet Threshold Model

Instead of relying on one metric, create a multi-factor review.

For example:

Level 1: Automatic Review Trigger

Flag a general-purpose vehicle when one or more conditions occur:

Low annual mileage
Low trip frequency
Long idle periods
Low percentage of available days used

This creates the review list.

Level 2: Operational Context

For flagged vehicles, evaluate:

Department
Location
Vehicle class
Mission
Seasonal demand
Maintenance downtime
Reservation availability

Level 3: Financial Context

Review:

Operating cost
Maintenance trend
Replacement timing
Cost per reservation
Potential capital avoidance

Level 4: Alternative Capacity

Determine whether demand could be met through:

Another existing vehicle
Shared motor pool capacity
Reassignment
Temporary rental
Another nearby site

Level 5: Recommended Action

Classify the asset:

Retain
Reassign
Pool
Replace
Monitor
Remove
Do not replace

This approach preserves consistency without letting one arbitrary number determine the outcome.

How to Establish Your First Utilization Thresholds

Government fleets do not need perfect benchmarks before getting started.

Use your own fleet history.

Step 1: Group Comparable Vehicles

Create peer groups by:

Vehicle class
Mission
Location where appropriate

Step 2: Review at Least 12 Months of Activity

Longer history is even better when demand is seasonal.

Include:

Mileage
Trips
Days used
Availability
Costs

Step 3: Identify the Highest and Lowest Performers

Look for obvious differences among similar vehicles.

Ask:

Why does one sedan complete 200 trips while another completes 30?
Why does one location have much lower utilization?
Are legitimate mission differences involved?

Step 4: Establish an Internal Baseline

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.

Step 5: Test the Threshold

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.

Step 6: Document Exceptions

Define legitimate reasons a vehicle may remain below the threshold.

Examples include:

Emergency function
Specialized equipment
Remote service requirement
Accessibility need
Seasonal mission

Require the reason to be documented rather than assumed.

Step 7: Review the Threshold Regularly

Fleet demand changes.

Revisit standards as:

Departments change
Shared pools expand
Locations consolidate
Policies evolve
New vehicle classes enter the fleet

Utilization benchmarking should be an ongoing management process rather than a once-a-year exercise.

Use a Review Range Instead of a Hard Cutoff

Use a Review Range Instead of a Hard Cutoff.

Green: Normal Utilization

The vehicle performs within the expected range for its peer group.

No action is required beyond ongoing monitoring.

Yellow: Review

Utilization is meaningfully below the peer-group norm.

Investigate:

Mission
Cost
Availability
Location
Alternatives

Red: Strong Right-Sizing Candidate

The vehicle shows several concerning signals, such as:

Very low use
High cost
No unique mission
Available substitutes
Declining utilization

This approach is often more useful than declaring:

“Anything under 5,000 miles must go.”

It acknowledges that fleet decisions involve degrees of evidence.

How Reservation Denials Protect Against Thresholds That Are Too Aggressive

Utilization thresholds help identify potentially excess capacity.

Reservation denials help identify the opposite problem.

Before removing several low-use vehicles, look at:

How often drivers cannot obtain vehicles
Which vehicle classes are being denied
Which locations are affected
What employees do after a denial

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.

How Cost Helps Prioritize Which Low-Use Vehicles to Review First

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:

Maintenance expense
Age
Replacement timeline
Fuel
Insurance
Parking
Cost per reservation

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.

How to Handle Department Pushback

Utilization thresholds can become contentious when departments believe fleet is trying to take away their vehicles.

The strongest response is transparency.

Show:

The standard being applied
How similar vehicles perform
The department’s actual usage
Annual vehicle cost
Available alternatives
Peak-period demand
The proposed service model

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.

How Fleet Management Software Makes Utilization Thresholds More Defensible

Manual mileage reports can identify vehicles that move very little.

A broader fleet management system can add context.

Useful information includes:

Reservations
Completed trips
Mileage
Driver activity
Vehicle availability
Department
Location
Key access
Maintenance status
Reservation denials
Operating costs

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.

Case Study: Forsyth County Uses Utilization Data to Make Defensible Fleet Reductions

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.

A Practical Government Fleet Utilization Threshold Worksheet

For each peer group, document:

Vehicle Group

Example:

General-purpose sedans

Baseline Measures

Median annual mileage
Median trips per vehicle
Median days used
Average availability
Average annual operating cost

Review Triggers

Example:

Flag vehicles with:

Significantly lower mileage than peers
Significantly fewer trips
Long idle periods
High cost relative to use

Required Context

Before recommending action, review:

Mission
Location
Department
Vehicle availability
Maintenance downtime
Seasonal demand
Available alternatives

Potential Action

Retain
Reassign
Pool
Monitor
Replace
Remove
Do not replace

Documentation

Record:

Why the vehicle was flagged
Which data was reviewed
Department explanation
Final decision
Date for next review

That creates consistency and an audit trail around the right-sizing process.

Common Mistakes When Setting Fleet Utilization Thresholds

Mistake 1: Using Mileage Alone

Mileage measures distance, not complete operational demand.

Mistake 2: Using the Same Threshold for Every Vehicle

Different vehicle classes and missions require different expectations.

Mistake 3: Ignoring Availability

Vehicles that spend significant time in maintenance cannot be evaluated as though they were continuously available.

Mistake 4: Looking at One Month

Government fleet demand may fluctuate with seasons, projects, weather, and program schedules.

Mistake 5: Ignoring Cost

Two equally underused vehicles may create very different financial consequences.

Mistake 6: Treating the Threshold as an Automatic Removal Rule

A threshold should initiate analysis.

Mistake 7: Failing to Review the Standard

An appropriate benchmark today may no longer fit the fleet several years from now.

Related Resources

The Bottom Line

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:

Mileage
Trip frequency
Days used
Availability
Operating cost
Vehicle class
Department or location demand
Mission requirements
Available alternatives

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.

Next Steps

Start with one high-volume vehicle class, such as general-purpose sedans, SUVs, or pickups.

Review at least 12 months of:

Mileage
Trips
Days used
Availability
Operating cost

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.

Brian Hall