The BEAD FEE Act of 2025 amends the Infrastructure Investment and Jobs Act to make access to Broadband Equity, Access, and Deployment (BEAD) grant funds conditional on how States and political subdivisions charge fees tied to broadband infrastructure. After enactment, the Assistant Secretary must withhold most BEAD funds from any eligible entity that charges authorization or right‑of‑way fees unless those fees meet new statutory standards.
This is a federal leverage bill: it does not directly set local taxes or authorize new spending, but it forces states and localities that want BEAD funding to revise fee schedules, justify charges with cost-based calculations, and publish fee structures. That will shift both the administrative work of fee-setting and the financial calculus for deploying broadband in underserved areas.
At a Glance
What It Does
The bill bars the Assistant Secretary from making BEAD grant funds available to an eligible entity (with a narrow carve-out) if the entity or any political subdivision charges a fee for considering requests to place, construct, or modify broadband infrastructure, or charges for use of a right‑of‑way, unless that fee is competitively neutral, technology neutral, nondiscriminatory, publicly disclosed, calculated from actual and direct costs, and itemized between nonrecurring and recurring uses and between existing and new infrastructure.
Who It Affects
Primary targets are State broadband offices, state and local permitting authorities, and municipal or county owners/managers of rights‑of‑way that impose permit or ROW fees. Broadband service providers and contractors seeking permits or access to municipal infrastructure are directly affected by any changes to fee structures and disclosure practices.
Why It Matters
By conditioning federal grant eligibility on fee practices, the bill aims to reduce per‑mile deployment costs and inconsistent local barriers that delay projects, while imposing transparency and cost‑justification obligations on local governments — a shift that will drive administrative work, potential local revenue impacts, and legal friction over fee formulas.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill inserts a new paragraph into the BEAD statute that turns federal grant eligibility into a compliance lever: states (and their political subdivisions) that charge fees related to permitting or using public rights‑of‑way for broadband projects must ensure those fees meet a four‑part statutory test or risk losing most BEAD funding. The test requires fees to be neutral across competitors and technologies, publicly posted, rooted in measurable direct costs, and presented in a way that separates one‑time charges from recurring charges and distinguishes use of existing infrastructure from entirely new placements.
Operationally, that means state broadband offices and local permitting bodies will need to inventory current fee schedules, perform cost studies that isolate 'actual and direct' costs (for example, plan review, processing, and repairs/replacements tied to broadband work), and adopt clear public disclosures explaining how each fee category is calculated. The bill explicitly allows charges only for objectively reasonable costs tied to review/processing and to repairs, replacement, or facilitating equipment — it does not authorize fees to cover general municipal overhead, unrelated staff time, or revenue beyond demonstrable impacts from the broadband activity.The statute uses the potent enforcement tool of withholding funds from the Assistant Secretary — not fines, not private rights of action.
The text carves out a specific grant category (an exception for 'paragraph (1)(C)') from this restriction, so covered entities must check BEAD’s underlying statutory paragraphs to understand which awards are affected. The bill provides no administrative dispute resolution, no safe harbor timetable for fee changes, and no detailed standard-setting process, leaving implementation choices to federal guidance and, likely, litigation over ambiguous terms like 'objectively reasonable.'
The Five Things You Need to Know
The Assistant Secretary must not make available BEAD grant funds to an eligible entity (except for grants under paragraph (1)(C)) if the entity or any political subdivision charges an authorization or right‑of‑way fee that fails the bill’s tests.
Required fee characteristics are: competitively neutral, technology neutral, nondiscriminatory, publicly disclosed, and calculated from actual and direct costs using only costs that are 'objectively reasonable.', Permissible cost bases are limited to review and processing of requests and to repairs or replacement of components/materials or equipment that result from or facilitate the broadband placement, construction, or modification.
Fees must be described to a requester in a way that separately identifies nonrecurring versus recurring charges and distinguishes charges for using infrastructure already hosting broadband from charges for infrastructure with no broadband present at the time of request.
The statutory weapon for enforcement is denial or withholding of BEAD funds by the Assistant Secretary rather than a new federal fee regime or civil penalties, amplifying federal leverage over state and local fee practices.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Short title
Provides the Act’s short names: 'Broadband Expansion And Deployment Fee Equity and Efficiency Act of 2025' and 'BEAD FEE Act of 2025.' This is a standard naming provision with no operational effect, but it frames the bill’s purpose for guidance, rulemaking, and litigation references.
Conditioning BEAD funds on fee practices
Adds a new paragraph that prevents the Assistant Secretary from providing BEAD funds to an eligible entity if that entity, or any political subdivision, charges specified fees unless those fees satisfy the statutory criteria. The practical effect is to make federal grant eligibility contingent on state and local fee reforms rather than to directly regulate the substance of municipal legislation.
Neutrality and nondiscrimination requirement
Specifies that acceptable fees must be competitively neutral, technology neutral, and nondiscriminatory. In practice, authorities will need to review fee rules to ensure they do not advantage a specific carrier type (e.g., incumbent cable over fiber startups) or a particular technology and may need to rewrite ordinances or schedules.
Public disclosure and cost‑based calculation
Requires public posting of fee schedules and ties allowed fees to narrowly defined cost categories: (i) review and processing and (ii) repairs/replacement or equipment directly resulting from broadband work. The bill adds the qualifier 'objectively reasonable' for cost selection, which obliges localities either to document supporting cost studies or accept federal scrutiny when BEAD eligibility is determined.
Itemization and distinction of fee types
Requires fee descriptions to distinguish between nonrecurring and recurring charges and to separately address infrastructure already hosting broadband versus infrastructure without broadband at request time. That forces greater granularity in permit invoices and creates different pricing outcomes depending on whether an operator is collocating on existing poles or building new pathways.
This bill is one of many.
Codify tracks hundreds of bills on Infrastructure across all five countries.
Explore Infrastructure in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Broadband deployment contractors and service providers — They should face fewer unexpected or opaque local fees and clearer, standardized cost categories, which simplifies project budgeting and reduces negotiation time with localities.
- Residents in underserved areas — Standardized, cost‑based fees are intended to lower deployment costs and reduce delays, accelerating buildout timelines for communities targeted by BEAD funds.
- State broadband offices administering BEAD funds — The law gives them a clear statutory lever to require local compliance as a condition of funding, simplifying enforcement strategy compared with ad hoc negotiations.
- New market entrants and smaller ISPs — Technology and competitive neutrality requirements reduce the risk that legacy franchise or fee structures favor incumbents, improving access to ROW or municipal infrastructure.
Who Bears the Cost
- Local governments and political subdivisions — They may lose fee revenue or face the administrative burden and expense of conducting cost studies, rewriting ordinances, and establishing public disclosures to meet the statute’s standards.
- Small municipalities with limited staff — Preparing the documentation to demonstrate fees are 'objectively reasonable' and publishing itemized fees will consume scarce legal and accounting resources.
- State agencies managing finance and legal compliance — State-level staff will need to coordinate across numerous localities to certify compliance or redesign grant conditions, adding administrative workload.
- Entities that monetize ROWs (e.g., utilities or municipal utilities) — Those owners face potential reductions in revenue if their existing fee structures exceed what the statute allows as 'actual and direct' costs.
Key Issues
The Core Tension
The central dilemma is between national deployment goals (lowering and standardizing local fees to speed broadband buildout) and local fiscal autonomy and practical cost recovery; the bill forces a choice by tying federal dollars to narrow fee rules, but it supplies ambiguous legal standards and no funding to backfill local revenue, creating trade‑offs without clear implementation pathways.
The bill uses a blunt instrument — withholding BEAD funds — to push fee reforms, but it leaves critical implementation questions unanswered. 'Objectively reasonable' is undefined, so municipalities will need either federal guidance or court clarification before knowing which cost items survive scrutiny. The absence of a transition or grandfathering provision means fees in place at enactment could immediately threaten BEAD eligibility, pressuring quick local changes.
There are also federalism and fiscal tensions. Local governments use ROW and permitting fees both to recover direct costs and to raise revenue; forcing a narrow cost‑recovery model risks revenue shortfalls unless states or the federal government provides offsets.
The carve‑out for 'paragraph (1)(C)' creates an unexplained exception that could produce uneven application across types of BEAD awards. Finally, practical problems — distinguishing existing infrastructure from 'no infrastructure' in complex urban ROWs, allocating shared repair costs among multiple utilities, and policing disclosure accuracy — will create compliance frictions and likely litigation over the statute’s vague standards.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.