Who Gets the Airport Ride? Maharashtra Wants to Audit the Algorithms Behind Your Cab

Every time a passenger in Mumbai taps a button for a cab, a piece of software decides which driver gets the job. Independent taxi drivers have long suspected that this decision is not neutral. Maharashtra’s government now says it wants to look inside the box.

Chief Minister Devendra Fadnavis has told the transport department to build a digital platform to oversee app-based transport as part of the proposed Maharashtra Motor Vehicle Aggregator Rules, 2026. The amended rules are expected to define clearly how technology and algorithms may be used to allocate rides, and the state plans to audit those allocation systems.

The complaint

Individual drivers who own one car say that the most valuable trips, airport runs and long-distance bookings, go disproportionately to vehicles owned by large fleet operators. For a driver paying off a loan, a few lucrative trips a day can be the difference between a profit and a loss. Transport Minister Pratap Sarnaik has framed the plan as a way to end the “monopoly” of fleet owners.

What the platform would do

• Keep a unified record of every vehicle and driver working through aggregators, including registration, parking arrangements, licences and police verification.
• Track in real time who is driving which vehicle in which shift, so that information is available immediately after an accident or incident.
• Use AI-based analytics to monitor working hours and compliance.
• Regulate surge pricing, watch geo-fencing practices and add safeguards against arbitrary suspension of driver accounts.

The hard part: auditing code

Promising to audit an algorithm is easier than doing it. Ride allocation depends on hundreds of signals, from distance and ratings to acceptance rates and predicted demand. A fleet vehicle may get more airport jobs simply because it is positioned near the airport more often, not because the code favours its owner. Regulators will need access to data, clear fairness metrics and staff who can read both statistics and software.

There is also a privacy tension. A system that records every driver’s shift and location in real time is a powerful safety tool, but it is also a surveillance tool. Clear rules on who can see the data, and for how long it is kept, will decide whether drivers see the platform as protection or as one more boss watching them.

Why other cities will watch

India’s gig economy is growing fast, and arguments about opaque algorithms are not limited to taxis. Food delivery and quick-commerce workers raise similar complaints about who gets orders and why accounts are blocked. If Maharashtra can turn “algorithm audit” from a slogan into a working process, it could become a template for the rest of the country. If not, it risks becoming another database that drivers must feed without seeing any change on their screens.