White paper · Bengaluru · 2026

One city, many hails

A point-to-point transport framework for Bengaluru, and how to get there without a new statute in year one

Karnataka regulates road transport by what kind of vehicle you are sitting in. Every workable framework in the world now regulates by how the ride was hailed. Almost every failure in Bengaluru's cab, auto and bike taxi policy over the last decade follows from that one distinction, and correcting it is cheaper, faster and more popular than anything currently on the table.

Executive summary

Bengaluru has roughly 3.6 lakh autorickshaws, tens of thousands of cabs, and a suspended bike taxi sector, governed by a stack of instruments written in 1989, 2016, 2022, 2024 and 2025 that do not agree with one another. Fares are capped but not enforced. Meters are mandatory but not used. Bike taxis are legal, then illegal, then legal, and now before the Supreme Court. Every constituency is angry, and each is angry about something different.

The diagnosis in this paper is that Karnataka has been solving the wrong problem with the wrong instrument aimed at the wrong party. It caps the passenger's price when the actual grievance is the driver's income. It regulates 4,00,000 vehicles when it could regulate four platforms. It fixes rupee amounts that go stale in eighteen months instead of writing formulas that update themselves. And it applies one rulebook to a street hail and an app booking, which are economically different transactions.

Twelve recommendations follow, in three horizons. Four can be done inside ninety days by executive order with no new law and no new money. Four more need rules under powers the state already holds. Four are structural and need legislation. Each is specified with its legal instrument, its signing authority, its cost, its political return and its most likely failure mode.

The political argument is straightforward. The first four recommendations produce visible wins within a quarter — a binding fare promise to every commuter, a cost removed from every driver, and the first open mobility dataset published by any Indian city. The harder reforms then arrive with credibility already banked.

Part one

The gap, stated precisely

"Archaic legislation versus new-age business" is the popular framing and it is too vague to act on. The gap is made of five specific design errors, each of which is separately fixable.

Error one: the rules classify by vehicle, not by hail

Karnataka's framework asks what the vehicle is — motor cab, contract carriage, autorickshaw, motorcycle — and applies a rulebook accordingly. That made sense when the vehicle determined the transaction. It no longer does. The same Swift Dzire is a street taxi at the airport rank at nine in the morning and an app-dispatched cab at ten. The two transactions have opposite information properties.

In a street hail, the passenger cannot compare prices, cannot verify the route, cannot see who the driver is, and learns the fare at the end. Every one of those is a genuine market failure and the meter is the correct, proven answer to it. In an app hail, the price is quoted before boarding, the route is recorded, the driver is identified, and the receipt is itemised. The meter answers a question nobody is asking, while the real problems — the platform's undisclosed deduction, the cancellation that never appears in any record, the fare that changes after the ride — go untouched.

Singapore resolved exactly this in its Point-to-Point Passenger Transport Industry Act of 2019, which regulates street-hail and ride-hail services as two licensed categories under one law and one regulator. That is the single most transferable idea in this paper, and it requires no technology Karnataka does not already have.

Error two: the state caps the passenger's price when the grievance is the driver's income

Karnataka's central price instrument is a ceiling: ₹100, ₹115 or ₹130 for the first four kilometres depending on what the car cost, with surge, flexi-fares and per-minute charges prohibited. It has been in force since March 2024 and is not observed.

Meanwhile the actual crisis is on the supply side. Cabs presenting at the airport ride-hailing kiosks fell from a reported 1,500–2,000 to under 500 across 2024, with drivers selling cars to buy autos, because after roughly thirty per cent platform commission, about ₹300 of airport charges and around ₹200 of fuel, an airport run that had paid a driver about ₹400 was paying ₹130 to ₹150. A fare ceiling does not touch any of the three deductions in that sentence. It is the wrong lever pointed at the wrong end of the transaction.

Error three: rupee amounts instead of formulas

Cab fares were revised in 2018, 2021 and 2024. Auto fares were revised in 2021 and then not again until August 2025. Each revision is a political event: unions demand more, the department offers less, drivers boycott, the government absorbs the anger, and the number then goes stale for three years while fuel, insurance and vehicle prices do not.

A formula removes the fight. If the base fare is defined as a published function of fuel price, consumer price inflation, insurance and vehicle cost, and is recomputed and notified every April by the same officer who signs the circular, drivers receive an automatic annual correction, the government stops owning each increase, and no one has to protest to be heard.

Error four: regulating the many instead of the few

Enforcement cost scales with the number of parties regulated. Karnataka has chosen, repeatedly, to regulate around four lakh vehicles rather than the three or four companies that dispatch a large share of their trips. The department has 286 motor vehicle inspector posts vacant even after inducting 84 in 2024; in 2018 more than 1,200 of about 2,800 sanctioned posts were unfilled. Roadside enforcement at that ratio has a detection probability near zero, and everyone in the market knows it.

Auditing four companies' trip records is a job for six analysts and a database. It is the only version of this that arithmetic permits.

Error five: pricing capital instead of service

The fare slabs are set by the purchase price of the vehicle, so the same six-kilometre ride costs ₹100 or ₹130 depending on the driver's invoice. This prices the wrong thing. It gives a driver a reason to buy a more expensive car in order to earn more per kilometre, in a city with a congestion problem and a fuel import bill, and it gives the passenger a fare that varies for reasons that have nothing to do with the journey.

None of these five errors is about technology, and none requires the state to become more permissive. Each is a mismatch between an instrument and the thing it is pointed at.

Part two

What the Bengaluru evidence establishes

Five findings from the record constrain what a workable framework can look like. They are not opinions and they are not contested.

Hardware mandates have never produced compliance here

Digital meters arrived in Bengaluru's autos in 2004 and were tampered with. A January 2013 notification required digital electronic meters in every motor cab inside BBMP limits; years later thousands of vehicles were still on mechanical meters. When auto fares rose in August 2025, unions instructed members not to recalibrate their meters at all, an RTO official warned that non-compliance could affect fitness certificates and permits, and the boycott went ahead anyway. Thirty years of evidence says a device mandate does not survive contact with a driver who does not accept the fare it enforces.

Commuters want regulation and do not believe in this instrument

Large repeated national surveys find 82 per cent of app taxi users experienced driver cancellations in the previous year, up from 75 per cent in 2023; 45 per cent were charged cancellation fees, up from 23 per cent; only 18 per cent saw any improvement after government action. And 82 per cent want the government to set common standards. The appetite for state intervention is not in doubt. But the same commuters, asked about a fare revision, said revising a fare nobody charges is pointless because nobody runs the meter. Public support is available for a rule that visibly works, and is already exhausted for rules that do not.

The metered alternative already exists and is starved of supply

Nagara, backed by the Karnataka State Drivers' Council, offers exactly what the state says it wants: government-fixed fares, no surge, no commission, meters calibrated and sealed by Legal Metrology, bookable by app, web, WhatsApp or street hail. By mid-2025 it had about 11,000 autos onboarded and 150 cabs, and had completed roughly 3,000 rides in total. Either drivers will not work at the notified fare, or the product is too weak to matter. Both readings point the same way for policy: the notified fare cannot be assumed to attract supply, and a framework that depends on that assumption will fail.

Suppressing supply raises prices faster than any cap lowers them

After bike taxis stopped in June 2025, app auto fares in Bengaluru ran twenty to thirty per cent above the meter rate and the Transport Minister had to write to his own commissioner. A year later commuters were reporting short auto rides quoted at two to three times the meter. Every fare crisis in this city over the last three years traces to a supply constraint rather than to a sudden change in platform behaviour.

The state does not lack authority; it has an unenforced judgment in hand

Since May 2024 the department has held a High Court ruling upholding its auto fare notification and restraining aggregator surge. It has not enforced it. Any proposal that assumes the binding constraint is legal power is misdiagnosing the problem. The binding constraints are administrative capacity, the choice of instrument, and the willingness to name a penalty and collect it.

Part three

What works elsewhere, and why it transfers

Three jurisdictions have solved parts of this problem in ways that map cleanly onto Karnataka's existing powers. None of them requires wealth Bengaluru does not have; all of them require a decision Bengaluru has not made.

Singapore: regulate the hail, not the vehicle

The Point-to-Point Passenger Transport Industry Act 2019 gives the Land Transport Authority one framework covering both street-hail and ride-hail services, with separate operator licences for each. Street-hail keeps metered, regulated fares because the passenger cannot shop. Ride-hail does not, because the passenger is quoted a price and can compare — but the operator carries licensed duties for safety, driver standards and incident reporting. Operators below a size threshold are exempt from licensing altogether, so small and cooperative players are not crushed by enterprise compliance.

Why it transfers: Karnataka already has two rulebooks, one for taxis and one for aggregators. It does not need to write a new philosophy, only to redraw the boundary between them along the hail rather than along the vehicle. And the size exemption is the mechanism that would let Namma Yatri, Nagara, driver cooperatives and any Sahkar Taxi vehicle operate without the compliance load designed for Uber.

New York: put the floor under the driver, not the ceiling over the passenger

Since 2019 New York has set a minimum per-trip payment that high-volume platforms must pay drivers. It is a formula, not a number: a per-mile rate covering vehicle costs plus a per-minute rate targeting a take-home income, both divided by the industry utilisation rate — the share of a driver's logged-in time actually spent carrying a passenger. Dividing by utilisation is the elegant part: if a platform floods the city with drivers who then sit idle, utilisation falls and the per-trip rate the platform must pay rises. The rates are adjusted annually for inflation, and enforcement is an audit of trip records plus a public calculator any driver can use to check their own pay.

Why it transfers: this is the direct answer to the airport exodus, to the union grievance, and to the central guidelines' requirement that owner-drivers receive at least eighty per cent of the fare — which is a share rule, and a share of a shrinking fare is still shrinking. A floor expressed in rupees per kilometre and per minute, indexed annually, is enforceable from data the platforms already hold and does not require the state to have any view at all about what the passenger pays.

New South Wales: one regulator, one law, duties instead of tick-boxes

The Point to Point Transport (Taxis and Hire Vehicles) Act 2016 replaced a patchwork with a single Commissioner covering taxis and rideshare together, imposing outcome-based safety duties on booking service providers rather than prescriptive equipment lists, and funding the transition — including compensation to legacy licence holders — with a small per-trip levy.

Why it transfers: Karnataka's incumbent taxi and auto operators have a legitimate grievance that they were regulated while the platforms were not. A per-trip levy that funds a transition for legacy operators is the standard way that grievance has been settled elsewhere, and Karnataka has already built the collection machinery — the gig workers welfare fee runs on a per-transaction levy with a payment verification system.

India's own building blocks, already paid for

What none of these do

No jurisdiction in this list mandates a physical meter in an app-dispatched vehicle. Several mandate published fares, receipt standards, data reporting, driver pay floors and licensed operator duties. The global direction of travel is from equipment to obligations, and from inspecting vehicles to auditing records.

InstrumentKarnataka todayWhere it leads
Basis of classificationVehicle typeHail type — street, stand or app
Price instrumentFixed rupee ceiling on the passengerIndexed base fare, capped multiplier, floor under the driver
Revision cycleEvery three years, politicallyAnnual, by published formula
Enforcement target~4 lakh vehicles3–5 licensed platforms plus street-hail vehicles
Evidence of complianceA sealed device on a dashboardA per-trip data filing that can be audited
RegulatorTransport Dept, DTA, Legal Metrology, Labour Dept, courtsOne point-to-point authority with a data unit
Part four · Horizon one

Ninety days, executive action, no new law

Everything in this horizon can be done by the Commissioner or by a government order under powers already exercised. None of it needs the legislature, new money, or a single new post. All four are visible to the public within one quarter.

Recommendation 1

Split the rulebook by how the ride was hailed

Issue a clarificatory order reading the meter requirement as applying to street-hailed and stand-hailed trips — kerbside, taxi rank, airport queue, prepaid booth — and not to trips dispatched by a licensed platform that quotes a fare before boarding, records the route, and issues an itemised receipt. Where a vehicle does both, the meter is required and must run only for the street-hailed leg.

This is not a relaxation. It reassigns the instrument to the transaction where it works, and it makes the August 2026 circular enforceable instead of universal and ignored. It also removes a hardware cost and a fresh inspection discretion from tens of thousands of drivers, which is the part they will notice.

InstrumentClarificatory circular now; proviso to Rule 129 and Rule 7(D) at the next amendment
Signed byCommissioner for Transport and Road Safety
CostNil
Political returnA cost removed from every driver; street-hail overcharging still addressed; no constituency loses
Failure modeRead as a concession to aggregators. Mitigate by pairing the announcement with Recommendation 2 on the same day
Recommendation 2

Make the quoted fare binding

One sentence of law: the fare displayed to a passenger at the time of booking is the maximum chargeable for that trip, except for waiting time and route changes requested by the passenger, both of which must be itemised. Any excess is refundable to the passenger within seven days, and the liability sits on the platform, not the driver. A second sentence: cancellation fees may not be charged where the driver cancels or where the platform reassigns the trip.

This is the single most popular thing available to the government at zero cost. It converts the most common complaint in the city into a self-documenting violation, because the platform's own record contains both numbers.

InstrumentLicence condition under the 2016 aggregator rules; notification for non-licensed operators
Signed byState Transport Authority; Transport Secretary for the notification
CostNil
Political returnImmediate and universal. Every commuter understands "the price you were shown is the price you pay"
Failure modePlatforms inflate the quote to protect themselves. Mitigate with Recommendation 5's multiplier cap and by publishing quote-to-charge distributions from Recommendation 3
Recommendation 3

Require a per-trip data filing, and publish the anonymised version

Every licensed platform files a daily machine-readable record for each trip: origin and destination zone rather than exact address, distance, duration, fare quoted, fare charged, platform deduction, driver payout, waiting time, cancellation and by whom, and vehicle class. Personal identifiers are not filed. The state publishes a monthly anonymised open dataset.

This is the load-bearing recommendation. It turns every other rule in this paper from an aspiration into a query. It is also the one with the strongest claim on Bengaluru's own identity: no Indian city currently publishes open ride-hailing trip data, and the city that will not do it is the one that calls itself the country's technology capital.

InstrumentLicence condition; aligns with the central guidelines' state control centre requirement; can share the filing rail already built for the gig welfare fee
Signed byState Transport Authority, with the Labour Department for the shared rail
CostModest. A six-person data unit and a managed database. Well under one crore a year
Political returnHigh and distinctive. "Bengaluru publishes India's first open mobility dataset" writes itself, and researchers and civic groups will do the analysis free
Failure modePlatforms litigate on privacy or commercial confidentiality. Mitigate by filing zones not addresses, by aggregating the public release, and by pointing to the precedent that per-transaction reporting is already law here
Recommendation 4

Publish a monthly enforcement scorecard

Four numbers on the department's website every month: fitness certificates refused and why, penalties imposed on platforms, refunds ordered to passengers, and complaints received and closed. All four are generated internally already. None requires a new power.

The department's credibility problem is not that it lacks rules. It is that thirty years of announcements have not been followed by counts. Publishing counts is the cheapest credibility purchase available, and it is the discipline that makes the later horizons believable.

InstrumentDepartmental order
Signed byCommissioner
CostNil
Political returnModerate at first, compounding. It is also the strongest available answer to the charge that the department only issues circulars
Failure modeThe numbers are embarrassing in month one. That is the point; publishing them from a low base makes every subsequent improvement legible
Part five · Horizon two

Six to twelve months, rules under existing powers

Recommendation 5

Adopt the central aggregator guidelines with Karnataka amendments

Notify state rules aligned to the July 2025 central framework, with three local departures. First, cap the peak multiplier at 1.5 times the base fare rather than two, on the ground that Bengaluru's peak is structural congestion rather than genuine scarcity and a doubling at 6 p.m. every weekday is not a scarcity signal. Second, require the entire premium above base fare to accrue to the driver, which the High Court has already held. Third, require the multiplier in force and the reason for it to be displayed to the passenger at the moment of quoting.

A band with a hard ceiling on the multiplier is stricter in practice than the current prohibition, because a prohibition that is not enforced is a ceiling of infinity.

InstrumentRules under Sections 93 and 96 of the Motor Vehicles Act, replacing or amending the 2016 rules
Signed byTransport Secretary, with Cabinet approval
Political returnEnds the "Karnataka has not adopted the central guidelines" criticism; converts an unenforceable ban into an enforceable limit; the premium-to-driver rule is a direct win with unions
Failure modeRead as legalising surge. The framing must be that surge already happens without limit and this is the first rule that actually bounds it
Recommendation 6

Replace vehicle-price slabs with an indexed fare formula

Define the base fare as a published function of fuel price, consumer price inflation, third-party insurance premium and a vehicle cost index, computed and notified every April by the Commissioner without a fresh Cabinet decision each time. Publish the formula, the inputs and the arithmetic. Classify by vehicle capacity and comfort — small, sedan, large, premium — rather than by invoice value.

This ends the three-year cycle of staleness followed by a bruising revision, and it removes the incentive to buy a costlier car to earn a higher rate.

InstrumentNotification under Section 67 of the Motor Vehicles Act, replacing the February 2024 order
Signed byTransport Secretary; annual recomputation delegated to the Commissioner
Political returnDrivers get an automatic annual correction without protesting for it; the government stops absorbing the anger of every individual hike
Failure modeFormula disputes replace fare disputes. Mitigate by publishing the inputs monthly and constituting a small standing panel with union and platform representation to review the formula every three years
Recommendation 7

Set a minimum per-trip payment to the driver

Adopt the New York structure adapted to Indian costs: a per-kilometre component covering vehicle running costs and a per-minute component targeting a take-home income, both divided by the measured utilisation rate for the platform's fleet, indexed annually to the same inputs as Recommendation 6. Audit it from the Recommendation 3 filing. Publish a calculator so any driver can check a day's earnings.

This is the structural answer to the airport exodus, to the union grievance about commissions, and to the reason drivers refuse trips and demand cash. It regulates the platform, which is the party that can pay, and it makes the eighty per cent share rule in the central guidelines meaningful by putting a floor under the amount being shared.

InstrumentLicence condition and rules under Section 93; supported by the gig workers welfare framework
Signed byTransport Secretary with the Labour Department
CostAnalytical capacity only. The data is being filed under Recommendation 3
Political returnVery high with the constituency that is currently most organised, most angry and most likely to protest
Failure modePlatforms restrict driver logins to manage utilisation, or raise passenger fares. New York's answer to the first is a utilisation floor below which the actual measured rate applies; the second is bounded by Recommendation 5
Recommendation 8

Notify bike taxi rules and end the litigation

Frame the policy the courts have twice invited: transport registration or a permit category for two-wheelers carrying passengers, a licensed operator obligation, mandatory two-helmet provision, third-party and rider insurance minimums, a rider working-hours limit, a fleet cap reviewed annually, and an electric preference phased rather than immediate. Price it as a distinct category rather than forcing it into the auto fare table.

Bike taxis are the cheapest motorised mode available to the lowest-income commuters and the strongest first and last mile feeder the metro has. Their suspension is the single clearest cause of the auto fare inflation the government is currently trying to fix by other means. Notifying rules also removes the state's weakest legal position and ends an expensive appeal.

InstrumentRules under Section 93 read with the central guidelines' provision for state permission of non-transport motorcycles
Signed byTransport Secretary with Cabinet approval
Political returnLarge. Restores a mode with a visible constituency of riders and commuters, and lowers auto fares through competition rather than through enforcement the department cannot staff
Failure modeAuto union opposition, which is real and organised. Sequence it after Recommendations 6 and 7 so that auto drivers have received an indexed fare and a payment floor before bike taxis return, and frame the fleet cap and the metro feeder role explicitly
Part six · Horizon three

Twelve to twenty-four months, institution and statute

Recommendation 9

Create a Karnataka Point-to-Point Transport Authority

One regulator for every hired point-to-point journey — street taxis, app cabs, autos, bike taxis and whatever arrives next — with a Commissioner, a standing data unit, a public complaints tribunal, and outcome-based duties on operators rather than equipment schedules. It absorbs the aggregator rules, the fare notifications, the District Transport Authority's fare-fixing role for autos, and coordination with Legal Metrology for the street-hail fleet.

Today a Bengaluru commuter's fare is governed by four different bodies and at least five instruments, none of which cross-references the others. That is the deepest source of the incoherence this paper describes, and no circular can fix it.

InstrumentState legislation, modelled on the New South Wales point-to-point statute
Political returnLegacy-scale. Karnataka wrote India's first aggregator rules in 2016 and India's first platform gig workers law in 2025; this is the third first, and the one that ties them together
Failure modeCreating a body without staffing it, which is how the current department arrived at 286 vacancies. The statute should tie the authority's funding to a per-trip levy so its capacity grows with the industry it regulates
Recommendation 10

Tier the licence, and exempt small and cooperative operators

Three tiers. Large operators above a threshold of daily dispatches carry the full obligation set: licence, data filing, driver pay floor, control room, insurance, incident reporting. Mid-sized operators carry data filing and pay-floor obligations with lighter administrative requirements. Operators below the threshold — cooperatives, union-run apps, ONDC participants, single-city entrants — register rather than licence, and file a simplified monthly return.

Singapore exempts ride-hail operators below a fleet threshold for exactly this reason. Without a tier structure, every rule in this paper becomes a moat that protects the two incumbents the state is trying to discipline.

InstrumentSchedule to the new statute; can be prototyped earlier as a licence-fee waiver under the 2016 rules
Political returnDirectly supports the cooperative-taxi and self-reliance agenda with real machinery instead of an app launch
Failure modeStructuring to stay under the threshold. Mitigate by setting the threshold on dispatches rather than registered entities and by aggregating commonly controlled operators
Recommendation 11

One filing rail, two purposes

Merge the transport data filing with the gig workers welfare fee's payment verification system, so a platform reports each transaction once and both departments read the same record. Publish a single schema and a single API.

The platforms' most credible complaint about Karnataka is duplicated and unpredictable compliance. Removing a filing while adding an obligation is the trade that makes the rest of this package negotiable.

InstrumentJoint order of the Transport and Labour Departments; schema published as an open standard
Political returnImproves the ease-of-doing-business position while tightening enforcement, which is a rare combination and worth saying out loud
Failure modeInter-departmental ownership disputes. Assign the schema to one custodian in the order itself
Recommendation 12

Tie permits to service outcomes and to the metro

Stop treating permits as a fixed stock and start issuing against measured need: publish quarterly service-level data by ward — availability, wait time, cancellation rate, price relative to base — and release permits into the zones and hours where service is failing, with a feeder category for vehicles operating within a defined radius of metro and major bus stations at an integrated fare.

The city's mobility problem is not that too many people want to drive strangers around. It is that supply is fixed by a licensing decision taken years ago while demand moves every quarter.

InstrumentPermit policy under the new statute; feeder category coordinated with BMRCL and BMTC
Political returnConnects transport regulation to the metro programme, which is the government's most visible infrastructure story
Failure modeExisting permit holders resist dilution. This is the grievance the New South Wales levy was designed to settle, and Recommendation 9's levy can do the same here
Part seven

The political economy of getting it done

A reform package that is technically right and politically naive does not survive its first union meeting. Four groups have to be handled, and they do not want the same thing.

Auto and street taxi unions

They are the most organised constituency, they can put fifty thousand drivers behind a boycott, and their grievance is genuine: they were regulated while the platforms were not, and they were undercut by fares funded from investor capital. What they want is an income they can predict. Recommendations 6 and 7 give them exactly that, and give it to them automatically each year rather than as a concession extracted by protest. They will oppose Recommendation 8 on bike taxis, which is why it must come after, not before.

App drivers

Numerically large, weakly organised, and the group whose exit is currently doing the most damage — at the airport, at night, and in the rain. They care about the deduction, not the fare. Recommendations 2, 3 and 7 are addressed to them, and the driver-facing pay calculator is what makes the reform visible in their hands rather than in a gazette.

Platforms

They will litigate any rule that increases cost and welcome any rule that increases certainty. The trade available here is real: a bounded multiplier and an indexed base fare are better for them than a frozen ceiling they are currently breaking every day, and a merged filing rail removes a compliance burden. Rapido's decision to take a Karnataka licence to 2031 shows that at least one of them will trade compliance for certainty. The package should be presented as that trade, explicitly.

Commuters

The largest group, the least organised, and the one whose support is already conditional. They will not be moved by a framework. They will be moved by one sentence — the price you were shown is the price you pay — and by the wait time at the airport falling. Every communication should lead with those two things and leave the architecture to the annexure.

Sequencing, and what to announce first

Announce Recommendations 1 and 2 together, on the same day. The first removes a cost from drivers, the second gives a guarantee to passengers, and neither costs anything. Publish Recommendation 4's first scorecard sixty days later, from whatever base exists. Release Recommendation 3's first open dataset at the ninety-day mark with a public hackathon, which converts a compliance measure into a technology-capital story at almost no cost. Only then open the rule-making on fares, pay floors and bike taxis, with three visible wins already banked.

The reform that fails is the one that starts with the statute. The reform that works starts with a promise a commuter can check on their phone in the first week.

The reputational argument, made honestly

Bengaluru's claim to be India's technology capital is currently doing no work in its own transport regulation. The city that built the country's open mobility protocol regulates fares with a sealed mechanical device and a fitness certificate. The gap is not a matter of image; it is a live cost, because the state is spending administrative effort on inspections it cannot staff instead of on analysis it could do with six people and a database. Closing that gap is not a branding exercise. The branding is simply what falls out of doing it.

Part eight

What to measure

A framework that cannot be scored will be argued about forever. Eight indicators, all derivable from the Recommendation 3 filing, published monthly.

Part nine

Where this fails

  1. The data unit is never staffed. This is the most likely failure and it kills everything downstream. Mitigation: fund the unit from a per-trip levy in the enabling instrument rather than from the departmental budget, and contract the first eighteen months to an external analytics partner with a public deliverable.
  2. Litigation freezes the package. Karnataka's default outcome for a decade. Mitigation: sequence the non-litigable items first, since neither a binding-quote rule nor an open dataset gives a platform much to challenge, and let the contested items arrive when the easy ones are already in force and popular.
  3. The pay floor pushes fares up. Possible, and the honest answer is that some of it will pass through. The counter is that the current alternative is not cheap rides but absent ones, and that the multiplier cap bounds how far it can go. This should be modelled and published before adoption, not defended afterwards.
  4. Bike taxis reignite the union fight. Mitigation is sequencing and the fleet cap, and a candid public position that the cheapest motorised mode for low-income commuters is not something the state can keep suspended while it decides.
  5. The formula becomes the new argument. Real, but a bounded one. A published formula with published inputs is a far better argument to be having than a three-yearly fight over a single number.
  6. Nothing is published. If the monthly scorecard and the open dataset do not appear, none of the rest of this happened. That is the test to apply, and it is deliberately easy to check.
Annexure

Instruments and signatures

RecommendationInstrumentSigned by
1 · Split by hail typeClarificatory circular, then rule provisoTransport Commissioner
2 · Binding quoted fareLicence condition and notificationState Transport Authority / Transport Secretary
3 · Per-trip data filingLicence condition; shared rail with LabourState Transport Authority
4 · Monthly scorecardDepartmental orderTransport Commissioner
5 · Adopt central guidelinesRules under Sections 93 and 96, MV ActTransport Secretary, Cabinet
6 · Indexed fare formulaNotification under Section 67, MV ActTransport Secretary; annual recomputation delegated
7 · Driver payment floorLicence condition and rules under Section 93Transport Secretary with Labour Department
8 · Bike taxi rulesRules under Section 93 with central guidelines Clause 23Transport Secretary, Cabinet
9 · Point-to-Point AuthorityState legislationLegislature
10 · Tiered licensingSchedule to the statute; prototyped by fee waiverState Transport Authority, then legislature
11 · Single filing railJoint departmental order; open schemaTransport and Labour Departments
12 · Outcome-linked permitsPermit policy under the statutePoint-to-Point Authority with BMRCL and BMTC

This paper draws its Bengaluru evidence from the companion dossier on the 20 August 2026 taxi meter circular, which carries the full tiered evidence ledger and the open questions that remain unresolved. Where this paper states a figure, that ledger states its source and its reliability. Recommendations are the author's; they have not been discussed with any of the parties named.

Principal references