Miya Bholat
Oct 16, 2026
Municipal Fleet Utilization: Setting Minimum Targets
A minimum utilization target for a municipal fleet is a documented threshold that determines when a vehicle's continued assignment must be justified, reassigned, pooled, or discontinued. A practical starting point for general purpose municipal vehicles is to evaluate annual mileage thresholds between 3,000 and 6,000 miles, then adjust them to actual department demand and vehicle class. Within fleet management software, the target becomes an enforceable policy when it includes a measurement period, written exceptions, annual reviews, and clear accountability.
Without that policy, an underused vehicle can remain assigned for years because someone might eventually need it. Departments retain assets without demonstrating demand, maintenance and ownership costs continue, and fleet managers face difficult budget questions without consistent evidence.
Key Takeaways
- Start with a defensible baseline. Use historical municipal fleet data and comparable public sector thresholds rather than adopting one universal mileage requirement.
- Set targets by vehicle class. Administrative vehicles, heavy equipment, seasonal units, and emergency vehicles need different utilization measures.
- Require written exceptions. Every vehicle below its target needs a documented operational justification and an expiration date for that approval.
- Review utilization annually. Evaluate a complete year of activity and monitor exceptions throughout the year.
- Connect targets to financial decisions. Use utilization evidence when approving replacements, departmental chargebacks, and additional vehicle requests.
- Make departments accountable. Fleet management should monitor compliance while department heads justify continued assignments.
Why Municipal Fleets Need a Minimum Utilization Target
A utilization target establishes who must explain an underused vehicle, what evidence they must provide, and who can approve its retention. Without those rules, department preferences can outweigh taxpayer value.
A 2026 Salt Lake County performance audit shows the consequences. According to the County Auditor's August 2026 report, 80 of 147 vehicles, or 54%, fell below the county's 6,000 mile annual threshold. The audit also found that 7 of 11 motor pool vehicles, approximately 64%, received no use during 2025. Several departments lacked documented utilization reviews, even when continued vehicle use could be reasonably justified.
The audit found no evidence of vehicle misuse. Instead, it exposed weaknesses in oversight, documentation, and reporting.
For government fleet management, the difference between having a target and enforcing it is significant:
- Without a written policy: Departments keep lightly used vehicles, decisions depend on individual managers, and auditors may question retention.
- With a written policy: Every department faces the same review process, exceptions require evidence, and decisions have an auditable record.
The objective is not to remove every lightly used vehicle. It is to demonstrate why each publicly funded asset deserves continued investment.
What Counts as a Minimum Utilization Target
Miles, Hours, or Days Used
Municipal fleets generally measure minimum usage using three operational indicators:
- Annual mileage: Best for administrative sedans, pickups, vans, and general transportation vehicles.
- Engine hours: Better for stationary or slow moving equipment, including loaders, sweepers, and utility equipment.
- Days used: Useful for shared motor pools, seasonal vehicles, and equipment with irregular operating schedules.
A fleet utilization rate measures how much available capacity the organization uses. A minimum utilization target turns that information into a rule for reviewing vehicle assignments.
For example, a public works truck may accumulate relatively few miles while completing substantial work at job sites. Mileage alone would misrepresent its contribution.
Why a Single Number Is Not Enough
A complete minimum utilization policy contains three elements: a measurable threshold, a review period, and a documented exception process.
A sedan traveling 2,500 miles annually might fall below a 5,000 mile target. That should trigger a review, not immediate disposal.
The department might demonstrate that the vehicle provides essential field coverage. Alternatively, the review could identify an opportunity to share transportation across departments.
The eventual decision should follow the same evidence based process used for fleet rightsizing, while the minimum target determines when that evaluation becomes mandatory.
The policy should also name the approving authority, justification deadline, and procedure for appealing a decision.
How to Set Your Minimum Utilization Target
Start From Real Public-Sector Thresholds
Public fleet policies provide useful reference points, but their thresholds vary substantially.
Salt Lake County's August 2026 audit documented a 6,000 mile annual benchmark. An earlier Montgomery County, Maryland, Inspector General review identified 215 vehicles traveling fewer than 5,000 miles in fiscal year 2011. That review also reported approximately $522,000 in savings from a previous reduction in the county's light vehicle fleet.
Oklahoma provides another lesson in how thresholds and enforcement can change. Its 2023 statewide fleet review found that 7,955 vehicles traveled fewer than 12,000 miles annually. Later in 2023, the state reported 655 vehicles returned and approximately $5.9 million in projected savings.
The state's June 2025 fleet reduction update described renewed agency reviews, identified vehicles for return, and centralized reporting improvements.
These examples demonstrate why a municipal fleet should not automatically copy a state threshold. Use 3,000 to 6,000 annual miles as a possible initial screening range for low mileage municipal transport vehicles, then verify whether local operations support it.
Calibrate to Your Own Fleet Data
Begin with 12 complete months of actual vehicle usage. A shorter reporting period can incorrectly classify snow equipment, seasonal inspection vehicles, and emergency backup units.
Build the proposed target using this process:
- Collect: Export mileage, engine hours, days used, vehicle class, assignment, and downtime for each unit.
- Group: Separate comparable vehicles by operational role and department.
- Analyze: Sort annual usage from lowest to highest and identify a natural drop in the distribution.
- Validate: Review vehicles near that point with department managers before approving the threshold.
Use trip and mileage tracking to compare recorded mileage with actual trips and investigate missing or inconsistent data.
For example, suppose most administrative sedans travel between 5,500 and 9,000 miles annually, while a smaller group travels below 3,000. A 4,000 mile review threshold might separate normal operating vehicles from those requiring justification.
That figure is illustrative, not a universal benchmark. Confirm the result against the department's operational requirements before adoption.
Set Different Targets by Vehicle Class
A municipal fleet can operate sedans, sanitation trucks, construction equipment, and emergency vehicles within the same organization. One mileage standard cannot represent all their responsibilities.
Class based targets should reflect actual operating conditions and the information available through GPS tracking and telematics.
The following framework provides starting points for local calibration.
| Vehicle Class | Suggested Minimum Basis | Exception Considerations |
|---|---|---|
| Administrative sedans and vans | Annual miles, evaluate 3,000 to 6,000 | Limited routes or mandated assignments |
| General purpose pickups | Annual miles, calibrated by duty | Field inspections and job site work |
| Heavy equipment | Annual engine hours | Specialized equipment and seasonal projects |
| Snow and seasonal units | Days or hours used during operating season | Weather conditions and emergency readiness |
| Motor pool vehicles | Days booked and actually used | Shared capacity and peak demand |
| Emergency and backup units | Mission readiness and verified demand | Response requirements and approved reserve capacity |
These are proposed review measures, not published minimum requirements for every class.
The U.S. Department of Energy's Vehicle Allocation Methodology guidance supports using mileage, operating hours, mission requirements, and other utilization criteria to evaluate fleet needs.
Building the Exception and Mission-Essential Carve-Out
A minimum target must recognize that some municipal assets provide value through availability rather than frequent use.
Emergency response vehicles, specialized equipment, and backup units may justify continued ownership even when they operate infrequently.
For public works fleet management, particularly, low annual usage might reflect unpredictable seasonal demand rather than unnecessary capacity.
Common exceptions include:
- Emergency response: Vehicles required to meet response and coverage obligations.
- Seasonal operations: Snow removal, storm cleanup, and seasonal maintenance equipment.
- Backup capacity: Units retained to maintain service during failures or demand surges.
- Specialized or grant funded equipment: Assets with limited applications or funding restrictions.
An exception should establish the vehicle's mission, required availability, alternatives considered, approving official, and next review date.
This also addresses the ghost assignment problem. A vehicle may remain attached to a department because a particular employee traditionally controls it, even though operational demand no longer supports dedicated ownership.
An unsupported assignment is not a legitimate exception. Require evidence of actual need, then reassess that need each year.
Keep approval forms, supporting records, and expiration dates together through a vehicle document management system so reviewers can distinguish an approved exception from an undocumented arrangement.
An exception should never become permanent merely because nobody reopened the decision.
Enforcing the Target: The Annual Review Cycle
The Review and Notification Workflow
A policy becomes enforceable when every department receives the same information, deadlines, and opportunity to justify its vehicles.
Start by defining the review year, approved targets, and responsible decision makers. Fleet management should then use consistent fleet reports and dashboards to identify vehicles falling below their assigned thresholds.
A practical annual workflow follows:
For every vehicle, preserve the actual usage, applicable target, department response, exception decision, approver, and effective date.
Tying the Target to Chargebacks and Budget
Minimum targets influence behavior when departments see their financial consequences.
A department retaining an underused vehicle should understand its annual ownership and maintenance costs. Internal chargebacks can make those costs visible, while approved mission exceptions protect genuine operational needs.
Replacement approval provides another enforcement point. Before approving another vehicle, require departments to demonstrate that their existing assets meet minimum usage standards or have valid exceptions.
Include utilization alongside government fleet replacement priorities so departments cannot automatically replace an underused vehicle simply because it reaches its planned retirement age.
A useful budget approval rule is: No replacement or additional dedicated assignment without a current utilization review and documented operational justification.
Common Reasons Minimum Targets Fail
Even a well designed policy can fail when departments do not follow the review process.
The most common problems are:
- Department politics: Vehicle assignments become perceived entitlements instead of operational decisions.
- Outdated thresholds: Targets remain unchanged despite new service areas, staffing, or operating responsibilities.
- Weak exception controls: Managers approve verbal or permanent exceptions without reviewing evidence.
- Fragmented records: Departments maintain inconsistent mileage, assignment, and maintenance information.
The final problem can undermine the entire policy. A vehicle may appear underused because mileage reports are incomplete, or highly utilized when records contain duplicated activity.
Reducing inconsistent fleet data across teams requires consistent vehicle IDs, reporting periods, meter readings, and departmental assignments.
AUTOsist can support that process by keeping vehicle usage, reporting, service history, and maintenance records accessible for annual reviews. However, the municipality still needs written policies, responsible reviewers, and consistent enforcement.
Frequently Asked Questions
-
Do federal minimum mileage requirements apply to municipal fleets?
No. Federal mileage guidelines do not automatically apply to city or county fleets. Municipalities generally establish their own thresholds, subject to applicable state and funding requirements. -
Should departments drive more miles just to meet the minimum target?
No. Unnecessary driving increases costs without improving fleet efficiency. A vehicle below its target should undergo an assignment review instead. -
How should vehicle downtime affect a utilization review?
Record downtime separately from actual usage. Determine whether low utilization resulted from limited demand or extended repairs before making a retention decision. -
What evidence is needed to justify keeping an underused municipal vehicle?
Departments should provide trip records, operational requirements, response time needs, and reasons shared vehicles cannot meet demand. The justification should receive written approval. -
Can departments still face chargebacks for approved low utilization vehicles?
Yes. Approved exceptions justify vehicle retention but do not eliminate ownership and maintenance costs. Chargebacks should follow the municipality's documented cost allocation policy.
