Why BEAD Non-Deployment Funds Won't Cover Your Pole Replacements

If you manage a BEAD deployment, you have heard two numbers together all year: $42.45 billion, the size of the program, and roughly $21 billion, the amount left on the table after states ran their lowest-cost selection rounds. That second number started a lot of hallway math on engineering teams. The hope was that some of the leftover money would circle back as non-deployment funding and absorb the pole replacement bills stacking up on make ready estimates.

On September 3, 2026, NTIA answered that hope with its Supplemental Deployment Policy Notice. The leftover money is going back into deployment. There is no pole fund coming, and the non-deployment guidance NTIA promised in 2025 still does not exist.

That answer changes how you plan, budget, and document pole replacement costs on every BEAD route you touch. This guide covers what non-deployment funds were supposed to be, what NTIA actually did with the savings, where pole replacement costs live inside a BEAD subgrant, and why tracking the cost causer on every pole is the discipline that protects your funding through the full audit horizon.

See how Katapult Pro's engineering design tools support cost causer tracking from the first field visit.

What Are BEAD Non-Deployment Funds?

The Broadband Equity, Access, and Deployment program was funded at $42.45 billion under the 2021 Infrastructure Investment and Jobs Act, with one core job: reach every unserved and underserved location in the country. Non-deployment funds are whatever remains of a state's allocation after that job is covered.

Under the original 2022 Notice of Funding Opportunity, states could spend leftover money on the adoption side of the digital divide. The eligible list included digital skills training, telehealth and remote learning support, device and subscription assistance, digital navigator programs, and similar work that helps people use the networks once they exist. Utility pole work never appeared on that list. A few states floated pole ideas in their draft proposals, and West Virginia went furthest, setting aside roughly $30 million in its draft for a statewide pole inspection database and make ready support. Those plans did not survive 2025.

So even under the friendliest version of the rules, non-deployment money was aimed at adoption programs, not at the poles your fiber hangs on. The idea that leftover BEAD funds might cover pole replacements was always an industry proposal, not a program rule. It is worth understanding how that proposal played out, because the story explains where things stand today.

What Happened to the $21 Billion

In June 2025, NTIA issued the BEAD Restructuring Policy Notice and rebuilt the program around a technology-neutral, lowest-cost selection round it called the Benefit of the Bargain. The same notice rescinded approval for every non-deployment activity states had already gotten approved, and stated that funding for non-deployment purposes was under review pending future guidance.

The restructured bidding produced dramatic savings. The Advanced Communications Law and Policy Institute at New York Law School tallied state plans and found states committing an average of 47.3 percent of their allocations to deployment, leaving roughly $20 to $21 billion unclaimed. NTIA has used the $21 billion figure, and by late August 2026 the agency announced that all 56 final proposals were approved, with Illinois closing out the list.

While the guidance stayed in limbo through late 2025 and 2026, the industry lobbied for a piece of the savings. Groups including the Advanced Communications Law and Policy Institute and Conexon publicly urged NTIA to let states use leftover funds to offset unexpected pole costs. Congress moved too: the SUCCESS for BEAD Act, a bipartisan bill from Senators Roger Wicker and Shelley Moore Capito, would write specific non-deployment uses into law. As of this writing, the bill has not passed and NTIA has not adopted the pole proposal.

Then came the September 3, 2026 Supplemental Deployment Policy Notice. Instead of opening non-deployment spending, it created a second Benefit of the Bargain round. States receive a supplemental eligible location list built from updated FCC map data, run a challenge process, and rebid to cover locations that fell through the cracks: defaults in other federal programs, provider misreporting, and map corrections. NTIA reserved the right to reject proposals with excessive deployment costs, and it stated plainly that "other uses of BEAD funding will be addressed in subsequent guidance."

Two things follow from that notice. First, there is no pole fund. If your deployment budget assumed leftover BEAD money would backfill pole replacement costs, remove that assumption now. Second, the true-up round means more construction, and more aerial construction means more poles, at the same time NTIA has said it will scrutinize cost levels. Teams that can show clean, defensible pole costs walk into that round with an advantage, because cost discipline is now part of how proposals get judged.

Where Pole Replacement Costs Live in a BEAD Budget

Pole replacements are an eligible deployment cost inside your subgrant. That has been true all along, and it remains true after the September notice. What governs them is not a pole-specific rule but the general federal cost principles: every cost charged to the award must be reasonable, necessary, allocable, and allowable under 2 CFR Part 200, or under 48 CFR Part 31 for commercial entities. NTIA's program FAQs confirm that BEAD does not restrict eligible uses to capital expenses; everything runs through those cost principles instead.

Notice what is missing. There is no NTIA cap on pole replacement spending, no NTIA betterment rule, and no pole line item in the program documents. The vocabulary you hear in pole attachment disputes, terms like cost causer and betterment, comes from FCC pole attachment law. The grant side speaks a different language: allocability, the question of whether a cost belongs on your award at all. Keeping those two frameworks straight is most of the battle, and connecting them correctly is where the money is.

The exposure is not small. In a May 2026 analysis, the Advanced Communications Law and Policy Institute estimated that BEAD-funded aerial fiber will touch about 3.95 million utility-owned poles across 2,053 electric utility service territories, spread over roughly 188,000 planned aerial route miles. Their cost scenarios put total pole-related costs between $534 million and $4.63 billion nationally, with a base case around $1.25 billion. Those are planning models rather than engineering actuals, and the institute says so, but the spread itself tells you something: nobody can price this precisely, partly because oversight is a patchwork. By the same analysis, the FCC directly regulates only about one in ten of the poles BEAD will touch. The rest sit under state rules or under cooperative and municipal frameworks that federal pole attachment law does not reach.

A handful of states run their own pole replacement reimbursement programs, funded with state or ARPA dollars rather than BEAD. Texas operates a $75 million fund that reimburses the lesser of half the replacement cost or $5,000 per pole, and it had paid out $28.3 million across roughly 19,000 replaced poles as of August 2025. Ohio reimburses up to about $7,500 per pole from a roughly $50 million program, and Kentucky reimburses up to $5,000 per pole. North Carolina stood up a $100 million program and later redirected a large share of it to Hurricane Helene recovery. These programs matter for two reasons. They show what a documented, per-pole reimbursement regime looks like in practice. And they carry a compliance catch: federal grant rules prohibit billing the same cost to two funding sources, so a pole reimbursed by a state fund cannot also be charged to your BEAD award. Pole-level records are what keep those channels separated.

The Two Ledgers Every BEAD Pole Lives On

"Why should I have to pay for somebody else's mistakes?" Attachers have asked that question about pole replacement estimates for decades. The FCC's cost causation rules exist to answer it, and we broke down the full framework in our guide to make ready cost sharing. The short version: you pay for the work your attachment causes, and not for someone else's non-compliant construction or the pole owner's deferred replacements.

Three exceptions to the default carry real money. A red-tagged pole, one already slated for replacement for reasons other than capacity, costs the new attacher only the incremental expense of accommodating the new attachment. A replacement not necessitated solely by the new attachment gets shared. And a pole with pre-existing violations cannot be billed to the new attacher at full replacement cost. In February 2026, the FCC's Rapid Broadband Assessment Team issued its first accelerated docket ruling, in Comcast v. Appalachian Power, and reaffirmed that last principle: the attacher owes only the incremental cost of the stronger or taller pole its attachment requires. The Commission resolved the case in about 60 days and framed the dispute in BEAD terms, because Comcast held a $126 million BEAD grant to reach roughly 13,000 Virginia locations and the pole fight stood in the way. A second complaint between the same parties is already pending, so this docket is not slowing down.

Here is the part that changes your grant math: the FCC ledger and your grant ledger describe the same pole. When the FCC framework assigns part of a replacement to the pole owner or to a prior attacher, that portion is not your cost. And a cost that is not yours is hard to defend as allocable to your federal award. Charging 100 percent of a shared-responsibility pole to the grant creates two exposures at once. You overpaid the utility under FCC rules, and you billed the government for money you had a path to recover from someone else.

To be precise about what the rules say and what they do not: NTIA has not published guidance telling subgrantees how to treat disputed or shared pole costs. The conclusion above comes from applying the standard cost principles to the FCC's allocation outcome. That is analysis, not a quoted rule. It is also the conservative reading, and the conservative reading is the one an auditor is most likely to take when tracing a six-figure invoice years from now.

One more constraint worth naming. Pole replacements sit outside the self-help remedies attachers can use elsewhere in the make ready process, and that did not change when the FCC's Fifth Report and Order took effect in May 2026. You cannot route around the pole owner on a replacement. The cost conversation is going to happen on every one of these poles, so the real question is whether you walk into it with pole-level evidence or with a lump-sum invoice and a bad feeling.

What the Audit Will Ask About Your Pole Costs

Texas already previewed how pole spending gets audited. In October 2025, the Texas State Auditor's Office reviewed the state's Broadband Pole Replacement Program and reported that the administering agency had no process to independently verify that replaced poles sat in unserved areas or that the reimbursed costs were supported. That finding landed on a simple state program with a $5,000 per-pole cap. A BEAD subgrant carries more money, more rules, and a much longer tail.

The compliance horizon is longer than most build schedules. Any entity spending $1 million or more in federal awards in a fiscal year triggers a single audit under 2 CFR 200. Records must be kept for at least three years after final closeout, and the federal interest in a BEAD-funded network runs about ten years, so retention planning should follow the decade rather than the project. Reporting runs on its own clock: semiannual federal performance and financial reports, with most state broadband offices layering quarterly reporting, milestone-based reimbursement, and clawback provisions on top. Build America, Buy America adds a materials layer, because the iron and steel in poles and hardware generally carry a domestic preference, which means supplier certifications belong in the same record as the pole photos.

Now picture the trace. An auditor pulls one replacement invoice from your 2027 construction season and asks what supported it. A defensible answer shows the pre-construction condition of the pole, the engineering analysis that made the replacement necessary, who caused any pre-existing condition on the pole, how the cost was allocated among the responsible parties, and proof that your award paid only your share. That is not a package anyone can rebuild in 2032 from a contractor's archived inbox and a route-level spreadsheet. It either exists at the pole level from the start, or it does not exist.

Managing pole replacement costs across a BEAD route? Katapult Pro's engineering design tools break down pole loading by attacher, tie photo-documented conditions to every pole record, and keep the cost allocation evidence in one system instead of scattered across contractor archives.

Schedule a demo | See the engineering design tools

What Cost Causer Records Do for Pole Owners

If you manage joint use for a pole owner, none of this reads like someone else's problem. Pole owners absorbed real pressure this cycle. NTIA's January 2026 general terms require subgrantees that own poles to follow FCC pole attachment rules across their entire footprint for the life of the federal interest period, including owners the statute previously exempted. The National Rural Electric Cooperative Association reported in September 2026 that 20 of the 63 electric cooperatives originally slated to participate in BEAD have withdrawn from the program, and it named those pole conditions among the reasons. Utilities and co-ops are not obstructing this buildout. Many are deciding whether they can afford to participate in it at all.

Cost causer allocation protects the owner side of the pole too. When a replacement cost splits by cause, the owner does not absorb a violation created by a 2014 attachment, and does not spend eighteen months disputing a lump-sum estimate that nobody can trace. The same pole-level record that keeps a subgrantee's grant clean gives the owner a defensible basis for every estimate it sends, which matters more now that estimates get tested on a 60-day docket. Both parties are better off arguing from the same photo than from two different spreadsheets, and the joint use teams processing this application surge need that shared record as much as the attachers do.

Building the Pole-Level Record

For every pole your build touches, the file should hold five things. The calibrated photos of existing conditions, captured before construction, with measurements someone else can verify. The loading analysis, broken down by attacher, so the record shows who consumes capacity and how much. The make ready design, with each work item classified by cause: required by the new attachment, caused by a pre-existing violation, or triggered by standards that changed since the last construction event. The estimate and invoices, tied to the pole rather than buried in a route total. And the allocation decision itself: who paid what share, and why.

The record starts in the field, where ground-level photo collection captures measurable documentation without anyone entering the power space. It becomes decisive in design, and this is the work Katapult Pro's engineering tools were built around. Attacher filters isolate each party's loading contribution, which is exactly the evidence a cost split rests on. Photo-documented conditions live on the pole record next to the analysis and the design, so the cause determination is attached to its proof. And because the data stays with the pole record after the job closes, pole replacement costs can be tracked, stored, and reported on for years after a broadband project like BEAD wraps up. Your retention obligation outlives the construction crew, and the record should too.

None of this requires heroics. It requires deciding, before construction starts, that cost causation gets determined and documented pole by pole, project by project, subgrantee by subgrantee, instead of reconstructed later under audit pressure. Teams that make that decision early spend their dispute energy on the handful of genuinely hard poles instead of on every pole.

Frequently Asked Questions About BEAD Non-Deployment Funds

What are BEAD non-deployment funds?

Non-deployment funds are the portion of a state's BEAD allocation left over after every unserved and underserved location is covered. The original 2022 rules allowed states to spend them on adoption-side programs like digital skills training and telehealth support. NTIA rescinded those approvals in June 2025, and as of September 2026 the leftover funds are directed into a supplemental deployment round while dedicated non-deployment guidance remains unissued.

Can BEAD non-deployment funds pay for utility pole replacements?

No. Pole work was never on the eligible non-deployment list, and the September 3, 2026 Supplemental Deployment Policy Notice directs leftover funds into a second deployment round rather than opening new spending categories. Industry groups have urged NTIA to allow leftover funds to offset pole costs, but NTIA has not adopted that proposal.

Are pole replacements an eligible BEAD cost at all?

Yes. Pole replacement and make ready costs are eligible deployment costs within a subgrant. They are governed by the federal cost principles in 2 CFR Part 200, which require every charged cost to be reasonable, necessary, allocable, and allowable. There is no NTIA-specific cap or pole line item.

What did the September 3, 2026 Supplemental Deployment Policy Notice do?

It created a second Benefit of the Bargain selection round using leftover BEAD funds. States receive a supplemental eligible location list built from updated FCC map data, run a challenge process, and rebid to cover locations missed because of program defaults, provider misreporting, or map corrections. The notice authorizes no other uses of BEAD funding at this time.

How do FCC cost causer rules affect what I can charge to a BEAD grant?

FCC rules can assign part of a pole replacement cost to the pole owner or a prior attacher, through the red-tagged pole rule, the shared-cost rule for replacements not necessitated solely by the new attachment, and the pre-existing violation principle the FCC reaffirmed in its February 2026 Comcast v. Appalachian Power ruling. A share the rules assign to another party is difficult to defend as allocable to your federal award, so document the allocation on each pole and charge the grant only your share. NTIA has not issued an explicit rule on this point; the conclusion follows from applying standard cost principles.

How long do BEAD pole cost records need to be kept?

Federal rules require records for at least three years after final closeout, and the federal interest in a BEAD-funded network runs about ten years. Since disputes and audits can surface late in that window, plan pole-level record retention around the decade, not the construction schedule.

Can a state pole replacement fund and BEAD money cover the same pole?

Not the same cost. Federal grant rules prohibit seeking reimbursement for the same cost from two funding sources. A team can use a state fund like the Texas, Ohio, or Kentucky programs for one portion of a pole's cost and BEAD for a different, documented portion, but the pole-level records must show exactly which dollars covered which work.

Ready to Put Every Pole on the Record?

The policy picture will keep moving. NTIA has promised subsequent guidance on other uses of BEAD funds, Congress has a bill pending that would define them, and the FCC has an open rulemaking on further pole attachment reforms. Any of those could open a new funding channel for pole costs, and if one does, the teams that can produce pole-level cost causation records on request will be first in line for it. If none of them arrive, the same records are what protect the grant money you already have.

Either way, the work is identical: determine who caused what on every pole, document it with evidence that holds up, charge each party its share, and keep the record for the decade the federal interest demands. That is a data problem before it is a legal problem, and it is solvable with the workflows your team already runs.

If you are building the pole-level documentation process for a BEAD route, or untangling cost allocation on one that is already under construction, we would welcome the conversation. Schedule a call with our team to see how Katapult Pro supports the field data, loading analysis, and cost causer records that keep pole replacement costs defensible for the life of the grant.