The federal partner is leaving the room. Most cities have no systematic way to know which of their districts were designed around that partner's presence — and which can hold without it. That audit is now urgent.

The March editorial named a structural condition that most of the district sector has not yet engaged with directly: special tax districts in America were built over the last fifty years in a funding ecosystem that included a federal partner. Lease revenues from federal offices anchored weekday foot traffic in commercial corridors. CDBG grants funded the planning work, small business support, and corridor infrastructure investments that districts leveraged. EDA grants capitalized the transit and streetscape projects that made districts viable. And the administrative capacity of federal agencies — the staff who processed grants, managed reporting, and built relationships with local economic development offices — made all of it work at the operational level.

The federal partner is leaving the room. Most cities have no systematic way to know which of their districts were designed around that partner's presence — and which can hold without it.

That ecosystem is contracting. DOGE has terminated nearly 700 federal leases. The Trump administration's FY2026 budget proposed eliminating CDBG entirely. HR2766 — the Special District Fairness and Accessibility Act, which passed the House 352-27 and has bipartisan Senate sponsorship — cannot advance through the Senate. And the administrative capacity that delivered federal dollars to local corridors has been deliberately reduced across multiple agencies. The direction of travel is structural. It is not reversing in the next electoral cycle regardless of who holds the White House.

The question for city economic development staff managing district portfolios is not whether this matters. It is which of your districts are materially exposed — and what that exposure actually means operationally.

Four Dimensions of Federal Dependency

Federal dependency in a district portfolio shows up in four distinct ways, each requiring a different response.

The first is tenant dependency: districts whose assessment base includes significant federal office occupancy. When federal agencies consolidate, downsize, or vacate, those buildings lose commercial tenants, generating assessment pressure and programming obsolescence simultaneously. Washington DC's ten BIDs are the extreme case, but mid-market cities with significant federal agency presence — Kansas City, Atlanta, Denver, Albuquerque — carry versions of this exposure that their district enabling documents do not reflect.

The second is grant dependency: districts whose programming budgets assume CDBG-funded city support, EDA-funded infrastructure grants, or federal pass-through resources that flow through the city to district corridors. This is frequently invisible in district financial statements because the federal money shows up as city funding. When the city loses the federal grant, the district loses the city program — and the district's enabling documents describe no mechanism to address the gap.

The third is capital dependency: districts whose long-term growth plans require federal infrastructure investment they cannot capitalize locally. The KC Streetcar TDD is the clearest current example: a genuinely self-reinforcing operations model, assessment-funded and sales-tax-grown, that cannot build its next line without federal grants. The self-reinforcing model solves the operations problem. It does not solve the capital problem. Any district with unfunded capital projects in its development plan that assume federal participation has this exposure.

The fourth is recognition dependency: districts that cannot directly access federal grant programs because they are not recognized as eligible units of local government under federal law. This is the HR2766 problem. Until OMB issues the guidance that bill would require, many special districts must route federal grant applications through their city — creating administrative overhead, timing delays, and political friction that limits the total federal resources accessible to district corridors. If HR2766 stalls permanently, that dependency is structural rather than temporary.

The Audit Framework

A federal dependency audit for a city district portfolio does not require sophisticated modelling. It requires answering four questions for each district under management, in sequence.

First: what percentage of the district's assessed property base is occupied by federal tenants? Any district where federal occupancy exceeds 15% of assessed value warrants a formal scenario analysis of what the assessment base looks like if that occupancy contracts by half. This is now a routine risk management question, not an edge case.

Second: what city programming within the district boundary is funded wholly or partially by federal grants that flow through the city? CDBG-funded small business technical assistance, EDA-funded corridor streetscape grants, federal transportation funding for pedestrian infrastructure — any of this that the district's programming plan assumes will continue needs to be modelled against a scenario in which it does not.

Third: does the district's long-term development plan contain capital projects that require federal co-investment to advance? If yes, what is the local-only financing alternative, and has that alternative been costed? Districts with unfunded federal-dependent capital projects should either develop credible local-only alternatives or formally revise their development plans to remove projects that are not viable without federal participation.

Fourth: is the district currently able to apply directly for federal grants, or does every federal application route through the city? If the latter, the city should be actively supporting HR2766 and S.2014 — not as abstract advocacy but as a concrete operational interest. Direct district eligibility reduces administrative burden, accelerates grant timelines, and expands the total federal resources accessible to the portfolio.