The clock runs out on D.C.'s Metro deal in 21 days, and the Council isn't even back at work yet

Eight days. That's all the Council has.

The District of Columbia's dedicated-funding agreement with the Washington Metropolitan Area Transit Authority expires on September 30, 2026. The D.C. Council doesn't return from recess until September 22. Do the math: eight working days to authorize what comes next for a transit system that moves roughly 600,000 people on a busy weekday and whose capital budget depends, in no small part, on the District keeping its end of a six-year deal.

For most riders, this is invisible bureaucracy. For anyone who has watched Metro service degrade before dedicated funding existed, it is anything but.

What the expiring deal actually says

Under the agreement, the District committed to providing WMATA a dedicated funding grant of $178.5 million in each of District Fiscal Years 2021 through 2026. That money flows specifically to capital projects: replacing, rehabilitating, and modernizing existing capital assets of the system to address issues of safety and reliability, including railcars, rail systems such as propulsion and signals, and track and structures rehabilitation.

The agreement's term ends September 30, 2026. The District may exercise options to renew it no more than six times, each for a six-year period. But that renewal is not automatic. The District must give WMATA preliminary written notice of its intent to renew at least thirty days before the agreement expires. That 30-day window opened September 1. Whether that notice has been transmitted to WMATA is not yet publicly confirmed.

The original agreement stipulated that no later than March 30, 2026, the District and WMATA agree to commence discussions to determine if the District will renew the agreement for a successive term. Those discussions have been underway for months. What they haven't produced yet is a new, signed deal.

Mendelson's math problem

Renewal isn't a rubber stamp. Council Chair Phil Mendelson has raised pointed objections to how costs are divided across the region, and those objections don't disappear just because a deadline is arriving.

At an October 2025 task-force meeting, Mendelson abstained from a vote on a broader regional framework, saying he supported the intent but took issue with the funding formula. Under the proposal at that time, the District would be responsible for $173 million of the first year's costs, Maryland for $152 million, and Virginia for $136 million.

"The District of Columbia has for too long paid more than its share. We just can't keep doing that," Mendelson said at that meeting. That sentiment hasn't changed, and it lands squarely on the Council's plate the moment members walk back into the Wilson Building on September 22.

The bigger framework hovering overhead

The expiring bilateral deal sits inside a much larger regional conversation about Metro's long-term financial stability. In November 2025, the WMATA and Metropolitan Washington Council of Governments boards acted on a task force's recommendations. The COG and WMATA boards jointly endorsed recommendations from the DMVMoves Task Force, calling on regional leaders to advance funding solutions to support Metro's long-term modernization. A key proposal includes $460 million in new annual capital funding for Metro, beginning in Fiscal Year 2028.

The DMVMoves framework recommends $460 million in additional funding split between Virginia, Maryland, and D.C., starting in fiscal year 2028 and rising after that at a rate of 3 percent per year. "This is a real milestone," said Ward 6 Councilmember Charles Allen, who cochaired the 22-member panel. If the proposal wins eventual support from all the required government bodies, the additional funding "will move us from bouncing from crisis to crisis to crisis" to stability.

Allen's optimism is real. So is the gap between a regional vision and an actual signed agreement. Following the joint endorsement, regional advocacy was set to begin seeking enactment of funding legislation by the D.C. Council and the Maryland and Virginia state legislatures. Maryland and Virginia have moved. The unanimous endorsements of DMVMoves by local governments in Maryland and Virginia sent what COG Executive Director Clark Mercer called a clear signal that Metro and the transit network are central to the region's success. D.C. has not yet enacted its piece.

That gap is the story right now. The DMVMoves framework doesn't kick in until FY2028 at the earliest. The model wouldn't take effect until 2028 and would require buy-in from all three jurisdictions. The District still needs a bridge, and that bridge is what the Council has to build in eight days.

What WMATA's operating picture looks like

The capital-funding question lands while WMATA is managing real operational pressure. D.C., Maryland, and Virginia are expected to cover about 77 percent of WMATA's $2.6 billion operating budget. The remainder comes from fares, parking fees, advertising, and other income streams. Fare revenue still hasn't recovered to pre-pandemic levels, in part because reduced ridership from remote work and a smaller federal workforce has kept fare collections low.

The capital picture is separate from operations, but both lines converge at the same pressure point: a transit authority that cannot plan multi-year capital projects without knowing what the District will contribute year to year. Contractors don't sign railcar overhaul contracts on a month-to-month basis. Letting the dedicated-funding agreement lapse, even briefly, creates procurement gaps that cost money and time that Metro doesn't have.

The RFK connection

There's a second reason the Council needs to get Metro right before October 1. The Stadium-Armory station is the front door to the future RFK campus and a new Commanders stadium. In July, the WMATA board acted on agreements with the District covering two projects. The board's unanimous votes authorized entering into reimbursable agreements with the District. The step will let WMATA and the District collaborate on improvements to the Stadium-Armory station and the design of the Gold Line of dedicated bus lanes.

The D.C. Council had previously appropriated $300 million over four fiscal years for the Stadium-Armory Improvement Project and $5 million to design dedicated bus lanes to the RFK campus. Allen spelled out the urgency plainly at a July Council roundtable. "The most urgent issue is D.C. government and Metro have not signed an agreement about allowing major improvements needed at the Stadium-Armory station to move forward. '2030 may feel like it is a long way off, but it is right around the corner,' Allen said. 'They need this in three weeks.'

That was in early July. The reimbursable agreements were eventually signed. But the broader dedicated-funding picture remains open, and every day of ambiguity is a day that Metro's capital planners cannot fully book the work.

What September 22 looks like

When the Council gavels back into session, it faces a checklist that would be daunting in any September. There is the budget dispute between the Council and the CFO. There is Trayon White's bribery trial beginning in federal court. There is the November general election, with Janeese Lewis George as the Democratic nominee for mayor. The November 3 election is an open-seat contest, with primary elections having been held on June 16, 2026.

And then there is this: a funding agreement worth $178.5 million a year that runs out on the last day of the month. Council staff have been working through recess on the renewal language. Whether the votes are there, and whether the Council and Mendelson can resolve the formula dispute quickly enough, is the question that starts getting answered the moment the September 22 gavel drops.

If the Council fails to act before September 30, WMATA does not immediately go dark. The agency has reserves and operating funds. But Allen, who co-chairs the DMVMoves task force, has said he fully expects D.C. will be able to fund its share of the budget. The operative word is expects. Expectations are not legislation.

Riders heading to the Gallery Place platform on the morning of October 1 won't notice anything different. The trains will run. What they won't see is whether the District signed the paperwork that keeps the capital program funded for the next six years, or whether it punted into ambiguity again.

What D.C. Residents Should Watch

• September 22: The Council's first day back. Watch for any emergency vote or consent calendar item on a Metro funding renewal. If leadership has the votes lined up, it could move fast and quietly.
• September 30: The literal expiration date of the D.C.-WMATA dedicated funding agreement. Any gap between this date and Council action is a gap worth tracking.
• Council Chair Phil Mendelson's position: He abstained on the regional DMVMoves vote over the funding formula. Whether he moves from abstention to opposition on any renewal deal is the swing factor.
• The DMVMoves legislation: The $460 million regional framework needs D.C. Council legislation to become real. The September 30 deadline is separate from, but connected to, whether that legislation gets drafted and introduced this fall.
• Stadium-Armory capital work: The $300 million in appropriated Stadium-Armory funds tied to the RFK campus depend on a stable D.C.-WMATA relationship. Any funding lapse creates procurement risk for a project with a hard 2030 timeline.

Sources: WMATA/D.C. Dedicated Funding Grant Agreement (FY21-26); WMATA/COG DMVMoves Endorsement, November 2025; FFXnow: DMVMoves task force vote, October 2025; WMATA: Virginia and Maryland DMVMoves endorsements, February 2026; NBC4 Washington: Stadium-Armory agreement deadline, July 2026; WJLA: WMATA board RFK transit vote, July 2026; The 51st: Metro uncertainty and D.C. budget, 2025; D.C. CFO: FY2026 WMATA budget agency summary