DC Waymo Bill: 200-Car Cap, a Mileage Fee and a Vote Clock

A Washington, D.C. bill would let Waymo run a commercial robotaxi service in the District for the first time, with an initial cap of 200 vehicles and a per-mile fee that funds Metro and support for displaced drivers. Councilmember Charles Allen's bill is moving on a tight clock, with a committee markup reportedly set for November 9. The incoming mayor wants a delay. That makes it one of the first big tests of how a city balances robotaxis against labor.

This post separates what is confirmed from what is framing or unverified. We rely on FOX 5 DC, which reported the bill's introduction, and City Cast DC, which covered the political fight on October 16.

TL;DR: confirmed and unconfirmed

What the bill requires

According to FOX 5 DC's report on the bill's April introduction, the legislation sets requirements for companies, including:

• Equal service across neighborhoods. Similar wait times in areas such as Shaw and Congress Heights.
• Liability rules for crashes.
• Coordination with first responders, and contingency plans for emergencies such as power outages.
• Data sharing with the city to monitor effects on traffic, safety and employment.
• A vehicle miles traveled (VMT) fee for operators, with revenue split between WMATA, the regional transit agency, and workforce support programs for rideshare drivers.
• Discounts for trips that connect to Metro stations, to encourage public transit use.

City Cast DC adds that the measure requires a large portion of the fees and tax dollars paid by AV companies to go toward helping workers, and caps the initial rollout at 200 vehicles. Allen called it "one of the most progressive and substantial pieces of legislation you'll see in the country," and said "the worst thing we could do is repeat the same mistakes when Uber and Lyft came into the marketplace."

Is it an "automation tax"?

The headline you may have seen calls the fee a first-in-nation tax on automation. That is a label from commentators and social posts. The bill's text, as described by FOX 5 DC, calls it a vehicle miles traveled fee. It is charged to operators by distance driven, not as a levy on the use of automation as such. Whether it is the first of its kind anywhere is a claim we could not verify. Other cities have discussed fees on rides or miles. Treat "first-in-nation" as unconfirmed.

The distinction matters for how readers should think about the policy. A per-mile fee ties revenue to road use and congestion, which is a familiar transport policy. A tax on automation per se would be a labor-market tool. The bill's backers present it as the first kind, with proceeds used for the second purpose: money for transit and for workers.

Who supports and who opposes

Supporters include Allen, who argues the bill protects workers while giving residents a new option. Backers also claim, according to social posts we reviewed, that robotaxis can reduce traffic injuries and that competition can push up pay at Uber and Lyft. We have not verified those claims for DC, and the research on both is mixed.

Waymo says it will support "safer roads, hundreds of new jobs, and expanded access to reliable transportation options," and plans three maintenance and repair depots in the District, per a spokesperson quoted by City Cast DC. City Cast DC reports that Waymo has hired local lobbyists, met with elected officials and underwritten community groups.

Opponents include presumptive mayor-elect Janeese Lewis George, who called the push "irresponsible" and warned it would "put countless workers at risk." She wants the Council to wait until next year, when she will almost certainly be mayor, per City Cast DC. Opponents have also rallied outside the Wilson Building and sent text messages warning that AVs are unsafe, the outlet reports.

Outside pressure runs the other way: City Cast DC notes that in June a group of Republican lawmakers wrote to Mayor Muriel Bowser demanding the District legalize Waymo. Bowser is generally positive about robocabs and would likely sign the bill.

The clock

The legislative calendar drives the story. City Cast DC explains that to reach Bowser before she leaves office, the bill must be voted out of Allen's committee and receive two passing votes in the full Council. In practice, that means a markup by mid-November. The legislative session ends in December, and if the bill does not pass, it would start over in 2027, with a Council that City Cast DC expects to be more skeptical of big business after progressive primary wins.

A markup on November 9 would fit that timetable. We found that date in one opinion piece and an aggregator relaying a social post. We could not confirm it on the Council's calendar, so check the Council's schedule before relying on it.

Car on a curving road with a green path ahead, representing Waymo's proposed commercial robotaxi service in Washington, D.C.

How this compares with other Waymo markets

DC differs from cities where Waymo already operates. Elsewhere, the fight has been with state regulators or with the company's own pace of expansion. In DC the District Council must write a law to make driverless commercial service legal. For the larger picture of the company's growth, see our posts on Waymo's expansion to 14 US cities, the reported 20,000-vehicle fleet plan and the first Canadian launch in Toronto. On the competitor side, see Uber and Wayve in the UK and the Bolt and Lucid robotaxi plan.

What this means for people who follow AI

Robotaxis are one of the few AI systems that people meet in the street, and local law decides where they run. The DC bill is a template to watch because it ties permission to money and jobs: a fleet cap, a fee, a worker fund, data sharing. If it passes, other cities may copy the structure. If it fails or stalls into 2027, it will show how much a labor-friendly incoming mayor can slow a technology that the outgoing one supports.

For builders of autonomy software, the data-sharing and equity-of-service requirements are worth reading closely. They hint at the compliance load other jurisdictions may impose: reporting on wait times by neighborhood, on crashes and on employment effects.

Three scenarios for the next two months

The timeline gives the bill three plausible paths. These are our reading of the reported calendar, not predictions from any source.

1. It clears committee and the full Council in 2026. Allen holds the markup in mid-November, the committee votes it out, and two full-Council votes follow before the session ends in December. Bowser, who is generally positive about robotaxis, would likely sign. Waymo could then plan a first phase of up to 200 vehicles, though the bill's rules on equity, data and emergencies would have to be met first.
2. It is amended to ease opposition. The mayor-elect's concern is jobs. Amendments could raise the share of fee revenue that goes to drivers, lower the cap, or add a review period. The committee's decision at markup would show which side is gaining.
3. It stalls and restarts in 2027. If the votes are not there, or if Allen yields to the incoming mayor's request, the bill would have to be reintroduced in a new session. A Council that City Cast DC expects to be more skeptical of big business would then decide.

What it would take to judge the policy

Whatever passes, the useful questions are measurable. How many vehicles run, and where? What do wait times look like in the neighborhoods the bill names? How much does the per-mile fee raise, and how much reaches drivers? Did crashes, injuries or traffic change? The data-sharing requirement is meant to answer these, which makes it as important as the fee. If the city gets regular, public reporting, residents and researchers can test the claims made by both sides, including the safety and wage claims we could not verify for DC.

What we do not know

• Whether the November 9 markup is on the calendar.
• The vote count. We found no reliable tally.
• The exact fee rate per mile. Our sources do not give one.
• Whether the 200-vehicle cap is a permanent limit or an initial phase that can grow. City Cast DC calls it the initial rollout.
• Whether amendments at markup will change the cap, the fee or the timing.

Bottom line

The DC bill is real, specific and moving, with a 200-vehicle initial cap, a per-mile fee for Metro and displaced drivers, and a short window to pass in 2026. The "first-in-nation automation tax" label and the November 9 markup date are not confirmed. The political risk is the incoming mayor's call for a delay. Watch the Council calendar and the committee vote.

Related reading

• Waymo expands to 14 US cities
• Waymo's reported 20,000-vehicle fleet by 2027
• Waymo Toronto: first Canadian robotaxi launch
• Uber and Wayve race Waymo in the UK
• Bolt and Lucid 25,000 robotaxis
• Uber's 700 driverless vehicles by year end

Details are accurate as of November 5, 2026, based on FOX 5 DC and City Cast DC reporting. The legislative schedule may change.