Car Rental Fleet Optimization
- Fleet Optimization
- Demand Forecasting
- Dynamic Pricing
- Revenue Management
Project Snapshot
Client
Regional Car Rental Operator
Location
40+ Branch Locations Across the United States
Industry
Car Rental & Mobility
Services
- Fleet Optimization & Scheduling
- Demand Forecasting
- Dynamic Pricing & Revenue Management
1. Introduction
A regional car rental operator had a fleet of roughly 3,000 vehicles and strong demand across more than 40 locations. But too many vehicles were sitting idle while nearby branches were running short.
The problem was not a lack of cars or customers. Fleet scheduling was managed through spreadsheets, pricing was updated manually, and the two teams worked from different systems.
As a result, vehicles were often in the wrong place when demand arrived, while prices could not react quickly to changing market conditions.
The client initially saw this as two separate problems: fleet utilization and pricing. DataTheta found that both came from the same issue. Scheduling and revenue decisions were being made without a shared view of demand, and availability.
2. Business Context
The client was a mid-size car rental operator managing approximately 3,000 vehicles across more than 40 US branch locations.
The business had grown through a mix of corporate-owned locations and franchise partners. Over time, its operating systems had grown in the same way. Reservation data sat in one platform, fleet information in another, maintenance records in separate tools, and many local scheduling decisions were still managed in spreadsheets.
This created a major operational problem. Branch managers could see what was happening at their own location, but they had limited visibility into demand and vehicle availability across the wider network.
The revenue team had a similar limitation. Prices were mainly set using historical averages, manual competitor checks, and weekly rate reviews.
The business needed a way to connect fleet availability, expected demand, and pricing so that vehicles could be positioned where they were most valuable.
80%+
Fleet Utilization
20 Points
Utilization Improvement
14 Weeks
Core Programme
Continuous
Pricing Optimization
3. The Challenge
The existing operating model was too reactive.
Branch managers were manually coordinating pickups, returns, cleaning, maintenance, and vehicle transfers. Shared spreadsheets were usually updated once or twice a day. By the time a shortage or excess was visible, the opportunity to respond had often passed.
One branch could have several vehicles sitting idle while another nearby location faced a shortage of the same vehicle class.
Pricing had the same problem. Rates were generally updated weekly using historical demand and manual market checks. The process could not respond quickly when booking velocity increased, a local event created a demand spike, weather conditions changed, or competitors adjusted their rates.
The bigger issue was that fleet and revenue teams worked independently.
Pricing decisions were made without a clear view of upcoming vehicle availability. Fleet transfers were made without knowing where the strongest revenue opportunity existed.
The business had enough data to make better decisions, but that data was fragmented across different systems and processes.
4. The Strategic Reframe
DataTheta did not treat scheduling and pricing as separate improvement programmes. Both decisions depended on the same information.
4.1) Treat Fleet and Pricing as One Revenue System
A vehicle only creates value when it is available in the right location at the right time and at the right price.
That meant fleet allocation could not be optimized using operational data alone. Branch managers also needed visibility into expected demand and commercial opportunity.
In the same way, the pricing team could not set rates intelligently without knowing how many vehicles would actually be available.
The two functions needed to work from the same demand and availability signals.
4.2) Build the Data Foundation Before the AI Models
The client wanted better forecasting and automated pricing, but adding AI directly on top of fragmented systems would have created unreliable recommendations.
DataTheta therefore started with the underlying data.z
Booking, fleet, maintenance, transaction, and branch information needed to be brought together before forecasting, scheduling, and pricing models could be trusted.
The goal was not simply to automate existing decisions. It was to create a shared operating view that allowed better decisions to happen.
5. The DataTheta Solution
DataTheta built the solution around a unified data foundation, demand forecasting, fleet optimization, and dynamic pricing.
5.1) Unified Fleet and Booking Data Foundation
Booking records, vehicle information, fleet telematics, maintenance logs, and branch-level transaction data were consolidated into a shared warehouse.
A consistent vehicle- and branch-level structure gave the business a common view of vehicle status, upcoming bookings, maintenance requirements, and availability across locations.
For the first time, fleet and revenue teams could work from the same operational data.
5.2) Branch-Level Demand Forecasting
DataTheta developed forecasting models using historical booking patterns, seasonality, turnaround times, local events, and other demand signals.
The models predicted expected demand by branch and vehicle class up to three weeks ahead.
Instead of waiting for shortages to appear, managers could see where demand pressure was likely to develop before it affected customers.
5.3) Fleet Scheduling and Rebalancing
The demand forecast fed into an optimization layer that helped managers decide how vehicles should move through the network.
The system identified vehicles approaching idle thresholds and recommended transfers to locations where demand was expected to be stronger.
Maintenance and cleaning windows were also scheduled around expected downtime where possible, reducing the chance that vehicles would be unavailable during high-demand periods.
Branch managers received daily rebalancing recommendations instead of manually comparing spreadsheets across locations.
5.4) Guardrailed Dynamic Pricing
DataTheta then added a dynamic pricing model using the same data foundation.
The model considered booking velocity, forecast demand, expected utilization, local events, weather conditions, and competitor pricing signals.
The system could recommend or apply smaller pricing adjustments throughout the day rather than waiting for a weekly rate review.
The revenue team still retained control.
Rate-change limits, minimum and maximum price boundaries, vehicle-class rules, and manual overrides were built into the process so that automation remained visible and manageable.
6. Implementation Approach
The engagement was delivered over a 14-week core programme, with data engineering, data science, optimization, and operational adoption progressing together.
6.1) Unify
DataTheta first brought booking, fleet, maintenance, transaction, and branch data into a common structure.
This created the reliable data foundation required for every later decision.
6.2) Forecast
Historical patterns and current demand signals were used to forecast expected bookings by branch and vehicle class.
These forecasts gave the business an earlier view of likely shortages and excess capacity.
6.3) Optimize
Demand forecasts were connected to fleet scheduling.
The system recommended inter-branch transfers and better timing for maintenance, cleaning, and vehicle availability.
Managers could act before imbalances became operational problems.
6.4) Price
Finally, the same demand and utilization signals were connected to pricing.
Dynamic pricing was introduced with commercial guardrails, giving the revenue team faster decisions without turning pricing into an uncontrolled black box.
7. Business Impact
Within the first two full quarters after rollout, fleet utilization moved from the low 60% range to the low 80% range.
The improvement came largely from identifying idle vehicles and expected branch shortages earlier. Instead of reacting after demand arrived, managers could move vehicles before the imbalance affected availability.
Revenue per available vehicle-day also improved as pricing became more responsive to demand. Local events, holiday weekends, booking spikes, and other short-term changes could be reflected faster than under the previous weekly pricing process.
Branch managers spent less time reconciling schedules and spreadsheets, while pricing moved from periodic manual reviews toward continuous adjustment.
Most importantly, fleet and revenue teams stopped working from separate versions of the business. Both functions could now see the same availability, demand, and utilization picture when making decisions.
8. Conclusion
The problem initially looked like poor fleet scheduling and slow pricing.
In reality, both were symptoms of the same issue. Fleet, booking, and revenue decisions were being made from fragmented data.
By creating one shared data foundation first, DataTheta was able to connect demand forecasting, fleet rebalancing, and dynamic pricing.
The result was higher utilization, faster commercial decisions, and a fleet that could respond more closely to where demand and revenue opportunity actually existed.
“Before this, fleet and pricing were making separate decisions from separate information. Once we could see demand, availability, and pricing together, the decisions became much clearer. We stopped reacting to yesterday’s problem and started planning for what was coming next.”
Related Case Studies
When the Data Can’t Be Trusted, Neither Can the Model
14-day advance failure prediction
- AI-Ready Data
- Data Governance
- Manufacturing Analytics
Car Rental Fleet Optimization
14-day advance failure prediction
- Fleet Optimization
- Demand Forecasting
- Dynamic Pricing
The Specialist a Stalled Project Needed – In Two Weeks, Not Two Quarters
14-day advance failure prediction
- Specialist Talent Augmentation
- Apache Kafka
- Real-Time Analytics
