An urban mobility feasibility study turns an attractive idea into a decision that can be tested. It should reveal the service people need, the conditions required to deliver it, the risks that remain, and the evidence needed before investment or procurement.
The study is strongest when strategy, planning, technology, hardware, infrastructure, operations, safety, and economics are evaluated as one system. The following framework can be used by governments, developers, universities, campuses, resorts, industrial sites, and private operators.
Step 01
Define the problem before choosing the vehicle
Start with the movement problem: who needs to travel, between which places, at what times, and why existing options are insufficient. Separate user needs from assumptions about scooters, bicycles, shuttles, or other modes. A useful study defines measurable objectives such as improving first-and-last-mile access, reducing internal car trips, connecting transit, or improving movement across a controlled site.
Minimum questions to answer
- Primary user groups and accessibility needs
- Origins, destinations, trip purpose, and peak periods
- Current transport alternatives and service gaps
- Project objectives and measurable outcomes
Step 02
Measure demand and trip patterns
Demand should be estimated from multiple sources rather than a single survey or optimistic headline number. Combine available travel data, site counts, stakeholder interviews, land-use patterns, seasonality, and direct observation. Test a range of adoption scenarios. The output should identify where demand is concentrated, when it changes, and which trips the service can realistically support.
Minimum questions to answer
- Daily, weekly, and seasonal demand ranges
- Trip length and duration distribution
- Peak demand by zone and time
- Likely repeat use versus occasional use
Step 03
Map regulation and stakeholder responsibilities
A technically sound service can still fail if permissions, public-space rules, insurance, data obligations, or enforcement responsibilities are unresolved. List every authority and stakeholder who can approve, enable, operate, or constrain the project. Confirm the rules that apply to vehicles, riders, parking, speed, procurement, payments, safety, and personal data.
Minimum questions to answer
- Permits, licenses, and operating authority
- Vehicle and rider requirements
- Parking, right-of-way, and charging rules
- Ownership of enforcement and incident response
Step 04
Choose a service model that fits the context
Define whether the service should be public, private, employee-only, resident-only, tourist-focused, station-based, free-floating, subscription-based, trip-priced, subsidized, or included within another service. The operating environment should drive this choice. A resort, university, residential community, municipality, and mobility operator require different controls and customer experiences.
Minimum questions to answer
- Eligibility and service-access model
- Pricing, subsidy, or membership structure
- Service area, hours, and operating rules
- Operator, owner, and partner responsibilities
Step 05
Size the initial fleet and coverage conservatively
Fleet sizing links demand, availability targets, vehicle productivity, charging cycles, maintenance downtime, rebalancing capacity, and seasonal variation. Avoid treating the first fleet estimate as a fixed procurement quantity. Build low, expected, and high-demand scenarios, then define a pilot fleet that can test the most important assumptions without locking the project into premature scale.
Minimum questions to answer
- Fleet availability and reserve ratios
- Coverage zones and station capacity
- Charging and battery-turnaround assumptions
- Expansion triggers based on observed use
Step 06
Plan parking, docking, charging, and maintenance together
Infrastructure is part of the service—not a separate afterthought. Map where vehicles begin and end trips, how they are charged, how damaged vehicles are isolated, how parts move, and how field teams reach problem locations. Assess power, civil works, land permissions, visibility, accessibility, weather, security, and maintenance access.
Minimum questions to answer
- Parking or docking locations
- Power and charging architecture
- Warehouse, workshop, and spare-parts flow
- Field-team access and recovery routes
Step 07
Define technology, data, payments, and integrations
Specify the experience required for users, field teams, managers, support staff, and decision-makers before selecting a platform. Document vehicle and IoT compatibility, account creation, payments, geofencing, tasks, maintenance, support, analytics, roles, data ownership, security, and integration requirements. Technology evaluation should follow the operating model.
Minimum questions to answer
- Rider and customer-support journeys
- Fleet, IoT, and field-operations workflows
- Payments, identity, and third-party integrations
- Reporting, privacy, security, and data ownership
Step 08
Design the operating and safety model
Translate the service concept into daily roles, shifts, procedures, tools, and escalation paths. Define who charges, inspects, rebalances, repairs, supports users, responds to incidents, and reviews performance. Include preventive maintenance, training, safety communications, emergency response, supplier support, and service-continuity procedures.
Minimum questions to answer
- Team structure and shift coverage
- Inspection and preventive-maintenance standards
- Incident, complaint, and emergency procedures
- Service-level and safety indicators
Step 09
Test economics under several scenarios
A feasibility study should show how capital cost, operating cost, revenue, subsidy, utilization, asset life, maintenance, payment fees, staffing, insurance, infrastructure, and replacement cycles interact. Use ranges and sensitivities rather than presenting one forecast as certainty. Make clear which assumptions have the greatest effect on viability.
Minimum questions to answer
- Capital and implementation costs
- Monthly operating-cost structure
- Revenue or funding assumptions
- Break-even, sensitivity, and downside scenarios
Step 10
Design a pilot with explicit acceptance criteria
The pilot is an instrument for learning, not a smaller version of the final service. State which assumptions it must test, what data will be collected, how long the test must run, and what results allow the project to expand, change, or stop. Assign owners for decisions before launch so evidence leads to action.
Minimum questions to answer
- Pilot questions and success measures
- Baseline, measurement, and reporting method
- Operational review cadence
- Go, revise, expand, or stop criteria
Decision package
What a useful feasibility study should deliver
The final output should be concise enough to support a decision and detailed enough to guide the next phase. It should state what is known, what remains uncertain, who owns each dependency, and how the project can validate its highest-risk assumptions.
- Executive recommendation and decision conditions
- Demand, service-area, and user analysis
- Recommended service and governance model
- Technology, vehicle, infrastructure, and operating requirements
- Financial scenarios, risks, and sensitivities
- Pilot scope, timeline, measurement plan, and acceptance criteria
Need an independent project assessment?
Scooby Mobility supports feasibility, urban mobility planning, technology requirements, hardware assessment, implementation, and operating-model design.