Fleet maintenance is one of the largest ongoing cost drivers in a car sharing operation. What makes it particularly difficult to control is that your vehicles are never in one place, especially when you operate a free-floating service. Without data telling you what's happening across the fleet, you end up reacting to problems rather than preventing them. And reactive maintenance is almost always more expensive than the alternative.
In this lesson, we'll cover how to shift from reactive to proactive maintenance and how to organize field and workshop work. We'll also look at the decision between in-house and outsourced operations, and how customers can act as an extra layer of visibility for problems that telematics cannot capture.
Reactive maintenance is what happens without a data infrastructure in place. You wait until a customer calls in about a warning light, low tire pressure, or a vehicle that will not start. Alternatively, you send staff on regular check-up drives at fixed intervals to assess vehicle condition across the fleet.
Both approaches are expensive in different ways. Customer-reported problems mean the issue has already affected a booking. Regular check-up drives burn staff time and fuel, and many visits find nothing wrong. You drive out, confirm everything is fine, and drive back.
Proactive maintenance aims to minimize these blind runs. Instead of visiting vehicles on a schedule, you respond to specific signals from your fleet health monitoring. A warning light appears somewhere in the fleet, you receive an alert, track what the light does, and decide how to act.
Some warning lights call for immediate action. Others, like a low washer fluid alert, can safely wait a day or two. Pulling a vehicle from the reservation system costs you short-term revenue. Keeping it online when a serious fault appears can turn a routine service visit into a major repair. Proactive monitoring gives you the data to make that judgment early.
Source: Insights Interview on Free-Floating Car Sharing with Bolt Drive
Once your data infrastructure is in place, the question is how to act on it. Operators use two broad models for organizing maintenance work, and neither is clearly better for all situations.
Tasks come in as tickets and team members pick them up based on their own judgment about urgency and sequence. Staff bring their experience to prioritization, which tends to work well when the team is capable and motivated. People generally like the approach because it gives them ownership over how they work.
A manager or system routes tasks to specific staff. Priorities can be set by topic or vehicle status, and assignments can be batched geographically to reduce travel time between vehicles. This model works better when the team is larger and someone is actively managing the work queue.
No clear pattern has emerged from operator experience about which model performs better. Context determines its fit, and most operators arrive at their approach through trial rather than upfront planning.
Most operators combine field operations with a central workshop rather than relying on either alone. The goal is to handle as much as possible on-site, bringing vehicles in only when the issue genuinely requires it.
A common setup is a small internal service fleet: vehicles stocked with the supplies field staff need for roadside repairs. Typical contents include:
Field-first operations keep workshop load manageable and reduce the staff time spent on vehicle transport. Some operators who are already attending to a vehicle choose to run a full inspection and clean at the same time, converting a small task into a complete service run.
Oil changes, tire replacements, and safety-critical failures such as driver assistance system faults always require a workshop visit. Everything else depends on what your field team is equipped and trained to handle.
Before building internal maintenance capability, it is worth asking whether you want to build it at all. Some operators outsource maintenance successfully. They have found partners with strong local experience who take on the work reliably, and they have concluded that the investment in training, tooling, and management overhead is not worth it for their scale or context.
Outsourcing also solves a hiring problem in markets where qualified field staff are genuinely difficult to find. Keeping a specialist partner available, even if most day-to-day work happens in-house, gives you a buffer when the team is stretched or when you need to scale up quickly.
The decision is not fixed. Operators often adjust as they grow. They bring more capability in-house once they understand the work well enough to manage it, or they contract out when operational complexity outpaces what the team can handle.
Telematics tells you a great deal about the mechanical and electronic state of each vehicle. It does not tell you that a headrest is missing, that there is interior damage, or that a previous trip left the cabin in poor condition. For physical issues, your customers are often the first to notice.
Operators encourage reporting in different ways from in-app prompts at trip end, rewards for damage reports that lead to a repair, to free rental minutes for flagging serious faults. The right approach depends on your platform and customer base.
There is also a community dimension. Customers who feel connected to the service are more likely to report problems than those who treat it as purely transactional. An engaged customer who notices a warning light is a free maintenance signal. Building that relationship is worth more than any reward structure alone.
Reactive maintenance means waiting for customer reports or visiting vehicles on a fixed schedule. Proactive maintenance uses telematics alerts to respond to specific signals, reducing blind check-up runs and catching problems earlier.
A model where maintenance tasks come in as tickets and team members prioritize and pick them up themselves. It works well when the team is experienced and motivated, and gives staff more ownership over how they work.
Oil changes, tire replacements, and safety-critical failures always require a workshop. Minor issues such as fluid top-ups, jump starts, and basic diagnostics can usually be handled in the field with the right equipment.
It depends on scale, hiring conditions, and available partners. Some operators outsource from the start. A hybrid model, with a specialist partner available as backup, is a common middle ground even for mostly in-house operations.
Customers spot physical issues telematics cannot detect: interior damage, missing items, cabin condition. In-app prompts, rewards for actionable reports, and building community ownership all improve reporting rates and quality.