Every shared micromobility and car-sharing operator hits the same wall: vehicles end up where the last trip left them, not where the next trip will start. Left alone, a fleet drifts toward a handful of drop zones while demand pools somewhere else entirely, and the fix, someone physically moving vehicles, is one of the largest recurring line items in shared mobility operations. That’s fleet rebalancing. Getting it wrong is expensive in a specific way: not one bad decision, but a daily gap between where vehicles sit and where the next rider actually needs one.
Here’s what fleet rebalancing actually involves, why it’s a harder problem than “move vehicles to where demand is,” and how Myles, SWITCH’s AI agent for mobility and logistics (getswitch.io) approaches it.
What fleet rebalancing means
Rebalancing is the operational process of moving vehicles, scooters, bikes, cars, from zones where supply exceeds near-term demand to zones where it doesn’t, so the next rider finds a vehicle instead of an empty map. It applies across shared mobility formats. Scooter and bike rebalancing usually means a ground crew physically relocating vehicles by van or truck. Car-sharing rebalancing more often means routing the next available vehicle’s return trip through a demand zone, or flagging it for staff relocation.
Why rebalancing is a harder optimization problem than it looks
“Move vehicles to where demand is” sounds simple until you have to decide, every hour, which vehicles, moved by whom, at what cost, against a demand forecast that’s a prediction and not a fact. The labor cost is real and immediate, while the benefit is only a forecast: every rebalancing run costs a crew’s time and a vehicle’s fuel or charge, and the payoff, trips that wouldn’t have happened otherwise, only exists if the demand forecast driving the decision is accurate. Demand also shifts faster than a static rebalancing schedule can track. A fixed run at 6am and 6pm misses the weather change, the event that just ended, or the competitor promotion that pulled riders somewhere unexpected that afternoon. And zones interact with each other: pulling vehicles from Zone A to fix a shortage in Zone B can create a new shortage in Zone A an hour later if the forecast didn’t account for A’s own recovering demand.
This is why rebalancing algorithms range from simple threshold rules (“if a zone drops below N vehicles, dispatch a run”) to demand-forecast-driven systems that weigh the cost of a rebalancing run against the predicted trips it enables, before committing a crew.
Rebalancing approaches, from simplest to most adaptive
Threshold-based rebalancing triggers a run when a zone’s vehicle count crosses a fixed floor or ceiling. It’s easy to implement and blind to why the imbalance happened or whether it’s about to reverse on its own. Predictive, scheduled rebalancing uses a demand forecast to plan runs ahead of predicted shortages, rather than reacting after the shortage is already visible, though it still runs on a fixed schedule rather than responding to real-time shifts. Real-time, cost-aware rebalancing continuously weighs the forecast demand gain against the labor and vehicle cost of a specific move, and only dispatches when the math clears. That last approach is what scales past a handful of zones without turning into either a constant-motion fleet or a chronically undersupplied one.
How Myles approaches rebalancing
Rebalancing sits inside what Myles treats as one connected job, not two: forecasting demand by zone and by hour with a confidence range, and operations, which turns that forecast directly into a rebalancing plan and a ground-team assignment. The rebalancing recommendation is priced against the same forecast confidence the ops team already sees, rather than a separate tool making its own assumptions about a demand number nobody can audit. It’s grounded in the fleet’s own trip history and the surrounding city context, part of the roughly 350 million trips modeled monthly across SWITCH’s data layer, rather than a generic rebalancing heuristic applied the same way to every city.
Key takeaways
- Fleet rebalancing is the recurring cost of matching vehicle supply to demand, and one of the largest operational line items in shared mobility.
- The hard part isn’t moving vehicles. It’s deciding whether a specific move is worth its labor cost against an uncertain demand forecast.
- Rebalancing approaches range from static threshold rules to real-time, cost-aware systems that weigh forecast gain against dispatch cost before acting.
- Myles ties rebalancing directly to its own zone-and-hour demand forecast, so the recommendation and the forecast share the same confidence level.
Curious what a cost-aware rebalancing plan looks like for your fleet? Try Myles free for 14 days.
