BEAD compliance

BEAD pole-attachment compliance: what subgrantees now have to track

A January 2026 NTIA update quietly put far more BEAD-funded poles under FCC pole-attachment rules than most subgrantees realize.

If your build is funded in whole or in part by BEAD, your pole-attachment obligations may be broader than "the utility is FCC-regulated or it isn't." Here's what changed, and what it means for your reporting.

What changed

NTIA's January 2026 update to the BEAD Program's General Terms and Conditions requires BEAD subgrantees that own utility poles — including electric cooperatives and municipal utilities that were previously outside FCC jurisdiction — to comply with FCC pole-attachment rules for the duration of the federal interest period. That obligation applies across the subgrantee's entire pole footprint, not just the poles touched by the BEAD-funded build itself.

That's a meaningfully larger scope than the historical baseline. FCC jurisdiction over investor-owned utilities has applied in only 27 states; cooperatives and municipal utilities were generally exempt. BEAD changes that calculus for any co-op or muni that took subgrantee funding and owns poles.

$42.45B
total BEAD program funding
3.95M
utility poles BEAD construction will touch
41.8%
of planned BEAD fiber miles are aerial
~40%
of aerial BEAD miles run through co-op territory

Why this matters for your reporting

NTIA is requiring BEAD subgrantees to report on pole-attachment delays and FCC rule compliance as part of the program's oversight. If you can't produce a clean record of when an application was filed, when each FCC deadline was hit or missed, and what self-help remedies were triggered, you're building that record retroactively under a reporting deadline — instead of having it fall out of your day-to-day pipeline automatically.

What to have ready

Jurisdiction type per utility. FCC, state-regulated, cooperative, or municipal — and whether that utility is a BEAD subgrantee itself, which determines which rule set actually applies.
A timestamped deadline record. Completeness review, survey, estimate, and make-ready dates — as they were computed at the time, not reconstructed after the fact.
Self-help eligibility events. When a utility missed a survey or make-ready deadline, and whether you exercised the remedy.
Make-ready cost documentation. Estimates, invoices, and variance — useful both for your own budget and for demonstrating costs weren't unlawfully shifted.
An audit trail, not just current state. Who changed what, and when — status changes, estimate edits, document uploads — in case a reviewer asks how a number was reached.

This is exactly what PoleDocket's deadline engine, make-ready ledger, and audit log produce as a byproduct of normal use — not a separate compliance project. Status reports, cost-variance reports, and deadline-compliance reports are one click per application, scoped to whatever a grant administrator or auditor asks for.

If you're not sure which rules apply to a given utility

The safest default: if a utility is a BEAD subgrantee and owns the poles you're attaching to, assume FCC pole-attachment timelines apply to your entire relationship with them for the federal interest period — not just the BEAD-funded segment of your build. Confirm with the utility or your grant administrator where jurisdiction is unclear; the cost of assuming FCC timelines apply when they technically don't is much lower than the reverse.

Let your pipeline generate the compliance record

Every deadline, self-help event, and make-ready dollar tracked automatically — export a status or compliance report whenever your grant administrator asks.

Try the free calculator