Urban first and last mile
The train is fine. Getting to it isn't.
Rail and trunk bus carry people once they arrive. On-demand feeders close the two kilometres that decide whether they take the car instead.
Does this describe your network?
Four things every rail corridor planner says out loud
First and last mile is the part of the journey your network doesn't cover: home to the platform, platform to the office door. It is short, it is where riders decide to drive, and it is the cheapest part of the trip to fix. Below, each problem and the mechanism that answers it.
- 01Walkable on a map, not in lifeTwo kilometres of hill, dual carriageway or rain — and the car wins.See the scenario ↓
- 02Feeder buses miss the trainA connection that fails once is a connection nobody trusts again.See the scenario ↓
- 03Park-and-ride is full by eightEvery new space costs more than the trips it adds, and the queue starts earlier each year.See the scenario ↓
- 04Nobody sees it as one journeyA feeder outside the journey planner and the ticket doesn't exist for riders.See the scenario ↓
Scenario 01 — Walkable on a map, not in life
Start the journey at the door, not at the platform
Catchment maps draw circles; hills, motorway crossings and February weather don't respect them. Virtual stops placed on the residential streets themselves put the pickup within a short walk of the door, and pooled feeders bring several households to the same departure — so the first two kilometres stop being the reason to drive the whole way.
- Virtual stops in the streets
- Dynamic pooling
- Custom street rules
- Runs on your existing fleet
Scenario 02 — Feeder buses miss the train
Timed to the departure, not to a printed hour
A feeder on its own timetable meets the train by coincidence. Here the trip is planned backwards from the departure the rider is catching: pickup windows are set against the rail schedule, and the routing engine protects the connection when it assigns the vehicle. Riders see the arrival window, not a hope.
- Departure-anchored pickup windows
- GTFS feeds in and out
- Live tracking for riders
- Repeat commuter bookings
Scenario 03 — Park-and-ride is full by eight
Add catchment instead of adding car parks
A parking space serves one commuter per day and costs like construction. A feeder vehicle serves dozens and costs like a service line. Extending the catchment by shuttle also reaches the households that were never going to get a space — and takes the morning queue off the station approach roads.
- Zone-based catchment design
- Peak fleet sizing
- Multi-node interchange
- Cost per trip reporting
Scenario 04 — Nobody sees it as one journey
Appear inside the trip riders already plan
Riders don't plan a feeder and then a train; they plan a journey. A GTFS feed puts the on-demand leg inside the regional journey planner next to rail and tram, and open APIs let it be booked, paid and validated in the MaaS app your region already runs — so the whole trip is one decision.
- Journey planner integration
- MaaS booking and payment
- Existing fare systems
- Deep links and SSO
Typical service shape
What a feeder service usually looks like
Figures from Shotl’s first- and last-mile deployments, so you can hold them against your own corridor before any conversation. Your simulation will produce the real numbers.
- 6–8 min
- Average waits on feeders in Torre Baró and Wolfsburg — short enough to beat walking to the platform.
- 560 stops
- Virtual stops across Kawasaki’s residential catchment, placed in software with no infrastructure built.
- 65 km²
- A Bosch pilot linking its Schwieberdingen gates to nearby sites and transit nodes.
- Timed to rail
- Pickup windows planned backwards from the departure the rider is catching.
- 3 booking channels
- App, web portal and telephone — plus GTFS and API integration with the journey planner riders already use.
- Existing fleet
- Minibuses or vans you already run, sized by simulation rather than by guess.
FAQ
First and last mile questions, answered
What counts as first and last mile transport?
The short leg between a rider's origin or destination and the trunk network — home to the station, interchange to the workplace. It is usually one to three kilometres, and it decides whether the rest of the journey happens by public transport at all.
How do you guarantee the connection to the train?
Pickup windows are calculated backwards from the scheduled departure, and the routing engine only assigns a trip it can complete in time. Riders see a firm arrival window and can track the vehicle.
Is this cheaper than expanding park-and-ride?
In most corridors, yes. A parking space serves one commuter a day at construction cost; a feeder vehicle serves dozens at service cost — and it reaches the households that would never have got a space.
Does it need to be a separate app for riders?
No. The service can run white-label under your own brand, and it can also be planned, booked and paid inside the regional journey planner or MaaS app through open APIs.
Can it feed more than one station?
Yes. A single service zone can serve several rail stations and bus interchanges, with the engine choosing the node that fits each rider's onward journey.
From the blog
