One of the most consequential decisions in designing a microtransit program is choosing between on-demand service, fixed-route service, or a hybrid of both. Each model has distinct advantages, cost structures, and operational characteristics. The right choice depends on the specific context: the geography being served, the ridership patterns, the budget, and the goals of the program.
At Slidr, we operate both on-demand and fixed-route services across our university, community, and hospitality deployments. We have learned, sometimes through trial and error, that there is no universal answer. This article provides a framework for making the decision based on the factors that actually matter.
Fixed Route: The Traditional Model
Fixed-route service operates on a predetermined path with designated stops, running on a published schedule. It is the model most people associate with public transit: the bus that comes every 15 minutes and follows the same route every day.
The advantages of fixed-route service are predictability and efficiency at scale. When ridership is high and concentrated along a corridor, a fixed route is the most cost-effective way to move people. Riders know exactly where to wait and when the vehicle will arrive. Drivers follow a consistent path, minimizing training complexity and operational variability. The cost per ride decreases as ridership increases because the vehicle runs regardless, and each additional passenger is essentially free.
The disadvantages emerge when ridership is low or dispersed. A fixed-route vehicle running half-empty is expensive per passenger. A route that does not pass near a rider's actual origin or destination requires the rider to walk to and from stops, which may be inconvenient or, in the case of late-night service, unsafe. Fixed routes also lack flexibility. If demand patterns shift due to a schedule change, a new building, or seasonal variation, the route must be redesigned.
On-Demand: The Flexible Model
On-demand service operates without fixed routes or schedules. Riders request a pickup through an app, and a vehicle is dispatched to their location. The vehicle takes them directly to their destination or, in shared on-demand models, makes minor detours to pick up or drop off other riders heading in a similar direction.
The advantages of on-demand service are flexibility and rider convenience. The service goes where the rider is, eliminating the walk to a stop. It operates when the rider needs it, eliminating the wait for the next scheduled departure. It adapts automatically to shifting demand patterns without requiring route redesign. And for many riders, the experience of requesting a ride and being picked up feels natural and modern, matching the Uber and Lyft experience they already know.
The disadvantages are cost and complexity. On-demand service requires more sophisticated technology for dispatching and routing. At high ridership volumes, it can be less efficient than a fixed route because vehicles make more individualized trips. And wait times, while typically short, are variable rather than fixed, which some riders find frustrating.
When Fixed Route Makes Sense
Fixed-route service is generally the right choice when:
- Demand is concentrated along a corridor. If most riders need to travel between the same set of points (e.g., a parking lot and a campus core, or a hotel and an airport), a fixed route serves them efficiently.
- Ridership is high and predictable. When you can reliably fill a vehicle on every run, the cost per ride is low and the service is efficient.
- Service area is linear. Long, narrow service areas like a beachfront resort strip or a campus spine are naturally suited to a fixed loop.
- Riders value schedule predictability. Commuters who plan their day around transit schedules benefit from knowing exactly when the vehicle will be at their stop.
Slidr operates fixed routes in several university and community deployments where these conditions are met. For example, a campus with a large remote parking lot and a concentrated academic district benefits from a fixed shuttle loop during peak class hours. The route connects the two major nodes, runs every 8-10 minutes, and consistently carries near-capacity loads.
When On-Demand Makes Sense
On-demand service is generally the right choice when:
- Demand is dispersed. When riders are spread across a wide area with many different origins and destinations, fixed routes cannot serve them all efficiently.
- Ridership is moderate or variable. When demand fluctuates by time of day, day of week, or season, on-demand service scales naturally without the waste of running empty fixed routes.
- The service area is two-dimensional. A master-planned community, a large campus with buildings spread in every direction, or a resort with multiple venues scattered across a property all call for on-demand flexibility.
- Safety is a primary goal. Late-night safe ride programs are inherently on-demand. Students leaving the library at different times from different locations need rides that come to them.
Slidr's late-night university programs, including FSU's Night Nole, are on-demand because the use case demands it. A student finishing a study session at 11:30 p.m. cannot wait for a fixed-route bus that comes at midnight. They need a ride now, from where they are, to where they are going.
The Hybrid Approach
The most effective deployments often combine both models. A hybrid approach uses fixed routes during high-demand periods and on-demand service during lower-demand periods or in areas not well served by the fixed routes. This captures the efficiency of fixed routes when conditions favor them while maintaining the flexibility and coverage of on-demand service at other times.
UNA's Roar Ride program is a good example of the hybrid model. During peak academic hours, vehicles run fixed routes connecting residence halls, academic buildings, and key campus destinations. During evenings and weekends, the service shifts to on-demand mode, responding to individual ride requests through the Slidr app. This dual-mode approach maximizes both efficiency and rider satisfaction.
Implementing a hybrid model requires technology that supports both modes seamlessly. The rider app must communicate whether the service is currently in fixed-route or on-demand mode. Drivers must be able to switch between following a predetermined route and responding to dispatched ride requests. And the operations team must define clear triggers for mode transitions, whether based on time of day, day of week, ridership thresholds, or a combination.
Ridership Thresholds and Cost Implications
A useful rule of thumb: fixed-route service becomes more cost-effective than on-demand service when average vehicle occupancy consistently exceeds 50-60% of capacity. Below that threshold, you are running a vehicle with empty seats on a fixed schedule, and an on-demand model would serve the same riders at lower cost by eliminating runs with low or zero ridership.
For a six-passenger electric shuttle, that threshold is approximately 3-4 riders per trip. If your route consistently carries 3 or more passengers per departure, fixed route is likely the better model. If average occupancy is below that level for significant portions of the day, on-demand service or a hybrid model will deliver better economics.
Cost per ride typically ranges from $4 to $10 for on-demand service and $2 to $6 for fixed-route service at moderate to high ridership levels. The gap narrows as on-demand technology improves at batching riders and optimizing routes. In well-optimized on-demand systems, the cost premium over fixed route is 20-40%, which is often justified by the superior rider experience and higher utilization rates.
Technology Requirements
Fixed-route service has modest technology requirements: a schedule, a map, and optionally a GPS tracker so riders can see where the vehicle is. On-demand service requires significantly more infrastructure: a rider-facing app, a driver-facing app, a dispatching engine, dynamic routing algorithms, payment processing (if applicable), and analytics dashboards. The technology investment for on-demand is higher, but the data generated is also richer, enabling continuous optimization of the service.
Slidr's platform supports both models natively, which is why we can offer hybrid deployments without requiring clients to integrate multiple technology systems. A single app, a single driver interface, and a single management dashboard handle fixed routes, on-demand dispatching, and the transitions between them.
Making the Decision
If you are designing a microtransit program, start with three questions. First, where are your riders and where do they need to go? Map the origins and destinations. If they cluster along a corridor, lean toward fixed route. If they are dispersed, lean toward on-demand. Second, how does demand vary throughout the day and week? If there are clear peaks and valleys, a hybrid model likely makes the most sense. Third, what is the primary goal of the service? If it is commuter efficiency, fixed route excels. If it is safety, accessibility, or rider convenience, on-demand is stronger.
There is no single right answer, and the best programs evolve over time as ridership data reveals actual patterns that initial assumptions may have missed. Slidr works with every partner to design the initial service model, collect data from the first weeks and months of operation, and refine the approach based on what the data shows. The goal is not to be right on day one. It is to have the flexibility and the data to be right by day ninety and beyond.
