Robotics & AutomationRegulatory PolicyEconomics
The DC Robotaxi Bill Is Really Four Fights at Once
Four fights meet in one permit measure, and Congress can still block it.
A single DC bill, B26-0684, is where four fights collide, and the question under the jobs-versus-independence hearing is whether the District's guardrails are calibrated to the driverless-car failure modes the country has already documented or to the revenue and liability the bill can more easily price; how it resolves that, and whether Congress lets it, is what to watch.
- The bill would let DDOT permit fully driverless commercial service for the first time, gated by seven-figure fees, a 250,000-mile test wall, a 200-vehicle cap, a 15-cent-per-mile tax, an eight-ward equity mandate and a January 2028 launch, and it makes the AV maker the legally liable operator, which specialists call a national outlier.
- The labor fight is real on both sides: a large but contested, immigrant-heavy contractor base faces displacement, Waymo pledges hundreds of higher-skill ops jobs and Wards 5 and 7 investment, and disability riders testify to genuine independence; a workforce fund tries to bridge a mismatch no one can size precisely.
- Underneath the hearing is a market-structure fork, Waymo's owned-fleet model versus Uber's push for a mandate that AVs run on a human-driver network, and the bill's caps and tax effectively pick which company the AV era rewards.
- The safety record the Council must judge is other cities': strong per mile on serious crashes but failing in structured edge cases, first-responder scenes, school zones and buses, dawn deadheading, that the bill answers with insurance, caps and a self-reported plan rather than independent validation.
- The bill legalizes an eight-ward always-on sensor fleet while writing no rules on rider data or police access, just as the Supreme Court in Chatrie tightens Fourth Amendment limits on bulk location data.
- Because this is the District, an enacted act still faces a congressional Home Rule review, and a GOP Congress is pressing DC to move faster, not to block.
Under the Jobs-Versus-Independence Fight Sits Industrial Policy
For more than seven hours on July 13, 81 witnesses across 17 panels filed through a hearing room in the Wilson Building to tell the DC Council what driverless taxis would do to their city. Teamsters, SEIU 32BJ and transit-union members in the seats called the bill a job killer written for Silicon Valley billionaires; blind and disabled riders called the same technology an independence they had never reliably had; Waymo pledged hundreds of local jobs, and Uber warned that a driverless-only law would hand its rival a monopoly. The measure on the table, the Autonomous Vehicle Deployment Authorization Amendment Act of 2026, would give the District Department of Transportation something it has never run: authority to permit fully driverless commercial service, hedged with seven-figure fees, a per-mile tax, an eight-ward service-equity mandate and a fund for displaced drivers. Under the hearing's jobs-versus-independence binary sits the machinery, DC trying to shape how a safety-critical robotic system enters its streets using the levers of industrial and labor policy, at a moment when the federal government is pressing it to move faster and the technology's own record, gathered in other cities because the District has none, keeps failing in the structured edge cases the crash statistics do not capture. That the guardrails may be aimed at the revenue and liability the bill can price rather than at the failure modes regulators are acting on is our reading of the record below, not a charge we level at anyone.
- The Bill. Councilmember Charles Allen (Ward 6), who chairs the Committee on Transportation and the Environment, announced the measure on April 23 and formally introduced Bill 26-0684 on May 1 with Brooke Pinto (Ward 2) and Matthew Frumin (Ward 3). It amends DC's 2012 Autonomous Vehicle Act, which today allows testing only with a safety operator behind the wheel, to let DDOT permit fully driverless testing and then commercial passenger and goods service; the Bowser administration has issued no driverless permits, so this is net-new authority, not a tweak.
- The Hearing. The Committee on Transportation and the Environment held its public hearing on Monday, July 13, at the Wilson Building; it ran more than seven hours and drew 81 witnesses across 17 panels. The Teamsters, SEIU 32BJ, ATU Local 689 and the machinists rallied against the bill and recruited Uber and Lyft drivers to testify, while the American Council of the Blind and Waymo testified in favor; the bill remains in committee, with no markup or Council vote scheduled.
- The Guardrails. The design is the story: a $1 million application fee plus a $5 million permit against about $5,500 for a human ride-hail license, a 15-cent-per-mile tax, a 200-vehicle cap per company, a 250,000-in-DC-mile testing wall and no commercial service before January 1, 2028. It bolts on an eight-ward comparable-service mandate, a $5 million liability-insurance floor separate from the permit fee, and an Autonomous Vehicle Deployment Fund split evenly between public transit and a workforce fund for displaced rideshare drivers.
- The Fight. Both sides are real welfare claims on different populations. Teamsters Local 639 president Bill Davis called the bill's so-called guardrails a failure to protect middle-class professional drivers from Big Tech, and SEIU 32BJ's Jaime Contreras called it a job killer; disability advocates testified that robotaxis grant mobility independence; Uber, straddling the field, opposed the driverless-only design and lobbied for a mandate that AVs also carry human drivers, warning the bill would hand Waymo a de facto monopoly; and the DC Chamber of Commerce backed the bill while urging the Council to remove the 200-vehicle cap and lower fees.
- The Record. DC has no driverless service yet, so the Council is legislating on other cities' incident data, and that record is unsettling in a specific way. Twelve days before the hearing, NHTSA called driverless interference with first responders a functional insufficiency and said it would schedule meetings with developers by month's end to hear fixes; a Waymo struck a 9-year-old in a Santa Monica school zone; the NTSB found a Waymo passed a stopped Austin school bus after its remote assistant answered no to the car's school-bus query; and empty Waymos circled an Atlanta cul-de-sac at dawn, eight of them getting stuck.
The Guardrails Price Risk Rather Than Validate Safety
Bill 26-0684 would let DDOT issue three-year, revocable permits for driverless commercial service, but only after a wall of conditions: a $1 million application fee and a $5 million permit against about $5,500 for a human ride-hail license, a 250,000-in-DC-mile testing certification, a 200-vehicle cap per company, a 15-cent-per-mile tax, an eight-ward equity mandate, a $5 million insurance floor and no on-demand service before January 1, 2028. It also deems the automated-driving-system maker the legal operator whenever the system is engaged, with a rebuttable presumption if the logs show it active within 30 seconds of a crash, a rule specialists call a national outlier.
The record the Council is weighing comes from other cities, because the District has none of its own, and it says two things at once. Waymo reports about 94 percent fewer serious-injury crashes across 220.6 million rider-only miles, peer-reviewed at a smaller mileage. The failures regulators are acting on are a different animal. Twelve days before the hearing, NHTSA called driverless interference with first responders a functional insufficiency; a Waymo struck a 9-year-old in a Santa Monica school zone; and in Austin the NTSB found that a remote assistant answered no when a car asked whether it had stopped for a school bus with active signals, and the car passed the bus.
The judgment here, a reading of the bill text rather than a verdict on the vehicles, is that the safety layer is real and stops short of what that record says matters most. The bill requires a first-responder-interaction plan, a continuity-of-operations plan and quarterly crash reports the city must publish. It does not require independent validation of the safety case, published The Operational Design Domain, the mapped, geofenced conditions a driverless system is designed to handle, such as certain streets, speeds and weather., or a school-zone performance standard. The center of regulatory gravity has moved from crash rate, where these vehicles look best, to edge-case behavior, where the documented failures cluster. Insurance, caps, a tax and a self-reported plan are calibrated to what a city can price.
DC is writing the country's strictest AV rulebook into a federal squeeze
Regulatory Policy. Bill 26-0684 hands DDOT a permit regime it has never run and prices entry in the millions, putting DC at the restrictive pole of a state-by-state patchwork that runs from California's two-agency DMV-and-CPUC model to Texas's preemptive light touch. The live variable is federal: the SELF DRIVE Act and NHTSA's drive to prevent a patchwork target exactly this kind of high-friction local design.
Public Administration. The novelty is administrative, an eight-ward equity mandate, a company-funded workforce fund and phased vehicle caps that turn a yes-or-no on robotaxis into local industrial policy, but the binding constraint is capacity: the AV study the Council leaned on arrived roughly four and a half years late, and DDOT must now stand up permit adjudication, a per-mile-tax system and crash-data intake before the 2028 gate.
An enacted act clears the 30-legislative-day congressional review with its per-mile tax, fees and vehicle cap intact, and no appropriations rider follows. The federal squeeze never bound.
On the federal side: the fees, caps and per-mile tax are the high-friction design a national anti-patchwork push targets, so which of them survives Home Rule review?
The permit quietly picks a market structure and a labor settlement
Labor & Employment. The bill trades a large, contested base of low-barrier contractor driving slots, disproportionately immigrant and multi-job, for Waymo's pledged hundreds of higher-skill operations jobs, a mismatch in headcount, skills, schedule and geography a driver-transition fund is meant to bridge; academic modeling puts frontline job loss well above half in a full robotaxi shift.
Strategy & Operations. Underneath the labor hearing is a business fight: Waymo enters as a capitalized, vertically integrated operator, its $16 billion raise and Wards 5 and 7 pledge *positioning it to answer the equity objection and court the Council's approval*, while Uber lobbies for a rule that keeps AVs on its human-driver network, and the bill's structure effectively chooses between the two models.
Waymo declines to seek a DC permit and no operator applies at this fee schedule. The permit would have picked nothing, and DC would have chosen out of the market, not between two models.
On the market side: the fee schedule that sets concentration also sets which jobs survive, so is the Council picking a structure or letting one pick itself?
The evidence base is competent on average and failing at the edges
Robotics & Automation. Waymo's own data shows large reductions in serious-injury crashes per mile, yet the failures regulators are acting on are a different animal, first-responder interference, stopped school buses, a school-zone child strike, dawn deadheading, and the bill answers them with insurance, caps and a self-reported plan rather than validation matched to those modes.
Cybersecurity & Privacy. A permitted fleet is also a rolling sensor platform across all eight wards, and the bill writes no rules on rider data or police access even as the Supreme Court tightens Fourth Amendment limits on bulk location data and Waymo, in one recent case, remotely monitored the in-cabin video and called police itself.
NHTSA closes PE24016 and the PE25013 school-bus probe with no finding, and the July first-responder process ends at voluntary fixes. The edge cases would sit inside ordinary variance.
On the safety side: the failures regulators act on are edge-case behaviors the crash rate never captures, so what standard would validate those before deployment?
The Weave maps a single development across domains and across time. Each row follows one domain from where things stand now through the next eighteen months, and expands for the reasoning behind that trajectory.
- No local driverless record exists yet, so every finding rests on other cities' data.
- That absence is itself a finding, because it decides what evidence a vote can rest on.
- Legislating before deployment is the rare chance to require validation ahead of it, not after.
- Capability generalizes faster than permits get written, so authorization trails the technology.
- The scaling lever is the hardware cost curve rather than any single model breakthrough.
- A vehicle cap and a start date fix local supply while capability keeps moving past both.
- Federal preemption aims at design and performance, so liability and insurance rules survive it.
- The realistic federal risk is pressure on the guardrails rather than a ban on the regime.
- Home Rule adds a congressional review that no other city has to plan its rollout around.
- The theory of harm is foreclosure by capital, not size, which a vehicle cap only partly checks.
- Deep funding can absorb losses longer than any driver-owned rival, so entry closes quietly.
- Whether a transition fund actually returns the gain to those who lose it stays unanswered.
The Markup Decides Whether the Guardrails Are Real
Strip away the hearing's theatrics and the durable question is design: whether DC uses this bill to validate a technology's competence or to price its failures. The bill is in committee with no markup noticed, and the honest counter is that heavy local guardrails could simply push Waymo to a friendlier jurisdiction and leave DC with neither the jobs nor the accessibility gains, a trade a reader should weigh before treating the guardrails as free. What follows are the checkable signals.
- The Markup. Whether the Council amends the bill before it votes, and specifically whether any independent-validation, operating-domain-limit, vulnerable-road-user-performance or data-transparency requirement is added, is the tell for whether the safety layer graduates from a self-reported plan to a validated standard.
- The Home Rule Review. Whether Congress lets an enacted act stand. Any DC law faces a 30-legislative-day congressional review and possible disapproval or an appropriations rider, and with House Republicans already pressing for faster deployment, the live risk is federal pressure on the tax, caps and labor guardrails rather than on robotaxis themselves, our forward read.
- The 2028 Gate. Not a date on a calendar. The January 1, 2028 launch is a bill provision contingent on passage, and it would fall under a mayor not yet elected: Bowser is a lame duck whose term ends in January 2027, so even an enacted bill would hand the actual buildout to her successor, one from an AV-skeptical field of possible candidates. Read it as forecast, never as a scheduled milestone.
- The Data Question. Whether markup adds any rule on retention, transparency reporting or law-enforcement access to the fleet's sensor data. As drafted the bill is privacy-blank, so absent an amendment the regime defaults to warrant practice and a company disclosure policy, against a Fourth Amendment line that Chatrie is tightening.
- The Market Lock-in. Whether DC picks a structure or lets one pick itself. An owned-fleet permit favors Waymo's model; an Uber-style mandate to carry human drivers preserves the aggregator layer and some driver pool, and the same hybrid-network push is spreading to other jurisdictions, so DC's choice is early precedent for who the AV era rewards, our labeled forward read.
Every issue
- 01Intersection of the week
- 02Impact of the week
- 03The week in review
Wiiver Weekly
One free email, Saturdays at 7:00 AM ET.
Unsubscribe anytime.
Primary sources18
- WaymoWaymo Safety ImpactMar 19Primary · The evidence base is competent on average and failing at the edges · Is DC building a framework for the technology's competence or for its failures? · The Weave
- WaymoWaymo safety impact update: 170M milesMar 19Primary · Is DC building a framework for the technology's competence or for its failures?
- WaymoNext stop for Waymo One: Washington, DCMar 25Primary · Where Things Stand · The Weave
- DC Council LIMSBill 26-0684, Autonomous Vehicle Deployment Authorization Amendment Act of 2026May 1Primary · Is DC building a framework for the technology's competence or for its failures? · Looking Forward · Where Things Stand · The Weave
- Councilmember Charles AllenCouncilmember Allen to Introduce Legislation Allowing Autonomous Vehicles to Operate in DCApr 23Primary · DC is writing the country's strictest AV rulebook into a federal squeeze · Is DC building a framework for the technology's competence or for its failures? · Where Things Stand · The Weave
- Congressional Research ServiceCRS R47927: District of Columbia Local Lawmaking and Congressional AuthorityJan 1Primary · Is DC building a framework for the technology's competence or for its failures? · Looking Forward · The Weave
- Congress.govH.R. 7390, SELF DRIVE Act (119th Congress)Feb 5Primary · DC is writing the country's strictest AV rulebook into a federal squeeze · The Weave
- DDOTDDOT Releases Report on Autonomous Vehicle PolicyApr 15Primary · DC is writing the country's strictest AV rulebook into a federal squeeze · The Weave
- TeamstersDC Teamsters, Labor Coalition Demand City Council Reject Anti-Worker Waymo BillJul 13Primary · Where Things Stand
- IAM UnionIAM Union Opposes D.C. Autonomous Vehicle Bill, Calls for Stronger Worker ProtectionsJul 13Primary ·
- NHTSAAV Developers Told an Automated Vehicle That Cannot Safely Interact With First Responders Is a DangerJul 8Primary · The evidence base is competent on average and failing at the edges · Is DC building a framework for the technology's competence or for its failures? · Where Things Stand · The Weave
- NHTSA (ADS-developer letter)Letter to Automated Driving System Developers on First-Responder Interaction (Standing General Order)Jul 8Primary · Is DC building a framework for the technology's competence or for its failures?
- NTSBInvestigation HWY26FH008: ADS-Equipped Vehicle Collision with Student Pedestrian (Santa Monica)Mar 3Primary · Where Things Stand
- NHTSAConsent Order: Cruise Crash Reporting ($1.5M civil penalty)Jan 1Primary · Is DC building a framework for the technology's competence or for its failures?
- NHTSA ODIODI Resume PE25013: Waymo AV drives around a stopped school bus (opened 10/17/2025)Oct 17Primary ·
- NHTSA ODIODI Resume PE26001: Waymo AV striking a child in the area of a school (opened 01/28/2026)Jan 28Primary ·
- NHTSA ODIODI Resume PE24016: Unexpected ADS behavior (opened 05/13/2024)May 13Primary ·
- WaymoRiding on the 6th-generation Waymo DriverFeb 12Primary · The Weave
Secondary sources, by sector30
- Axios DCHouse Republicans press D.C. mayor to legalize WaymoJun 11Secondary · Is DC building a framework for the technology's competence or for its failures? · Looking Forward · The Weave
- Axios DCWaymo pledges DC jobs as robotaxi bill heads toward a Council voteJul 13Secondary · The permit quietly picks a market structure and a labor settlement · The Weave
- WTOP'Independence' and 'protection' among themes at Monday's DC autonomous-vehicle hearingJul 13Secondary · Is DC building a framework for the technology's competence or for its failures? · Where Things Stand · The Weave
- WJLADC bill would allow autonomous vehicles; marathon hearing draws dozens of witnessesJul 13Secondary · Where Things Stand · The Weave
- TechCrunchIn major privacy win, Supreme Court rules geofence warrants are protected by privacy rightsJun 29Secondary · The evidence base is competent on average and failing at the edges · Is DC building a framework for the technology's competence or for its failures? · Looking Forward
- WilmerHaleThe Fourth Amendment Moves to the Cloud: Chatrie v. United States and the Future of Digital PrivacyJul 2Secondary · Is DC building a framework for the technology's competence or for its failures?
- SCOTUSblogCourt rules that law enforcement's use of geofence warrant was a searchJun 29Secondary · Is DC building a framework for the technology's competence or for its failures?
- Sidley Austin (EHS Brief)D.C. Council Proposes a Costly Path for Autonomous Vehicles in the Nation's CapitalMay 14Secondary · DC is writing the country's strictest AV rulebook into a federal squeeze · The evidence base is competent on average and failing at the edges · Is DC building a framework for the technology's competence or for its failures? · The Weave
- Greenberg TraurigSelf-Driving Vehicles: Liability Assignment in Crashes and ViolationsMay 1Secondary · Is DC building a framework for the technology's competence or for its failures?
- NBC4 WashingtonWhat would Waymo mean for jobs and safety in DC?Jul 13Secondary · Is DC building a framework for the technology's competence or for its failures?
- AfroDMVDC's Waymo Bill and African-Immigrant Rideshare DriversJul 1Secondary · The permit quietly picks a market structure and a labor settlement · Is DC building a framework for the technology's competence or for its failures? · The Weave
- Chamber of ProgressDC's Autonomous Vehicle Bill: Fleet Cap and VMT TaxJul 1Secondary · Is DC building a framework for the technology's competence or for its failures? · Looking Forward · The Weave
- GWU EngineeringRethinking the Road: What a Shift to Robotaxis Means for Jobs and SocietyJan 1Secondary · The permit quietly picks a market structure and a labor settlement · Is DC building a framework for the technology's competence or for its failures? · The Weave
- Nature (Humanities & Social Sciences Communications)Impact of robotaxi entry on incumbent taxi drivers' income (Wuhan/Apollo Go study)Jan 1Secondary · The Weave
- TechCrunchUber's robotaxi lobbying effort has put it on a collision course with WaymoJul 13Secondary · The permit quietly picks a market structure and a labor settlement · Is DC building a framework for the technology's competence or for its failures? · Looking Forward · Where Things Stand · The Weave
- CNBCWaymo announces $16 billion fundraising roundFeb 2Secondary · The permit quietly picks a market structure and a labor settlement · Is DC building a framework for the technology's competence or for its failures? · The Weave
- TechCrunchWaymo robotaxis are now operating in 10 US citiesFeb 24Secondary · The Weave
- CNBCUber and Waymo end Phoenix robotaxi pilotJun 29Secondary · Looking Forward
- TechCrunchFeds demand autonomous vehicle companies stop interfering with first respondersJul 8Secondary · The Weave
- The San Francisco StandardWaymo robotaxis and emergency response: firefighters' obstruction reportsJul 10Secondary · The Weave
- CNBCNHTSA opens probe after Waymo strikes child in school zoneJan 29Secondary · Is DC building a framework for the technology's competence or for its failures? · Where Things Stand
- KVUEWaymo passing school buses in Austin prompted a human remote assistant, NTSB investigation findsJan 1Secondary · Is DC building a framework for the technology's competence or for its failures? · Where Things Stand · The Weave
- Smart Cities DiveCalifornia accuses GM's Cruise of misrepresenting safety information, suspends permitOct 24Secondary · Is DC building a framework for the technology's competence or for its failures?
- The Washington TimesWaymo robotaxis with no passengers circle Atlanta cul-de-sacs for hoursMay 15Secondary · Where Things Stand
- WSB-TV AtlantaEmpty Waymos invade Atlanta neighborhood, circle cul-de-sac for hours with no passengersMay 15Secondary ·
- Traffic Injury Prevention (Taylor & Francis)Comparative safety performance of autonomous driving (Kusano et al., peer-reviewed at 56.7M miles)Jan 1Secondary · Is DC building a framework for the technology's competence or for its failures? · The Weave
- NPRWaymo called the cops on teen riders, raising privacy concernsJul 10Secondary · The evidence base is competent on average and failing at the edges · Is DC building a framework for the technology's competence or for its failures? · Looking Forward
- 404 MediaLAPD publishes crime footage it got from a Waymo driverless carJan 1Secondary · Is DC building a framework for the technology's competence or for its failures?
- WIREDTesla Says It's Building a Wheelchair-Accessible RobotaxiJul 13Secondary · Is DC building a framework for the technology's competence or for its failures? · The Weave
- KXANNTSB: Human error prompted Waymo to pass stopped school bus in AustinJul 1Secondary · Where Things Stand