Fleet Right-Sizing: Two Methods Every Government Fleet Manager Should Know

Government fleet right-sizing uses two primary methods: the Vehicle Allocation Methodology (VAM), which starts with existing fleet data to identify over-allocated assets, and a zero-based mission approach, which starts with operational requirements to define what the fleet should look like. VAM works best when the goal is finding efficiencies in an existing fleet. The mission-based approach works better when the fleet may be undersized, mis-specced, or when you need a long-term asset planning framework. Most government fleets benefit from understanding both.

Why Standard Utilization Analysis Falls Short

The traditional approach to fleet right-sizing is straightforward: pull mileage and engine hours, identify assets below a utilization threshold, and make the case for elimination or reassignment.

This works reasonably well for fleets where driving equals working. But across government operations, that assumption breaks down regularly.

Perimeter patrol vehicles at a correctional facility may log only 10 miles per shift because the perimeter loop is half a mile. A utility van assigned to a campus plumber may log two miles a day while supporting dozens of completed work orders. A wrecker stationed at the entrance to a tunnel may sit idle for months, and be among the most critical assets in the fleet.

In all three cases, standard utilization data points toward elimination or consolidation. The operational reality points the other direction.

Jeffrey Dickman, Equipment Shop Supervisor at the Arizona Department of Corrections' Yuma Complex, described this reality directly in a Fleet Success Show conversation at GFX 2026: "The perimeter guards, they travel around a unit, probably a half mile in one lap, so in a day they travel 10 miles. It's nothing in the traditional utilization. But without it? You've got a big problem. Relative to its mission, it did a lot of work."

This does not mean utilization data is useless. It means utilization data needs context. And the two right-sizing methods described below provide different types of that context.

Method 1: Vehicle Allocation Methodology (VAM)

The Vehicle Allocation Methodology is a structured, data-driven process for identifying whether a fleet's current asset count and composition align with operational needs. The U.S. General Services Administration's Federal Management Regulation requires federal executive agencies to establish and document a VAM, with GSA recommending completion at minimum every five years.

The VAM process typically follows these steps:

Gather fleet data from your FMIS. This includes utilization history (miles, hours, days in service), maintenance cost, assignment history, and downtime records.

Establish a baseline fleet profile. Map each vehicle to the department or function it serves. Identify the mission each asset is meant to support.

Identify utilization outliers. Rather than measuring against a fixed threshold, compare vehicles within the same role or category. Assets in the bottom quartile of their peer group warrant further investigation, not automatic elimination, but a conversation about why they are there.

Assess mission criticality. For every low-utilization asset, ask: does operational policy require this vehicle to exist regardless of how often it moves? Hot-seat spares, emergency response vehicles, and mission-backup units often fall into this category. Criticality assessment typically requires input from department heads and operations staff, not just fleet data.

Score and prioritize. Combining utilization and criticality into a scoring framework produces a defensible list of elimination or reassignment candidates. High-utilization assets are almost certainly needed. Low-utilization, low-criticality assets are candidates for removal. Low-utilization, high-criticality assets, like the wrecker at the tunnel mouth, stay.

The U.S. Navy's recent VAM study, which evaluated more than 49,000 vehicles and identified thousands as candidates for elimination, highlighted mission criticality assessment and stakeholder engagement as essential to producing recommendations that held up under review. Data-driven analysis without operational context produces recommendations that departments will reject, and often should.

Method 2: Zero-Based Mission Analysis

Where VAM starts with the fleet, the zero-based mission approach starts with the work.

The concept mirrors zero-based budgeting: instead of justifying changes to what exists, you define from scratch what the operation requires. What roles need vehicles? What tasks do those vehicles support? When do they need to be available, how many people use them, and what physical requirements does the job place on the vehicle?

Only after that analysis is complete do you compare the result to the existing fleet.

This approach is a heavier lift than VAM. It requires conversations with HR and operations that go well beyond the fleet software. But it produces something VAM does not: a documented, mission-grounded asset plan that serves as a reference for years. When departments add staff, reassign roles, or change operating schedules, you have a framework for translating those changes into fleet requirements.

As Marc Canton, VP of Fleet Strategy at RTA Fleet, described in a Fleet Success Show conversation at GFX 2026: "Every time I've ever done a study like that, we have found that usually they need more vehicles, but we still save money because they need a lower spec than what they're currently getting today."

That last point is important. In many government fleets, the asset count may be defensible but the asset types are wrong. Inspectors driving one-ton trucks. Security personnel in full-size pickups when the job calls for a patrol cart or a compact SUV. The zero-based mission approach surfaces these mismatches in a way that standard utilization analysis cannot.

How to Choose the Right Method

The simplest way to choose between these approaches is to answer one question honestly: do you believe your fleet has too many vehicles, or too few?

If the answer is too many (or if you are under external pressure to demonstrate efficiency) start with VAM. It is data-forward, auditable, and produces actionable recommendations with a well-established federal precedent.

If the answer is too few (or if you suspect your current fleet is the wrong mix for what your organization actually does) start with the zero-based mission approach. It requires more upfront work but produces a foundation for long-term planning that VAM alone cannot provide.

In practice, many fleet managers use both over time: VAM to manage current fleet composition and identify near-term efficiencies, and the mission-based approach when major operational changes require a fresh look at what the fleet is actually trying to do.

Using Your FMIS to Support the Analysis

Neither approach requires starting from scratch. A well-maintained fleet management information system is the starting point for any right-sizing effort.

Utilization history, maintenance cost by asset, assignment logs, and downtime records are the foundation of VAM analysis. Mission data, like shift schedules, work order volumes by department, operational requirements by role, supplements the utilization picture with the context that makes recommendations defensible.

RTA Fleet's Fleet360 is built to centralize exactly this kind of data in a single system, making it accessible for the kind of analysis that right-sizing requires. The goal is not to let the software make the decisions, as Jeff Dickman noted at GFX 2026, "The software doesn't know your mission. It doesn't care. You've got to take your mission, take the data, and justify your data." The goal is to build the clearest possible picture from the data you have, then apply judgment to what the data is showing you.

Starting Points for Fleet Managers

If you are beginning a right-sizing process for the first time, or revisiting one after several years:

Pull your utilization data and sort it by asset type category. Identify the bottom quartile within each category and begin your investigation there.

For assets in the bottom quartile, have a conversation with the departments using them before drawing any conclusions. Understand the operational role, the coverage schedule, and whether the asset serves a hot-seat, backup, or emergency-response function.

For any asset targeted for potential elimination, document the mission criticality assessment alongside the utilization data. Defensible recommendations require both.

If your fleet may be undersized or mis-specced, begin a role-mapping exercise with HR and operations. Build the mission-to-vehicle requirements framework before you engage leadership on asset requests.

Right-sizing a government fleet takes time, organizational trust, and a willingness to do the investigative work that data alone cannot do. But the fleets that have done it well consistently come out with better asset utilization, lower total costs, and a much stronger position when talking to leadership about what they need.