Make Ready Cost Sharing: Who Pays for What on the Pole?

You submitted your attachment application six months ago. The survey came back. The engineering is done. And now you're looking at a make ready estimate with pole replacements that will blow your project budget. Half those poles were already in rough shape before you showed up. So why is the full replacement cost landing on your invoice?

If you're on the utility side, the math looks different. You weren't planning to replace those poles this year. Your capital budget didn't account for it. And now an ISP wants to attach, which triggers work you didn't ask for, and they want you to split the bill.

This is the fundamental tension behind make ready cost sharing. Both sides feel like they're subsidizing the other. Both sides have a point. And the regulatory environment around this issue is shifting faster than most teams realize.

This guide breaks down the current cost sharing framework, the critical exceptions that change who pays, the distinction between a true pre-existing violation and a pole that's simply aged out of compliance, and what all of this means for teams managing BEAD-funded deployments right now.

See how Katapult Pro supports make ready engineering workflows from the ground up.

What Is Make Ready Cost Sharing?

Make ready is the engineering and construction work required to prepare a utility pole for a new third-party attachment. That work can range from minor rearrangements of existing cables to full pole replacements, and the cost of that work is one of the most contentious financial questions in the pole attachment process.

The general rule under federal pole attachment regulations is straightforward: the new attacher pays for make ready. If your fiber build requires moving existing attachments, re-framing, or replacing a pole that can't support the new load, that cost lands on you. This is the baseline, and it makes intuitive sense. You're the one requesting the change.

But the real world is more complicated than the baseline rule. Poles carry decades of construction history. Equipment was installed by multiple parties across different eras, under different standards. Some of that equipment is in violation. Some of it was built correctly for its time but no longer meets today's codes. Determining who should pay for what requires untangling all of that history, and that's where disputes begin.

Cost sharing enters the picture when the make ready work serves multiple parties or corrects problems the new attacher didn't create. The principle behind cost sharing is cost causation: you should pay for the work your attachment causes, and not for someone else's deferred maintenance or non-compliant construction.

The Federal Framework: Where the Rules Stand Today

The FCC's pole attachment rules under 47 CFR § 1.1411 establish the default framework, and it applies to investor-owned utility poles. Three categories of exceptions to the "new attacher pays" rule matter most for cost sharing.

Red-Tagged Poles

Poles the utility has already flagged for replacement, independent of your attachment request, are a shared responsibility. If a pole needs to come down for reasons that have nothing to do with your project, you should only pay the incremental cost of accommodating your new attachment on the replacement pole. Not the full replacement.

This is the clearest cost sharing scenario, but it's also the most frequently disputed. What counts as "already flagged" varies. A pole on a published replacement schedule is one thing. A pole the utility's inspector noted as deteriorated in a routine inspection report is another. And a pole that everyone in the field agrees is in bad shape, but nobody has formally documented? That's where the arguments start.

Pre-Existing Violations

If equipment on a pole is already out of compliance before you showed up, you can't be billed to fix it. That cost belongs to whoever created the violation.

In February 2026, the FCC's Rapid Broadband Assessment Team (RBAT) applied this principle in its first accelerated docket ruling. In Comcast Cable Communications, LLC v. Appalachian Power Company, the RBAT found that a utility cannot charge a new attacher the full cost of replacing a pole with pre-existing safety violations. The attacher pays only the incremental cost of installing a stronger or taller pole than what would have been needed to correct the existing violation. The Commission rejected Appalachian Power's policy of requiring 100% upfront payment from the new attacher, holding that the utility bears the remaining replacement cost attributable to pre-existing conditions. That case was resolved in under 60 days and was tied directly to a BEAD-funded deployment in Virginia.

This ruling carries significant weight. It's the first formal decision under the FCC's accelerated docket for pole attachment disputes, and it establishes nationally applicable precedent on cost causation for pre-existing violations.

Compliance Upgrades

If a utility uses your attachment request as the trigger to upgrade a pole beyond what your attachment actually requires, you shouldn't be paying the full bill. Cost should be proportional: you pay for what your attachment necessitates, not for the utility's broader infrastructure improvement.

This exception is the most nuanced. A utility might argue that your attachment triggered the need for a taller or stronger pole. You might argue that the utility is using your application as a convenient excuse to upgrade infrastructure they'd need to address eventually. The line between "required by your attachment" and "triggered by your attachment but beneficial to everyone" is rarely clean.

The Distinction That Changes Everything: Non-Compliance vs. Pre-Existing Violation

This is where many ISPs get tripped up, and where many cost disputes originate.

Not every pole that fails a current engineering analysis has a "pre-existing violation." There's a critical difference between a pole that was built out of spec and a pole that was built perfectly to the standards of its era but no longer meets today's codes.

Construction standards evolve. NESC clearance requirements, loading specifications, and safety factors have changed over the decades. A pole built to the NESC standards of its era was perfectly compliant when it was installed. But codes evolve. What met the standard 20 years ago may not meet today's. That pole isn't in 'violation.' It's non-compliant. It will continue to be grandfathered in because the construction met the applicable code when it was performed.

Here's where it gets expensive: when a new attacher applies to that pole, the act of touching the pole triggers a requirement to bring it into compliance with current standards. The ISP looks at the engineering analysis, sees a bunch of clearance failures, and thinks, "These violations existed before we got here. We shouldn't be paying for this."

But those aren't violations. That's a pole aging through changing standards. Nobody did anything wrong. The construction was correct when it happened, and the pole has been grandfathered into continued compliance. Your attachment application is the event that removes the grandfather status and requires the upgrade.

This distinction matters enormously for cost allocation. A true pre-existing violation, where someone installed equipment out of spec or failed to maintain required clearances, has a cost causer. That party should bear responsibility. But a pole that's simply non-compliant with current standards, through no fault of any existing attacher, presents a much harder question: who should pay to modernize it?

Under the current regulatory framework, that cost typically falls to the new attacher. And for ISPs managing routes with hundreds or thousands of poles, many of which were built decades ago, the financial impact of this distinction can be staggering.

The Misalignment Both Sides Feel

It's worth being honest about the underlying tension here, because both ISPs and utilities are operating from legitimate positions that happen to be fundamentally misaligned.

From the ISP's perspective, they're being asked to fund utility grid hardening. Every pole replacement, every upgrade from 1990s standards to today's codes, every piece of power equipment that needs to be raised or replaced feels like an infrastructure investment that benefits the pole owner, not the attacher. The ISP is attaching a single fiber cable. The make ready bill includes upgrading transformers, replacing crossarms, and swapping out an entire pole. The ISP's reasonable question: "Why am I paying to modernize your grid?"

From the utility's perspective, ISPs want access to utility-owned infrastructure because it's cheaper than building their own. They want new customers, but they don't want to pay what it actually costs to safely accommodate their attachments. The utility didn't plan this capital expenditure. They didn't budget for these pole replacements. And when they provide an honest estimate of what the work costs, the ISP files a dispute. The utility's reasonable question: "If you don't want to pay for what it costs, don't build."

Neither position is wrong. The ISP isn't trying to freeload, and the utility isn't trying to gouge. They're operating in a system where the costs are real, the allocation rules are ambiguous in practice, and the stakes, both financial and regulatory, are enormous.

Acknowledging this misalignment is the first step toward resolving it. And resolution starts with clean, pole-level documentation that takes the ambiguity out of cost allocation.

The Detective Work Behind Make Ready Design

There's an investigative layer to the make ready design process that rarely gets discussed explicitly.

Whenever a pole shows violations or loading failures, the make ready designer has to do more than just propose a fix. They need to figure out who caused the problem and when it was created. Was this clearance violation caused by a cable company that attached too low? Was it caused by a power crew that installed a transformer after the comms were already in place? Did standards change after the last construction event?

This is "forensic make ready," and it matters because it directly shapes the cost estimate. A designer working through a route needs to make these determinations on every pole where the answer isn't obvious. They're looking at construction history, attachment records, loading contributions by attacher, and photo evidence of previous work to build a picture of what happened and in what order. When designers can filter loading percentages by individual attacher, they can isolate exactly how much load each party contributes, which matters when the question is whether a pole replacement is driven by the new attachment or by cumulative overloading from parties that were already there.

If the designer can clearly establish that a CATV company installed their cable 4 inches too low in 2015, creating a clearance violation the new ISP shouldn't have to pay to fix, that changes the cost estimate. If the violation's origin is ambiguous, the full cost typically defaults to the applicant.

But here's the uncomfortable reality that forensic analysis exposes: even when you can identify the cost causer, recovering that cost from them is a different problem entirely. Say the analysis shows a telephone company created a violation eight years ago. The regulations say the new attacher shouldn't pay for it. The utility agrees. But the utility now has to go back to that telephone company and collect. That's a billing dispute the utility didn't ask for, on work the utility didn't plan, for a problem they didn't create. In practice, the utility often ends up absorbing the cost because there's no efficient mechanism to recover it from the responsible party.

This is another layer of the misalignment. The regulatory principle of cost causation is sound. But the operational reality is that identifying the cost causer and actually recovering the cost from them are two very different things, and the gap between those two things often lands on the utility's balance sheet.

Why This Matters Right Now: BEAD and the Cost Dispute Crunch

Make ready cost disputes are one of the biggest friction points slowing BEAD-funded deployments. Attachers are seeing estimates that bear no relation to the actual scope of work. And utilities, under-resourced and managing application volume they weren't built for, are issuing ballpark numbers that create more disputes than they resolve.

The regulatory pressure isn't easing. The FCC adopted its Fifth Report and Order in July 2025, establishing new timelines for large pole attachment requests, improving the overall attachment timeline, and speeding up contractor approval processes. In the accompanying Fourth Further Notice of Proposed Rulemaking, the Commission is seeking comment on expanding one-touch make ready to complex work, setting deadlines for contractor onboarding, and further streamlining the attachment process. Multiple states are launching their own pole attachment reporting rules and dispute resolution processes. The environment is tightening from every direction.

For ISPs, BEAD funding comes with build-out deadlines that don't flex for cost disputes. Every month spent arguing over a make ready invoice is a month closer to a milestone you can't miss. The financial penalties for non-compliance under programs like RDOF include tiered support withholding that can escalate significantly.

For utilities, the volume of attachment applications driven by BEAD and private fiber builds is unprecedented. Many joint use teams are managing this surge with the same staffing levels they had five years ago. When a cost dispute lands on top of an already overwhelmed process, it doesn't just slow down one project. It cascades into backlogs that affect every attacher in the queue.

The teams that will navigate this environment successfully are the ones with documentation clean enough to survive scrutiny from both sides.

Struggling with make ready cost allocation on a complex route? Katapult Pro's engineering design tools give your team real-time loading analysis, attacher-level filtering for forensic make ready, and photo-documented pole conditions that hold up in disputes.

Schedule a Demo | Learn More About Engineering Design

What Clean Documentation Actually Looks Like

The phrase "clean documentation" gets thrown around, but what does it actually mean in the context of cost sharing?

It means pole-level records that capture existing conditions before any make ready work is proposed. Calibrated photos that show exactly where every attachment sits on the pole, with measurements that can be verified independently. Loading analysis that breaks down structural contributions by attacher, so you can see who's consuming capacity and how much. Make ready proposals that clearly distinguish between work caused by the new attachment and work caused by pre-existing conditions.

It means having the data to answer questions like: Was this pole already at 95% loading capacity before the new application? Which attacher's equipment is creating the clearance violation? Was this cable installed above or below the position required by the applicable standard at the time of installation?

For utilities, this level of documentation protects against disputes by providing the factual basis for cost estimates. When an ISP challenges a make ready bill, a utility with detailed, photo-documented, engineering-verified records has a defensible position. A utility working from a spreadsheet estimate and a set of field notes does not.

For ISPs, the same documentation provides the evidence needed to challenge costs that shouldn't be allocated to them. If the data clearly shows pre-existing violations caused by other parties, or if pole loading analysis demonstrates that the pole was already overloaded before your attachment was proposed, that's the foundation for a legitimate cost sharing claim.

Both sides benefit from the same thing: transparent, defensible data at the pole level. The teams that invest in this upfront spend less time and money in disputes later.

A Note on Applicability: IOUs, Co-Ops, and Municipalities

It's worth noting that the federal cost sharing rules discussed in this guide currently apply to investor-owned utility (IOU) poles. Electric cooperatives and municipal utilities operate under different frameworks. Some states have their own pole attachment regulations that apply more broadly, while others defer entirely to the federal rules.

But the direction is clear regardless of utility type. Accountability and documentation are becoming the expectation across the board. State-level regulatory action is increasing, and even utilities not directly subject to FCC pole attachment rules are seeing pressure from their own regulators and attaching companies to provide transparent cost breakdowns and defensible engineering documentation.

Whether you're subject to federal rules or not, the principles of cost causation, documented analysis, and proportional allocation apply to any pole attachment relationship.

Frequently Asked Questions About Make Ready Cost Sharing

Q: Who generally pays for make ready on utility poles? Under FCC regulations, the new attacher pays for make ready work. If your fiber build requires rearranging existing equipment, adding pole height, or replacing a pole, that cost defaults to you as the applicant. Exceptions apply for red-tagged poles, pre-existing violations, and compliance upgrades that exceed what your attachment requires.

Q: What is a red-tagged pole and how does it affect cost sharing? A red-tagged pole is one the utility has already flagged for replacement independent of any new attachment request. When a new attacher applies to a red-tagged pole, the attacher should only pay the incremental cost of accommodating their new attachment on the replacement pole. The cost of the replacement itself is the utility's responsibility, since it was already planned.

Q: What is the difference between a pre-existing violation and non-compliance with current standards? A pre-existing violation means equipment was installed out of spec at the time of installation. Non-compliance with current standards means equipment was built correctly under the codes in effect at the time, but those codes have since changed. Grandfathered equipment isn't "in violation" until new work on the pole triggers the requirement to bring everything up to current standards. This distinction significantly impacts who pays for upgrades.

Q: What is the FCC's Rapid Broadband Assessment Team (RBAT)? The RBAT is an intra-agency group created by the FCC in its December 2023 Fourth Report and Order and made operational in 2024. It is composed of Enforcement Bureau and Wireline Competition Bureau staff and was designed to expedite resolution of pole attachment disputes that impede broadband deployment. In February 2026, the RBAT issued its first ruling under the FCC's accelerated docket, finding that utilities cannot charge new attachers the full cost of replacing poles with pre-existing safety violations. The attacher pays only incremental costs.

Q: Do FCC make ready cost rules apply to all utilities? No. Federal pole attachment rules apply to investor-owned utilities. Electric cooperatives and municipal utilities operate under different frameworks, though many states have adopted their own rules that may apply more broadly. The trend across all utility types is toward greater documentation requirements and cost transparency.

Q: What does forensic analysis look like in make ready design? It's the investigative process of determining who caused a violation or failure on a pole and when it was created. Make ready designers perform this analysis to accurately assign cost responsibility and create construction plans that reflect true cost causation rather than defaulting all costs to the new attacher.

Q: How does BEAD funding affect make ready cost disputes? BEAD-funded deployments come with strict build-out deadlines. Cost disputes that delay make ready construction directly threaten an ISP's ability to meet those deadlines. The FCC has responded by establishing faster dispute resolution through the RBAT and is actively considering additional measures to streamline the attachment process.

Q: What documentation helps protect both sides in a cost dispute? Calibrated pole photos showing existing conditions, loading analysis broken down by attacher, make ready proposals that separate new-attacher-caused work from pre-existing conditions, and clear records of construction history. Both utilities and ISPs benefit from transparent, defensible data at the pole level.

Building a Process That Protects Both Sides

Make ready cost sharing isn't going to get simpler. The volume of attachment applications will continue to grow. The regulatory framework will continue to evolve. And the financial pressure on both utilities and ISPs will continue to intensify.

What can get better is the quality of information both parties bring to the table. When cost estimates are grounded in documented pole conditions, clear analysis of who caused what, and engineering data that both sides can verify, disputes become negotiations instead of battles.

The teams that invest in clean data collection, defensible make ready engineering, and transparent workflows are the ones that resolve cost disputes faster, protect their budgets, and keep their projects moving.

If your team is navigating make ready cost allocation on a complex route, or if you're building the processes to handle attachment volume at scale, we'd welcome the conversation. Schedule a call with our team to see how Katapult Pro supports the documentation, engineering, and analysis that make cost sharing defensible for everyone involved.