FCC Preemption of Local Broadband Permits: The Engineering Problem Behind the Policy

By the end of this piece, you will understand what the FCC's proposed preemption of local broadband permitting rules actually changes about how wired networks get built, and why the 120-day deadline the agency proposes is more than a bureaucratic number when the work involves physical infrastructure in a shared public corridor.

What the FCC is proposing

The Federal Communications Commission has opened a Notice of Proposed Rulemaking that would preempt state and local permitting rules governing the deployment of wired broadband networks. The agency's stated rationale is that too many local governments "excessively delay approvals and seek to extract exorbitant sums from providers, resulting in costs that render some deployments infeasible." The proposal includes a 120-day deadline for processing permits and limits on the fees and compensation that local governments can require from providers. The plan is supported by broadband providers, but it has drawn objections from local governments and national associations representing them.

Why local permits exist from an engineering standpoint

The objection filed on September 21 by the United States Conference of Mayors, National Association of Counties, National League of Cities, and National Association of Telecommunications Officers and Advisors makes the technical case most clearly. They describe local permitting as "an essential public safety function protecting residents, taxpayers, and all users of finite, multi-tenant public rights-of-way." The phrase "multi-tenant" is doing significant work here. A public right-of-way is not an empty conduit waiting for a single carrier's fiber. It contains gas lines, water mains, sewer laterals, electrical distribution, traffic signals, storm drainage, and often multiple telecommunications duct banks already in the ground. When a provider wants to pull new fiber or lay new conduit, the work must be sequenced around everything else already present in that corridor.

The same filing states that the "complex coordination required to safely deploy wireline telecommunications infrastructure in, above, and below public roadways cannot be reduced to an arbitrary federal deadline." This is not merely bureaucratic language. In practice, a single linear foot of new duct bank in a congested urban corridor may require coordination with multiple utility owners, a traffic management plan, structural review of existing crossings, and possibly the relocation of non-telecom infrastructure that sits in the planned path. Aerial deployments, which the phrase "above" in the filing acknowledges, carry their own set of coordination requirements involving pole attachments, vertical clearance standards, and the structural load limits of existing poles that may already be near capacity.

The 120-day clock the FCC proposes would, if enforced, force localities to either approve work that has not been fully coordinated across all affected utility owners or face a federal override. For a network engineer, the distinction matters: a permit that is processed quickly but has not accounted for a gas line three inches to the left of the planned boring path is not a solution. It is a liability that will surface during construction, at which point the project stops entirely and the cost of remediation dwarfs the original permit fee.

The permit-hoarding counter-argument

Local governments in the docket raise a different technical point that is harder to dismiss: that incumbent providers use permitting processes to block competition. The term permit-hoarding refers to the practice of securing permits for capacity in a duct bank or conduit that the provider does not actually deploy, effectively reserving physical space and preventing a competitor from using it. From a network engineering perspective, this is a real and measurable phenomenon. Duct banks have a finite number of sub-ducts, and if an incumbent holds permits for all of them, a new entrant cannot physically install fiber in that corridor without a full trenching project, which is orders of magnitude more expensive than pulling through existing duct.

The local governments' argument is that the FCC's attention is misdirected. Rather than removing the permitting process that prevents unsafe work, the agency should be addressing the competitive abuses that actually slow deployment. This is a distinction that matters technically: the permitting process itself is not the bottleneck in most cases. The bottleneck is the physical capacity of existing infrastructure and the willingness of incumbents to share it. A 120-day deadline does not create new sub-ducts in a full duct bank; it only changes the administrative timeline for the work that would follow once capacity is available.

What this means for people who run or depend on networks

For sysadmins and network engineers who operate their own infrastructure or depend on it, the stakes are less about the permitting process directly and more about the pace and cost of last-mile and middle-mile connectivity. If the preemption proceeds and the 120-day deadline is enforced, the near-term effect would be faster deployment in corridors where the delay was genuinely administrative rather than structural. The longer-term effect depends on whether the safety and coordination functions that permits enforce are preserved or eroded.

There is a specific technical risk worth noting for anyone who has watched a fiber build in a congested corridor. If localities are forced to approve work within 120 days without the coordination time they say they need, the result could be more conflicts in the right-of-way: damaged non-telecom utilities, incomplete structural reviews, and ultimately more outages. For a network operator, a single gas line strike or water main break during a fiber pull can shut down the project for weeks and create liability that dwarfs the permit fee that was being contested. The permitting process, for all its slowness, is the mechanism by which those conflicts are identified and resolved before a drill bit or a spade touches the ground.

For power users and small businesses in areas where broadband deployment has been stalled, the question is whether the preemption actually accelerates the specific build they are waiting for, or whether it simply shifts the delay from the permitting office to the construction phase. The source material does not provide data on which of these outcomes is more likely, but the engineering reality of multi-tenant rights-of-way suggests that a meaningful portion of the delay is structural, not bureaucratic. The 120-day deadline will only produce faster networks if the physical coordination it is meant to bypass was the actual constraint, and in most established corridors, it is not.

Source: arstechnica.com