This site has spent the fall documenting community networks that work: Lehi's take-rate numbers, Southwick's pilot, the Los Alamos open-access build and the FCC rulemaking that would shrink the local authority underneath all of them. Here is one more mechanism, and it is quieter and more total than the FCC docket: a clause in a contract every state has already signed.

The document that says it out loud

NTIA published a two-page notice for BEAD subgrantees, BEAD Subgrantees: Protect Your Rights. It tells ISPs what their states are required to include in every subgrant agreement and warns subgrantees to check that the language is "present, unaltered." Here is the required text, verbatim:

The Grantee, and any agency, instrumentality, or subdivision thereof, agrees not to enforce any law, regulation, executive order, contracting requirement, or other enforceable obligation that directly or indirectly regulates in any way the rates, terms, and conditions of broadband internet service, whether on a retail, wholesale, or network basis, or imposes net neutrality rules, open access, or other utility style rules on broadband internet service, against the Subgrantee or its affiliates anywhere it provides service within the Grantee's jurisdiction, while that Subgrantee has any subgrant that is still within its period of performance, extended period of performance, or federal interest period. For purposes of this provision, a "net neutrality rule" is any law, order, contracting requirement, or other enforceable obligation by the Grantee that prohibits internet service providers from, among other things, blocking content, throttling speeds, imposing data caps, or engaging in paid prioritization, or that imposes a general conduct or similar standard upon internet service providers.

Read the pieces:

  • Who is bound: "The Grantee, and any agency, instrumentality, or subdivision thereof." The state, its agencies, and — depending on how a court reads "instrumentality or subdivision" — the instruments of local government too: a state broadband office, a municipal utility, a city broadband division.
  • Where: "anywhere it provides service within the Grantee's jurisdiction." Not the BEAD-served rural footprint. The ISP's entire in-state service area, including its wireless networks.
  • How long: "while that Subgrantee has any subgrant that is still within its period of performance, extended period of performance, or federal interest period." The clause outlives the grant check. The federal interest period on physical assets runs to the end of the asset's program lifetime. For fiber in the ground, that is not a news cycle.
  • What it suspends: anything that "directly or indirectly regulates in any way the rates, terms, and conditions of broadband internet service" — with net neutrality, open access, and utility-style rules named explicitly. The definition of "net neutrality rule" stretches to "a general conduct or similar standard." The direct or indirect language is the whole ballgame: indirect economic regulation is exactly what a utilities commission does.

Who the funded ISPs are, in practice: per the California breakdown, roughly 69% of the state's $1.42 billion BEAD award flows to Comcast ($400M), AT&T ($331M), Verizon/Frontier ($173M), Amazon's Kuiper ($55M), and SpaceX's Starlink ($22M). Three of the four major home-internet providers, two of the three major wireless carriers, and both dominant satellite operators, exempted from state broadband law, statewide, for the length of the grant.

The coverage count

The American Prospect reported on October 19 that every U.S. state and territory has accepted BEAD funding on these terms except two: Illinois and California. New York signed despite its own Affordable Broadband Act — the signature made the state's own law unenforceable against its BEAD recipients. Illinois and California are the only jurisdictions still holding out, and California's decision window closes November 1.

So this is not a California story that happens to have a national element. It is a national story with two states still deciding whether to join.

The engineering argument, and how it cuts both ways

The industry argument for why the exemption must cover the ISP's entire footprint, not just BEAD-served locations, is engineering, and it is sound: carriers do not run two networks. A Comcast or Verizon traffic-management platform makes policy decisions across a unified statewide architecture — shared backhaul, shared routing, shared enforcement points. There is no meaningful way to apply net neutrality "only at BEAD-funded last-mile connections" while the upstream platform routes traffic for everyone. Location-scoped enforcement would be trivially circumventable.

But that same fact, read honestly, means the deal asks a customer in San Francisco or Sacramento to give up their state's net neutrality protections — for infrastructure money their address will never benefit from. The $1.42 billion pays for last-mile in unserved areas. The exemption covers every connection the five majors have in the state. The engineering truth that makes the exemption "necessary" also makes it universal.

What the money costs, both sides of the ledger

California's award: $1.42 billion, formally awarded in August 2026, covering roughly 270,000 homes and businesses. Against it:

  • The net neutrality law. SB 822 (2018) bans blocking, throttling, and paid fast lanes, and is the strongest state law on the books — the federal rules died in a court challenge in 2025, so state laws are now the only active net neutrality regime in the United States. SB 822 survived three federal court challenges, and when it became enforceable, AT&T and Verizon stopped zero-rating their own video apps within months. That is what a working consumer rule does, and it is what the clause suspends. (TechTimes has the detail; dig.watch has the policy frame.)
  • Affordability. The CPUC's January 2026 approval of the Verizon-Frontier acquisition attached a $20/month low-income plan — 5.8 million households qualify. Stanford's Barbara van Schewick's arithmetic: at a deliberately conservative 20% enrollment, that is $4.2 billion in savings over ten years — roughly three times the award. Public Knowledge puts the broader cost of Condition 50 across California's protections at $5 to $16 billion. The federal subsidy that used to backstop low-income households, the Affordable Connectivity Program, died in June 2024.
  • Public safety. AB 1699 (2019) requires mobile providers to keep emergency responders at full speed during active emergencies. The law exists because during the 2018 Mendocino Complex Fire, Verizon throttled Santa Clara County firefighters mid-response and offered to restore full service if they upgraded their plan. Verizon is a BEAD recipient. Condition 50 suspends the law against them for the grant period.

Public Knowledge's summary is the sharpest one-liner on record: signing with Condition 50 in it "would basically give the Trump administration a $1.42 billion choke chain to yank whenever it doesn't like California's broadband or other tech policy." That is the clause's second function. It is not only a shield for five ISPs; it is a lever on the state that holds the cash.

van Schewick's argument, as summarized by TechTimes: the BEAD statute itself requires states to ensure that funded providers comply with "all applicable Federal, State, and local laws." A federal agency cannot, through grant fine print, contract states out of what Congress wrote into the authorizing statute. That challenge is worth bringing — before the state signs. After the signature, the state is on the other side of its own contractual commitment, enforcement of the suspended laws risks a disbursement cutoff, and the challenge becomes dramatically harder.

The timeline detail that should bother anyone who cares about auditability: per the EFF/ILSR conversation, NTIA exempted the BEAD restructure from Administrative Procedure Act public comment — the clause went into the general terms without a comment cycle, and then per NTIA's own notice states "may not omit, alter, or otherwise attempt to contract around such language" in their subgrants, with non-compliance putting both the subgrant and the state award at risk. Fifty-four jurisdictions signed anyway. That is what an unappealable term looks like after it has been deployed at scale.

The part community networks should actually copy

Strip the politics and this is a contract-review problem, and the method transfers down to every size of project this site covers — a PUD grant, a state subgrant to a county network, a co-op's USDA loan, a franchise renewal:

  1. The grant is a purchase of lawmaking power. The headline number ($1.42B) is the money. The duration clause, the scope clause, and the affiliate clause are the other side of the sale. Price both columns before anyone signs anything. California's ledger reads $1.42 billion in, $4.2–16 billion of existing consumer protections out.
  2. Read the duration clause like an auditor. "Period of performance, extended period of performance, federal interest period" — each of those tails extends past the council meeting, the mayor's term, and possibly the staff who wrote the application. Whoever signs is signing away enforcement authority for years beyond their own tenure. That is a governance question, not a procurement detail: it belongs to the body accountable for the whole term, not to the grant writer under deadline pressure.
  3. Watch the scope words. "Directly or indirectly." "In any way." "Anywhere it provides service." "Or its affiliates." "A general conduct or similar standard." These are the phrases that make a narrow-sounding term total. In any grant agreement you sign, find them and cost them out.
  4. Notice who the strings bind. Condition 50 does not ask the subgrantee to do much. It asks the state to surrender enforcement power over the subgrantee — and NTIA's compliance machinery polices the state. Strings in intergovernmental funding run downhill from the top of the stack and bind everyone below the top level, whether or not any single community agreed to them.
  5. Audit the whole document, not just the part that hurts. The same NTIA notice contains Section 13.D permitting obligations, and some of those are genuinely useful to builders: 90-day permit decisions, a single point of contact, batch processing, cost-limited fees, escalation roundtables. The package also gives BEAD subgrantees a right to FCC-style terms for access to municipally owned poles — which, for a community that owns poles, is a federal contract converting a local asset's terms without the locality having negotiated them. Useful and extractive provisions arrived in the same envelope. That is normal. Read all of it.
  6. The people with the least leverage are the ones whose state already signed. Fifty-four jurisdictions accepted. If your community is in one of them, the state's net neutrality, open-access, and affordability rules are suspended against every funded ISP in your state for the grant duration — regardless of what your county or your co-op wanted. The two states still unsigned, Illinois and California, are holding the only remaining decision points. If you live there, your window is before November 1, and van Schewick's analysis plus Public Knowledge's are the two documents to hand your representatives.

Worth watching

  • California's decision, deadline November 1, 2026: Newsom signs → the protections are suspended and the challenge happens from the other side of a signed contract; or he signs with a reservation/litigation posture → contested; or he refuses → the state forfeits $1.42B and the argument "you can challenge and keep the money" gets a test case anyway. Any of the three outcomes is educational.
  • Illinois, also unsigned: watch whether it follows New York's pattern or holds out.
  • van Schewick's analysis page (hosted summary here) and the Preemption Tracker-style follow-up: if a state does sign, when the state's first suspended-law attempt is enforced against a BEAD ISP, someone will litigate the "instrumentality or subdivision" reach — that case will tell every municipal network whether its own contracts are exposed.
  • The EFF/ILSR conversation is the best plain-language record of the whole dispute: Unbuffered Episode 30.

The FCC docket this site covered in September shrinks what local governments may do in their rights-of-way, with a comment deadline. Condition 50 is its mirror image: it shrinks what states may require, pre-signed, nationwide, with the money as the consideration. One is being litigated in the open. The other was signed by fifty-four governments while most of their constituents had never heard of it. Between the two, the lesson for anyone building community infrastructure is the same one: the contract is the law. Read it, price it, and if you are going to challenge a term, do it before you sign.