A university should consider moving a department-assigned vehicle into a shared motor pool when the vehicle has consistently low utilization, similar shared vehicles can meet the department’s demand, and broader access would improve fleet efficiency without disrupting campus operations. The decision should be based on utilization, trip patterns, vehicle availability, department needs, cost, and the consequences of not having a dedicated vehicle.
For colleges and universities, this analysis can uncover opportunities to reduce unnecessary vehicle ownership while improving access across campus. The goal is not to eliminate assigned vehicles. It is to determine which vehicles genuinely require dedicated access and which transportation needs can be served more efficiently through sharing.
Key Takeaways
Department-assigned vehicles are common on university campuses.
Facilities may have vehicles for maintenance crews. Admissions may maintain vehicles for recruiting travel. Academic departments may use vans for fieldwork. Athletics, advancement, research teams, mail services, and other groups may have vehicles dedicated to their operations.
Some of these assignments make sense.
Others continue because:
The department has always had the vehicle
Over time, those assumptions can produce a campus where one department struggles to find vehicles while another has cars parked for days or weeks.
That is particularly expensive because an assigned vehicle continues generating costs whether it is used every day or only a few times each month.
Those costs may include:
A shared motor pool distributes those fixed costs across more users and more productive trips.
Agile Fleet's utilization benchmarking guidance specifically recommends examining whether departments are retaining assigned vehicles despite low usage and whether shared resources could serve the same needs.
The distinction is not simply where the vehicle is parked.
An assigned vehicle generally provides one department or group with priority or exclusive access.
A shared motor pool makes vehicles available across approved users based on actual transportation needs.
That changes the operating model.
With an assigned vehicle, the department essentially reserves capacity continuously.
With a shared vehicle, the organization reserves capacity only when someone actually needs it.
That distinction is what creates the potential efficiency.
Imagine three university departments that each own four vehicles.
If each department needs all four vehicles only during occasional peak periods, the university may own 12 vehicles even though simultaneous campus-wide demand rarely approaches 12.
A shared model allows fluctuations in one department to be balanced by lower demand elsewhere.
This is particularly useful on university campuses because demand can vary dramatically throughout the academic year. Admissions, athletics, academic departments, facilities, and student programs rarely experience their busiest periods at exactly the same time.
Agile Fleet's university motor pool guidance notes that fluctuations between departments can make shared capacity more efficient than maintaining separate vehicles for every department's individual peak.
Start with actual activity.
Review at least several months of data and preferably a full year when campus demand is seasonal.
Look at:
Do not rely exclusively on mileage.
A vehicle may accumulate relatively little mileage while supporting frequent short trips around campus.
Another may travel hundreds of miles during one monthly trip but remain unused the rest of the time.
The better question is:
How much transportation demand does this vehicle actually serve?
Compare it with similar vehicles elsewhere on campus.
If one department sedan completes 35 trips per year while comparable shared sedans complete several hundred, that difference deserves investigation.
For a broader utilization framework, see How to Benchmark Fleet Utilization: 10 Metrics Every Fleet Manager Should Track.
Average utilization can hide important demand patterns.
A department may use a vehicle heavily during:
and barely use it during the rest of the year.
That does not automatically justify maintaining dedicated capacity year-round.
Map demand by:
Then compare those periods with availability in the shared pool.
If the department needs four vehicles during six weeks of the year but only one during the remaining 46 weeks, there may be a better way to support the peak.
Options could include:
The objective is to match permanent vehicle ownership with recurring demand rather than the single busiest week of the year.
Some department vehicles should remain assigned.
A vehicle may require dedicated access because it:
In these situations, low utilization alone may not indicate excess capacity.
Document the mission.
Ask:
What would the department be unable to do if this vehicle were no longer dedicated to them?
A specific operational answer supports continued assignment.
“We've always had one” does not.
This distinction helps universities protect genuinely necessary vehicles while identifying assets that are dedicated primarily because of historical practice.
4. Could Existing Motor Pool Vehicles Serve the Same Trips?
Next, compare the assigned vehicle's activity with existing shared capacity.
For every trip or common trip type, ask:
This is critical.
A vehicle can be underutilized and still be necessary if no realistic substitute exists.
Conversely, a department may have a vehicle parked beside a motor pool containing several comparable vehicles with available capacity.
In that scenario, the university is effectively paying for redundant capacity.
The decision becomes much easier to defend when utilization data shows both sides:
Low usage of the assigned vehicle + available capacity in the shared pool.
5. What Does the Assigned Vehicle Actually Cost?
Utilization explains activity.
Cost explains consequence.
Calculate the annual cost of keeping the vehicle assigned.
Depending on available data, consider:
Then compare that expense with the number of trips the vehicle supports.
For shared fleets, cost per reservation can be especially useful.
For example:
Vehicle A costs $8,000 per year and supports 40 trips.
Vehicle B costs $8,000 per year and supports 200 trips.
Both vehicles cost the university the same amount.
But the university is spending five times as much per trip to maintain Vehicle A's capacity.
That does not automatically mean Vehicle A should be pooled.
It does provide a strong reason to investigate.
See How to Calculate Cost Per Reservation in a Shared Fleet for the complete framework.
This is where many pooling proposals fail.
Fleet managers demonstrate low utilization and conclude:
“You don't need this vehicle.”
The department hears:
“You may not have transportation when you need it.”
Those are very different messages.
Instead, evaluate service risk.
If the vehicle enters the shared pool:
Departments are much more likely to accept sharing when the proposed alternative is dependable.
The objective should not be to take away access.
It should be to provide the same or better access with less dedicated capacity.
Look beyond the assigned vehicle itself.
The department may also be:
That information can reveal that the assigned vehicle is not actually meeting the department's transportation needs very well.
For example, if a department maintains two assigned vehicles but still regularly uses the motor pool, the university should ask whether the assigned/shared mix is appropriate.
The opposite can also be true.
If a department generates extensive mileage reimbursement despite a nearby shared fleet, the issue may be motor pool access or availability rather than assigned-vehicle capacity.
Evaluate the entire transportation picture rather than one asset.
Never evaluate the assigned vehicle in isolation.
Ask what happens to the entire shared fleet if it moves into the pool.
Adding an assigned vehicle to a motor pool may:
This is where department-level analysis becomes campus-level right-sizing.
An individual department may see one vehicle changing status.
The university may see an opportunity to avoid buying several vehicles over the next replacement cycle.
No single metric should determine the decision, but the case becomes stronger when several indicators appear together.
Potential signs include:
The combination matters.
A low-use vehicle with a specialized mission may remain appropriate.
A low-use standard sedan beside a well-performing campus motor pool is a very different situation.
Pooling is not always the right answer.
Continued assignment may be appropriate when:
The purpose of a pooling review is not to produce a predetermined outcome.
It is to replace assumptions with evidence.
A simple framework can make department conversations easier.
Evaluate:
If no, continued assignment may be appropriate.
If yes, continue.
Determine whether:
If no, the vehicle may still be necessary.
If yes, continue.
Evaluate:
If the university can maintain reliable access, the vehicle is a strong pooling candidate.
One of the easiest times to reconsider an assigned vehicle is when it reaches replacement age.
The university is already facing a capital decision.
Instead of automatically replacing the vehicle, ask:
Do we need to spend money recreating this dedicated capacity for another seven, eight, or ten years?
If a $35,000 vehicle is lightly used and the motor pool can absorb its demand, not replacing it creates immediate capital avoidance.
It also prevents years of additional:
A replacement cycle therefore becomes a natural right-sizing opportunity.
One reason departments may resist pooling is concern that the analysis is designed to justify a decision already made.
Use consistent metrics.
Compare vehicles using the same:
Avoid comparing a specialized department truck with a general-purpose pool sedan.
Compare like with like wherever possible.
Also account for maintenance downtime.
An assigned vehicle may show low activity because it spent several months unavailable for repair. That raises a vehicle reliability question, not necessarily a pooling question.
Data quality is essential before changing ownership or access models.
University fleets are different from many commercial fleets because activity follows the academic calendar.
Transportation demand can shift around:
A utilization report covering only June and July could make an essential academic-year vehicle appear unnecessary.
A report covering one unusually busy month could make occasional demand appear permanent.
Review at least one complete operational cycle.
For strongly seasonal departments, multiple years are even better.
Universities do not need to make every decision permanent immediately.
A pilot is often the best way to build confidence.
For example, a department could temporarily release two assigned vehicles into the shared pool while the university monitors:
The vehicles can remain physically available during the trial.
If the department's trips are absorbed without disruption, the university now has real evidence supporting permanent consolidation.
If significant service issues appear, the model can be adjusted.
This is often more persuasive than debating forecasts.
Moving an assigned vehicle into a shared pool can feel like a loss of control.
That reaction should be expected.
Agile Fleet's existing guidance on departmentally assigned vehicles notes that successful transitions require both organizational buy-in and clearly defined motor pool policies.
The conversation should therefore focus on what the department gains.
Instead of:
“We're taking your vehicles.”
use the data to demonstrate:
A shared motor pool can remove responsibilities departments may currently handle themselves, including:
A transition is much easier when employees understand the new service model rather than only the vehicle reduction.
For additional guidance, see Getting Driver Buy-In for Fleet Sharing Without Losing Momentum.
The hardest part of assigned-versus-shared analysis is often collecting trustworthy information.
Vehicle data may be spread across:
Fleet management software can help connect:
That allows university fleet managers to answer practical questions.
For example:
This turns the decision from a political discussion into an operational analysis.
FleetCommander’s university fleet management capabilities include centralized reservations, utilization reporting, role-based permissions, secure vehicle access, and departmental billing workflows.
Cornell University provides a useful example of how a university can challenge historical fleet assumptions using actual demand.
Cornell's motor pool once operated more than 230 vehicles. Before fleet management technology was introduced, reservations, dispatching, maintenance records, and billing were largely handled manually, leaving the university with limited utilization information.
After implementing FleetCommander, Cornell gained centralized reservation and utilization data and began evaluating demand by vehicle class and location. Early analysis showed the motor pool was less than 30% utilized.
That information allowed Cornell to make incremental changes rather than impose an immediate fleet reduction.
The university:
Cornell eventually reduced its motor pool substantially while continuing to serve campus transportation needs.
The lesson for other universities is not simply “reduce the fleet.”
It is:
Understand when transportation demand requires dedicated capacity and when the same demand can be served through a more flexible shared model.
Read Cornell University's Fleet Automation for the full story.
Create a list of department-assigned assets by:
Review at least one complete annual cycle when possible.
Include:
Calculate ownership and operating expense.
Flag low-use, high-cost assets for closer review.
Ask the department to explain why dedicated capacity is necessary.
Separate specialized requirements from preference.
Determine whether existing motor pool vehicles could fulfill the department's trips.
Review availability during actual demand periods.
Prioritize assigned vehicles already approaching replacement.
Avoiding an unnecessary purchase may produce the strongest immediate financial return.
Estimate what the same travel would look like using:
Compare both cost and service.
Temporarily move appropriate vehicles into the shared pool.
Do not immediately dispose of them.
Track:
If demand is absorbed successfully, the university can:
The strongest pooling candidates will usually produce the same answer across several dimensions:
Low dedicated demand + available shared capacity + no unique mission + meaningful cost savings.
Related Resources
Continue exploring university motor pools, utilization, fleet sharing, and right-sizing:
Universities should not choose between assigned vehicles and shared motor pools based on philosophy.
They should choose based on demand.
A department-assigned vehicle may make sense when:
A shared motor pool may make more sense when:
The strongest university fleets do not ask whether every vehicle should be shared.
They ask:
Which transportation needs require dedicated capacity, and which can be served more efficiently by capacity the university shares?
Answering that question with utilization, cost, availability, and department-level demand data can improve vehicle access while reducing unnecessary fleet ownership.
Next Steps
Start with department-assigned vehicles approaching replacement within the next one to three years.
For each vehicle, document:
Identify the vehicles where department demand could reasonably be absorbed by existing shared capacity.
Then test the change before committing to another replacement cycle.
FleetCommander helps colleges and universities centralize reservations, monitor utilization, manage driver eligibility, control vehicle access, and compare demand across departments and locations.
Explore FleetCommander for Universities to see how shared fleet data can support campus right-sizing, cost reduction, and more reliable vehicle access.