.png?width=1200&height=540&name=Thought%20Leadership%20Template%20(9).png)
A role-based self-assessment for pole owners, attachers, and OSP engineers
Federal dollars and federal scrutiny are converging on the utility pole at the same time. The Advanced Communications Law & Policy Institute's May 2026 BEAD Pole Analysis estimates BEAD-funded construction will touch roughly 3.95 million utility-owned poles across 2,053 electric utility service territories, with pole-related costs that could reach $4.63 billion.[1] Meanwhile, the FCC's Wireline Competition Bureau has formally reminded the 23 states (plus DC) that regulate their own pole attachments of their obligation to do so effectively, and is taking comment on whether its certification rules should change.[2] And under NTIA's January 2026 BEAD terms, pole-owning subgrantees whose poles aren't already regulated must follow FCC pole attachment rules for the full ten-year federal interest period on their networks.[3]
Look at what recent attachment disputes actually turn on. Not rates in the abstract, but questions of record: what is on the pole, who put it there, what condition was it in before construction started, and who can prove it. When the record is ambiguous, disagreements escalate to lawyers. When the record is defensible, most disagreements never happen.
Defensible field data has three properties, and every item below is tagged with the one it tests:
- Standardized: measured against real engineering standards, applied the same way by every crew and vendor
- Documented: photographic, timestamped, and inspection-backed, ready for an auditor or a courtroom
- Shared: every party working from one record instead of three competing versions
How to use this checklist
Find your role below and answer its six items. Answer yes only if the statement is true today for the programs you run, not true in a plan or a pilot. If your work spans roles (many consultants also manage attacher programs, and some utilities attach to poles they don't own), answer every section that applies.
For pole owners and utilities
You're accountable for the safety and integrity of the plant while application volume climbs and regulators ask harder questions. For a pole owner, defensible data is risk mitigation: it protects the grid, the ratepayer, and your program's authority to say no when no is the right answer.
1. Your engineering standards live where contractors work, not only in a PDF. (Standardized) A 3,000-page standards document nobody reads is not a standard in practice. When specifications live where field crews and design teams do their work, interpretation stops varying by vendor.
2. Every make ready requirement traces back to a specific engineering standard. (Standardized) "This doesn't meet our standards" is only a defensible answer if you can point to the standard. If you can't, the requirement reads as arbitrary, and arbitrary is what regulators and complainants look for.
3. Every attachment on your poles has an owner of record. (Documented) Unowned attachments are where safety violations, billing disputes, and transfer delays accumulate. If you can't say who owns what, you can't say who's responsible for what.
4. Post-construction inspections are documented, not just performed. (Documented) An inspection that isn't recorded might as well not have happened, because you can't show it to an auditor. Documented inspections turn completed work into a defensible position.
5. Your records show who changed what, and when. (Shared) An audit trail is what separates a record from a claim. If a measurement or a status changed, you should be able to show the history rather than assert it.
6. A regulator could review your program from your records alone. (Shared) With state attachment authority under active FCC review,[2] "effective regulation" gets demonstrated through pole owner records. If proving your program works requires assembling evidence from emails, spreadsheets, and institutional memory, the record isn't defensible yet, because assembly under pressure is where records fall apart.
For attachers and ISPs
You're measured on deployment timelines and funding compliance, and both run through poles you don't own. For an attacher, defensible data protects your schedule and your money: it's how you hold a shot clock, contest a cost that isn't yours, and satisfy a decade of federal obligations.
1. Pre-existing violations are documented before your construction begins. (Documented) The FCC's first-ever Accelerated Docket pole attachment ruling, decided in early 2026, hinged on exactly this: who bears the cost of violations that existed before the new attacher arrived.[4] The party with the pre-construction record wins that argument. The party without it pays for it.
2. Application status is visible without an email chain. (Shared) Shot clocks are hard to honor and hard to enforce when status lives in inboxes. Visible status protects your timeline and documents the pole owner's responsiveness at the same time, which matters if a dispute ever reaches a regulator.
3. Field data from every vendor arrives in one standard. (Standardized) Data collected three different ways by three different vendors has to be reconciled before it can be trusted, and reconciliation is where errors, delays, and unbillable hours hide.
4. Your as-built records could satisfy the ten-year federal interest period today. (Documented) BEAD's federal interest period runs a full decade,[3] which means the records your program creates this year need to hold up in 2036. Paper files and personal hard drives do not survive ten years of staff turnover.
5. Your measurements are verifiable, not just recorded. (Standardized) A height written on a form is an assertion. A height measured from a calibrated photo is evidence. The difference matters the day the pole owner, an auditor, or opposing counsel challenges the number.
6. You and the pole owner can look at the same record of the pole. (Shared) Most disputes start as version conflicts: your spreadsheet says one thing, theirs says another. A shared record removes the argument before it starts, because there's only one thing to look at.
For OSP engineers and consultants
You sit between the two parties above, and your deliverables become the record both sides rely on. When that record gets challenged, your engineering is what's being challenged, which makes defensibility your reputation in document form.
1. You design against the pole owner's actual standards, not your best interpretation. (Standardized) Rejections for "unclear reasons" usually trace back to an interpretation gap between your read of the standards and the owner's intent. Working inside the owner's real specifications is how the rework cycle stops.
2. Every crew on every project collects data the same way. (Standardized) When each client relationship comes with its own workflow, QC becomes a manual translation exercise that eats unbillable PM hours. A consistent collection methodology is the only way quality scales with headcount.
3. Every make ready call in your deliverable carries photo evidence. (Documented) A recommendation with evidence attached gets approved. A recommendation without it gets questioned, and every question is a delay your client experiences as your delay.
4. You document pole conditions before your design touches them. (Documented) Pre-construction documentation protects your client from inheriting someone else's violations, and it protects you from taking the blame when one surfaces after your crews have been on the pole.
5. Your handoff package can be audited without you in the room. (Shared) If the utility, the client, or a funding reviewer needs you on a call to explain the record, the record is incomplete. A defensible deliverable answers the questions before they're asked.
6. Your data flows into the client's environment without format conversion. (Shared) Every conversion between your tools and theirs is a place where data degrades and hours go unbilled. When your work lands in the owner's environment in the owner's format, the handoff stops being a translation project.
Scoring your readiness
Score the six items for your role. If you answered multiple sections, score each separately, because readiness in one role doesn't transfer to another.
Six yes answers. Your data practices, systems, and defensibility are best-in-class. Your only exposure is at the edges: vendor turnover, legacy data from before your current process, and keeping standards current as programs scale.
Four or five yes answers. You have real strengths and real gaps. Gaps tend to surface at the worst time, which is during an audit, a dispute, or a funding review rather than during normal operations. The items you answered no to can serve as your priority list.
Three or fewer yes answers. Your programs are running on records that would struggle under scrutiny. That's not an unusual position, because most attachment processes were built for a lower-stakes era, but the stakes have changed. The good news is that every item on this list is fixable with process and tooling that exists today.
What to do with your gaps
Most no answers on this list trace back to the same root cause: field data, engineering standards, and application workflows living in separate systems that were never designed to produce a shared, defensible record.
We work on this problem every day, both as the team behind Katapult Pro and as engineers running attachment programs on it for our own customers. If you want a second set of eyes on your gaps, we'll walk through your checklist results with you and be straight about which ones are process fixes and which ones need tooling.
Book a call with us to make a plan for BEAD defensibility.
Sources
[1] Advanced Communications Law & Policy Institute (BroadbandExpanded), BEAD Pole Analysis, Alex Karras and Michael Santorelli, May 2026. The analysis estimates 3,954,030 utility-owned poles across 2,053 electric utility service territories, based on 188,287 planned aerial fiber route-miles. https://broadbandexpanded.com/posts/beadpoles
[2] FCC Wireline Competition Bureau, Public Notice DA-26-579, Wireline Competition Bureau Reminds Reverse-Preemption States of Obligation to Effectively Regulate Pole Attachments and Seeks Comment on Need for Changes to the Commission's Certification Rules, WC Docket Nos. 17-84 and 10-101, released June 11, 2026. https://www.fcc.gov/document/wcb-reminds-reverse-preemption-states-pole-attachment-obligations
[3] NTIA, BEAD General Terms and Conditions, §13.D.1 (January 2026 update), requiring pole-owning subgrantees not otherwise subject to state or federal pole attachment regulation to comply with FCC pole attachment rules for the duration of the federal interest period, which BEAD guidance defines as ten years. Summary analysis: Davis Wright Tremaine, NTIA's BEAD Rules Extend FCC Pole Attachment Requirements to Certain Co-op & Municipal Poles, April 2026. https://www.dwt.com/blogs/broadband-advisor/2026/04/ntia-bead-rules-fcc-pole-attachment
[4] FCC Accelerated Docket proceeding, Comcast v. Appalachian Power Co., decided February 2026, in which the Commission found that requiring a new attacher to bear the full cost of pole replacements caused by prior users' violations conflicts with FCC rules and the Communications Act. Coverage: Telecompetitor, May 2026.
.png?width=680&height=1008&name=pole-no-bg%20(1).png)
