Sponsors (5)
The bill strengthens technical and compliance vetting to improve broadband quality and reduce waste, but that stricter approach risks excluding new/small providers, slowing deployment, and raising compliance costs.
Rural and urban communities will get higher-quality, more reliable broadband because applicants must demonstrate technical, financial, and operational capability and meet established technical standards before receiving subsidies.
Taxpayers are less likely to fund wasteful or noncompliant broadband projects because the FCC must vet applicants' compliance histories and capabilities before awarding subsidies.
Smaller providers and utilities with solid, compliant proposals can compete under a technology-neutral vetting process, potentially rewarding efficient or innovative solutions.
Small and new broadband providers (including startups) may be excluded from subsidy programs if they cannot meet documentation or prior-government-compliance requirements, reducing competition and market entry.
Rural and urban deployment could be slowed or deterred because strict vetting and higher penalties increase project risk and may reduce the pool of applicants.
Consumers and taxpayers could face higher costs because increased administrative requirements raise compliance expenses that may be passed on to customers or require more public funds to administer.
Based on analysis of 2 sections of legislative text.
Directs the FCC to vet applicants for new high-cost broadband awards, set technical/financial standards, begin rulemaking in 180 days, and impose minimum penalties for pre-authorization defaults.
Directs the Federal Communications Commission to create a formal vetting process for applicants and recipients of new high-cost universal service broadband awards. The FCC must start a rulemaking within 180 days to set technical, financial, and operational qualification standards, require a reasonable business plan, check applicants’ history with government broadband programs, and impose minimum penalties for pre-authorization defaults.
Introduced January 15, 2025 by Shelley Moore Capito · Last progress April 20, 2026