The bill adds Section 723 to the Communications Act to create two distinct pathways for placing telecommunications or broadband facilities where public rights‑of‑way intersect railroad corridors and where work occurs inside railroad rights‑of‑way. For projects authorized by state or local governments in public rights‑of‑way, providers submit a written notification to the railroad and move forward after a short notification window; for work inside a railroad carrier's right‑of‑way providers must submit a detailed application and the railroad must approve or deny within a statutory timeframe.
The statute limits a railroad carrier’s ability to veto projects to narrow safety and infrastructure‑interference grounds, requires compensation to equal actual costs reasonably and directly tied to railroad safety, centralizes disputes at the Federal Communications Commission (FCC) with tight adjudication deadlines, and directs the FCC to issue implementing regulations within one year. The result is a federal framework intended to speed broad deployment while preserving railroad safety oversight and a defined cost standard.
At a Glance
What It Does
Creates a notification-only route for state/local‑authorized builds in public rights‑of‑way that intersect railroad corridors (no railroad application required) and a separate application route for placements inside railroad rights‑of‑way that requires engineering plans and a railroad decision within 60 days. It caps carrier denials to two narrow reasons (substantial interference/damage or safety jeopardy) and limits compensation to actual costs tied to railroad safety.
Who It Affects
Internet service providers and broadband contractors building along or across rail corridors, municipal and state permitting authorities that issue public‑ROW authorizations, freight and passenger railroad carriers, and the FCC (with coordination responsibilities for FRA and the Surface Transportation Board).
Why It Matters
This statute federalizes and standardizes coordination between broadband projects and railroads, reducing timing uncertainty and the ability of carriers to block placements for non‑safety reasons. It reallocates dispute resolution and technical determinations to the FCC, creating predictability for deployment timelines but also concentrating implementation and enforcement responsibilities at federal agencies.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
The bill distinguishes two common deployment scenarios and prescribes different procedures for each. When a state or local government already authorizes a provider to place or modify facilities in a public right‑of‑way that intersects a railroad corridor, the provider must notify the railroad carrier in writing with basic project details (location, start date, duration, entry/exit points, and contact information).
After that notification the parties coordinate a date; work cannot begin sooner than a short waiting period and generally must begin within a roughly one‑month window unless they agree otherwise. The statute explicitly says providers do not need to submit a separate application to the railroad for these state/local authorized public‑ROW projects, and it bars railroad carriers from charging for the placement—subject to any payments the provider already owes under the state or local authorization.
If the work is inside a railroad carrier’s right‑of‑way, the provider must submit a fuller application to the railroad that includes engineering and construction plans (including bore plans where applicable), location and scheduling details, entry/exit points, and contact information. The railroad then has a fixed period—statutory 60 days—to approve or deny an application and must provide a written explanation if it denies.
The denial standard is narrow: the carrier can only refuse a project if it would substantially interfere with or damage railroad infrastructure or would jeopardize the safety of passengers or railroad employees. Once approved, the parties schedule work to begin within a short statutory window unless they agree to a different date.The bill sets the financial boundary for in‑ROW work: providers must pay compensation equal to the actual costs the railroad reasonably and directly incurs in relation to railroad safety.
If either side believes the other has not complied with the statutory rules—railroads claiming underpayment or providers claiming unlawful obstruction or excessive charges—the statute permits either party to petition the FCC. The FCC becomes the sole federal adjudicator, authorized to make factual findings, use technical experts, require reimbursement of expert costs from the adversely ruled party, and issue a final order on petitions within a specified short timeframe.To operationalize the statute the FCC must issue implementing regulations within one year.
Those rules must define how to assess the narrow denial grounds, what counts as actual costs, the adjudication procedures (including expert use and cost reimbursement), and any safe limits on where providers may work inside rail corridors to protect safety and operations. The FCC must coordinate those rulemakings and any factual findings relating to railroad safety with the Federal Railroad Administration and the Surface Transportation Board.
The Five Things You Need to Know
For public right‑of‑way projects authorized by state/local governments, providers need only submit a written notification to the railroad—no railroad application—and may not be charged by the railroad for that placement.
Railroad carriers must approve or deny in‑right‑of‑way applications within 60 days; denial is limited to showings that the project would substantially interfere with or damage railroad infrastructure or would jeopardize safety.
Providers must pay railroad carriers only the actual costs reasonably and directly incurred related to railroad safety for in‑ROW work—broader profit or access fees are excluded by the statute.
Either party can petition the FCC to resolve compliance or compensation disputes; the FCC is the sole federal forum and must issue a final order within a 90‑day statutory window (with limited exceptions).
The FCC must promulgate implementing regulations within one year and coordinate with the Federal Railroad Administration and the Surface Transportation Board on railroad safety matters.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Notification process for public rights‑of‑way intersecting railroad corridors
This subsection creates a streamlined path when a state or local government has already authorized placement in a public right‑of‑way that crosses or touches a railroad corridor. The provider must notify the railroad with location, timing, duration, entry/exit points, and contact details; after notice the parties coordinate scheduling. Importantly the statute removes a railroad application requirement in this scenario and forbids the railroad from imposing payment for the placement, while clarifying that any amounts owed under the state or local authorization remain unaffected.
Application and decision process for work inside railroad rights‑of‑way
This subsection governs any placement or modification that takes place inside a railroad carrier’s right‑of‑way. It requires a substantive application—including engineering and bore plans—then gives the railroad 60 days to approve or deny. The denial grounds are narrowly drawn (substantial interference/damage to infrastructure or jeopardizing safety) and a denial must identify the specific reason(s) and explain how they apply. After approval, the statute sets a short window for commencing work, and requires providers to pay only actual, reasonable safety‑related costs incurred by the railroad.
FCC petitions and adjudication procedures
Either railroad carriers or providers can petition the FCC for relief on claims ranging from underpayment to obstruction or undue charges. The FCC is designated the exclusive federal adjudicator; it may make necessary factual findings, employ technical experts to evaluate plans and safety issues, require reimbursement for expert costs from the party that loses on those issues, and must issue a final order within a prescribed period (90 days) except where limited extensions apply. The statute also requires the FCC to coordinate safety questions with the FRA and STB.
Party responsibilities and required FCC rulemaking
Railroad carriers must take protective measures and perform any work the provider is lawfully prohibited from doing under location‑or‑work limitations the FCC will define. Providers are not required to obtain additional insurance and must carry out all aspects of implementation they are permitted to perform, building and operating facilities in compliance with federal law and accepted industry standards the FCC may specify. The FCC must issue implementing regulations within one year to operationalize denial standards, actual‑cost calculations, adjudication rules (including expert use and cost recovery), emergency procedures, and special rules for closed or abandoned crossings.
Definitions
This subsection imports definitions and clarifies scope: ‘broadband service’ points to the FCC’s regulatory definition, ‘provider’ covers telecommunications or broadband service providers, ‘railroad carrier’ uses the statutory definition in 49 U.S.C. 20102, and ‘telecommunications or broadband service facilities’ is defined broadly to capture equipment used to provide or support those services, including facilities that also serve other functions.
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 providers and ISPs — Get a predictable federal process and statutory deadlines that reduce scheduling uncertainty and lower the risk of railroad‑level vetoes for projects already authorized in public rights‑of‑way.
- State and local permitting authorities — Gain deconflicted implementation because carriers cannot require separate railroad applications for state/local authorized public‑ROW placements, which helps align municipal permitting with deployment timelines.
- Consumers in rail‑adjacent corridors (urban and rural) — Stand to receive faster infrastructure rollout where rail corridors provide efficient linear paths for fiber and other broadband facilities.
- Construction and engineering contractors — Benefit from clearer technical standards and timelines for approvals and scheduling, reducing idle time and permitting delays on rail‑adjacent projects.
Who Bears the Cost
- Railroad carriers — Face operational and implementation burdens (protective measures, performing work providers cannot do) and potential short‑term costs that they must document as ‘actual’ to justify charges; they also bear the operational risk if expedited schedules create safety issues.
- Providers (especially smaller ISPs) — Must prepare detailed engineering applications for in‑ROW work, pay for the railroad’s actual safety‑related costs, and may face adverse FCC expert‑cost allocations if adjudications do not go their way.
- The FCC — Receives concentrated adjudicative responsibility and must build technical procedures, expert panels, and coordination mechanisms with FRA and STB within the statutory windows, which creates administrative workload and potential resource needs.
- Federal safety agencies (FRA, STB) — Must allocate staff time and technical resources to coordinate with the FCC on safety determinations and to support the FCC’s rulemaking and adjudications.
Key Issues
The Core Tension
The central dilemma is straightforward: the bill seeks to accelerate broadband deployment by restricting railroad veto power and imposing statutory timelines, but doing so risks pushing safety‑critical decisions into compressed federal processes and forcing railroads or providers to absorb uncertain costs tied to safety—there is no automatic win for both speed and uncompromised railroad safety without careful regulatory calibration.
The statute pressures a tradeoff between speed and railroad safety oversight. By narrowing denial grounds and imposing tight deadlines, the bill reduces procedural friction that delays deployments but also limits the railroad’s room to insist on conservative precautions unless they can demonstrate ‘substantial interference’ or a safety threat.
That legal standard may produce disputes over what counts as ‘substantial’ interference or which costs are truly ‘actual’ and ‘reasonably and directly incurred’ for safety—questions the FCC must resolve in its rulemaking and adjudications.
The FCC’s central role creates both clarity and new points of contention. Centralized adjudication should prevent forum shopping and split decisions among agencies, but it concentrates technical judgment at an agency that will have to rely heavily on outside experts and coordination with FRA and STB.
The reimbursement mechanism for expert costs—where the losing party reimburses the FCC for experts—creates an unpredictable financial exposure for participants and could deter petitions or encourage tactical filings. Further ambiguity surrounds closed or abandoned crossings and the limits the FCC may place on where providers can do their own work; those details will determine whether the statute truly expedites access or simply reshuffles costs and delay vectors to different stages of the process.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.