Feeder design principles that convert last-mile trips into rail boardings instead of leakage — so the line everyone invested in actually fills up.
Map the station catchment first
For each station, map the access catchment and where demand actually originates. The feeder network's job is to connect those origins to the station within a tolerable time and transfer — not to replicate legacy bus routes.
Design covered, uncovered and balanced feeders
Improve feeders where service exists but underperforms, create new feeders for genuine demand with no connectivity, and balance the rest around fleet, travel time and stop spacing.
Synchronise feeder timetables to rail
A feeder that arrives just after the train leaves loses the passenger. Align feeder timetables to metro timings so transfers connect, and the wait at the interchange stays short.
Use the right mode for the catchment
Not every feeder is a bus. Shared autos, e-rickshaws and micro-mobility can form structured feeder loops in dense or narrow catchments — organised into the network rather than left informal.
Remove duplication with city bus
Detect where city buses already shadow the rail corridor and reshape them as feeders rather than competitors, cutting redundant kilometres.
Checklist
- Station catchments and access demand mapped
- Covered / uncovered / balanced feeders defined
- Feeder timetables synced to metro timings
- Mode chosen per catchment (bus / shared / micro-mobility)
- City-bus duplication detected and reshaped
Put this into practice with RouteSync
Planning, operations, monitoring and reporting on one connected platform.