Minneapolis Robotaxi Ordinance Would Put a Paid Human in Every Driverless Car

Minneapolis is preparing to require a paid human safety monitor in the driver's seat of every commercial autonomous vehicle operating in the city, a rule that would put it at odds with the operators now expanding driverless fleets across the United States. The proposed Minneapolis robotaxi ordinance, drafted under the title "Workers Drive Minneapolis", would force companies including Waymo to keep a licensed driver at the controls, with immediate access to steering, braking and acceleration. A public hearing on the measure is scheduled for September 22.

The bill comes from council members Robin Wonsley, Jamal Osman, Jason Chavez and Aurin Chowdhury, who cite traffic safety and the job security of the thousands of people driving for Uber and Lyft in the Twin Cities. Operators would also need a city license, with a compliance deadline of October 2027 if the ordinance is approved.

Minnesota has no autonomous-vehicle rules of its own. State legislators did not pass proposed oversight during the 2026 session, leaving cities to set their own terms. Driverless taxi service is not currently permitted in the state, so the ordinance would write the terms of entry rather than roll back an existing market.

Waymo's Position in the Twin Cities

Waymo has been testing in Minneapolis since November 2025. Its vehicles carry a human in the front seat, and the company is not yet picking up paying passengers there. Waymo describes Minneapolis as an expansion site for its sixth-generation autonomous technology, which pairs automated sensor-cleaning mechanisms with software tuned for winter conditions such as heavy snow and ice. The company's stated plan is to move to rides with nobody in the driver's seat.

Waymo follows a staged rollout in each new market: manual street mapping by human specialists first, then employee-only testing, and only later public driverless ride-hailing. Minneapolis sits in the early part of that sequence, which means the ordinance would land before the company has carried a single paying passenger in the city.

The sensor-cleaning detail is central to the dispute. Snow and ice foul the lidar, cameras and radar that autonomous systems depend on, which makes Minneapolis a harder test than Phoenix or Austin. Waymo has invested in hardware that clears those surfaces without a person stepping out of the car. An ordinance requiring an in-cabin monitor does not block that hardware, but it keeps a wage on the books for every vehicle in the fleet, which is the opposite of what the technology was built to deliver.

The Arithmetic Behind the Minneapolis Robotaxi Ordinance

Removing the driver is the source of a robotaxi fleet's cost advantage. A driverless operator can run vehicles for longer hours, skip shift breaks, and spread fixed costs over more trips per day. The Minneapolis robotaxi ordinance restores the missing line item: a paid person in the driver's seat, earning at least minimum wage under the measure. That single requirement erases the per-mile savings that make driverless ride-hailing cheaper to run than a human-driven fleet at scale.

Waymo's trajectory shows why the stakes are high. The Alphabet subsidiary runs paid robotaxi service in 10 U.S. metropolitan areas and is pushing toward one million rides a week. Each added city raises density, which lifts utilization per vehicle and cuts the cost of each trip. A city-level mandate in one market is survivable; the same mandate spreading across dozens would reset the unit economics of the business.

For Waymo, the Minneapolis question is also a template question. A rule that survives legal challenge in one city gives similar campaigns elsewhere a draft to copy, and the company's cost model assumes a fleet with no wage line at all. The ordinance is an attempt to write that line back in.

That is the strategic logic behind the ordinance, and it is why the fight is not really about Minneapolis's streets. It is about which level of government sets the floor.

The timeline leaves a long runway. Even if the council approves the measure after the September 22 hearing, operators would have until October 2027 to secure a city license, which gives Waymo's supervised testing roughly another year. The rule would not stop the current phase; it would define what the city looks like in 2028.

A City-by-City Fight, Not a Federal One

Minneapolis is one front in a wider pushback. California ride-hailing rules require a human behind the wheel unless an operator holds permits to run without one, which has kept Tesla's robotaxi service in that state under supervision. Federal regulators have opened an investigation into Tesla's self-certification of the Cybercab, a vehicle designed without a steering wheel or pedals. Zoox, Amazon's robotaxi unit, has put vehicles with no steering wheel on the road in cities including Las Vegas and San Francisco.

Those designs expose a structural problem for the Minneapolis ordinance. A vehicle built without a steering wheel cannot seat a licensed human at the controls, so the rule would exclude that class of vehicle from commercial operation in the city entirely, while remaining satisfiable by Waymo's current hardware.

The pushback is not confined to Minnesota. Waymo and Zoox have run into organized resistance in a growing number of cities as local governments assert authority over driverless operations, and the disputes now turn on permits, fees and operating conditions rather than on whether the technology works.

Federal rules do not settle the question either. No federal safety standard has been written for vehicles that lack a steering wheel, and Zoox has published its own safety approach instead of complying with a government specification. That gap is what gives city councils room to legislate, and it is why Minneapolis can move faster than the statehouse.

Operators are also split on where the human belongs. Guident Corp. markets a platform that combines AI, remote monitoring and teleoperation for autonomous fleets, positioning the human-in-the-loop layer outside the vehicle. Minneapolis's ordinance picks the opposite architecture: the monitor sits inside the cabin, within reach of the wheel. That is a design mandate as much as a safety rule, and it narrows the set of systems that can legally operate.

The licensing deadline matters for the same reason. By tying continued operation to a city permit, the ordinance turns market access into a renewable condition rather than a one-time approval. Cities adopting that model gain an ongoing lever over fleet size, operating hours and where vehicles may drive, all without state legislation.

What the Drivers Get

The labor case is explicit in the bill's framing. Uber and Lyft drivers in the Twin Cities recently organized to win minimum compensation guarantees after long disputes with the rideshare platforms, and local labor groups have raised concerns about Waymo's arrival. Requiring a paid monitor converts each autonomous vehicle into at least one job, at least on paper.

The economics of that trade are contested. A monitor who watches and can take over in an emergency holds a different job from driving, yet costs the operator roughly the same wage. The ordinance guarantees the headcount without guaranteeing the career, and it does not ensure the monitor is a former rideshare driver.

Why this matters

The Minneapolis robotaxi ordinance shows that the binding constraint on robotaxi expansion may be municipal permitting rather than sensor performance or capital. One city can raise the operating cost of a driverless fleet by putting back the wage the technology was built to remove, and it can do that without any state or federal action. For operators, city-by-city licensing now carries as much planning weight as vehicle engineering. For cities, the permit is the lever.

Related Articles

• AV Emergency Response Coordination Act: Robotaxi Safety Bill
• Robotaxi safety operator injuries: hidden cost of scale-up
• NHTSA Opens Tesla Cybercab Safety Probe Into How 1,000 Driverless Robotaxis Were Certified

✔Human Verified

Researched and cross-referenced against primary sources by the Bytevyte editorial team. This article was generated with the assistance of artificial intelligence and reviewed by the Bytevyte editorial team.