BEAD Deployment Challenges: How Municipalities Stay in Control

The award agreements are signed, the subgrantees are chosen, and somewhere in your city, a construction calendar now exists with your community's name on it. If you're the broadband program manager, the digital equity officer, or the public works director who inherited broadband along with everything else, this is the moment the job changes. For three years the work was planning documents and challenge processes. Now it's crews, poles, and permits, and the questions coming at you are different: which neighborhoods get built first, whether the schedule is real, and what the city will actually hold in its hands when the trucks leave.

The tempting move is to treat the buildout as the provider's problem. Award the local match, expedite the permits, stay out of the way, and let companies that build networks for a living do what they do. And what they do might be to throw money at the problem until they get permission to build. 

That approach feels efficient right up until a council member asks which blocks got fiber this quarter and the only answer available is the provider's own map. It also leaves the city carrying federal compliance exposure without the records to answer for it, because BEAD's reporting and audit obligations do not disappear just because the construction happened on someone else's spreadsheet.

This guide covers where BEAD stands as of August 2026, why pole attachments and permitting have become the deciding factor in whether builds hit their milestones, what a city gives up when it hands off the build without keeping its own records, and how joint use management gives municipalities a working system for staying in the driver's seat, whether the city owns the poles, governs the rights-of-way, or simply refuses to be a bystander in its own footprint.

See how Katapult Pro supports that work from application intake to verified as-builts.

Key takeaways:

• BEAD has moved from award to execution. As of mid-August 2026, 55 of 56 eligible states and territories have NTIA-approved Final Proposals and 53 have signed award agreements, which means the risk now lives in the field, not in the paperwork.
• Pole attachments are the documented bottleneck. Research from the Advanced Communications Law and Policy Institute at New York Law School estimates BEAD builds will touch roughly 3.9 million utility-owned poles, with pole-related costs between $534 million and $4.63 billion nationally.
• Federal rules require records the city should want anyway. BEAD subgrantees face location-level reporting and record retention that stretches years past construction, and cities that rely on provider-held data have no independent way to verify what was built.
• Joint use management works in every municipal scenario. The same shared system of applications, field data, and as-builts serves a city that owns poles, a city that governs rights-of-way, and a city that participates as a funder and advocate.

The BEAD Picture In August 2026

The Broadband Equity, Access, and Deployment program allocated $42.45 billion to close the connectivity gap, and after four years of planning it is finally producing construction. According to NTIA's BEAD Progress Dashboard, 55 of 56 eligible states and territories have approved Final Proposals and 53 have signed and returned their award agreements as of mid-August 2026, with the first BEAD-funded construction already underway.

The program has changed since it was first proposed. In June 2025, NTIA issued its Restructuring Policy Notice, replacing the original fiber-preference framework with the technology-neutral Benefit of the Bargain approach and requiring states to re-run their subgrantee selections. NTIA reported in March 2026 that the restructuring produced savings of at least $21 billion, roughly half the program, with decisions still pending on how those non-deployment funds can be used. Some industry groups have asked NTIA to let states apply a portion of the savings to unexpected pole-related costs, but as of this writing that question remains unsettled.

The dates and timelines are mostly finalized. BEAD subgrantees generally have four years from their subgrant date to complete construction, and the compliance framework around that window is federal. States must monitor subgrantees under 2 CFR 200.332, subgrantees must retain records for at least three years after final closeout under 2 CFR 200.334 (which the consultancy CTC Technology and Energy notes can stretch total retention to roughly seven years), and noncompliance carries remedies up to and including clawback under 2 CFR 200.339.

For a municipal broadband office, this shift changes the nature of the work. The question your state broadband office cared about last year was who wins the money. The question everyone will care about for the next four years is whether the build actually happens on schedule, on record, and in the neighborhoods it was promised to. We covered the deployer's side of that story in our guide to BEAD broadband deployment. This one is about the city's side.

Why Pole Attachments Decide Whether BEAD Builds Stay on Schedule

Most BEAD fiber will be attached to poles for a substantial amount of their route. The Advanced Communications Law and Policy Institute (ACLP) at New York Law School estimates that aerial construction will account for roughly 42 percent of BEAD fiber projects and that BEAD-funded builds will touch approximately 3.9 million utility-owned poles spread across more than 2,000 electric utility service territories. ACLP puts total pole-related costs somewhere between $534 million and $4.63 billion nationally, with a base scenario around $1.25 billion.

Each of those poles carries a process. An attacher applies, the pole owner surveys, engineering determines whether existing attachments need to move, make ready construction happens, and only then does fiber go up. The Pew Charitable Trusts reported in a March 2025 issue brief that getting a pole attachment permit approved can take months or even years, and that those delays put billions in federally funded deployment at risk. Commonly cited industry figures put make ready work in the range of $500 to $5,000 per pole.

The regulatory framework is trying to keep pace. The FCC's rules set survey and make ready shot clocks (45 days for surveys and 60 days for make ready in the communications space on standard-sized orders), and a July 2025 order extended defined timelines to larger applications, added 15-day notice requirements when a utility cannot meet a deadline, and expanded attachers' self-help options. In February 2026, the FCC's Rapid Broadband Assessment Team resolved its first accelerated pole dispute in about 60 days, clarifying that new attachers cannot be forced to pay the full cost of replacing poles with pre-existing violations. We break down the current timeline rules in our guide to the FCC pole attachment timeline changes. Jurisdiction adds another layer: 23 states plus the District of Columbia regulate pole attachments themselves rather than following FCC rules, and federal rules never applied to municipally owned or cooperative poles in the first place.

None of this makes pole owners the villain. A joint use department that processed a few hundred applications a year is now staring down thousands, often with the same handful of people and the same aging tracking systems. The disputes over who pays for pole replacements are genuinely unsettled questions of cost allocation, with electric utilities and cooperatives making a fair argument that their ratepayers should not subsidize communications infrastructure, and attachers making a fair argument that replacement charges can price rural builds out of feasibility. What a city can control is not the national cost causer debate. What a city can control is whether the applications, permits, and field data moving through its footprint are complete, visible, and verifiable, because incomplete applications and lost paperwork are the delays nobody has to accept.

What a City Gives Up When It Hands Off the Build

The hand-off path has real appeal. Providers have the crews, the capital discipline, and the construction experience. City staff are stretched across a dozen priorities, and broadband may be a fraction of one person's job. Writing a check and getting out of the way looks like humility about what the city is good at.

The history of fiber deployment suggests the city should keep at least one hand on the wheel. In 2017, the National Digital Inclusion Alliance documented how fiber-enhanced upgrades in Cleveland systematically skipped lower-income neighborhoods, a pattern researchers have since found in other markets by comparing deployment maps against income data. That history does not require bad intent from today's providers, and BEAD's location-based awards constrain where subsidized construction happens. It requires only that build priorities get set by an organization whose incentives differ from the city's, without a record the city can independently check. Deployment maps drawn by the builder, verified by the builder, and stored on the builder's systems are exactly that.

The compliance exposure is more concrete. BEAD reporting runs at the level of individual Broadband Serviceable Locations, state broadband offices monitor subgrantees against milestone schedules, and the record retention window stretches years past the last splice. When the auditable trail lives entirely in a provider's project management platform, the city is a guest in someone else's environment, and the data can leave with the relationship. A contractor changes, a provider gets acquired, a subscription lapses, and the as-built record for a federally funded build in your rights-of-way is suddenly an email request instead of a database you own.

There is also the equity question that municipal broadband staff raise more often than any other. A recurring ask we hear from city broadband programs is for deployment support that treats every provider evenly: the same application process, the same data requirements, the same visibility into status, regardless of the size of the company asking. That is hard to guarantee when every provider brings its own process and the city's only view is whatever each one chooses to share. It is straightforward when every application and permit flows through one system the city can see, because equal treatment becomes a property of the process instead of a promise.

Three Ways Municipalities Show Up in a BEAD Build

Cities do not all hold the same cards. Joint use management is the discipline of coordinating everyone who shares pole infrastructure, and its value to a municipality depends on which seat the city occupies. There are three.

If Your City Owns the Poles

Roughly 2,000 community-owned public power utilities serve customers across 49 states, according to the American Public Power Association, and many of them own the poles in their territory. If yours is one of them, federal pole attachment rules do not apply to you, which means the attachment process in your footprint is yours to define. That freedom is an advantage and a responsibility at the same time. Attachers arriving with BEAD deadlines will judge your city by how quickly a complete application moves, and your team will be judged internally by whether every attachment on your poles is documented, engineered, and safe.

A municipal pole owner needs the same things any pole owner needs during a deployment surge: a current inventory, published standards, a single intake for applications, engineering review tied to real field data, and a record of what actually got built. Our guide on how utility ownership types change joint use covers how the process differs for municipal systems, and our playbook for building a healthy joint use program walks through the program fundamentals in depth.

If Your City Controls the Rights-of-Way

Most cities do not own poles, but nearly all of them govern the rights-of-way those poles stand in. Permits, franchise agreements, traffic control, restoration standards, and inspection authority all run through the municipality, which makes the city a required stop for every crew in a BEAD build whether anyone planned it that way or not. Some states are building tools to ease that load, like the Illinois Office of Broadband's statewide permit map that aggregates permitting jurisdictions for builders, but inside city limits the process still belongs to the city.

For this seat, joint use management looks like permit and application tracking on shared data. When the city, the pole owner, and the attachers can all see the same application status, the same field photos, and the same construction schedule, the weekly coordination calls stop being archaeology sessions. The city gains the ability to answer, in minutes, which permits are open, which are stalled and why, and which closed without their restoration work verified.

If Your City Is a Major Stakeholder Without Pole Ownership

Plenty of municipalities enter BEAD holding neither poles nor unusual permitting power, and some sit alongside more than 300 municipal broadband networks nationwide that BroadbandNow counts as of 2026, each with its own posture toward private deployment. Even in the pure stakeholder seat, the city holds one bargaining chip that costs providers almost nothing and protects the community for decades: making a shared, location-level record of the build a condition of local cooperation, expedited permitting, or matching support.

That means requiring as-builts tied to Broadband Serviceable Locations rather than PDF maps, requiring photo documentation of construction in city rights-of-way, and keeping those records in a system the city controls. Providers who intend to build what they promised have little reason to object, and the city ends the program with an asset: a verified picture of its own infrastructure that outlives any single provider relationship.

How Municipalities Stay in the Driver's Seat: A Five-Step Framework

The pattern below works across all three seats because it is built on the same principle: the city keeps an independent, verifiable record of the build in its footprint, from first application to final inspection.

1. Put the inventory and the standards in one place. Whether it is poles the city owns or rights-of-way the city governs, execution starts with knowing what exists. Consolidate pole records, permit requirements, construction standards, and restoration specs into a single source your team and every applicant can reference, because the alternative is re-explaining the rules one email thread at a time.

2. Route every application through one intake. A single application and permitting front door, visible to the city, the pole owner, and every attacher, does more for execution than any other single change a municipality can make. Katapult Pro's pole attachment application portal was built for exactly this: every party sees the status of every request at every step, which removes both the black box that frustrates attachers and the favoritism concern that worries city leadership.

3. Make the field data verifiable. Applications and permits are only as good as the field reality behind them. Photo-documented data collection, with measurable heights and timestamped images tied to each pole location, gives the city engineering-grade evidence instead of assurances. When a question comes up two years later about what was on a pole before construction, the answer is a photo, not a memory.

4. Hold construction accountable. Approved is not the same as built correctly. Post-construction inspection closes the loop by verifying that what went up matches what was engineered and permitted, and it catches the violations and skipped restoration work that otherwise surface as complaints and change orders years later.

5. Own the as-built record. The end state of a well-run BEAD footprint is a location-by-location record of what was built, when, by whom, with photos and inspection results attached, stored in a system the city holds the keys to. Your GIS remains the system of record for enterprise asset data; the working record of the build feeds it cleanly instead of arriving as a box of redlines at closeout.

Coordinating a BEAD build across providers, permits, and pole owners is complicated enough without chasing status through inboxes. Katapult Pro gives municipal teams one place to manage applications, field data, construction status, and as-builts, whether you own the poles or govern the rights-of-way. Book a discovery call or see how the joint use workflow runs.

Where Katapult Pro for BEAD Deployment Fits

Katapult Pro for BEAD Deployment combines joint use, field data, and construction workflows as one working layer for deployment. It's a configuration of the tools our own teams use on deployment projects every day: the application portal for intake and status, photo-based field data collection, make ready engineering workflows, construction tracking, and post-construction inspection, all operating on one shared dataset the city can see and keep.

For a municipal pole owner, that means running the attachment program end to end: applications arrive through the portal, field data comes back photo-documented, engineering happens against real measurements, and every closed application becomes part of a growing verified record of your plant. For a rights-of-way authority, it means permit tracking and shared visibility across every provider and contractor working in the city. For a stakeholder city, it means a place to receive and hold the location-level as-builts you have made a condition of cooperation.

Two honest boundaries are worth stating. Katapult Pro is the working layer between field reality and your enterprise systems, not a replacement for your GIS, which remains your system of record. And the platform organizes and documents the deployment; it does not make the national pole replacement cost disputes go away. What it removes is the friction the city can actually control: lost applications, invisible status, unverifiable field claims, and records that leave when a contractor does.

Teams usually evaluate the fit by running a pilot project through the system and comparing the outputs against their current process. Implementation setup takes approximately 10 hours, and terms are month to month with no early termination penalties, which reflects how we think a public agency should be able to buy software: on results, not lock-in.

Common Mistakes Cities Make During BEAD Execution

Treating the award as the finish line. The announcement is when the political attention peaks and when the operational risk begins. Cities that stand up their tracking and records process in the first months of construction spend the next four years answering questions from a database, while the ones that wait end up reconstructing history from email threads, usually during an audit.

Letting every provider bring its own process. Five providers with five application formats, five status-reporting habits, and five definitions of done will consume more staff time in coordination than one shared process costs to set up, and the inconsistency itself becomes an equity problem when smaller attachers get lost in the shuffle.

Skipping post-construction inspection. Construction quality problems are cheapest the week the crew is still in town and most expensive when they surface as an outage, a clearance violation, or a resident complaint three years later. An inspection step with photo evidence protects the city, the pole owner, and honestly the provider too, since it settles disputes about workmanship with facts.

Waiting for a dispute to start keeping records. Every stalled application, missed window, and cost disagreement in a BEAD build eventually turns into a conversation about what happened when. The party with the timestamped record tends to win that conversation, and building the record after the dispute starts is not an option.

Confusing the provider's map with the city's record. Providers should absolutely keep their own systems, and good ones do. The mistake is the city having nothing of its own. Shared visibility during the build and a city-held record after it are what make the relationship durable instead of dependent.

Frequently Asked Questions About Municipal BEAD Deployment

What are the biggest BEAD deployment challenges for municipalities?

The recurring challenges are pole attachment and permitting delays, limited staff capacity to coordinate multiple providers, lack of visibility into where and when construction actually happens, and federal compliance obligations, including location-level reporting and multi-year record retention, that outlast the construction itself. Most of them trace back to fragmented processes and records the city does not control.

Do FCC pole attachment rules apply to municipally owned poles?

No. Section 224 of the Communications Act exempts municipally owned and cooperative poles from FCC pole attachment regulation, so a municipal pole owner sets its own rates, terms, and timelines, subject to any state requirements. Separately, 23 states plus the District of Columbia have certified to regulate attachments on investor-owned utility poles themselves rather than defaulting to FCC rules.

How long do BEAD subgrantees have to complete construction?

BEAD subgrantees generally have four years from the subgrant date to complete their deployment. Record retention obligations continue for at least three years after final closeout under 2 CFR 200.334, which is why cities and providers alike need records built to last well beyond the construction window.

What records should a city require from a BEAD-funded build?

At minimum: location-level as-builts tied to Broadband Serviceable Location IDs, permit and application histories, photo documentation of construction in public rights-of-way, and post-construction inspection results. The record should live in a system the city can access independently of any single provider or contractor.

What is joint use management for a municipality?

Joint use management is the coordination of everyone who shares pole and rights-of-way infrastructure: pole owners, attachers, and their contractors. For a municipality it covers attachment applications, permit tracking, engineering review, construction status, and as-built documentation, ideally on one shared dataset so every party works from the same facts.

Can a city use Katapult Pro if it doesn't own any poles?

Yes. Cities that govern rights-of-way use the platform for permit and application tracking with shared visibility across providers, and stakeholder cities use it to receive and hold location-level as-built records. Pole ownership changes which workflows matter most, not whether the system fits.

What happens if a BEAD project misses its milestones?

State broadband offices monitor subgrantees against their milestone schedules under 2 CFR 200.332, and sustained noncompliance carries federal remedies up to and including recovery of funds under 2 CFR 200.339. In practice, the earlier a schedule problem is visible, the more options everyone has, which is an argument for shared, current construction status rather than quarterly surprises.

Ready to Keep Your Build on the Record?

BEAD will connect millions of homes, and in most communities it will be the largest infrastructure investment in the public right-of-way in a generation. The cities that come out of it strongest will not necessarily be the ones that owned the most poles or wrote the biggest checks. They will be the ones that can answer, with evidence, what was built, where, when, and to what standard, because that record is what turns a four-year construction program into a permanent public asset.

Our team builds and runs these workflows on real deployments every day, for pole owners, attachers, and the engineering firms in between, and we have configured the same platform for every seat a municipality can occupy. If your city is heading into BEAD execution and the current plan is a shared drive and good intentions, it is worth an hour to see what the alternative looks like.

Book a discovery call with our team to walk through how Katapult Pro for BEAD Deployment would work in your footprint, whether you own the poles, run the permits, or simply intend to stay in the driver's seat.