6 Sections 45 minutes Author: Shared-Use Mobility Center
This Microtransit Learning Module gives readers an in-depth understanding of the operational components, applications, and steps to support a successful microtransit solution. Unlike many of the other shared modes of transit, microtransit takes many forms in how it operates through vehicles used and private partner configurations. The broad range of microtransit applications can help transit agencies meet specific transportation barriers.
Mobile technologies, especially location access through smartphones or tablets, are the foundation for microtransit service and support its operations, the rider experience, and access to the service. Rides are typically arranged through a smartphone app, in addition to a phone- or web-based booking system to support accessibility and address equity considerations.
Microtransit services can fulfill many different purposes, such as first and last mile connections to transit, transportation in areas with low population density and transit ridership, non-emergency medical transportation, paratransit, and commutes to employment hubs. Microtransit can also operate in a variety of service designs.
Microtransit service resembles Demand-Responsive Transportation (DRT) service in small-urban or less dense communities, or in more dense communities it is used to support fixed-route transit. Microtransit service usually develops through Public-Private Partnerships where the public agency either contracts the service out entirely to a private vendor or leases the dispatching and routing platform. In the later example, the public agency can either operate the vehicles and manage the drivers, or those services can also be contracted.
Communities interested in pursuing microtransit solutions should conduct a needs assessment and engage the community to find the right solution or combination of solutions for their community. For more information on community engagement, see the Community Engagement Learning Module or the Clean Mobility Options Implementation Toolkit.
Microtransit, like many on-demand mobility services, is an evolution of existing modes enabled by new technology advancements. The microtransit service model sits between traditional fixed-route transit and mobility-on-demand services such as dial-a-ride, paratransit services, or transportation network companies (TNCs). Microtransit functions like a demand-responsive service, but typically uses ad hoc pickup and drop-off points within limited service zones. Unlike other shared modes, microtransit can take many forms in how it operates, the types of vehicles it uses, and the partnerships (if any) that enable it. The broad range of possible applications for microtransit can also lead to its use for meeting unique existing transportation challenges. This learning module attempts to bring microtransit into focus for public agency planners. Microtransit demonstration projects and resulting studies show us that microtransit is not a one-size-fits-all solution. Rather, it is one of many tools available to help meet the mobility needs within a community.
Microtransit services draw components from both fixed-route transit and ride-hailing. It resembles traditional demand-response transportation (DRT), such as dial-a-ride, in that it often uses similar vehicles (passenger vans or cutaways) but with improved dispatching and routing, enabled by various mobile technologies, especially location access through smartphones or mobile tablets. Rides may be arranged through a smartphone app in addition to phone- or web-based booking systems. Microtransit can also provide pooled trips, ranging from fully private direct-to-consumer pooled ridesourcing services in passenger cars to general public services funded by government agencies with agency-branded vehicles.
In the public sector, microtransit faces a conundrum: in terms of trips per vehicle service hour, it is almost always less efficient than traditional fixed-route transit (as circuitous, point-to-point routes tend to reach fewer people per hour than straight-line routes). Unlike traditional fixed-route transit that can better scale, if a microtransit service becomes more popular, the number of vehicles and drivers (and the associated cost) must increase to accommodate the growth and maintain service quality. On the other hand, microtransit can be deployed in areas where fixed-route transit is difficult to operate (due to difficult topography or less dense communities, for example), or where a flexible service might provide first and last mile connections with faster response times than is possible with scheduled service. In these cases, microtransit can be a tool to serve populations in lower-density areas lacking other mobility options.
On-Demand Ridepooling World Map, an interactive map by lukas.foljanty@gmail.com displays active on-demand transit programs, helping to demonstrate how widespread microtransit is worldwide.
Although microtransit services can look different based on the region or needs of the community, the technical definitions cover some of the same concepts:
These definitions all locate microtransit as a transportation service nestled between fixed-route transit and ride-hailing. Fixed-route transit services have defined stop locations, routes, and schedules, and generally operate along straight lines or corridors. In North America, they are typically funded and operated by government agencies, though private services may also exist. Ride-hailing is an on-demand, point-to-point service that may or may not be shared, with reservations, dispatch, routing, and payment supported and enabled by location-aware mobile platforms. Microtransit combines elements of both into a new, technology-enabled, on-demand, shared mode. For additional shared mobility definitions and terms visit the Mobility Learning Center Definitions page.
The following graphic helps to visualize how microtransit fits into and supports other public transportation modes. In this graphic, Walkability is paired with Trip Length, shorter trips in more walkable communities are often carried out through Active Transportation (biking and walking), but as the trip length increases and in areas that are less walkable, other modes may be more appropriate, with microtransit positioned somewhere between fixed-route service and ridehail.
The appropriate mobility solution and service model for your community should be driven by the community’s needs, goals, and budget. The goals of a project can be high-level (for instance, to increase mobility options) or more granular (like to improve the level of service per user cost). Other goals could include reduced car dependency, increased mobility for older adults and people with disabilities, or increased public transit ridership. This independent evaluation report from the Mobility on Demand Sandbox program shows various examples of project goals, but agencies should develop their own based on the nature of the project and the community being served. Once the project goals are established, it is important to develop a set of performance benchmarks and identify the required data needed to measure whether or not a stated goal has been met. Community input is important throughout this process to identify the needs of a demonstration project’s intended users.
Having established a set of project goals the next step is to develop a set of performance metrics and the data needed to measure them to assess a pilot project’s effectiveness. Performance metrics can and should look beyond the bottom line costs to consider the equity and accessibility factors. Examples include:
SUMC’s Setting Project Goals and Performance Metrics Learning Module explores shared mobility goals and performance metrics further.
You can also visit the links below, all of which contain detailed goals and performance metrics for a variety of microtransit projects:
While somewhat dated, Performance Metrics is presented in the Transit Cooperative Research Program (TCRP) Synthesis 141, Microtransit or General Public Demand–Response Transit Services: State of the Practice, which is a meta-study of microtransit and a collection of case studies. As mentioned in the introduction of this Learning Module, when in a partnership, microtransit tends to fill needs where fixed-route service has trouble working, so its metrics will be different. As the synthesis notes:
Performance metrics should look beyond the bottom line. While metrics such as passengers per vehicle hour are important for evaluating a service, performance metrics should also take into account the service’s impact on equity, transit accessibility, and benefits to mobility freedom.
When developing and launching a microtransit program, it is important to identify a private partner whose goals and vision align with those of both the community and the transit agency. Having an aligned vision ensures that the partnership supports the microtransit objectives, and fosters long-term sustainability.
The following are some considerations when getting ready to procure microtransit services.
Before procuring services:
4. Speak with other cities, transit agencies, and technology vendors (microtransit examples reviewed in this learning module offer a starting point) to learn how different microtransit solutions have been used. Agencies can ask questions to learn more about service operations, including:
5. When appropriate, coordinate with neighboring transit agencies and service providers to strengthen partnerships and look for opportunities to collaborate. This can also help to determine services that might be duplicative of others or areas that have limited transportation options. This idea is explored further in the Universal Mobility Learning Module, Service Coordination section.
When you’re ready to procure services:
This list of considerations is not exhaustive but is intended to offer a starting point on how to approach the procurement process. Transit agencies should also familiarize themselves with local, state, and federal procurement guidelines and requirements.
Although the table below features pre-pandemic data from 2019, it still offers some insights into the state of public-private partnership (P3) microtransit ridership, service productivity, and costs, including the critical passengers-per-vehicle service hour measure. The examples offer a discrete set of performance metrics that, when applicable, can then be used to identify how well a project meets its stated goals. A performance metric might meet one goal, for example lowering the unit cost per trip, but other project goals should also be considered, such as providing equitable service across a geographic area. The data from this table is from TCRP Synthesis 141: Microtransit or General Public Demand–Response Transit Services: State of the Practice, published in 2019.
Respondents reported an almost remarkable consistency in average ridership ranging from 2.4 to 4.7 passengers per hour. As is the case with fixed-route services, DRT which operates in areas with greater population or employment density tends to perform better than DRT operating in areas of lower density.
Contract or In-house |
Cost/Vehicle Service Hour | Passengers/Vehicle Service Hour | Cost per Passenger Trip | |
AC Transit | In-house | $214.00 (Fully allocated) | 3 | $71.00 |
Cherriots | In-house | $65.00 | 3.5 | $18.57 |
DART (Dallas) | Contracted. DART provides vehicles and facilities but not fuel. | $46.00 | 2.5 for original DRT service
3.5 for new GoLink service |
$18.40
$13.14 |
Denver RTD | Contracted | $83.00 | 3.8 | $21.84 |
HART | Contracted | HART pays contractor by trip and not by hour. | 3.5 | $10.00 |
Houston METRO | In-house | $75.00 | 2.4 | $31.25 |
Kitsap Transit | In-house | $130.72 | 3.66 | $35.68 |
LYNX | Contracted | $41.17 | 3.3 | $12.60 |
MST | Contracted | $54.18 | 4.03 | $13.44 |
NVTA | Contracted | $44.48 | 2.6 | $17.00 |
NCTD | Contracted | $97.00 | 2.7 | $36.00 |
TDU | Contracted and In-house | $130.72 | 3.66 | $7.34 |
Source: Transit Cooperative Research Program (TCRP) Synthesis 141, Microtransit or General Public Demand-Response Transit Services: State of the Practice
Note: These numbers are self-reported figures from agencies that responded.
Because microtransit services often resemble existing demand-responsive transportation (DRT) or supplement fixed-route service, they can be operated in a wide variety of partnership configurations. Different types of partnerships reflect the capital and operational needs of the partnering agency. A microtransit service provider can partner with a city or transit agency to provide any or all of the technology, vehicles, drivers, maintenance, and other operations, according to the specific needs of the agency:
When developing and launching a successful microtransit program, it is crucial to identify a private partner whose goals and vision align with those of both the community and microtransit initative. Having an aligned vision ensures that the partnership supports microtransit objectives, and fosters long-term sustainability. Ultimately, a partner that is a good fit for the microtransit initiative can ensure that it becomes a vital, and well-integrated part of the community’s transportation options.
SUMC’s series of case studies on CPACS Ride, a community-led microtransit service in Clarkston, GA, shares insights on developing and launching an on-demand microtransit program. In particular, this case study detailing the procurement phase outlines key strategies for defining priorities during the RFP and contracting process and building partnerships.
Microtransit services broadly share the following characteristics:
Following are some of the more typical microtransit operational approaches. There is not a one-size fits all and agencies can use and adapt these approaches to best meet the specific needs of their communities.
Flex-route within a zone (also referred to as Point-to-Point service): Similar to a ridesharing service, the route is determined by riders’ origins and destinations within a predetermined zone, most commonly used in denser areas. The routing and dispatching software plans a route that accommodates multiple origins and destinations and riders are picked up and dropped off at those origin and destination sites. The green area in the graphic below shows the service area zone, with a microtransit van picking up passengers and dropping them off at their destinations.
Deviated Fixed-Route: This type of microtransit service is often used in lower-density communities, where microtransit vehicles might travel along a fixed route, but have the flexibility to deviate from that route for pick-up and drop-offs. This type of service can be helpful in lower-density areas, as the service can switch to flex-route service, as depicted in the graphic below.
First and Last Mile Service: Regardless of a city’s amenities or density, first and last mile services fill the gap between passengers’ starting or ending locations and public transportation. First and last mile service is especially important in small-urban and less-dense communities as the distance to public transportation can be lengthy compared to their higher-density urban counterparts, which are often closer to fixed-route public transportation. The graphic below shows fixed-route transit traveling from an urban core to a bus terminal, where microtransit service is available to take passengers to their destinations.
Hub and Spoke Model: This hybrid service model combines the benefits of point-to-point and first and last mile models to assist passengers with shorter trips. This model consists of several popular destinations that act as a terminal, with drivers picking up or dropping off passengers from that point within a zone. Terminals often include grocery stores, medical facilities, libraries, or downtown centers. The microtransit vehicle can make other stops along the way but the designated terminal points are given scheduling priority, making this type of microtransit useful in small towns, or denser communities. The graphic below shows how the hub and spoke routes could look as the microtransit vehicle serves either a designated zone or provides service across zones.
Virtual stops (also referred to as corner-to-corner service): This type of microtransit, typically used in more dense areas, uses routing and dispatching software to alert the microtransit operator to create an efficient route to multiple destinations, in which the operator may (through a location-enabled mobile app) direct users to set pick-up and drop-off locations within a reasonably walkable distance of origins and destinations. This allows for passenger grouping to reduce stops and increase vehicle utilization. The following graphic helps to visualize how virtual stops work, with riders being dropped off at various stops and walking to their final destination.
Within these service models, microtransit operators can customize how passengers are picked up and dropped off:
The above graphics help to illustrate the difference between the two microtransit models. The graphic on the left shows curb-to-curb service, while the right shows door-to-door service. Curb-to-curb service passengers are directed to walk to a specific pick-up site and are similarly dropped off a short distance from their destination. Door-to-door service passengers are picked up and dropped off at their origin and destination sites.
Microtransit services can operate with a variety of vehicles to suit the specific needs of a community or region. In a more dense community, a vehicle with a lower capacity may be a better fit, while in a more sparse community, a high-capacity vehicle may be a better fit. Some of the vehicle types used by microtransit operators are:
Public Transit Data Standards play an important role in the operations and rider experience of transportation services, as they support a range of functions from the discovery of services, operations, planning, scheduling, and payment. Specific to microtransit, GTFS-Flex is particularly important because it allows the rider to discover the availability of Demand Responsive Transportation (DRT) services that would not otherwise be readily available. Through this standardization, trip planners like Apple or Google Maps are able to display the zone-based microtransit service – making it possible for riders to discover DRT services that were otherwise unavailable through these applications. Using both GTFS-Flex and its parent data standard, GTFS–which makes available fixed-route transit information–users can discover the range of available public transportation services available to them.
GTFS-Flex requires planning and resources to implement and maintain, which should be accounted for in the project budget.
The Minnesota Department of Transportation (MnDOT) offers an example of a State DOT working with small-urban and rural transit agencies to develop a regional Mobility as a Service (MaaS) platform. The platform uses data standards to communicate a range of services including fixed – and flex-route transit, microtransit, paratransit, and human services transportation. The MaaS platform also uses the transactional data specification (TDS) to communicate trip scheduling across transit agencies and mobility providers.
Additional data standards are available and when fully implemented can help avoid vendor lock as the common data language used to communicate transportation services is not tied to a single proprietary platform. Data standards also help support a service’s ability to scale and serve new areas, as the framework for communicating transportation services uses a common data language. While still in its early stages, a handful of DRT services are using transactional data specifications to communicate the scheduling of DRT services across mobility providers and jurisdictional boundaries (including the MnDOT MaaS platform discussed above). For more information on transactional data specifications, see Modernizing Demand-Responsive Transportation for the Age of New Mobility (aarp.org).
Additional GTFS-Flex resources can be found: MobilityData, GTFS-Flex is Officially Adopted: Everything You Need To Know, and the Rural Transit Assistance Program GTFS Builder.
Additional data standards are available and when fully implemented can help avoid vendor lock as the common data language used to communicate transportation services is not tied to a single proprietary platform. Data standards also help support a service’s ability to scale and serve new areas, as the framework for communicating transportation services uses a common data language. While still in its early stages, a handful of DRT services are using transactional data specifications to communicate the scheduling of DRT services across mobility providers and jurisdictional boundaries (including the MnDOT MaaS platform discussed above). For more information on transactional data specifications, see Modernizing Demand-Responsive Transportation for the Age of New Mobility (aarp.org).
Like other shared-use transportation options, microtransit can provide efficient and environmentally sustainable services for passengers by reducing the number of single-occupancy vehicles on the road. Microtransit is an important tool that cities can use to improve connectivity and support the public transportation network. While it varies from place to place and vehicle types used, when sufficient passenger occupancy rates are met it can further reduce transportation-related GHG emissions and help to alleviate traffic congestion. Below are a few microtransit use cases to help demonstrate the potential climate mitigation impacts.
The Clean Mobility Options (CMO) program is an electric vehicle shared mobility program investing in California’s disadvantaged communities. CMO lists several goals of the program that help to demonstrate why electric vehicles are important and should be given further consideration:
Although electric vehicles can be a great solution for mitigating air quality issues and bridging the gap for first and last mile transportation, they can pose procurement and technology challenges that operators and municipalities should consider when planning for an EV fleet. Since microtransit vehicles are high in demand this can pose difficulties in procuring vehicles that are costly and can take considerable time to receive from time of ordering.
According to the International Finance Corporation (IFC)’s 2020 report, users and municipalities alike have run into these types of issues:
Cost Barriers:
Infrastructural Barriers:
Battery Range:
These ideas are explored further in SUMC’s The Importance of Shared, Electric Mobility Learning Module, and Electric and Equitable: Learning from the BlueLA Carsharing Pilot
Public microtransit services are distinguished by their partnerships between local governments or transit agencies and a private microtransit provider. Following are some examples and links to projects to help understand the different microtransit operational models.
The Federal Transit Administration (FTA) has supported microtransit through a variety of programs, including Innovative Mobility Integration (IMI) and Accelerating Innovative Mobility (AIM) grants through the Office of Research & Innovation. These demonstration projects help us to understand the role that microtransit can play in improving connectivity, addressing equity barriers, and improving access to important quality-of-life needs, like medical, employment, and food.
Following is an overview and links to additional resources for some of the FTA-supported microtransit demonstration projects:
As cities and regions explore mobility solutions to support their public transportation networks, microtransit is often looked at as an option. The following points provide an overview of some of the key considerations for microtransit implementation: