Karachi commuters plan around a bus system that publishes no schedule and follows none
My commute from Malir to my university and back consumes three to four hours daily, and the worst part is not the time — it is the uncertainty. Which routes are running today, whether the Peoples Bus will arrive in ten minutes or forty, whether the route past the flooded chowk changed — none of this is knowable in advance. So everyone pads every journey with worst-case buffers, and the city collectively burns millions of person-hours as insurance. The formal fleets (Peoples Bus, Green Line) have GPS units already — the data simply is not public. The informal fleet (coasters, chinchis, W-11s and their cousins) is untracked but highly patterned. A transit app that combines official GPS feeds (negotiable — the transport department wants credit for its buses being used), crowdsourced vehicle sightings from riders, and route knowledge mapped once by surveyors would give this city something it has never had: the ability to know before leaving. University students alone would carry the crowdsourcing load — we live this problem twice daily and would report buses for the same reason we report traffic on Maps.
A high-conviction problem with strong founder-market fit signals. The combination of severe price asymmetry, accessible demographics, and existing infrastructure makes this buildable within 9 months by a small team.
Solutions · 2
Crowdsourced vehicle sightings with student ambassadors at 40 key stops — ship the map in one semester
Build order for a student team: map the 25 highest-volume routes with surveyor rides (two weekends, GPS traces, stop inventory), launch report-a-bus (two taps: route number, direction) seeded by ambassador students posted at 40 major stops during peak hours for the first month, and show live 'last seen' positions with confidence decay. Even 15-minute-old sightings beat the current nothing. FAST and NED societies would staff this for the portfolio value alone — I ran our society's hackathon and know exactly who would build which module.
Negotiate the official GPS feeds with a public-dashboard trade: the transport department wants its buses seen
My thesis interviews included transport department officials, and the surprising finding: they WANT ridership visibility for the subsidized fleets — empty-seat kilometers are their budget nightmare. Offer a public real-time dashboard of Peoples Bus and Green Line performance (on-time stats they can cite in funding requests) in exchange for the GPS feeds. The informal fleet stays crowdsourced, but the official layer arrives free and instantly credible. I can draft the proposal with the right names on it; bureaucracies move when the ask arrives pre-written.
Discussion
Sukkur has the same problem at smaller scale — nobody knows if the Larkana coaster left yet. The pattern replicates in every city that has buses and no information.
My commute broke my last job — the unpredictability specifically. I now accept lower pay for walkable work. Multiply that wage discount across five million commuters and this is a macroeconomic problem.
The student-ambassador crowdsourcing MVP in solutions is a semester project waiting for a team. NED and FAST societies could staff it by next term.
Mother's version: I plan my daughter's pediatric appointments around bus uncertainty with two-hour buffers. The city taxes women's time hardest — we make more trips with less flexibility.