Pole Attachment Support

What Does the Pole Owner Need Before You Can Build?

Every pole you attach to belongs to someone: an electric utility, an incumbent telephone company, a municipality, or a joint use arrangement between them. Each has its own application process, data format, fee structure, and review queue, and none of them behave the same way.

The core question set is always similar, though: which poles, what you intend to attach, at what height, and what is already up there. A package that answers those questions completely, with field data that matches physical reality, moves through review. One assembled from a desktop route with estimated heights comes back for corrections, and the correction cycle is measured in weeks.

We assemble and submit those packages, respond to review comments, and track the tickets, so your project manager has one place to ask where a route stands instead of three companies to chase.

What Field Survey Data Prevents Rework?

The survey is where a pole attachment project is won or lost. We walk the route and record what is physically on each pole rather than what the records say should be there, because pole records and field reality drift apart over years of attachments, transfers, and replacements.

That data feeds the loading analysis and the make-ready estimate. Bad data produces an estimate that is wrong in both directions at once: poles flagged for work they do not need, and poles that need work nobody catches until a crew is standing underneath one with a reel on the truck.

We collect it once and reuse it. The same survey that supports the application supports the construction plan, the material list, and the as-built record at the end, which means one trip down the route instead of three and one version of the truth instead of several conflicting spreadsheets.

• Pole height, class, and material where visible, plus the owner tag data.
• Height to the lowest power conductor and to every existing communications attachment.
• Existing guys, anchors, risers, streetlights, and transformers on the pole.
• Midspan measurements at roadway and driveway crossings.
• Span lengths, direction changes, and obstructions along the run.
• Photographs of each pole face showing what the measurements describe.

What Does a Pole Loading Analysis Look At?

A pole loading analysis asks whether a pole can safely carry everything on it once your cable is added. The pole owner or its engineering contractor runs it, usually in modeling software, and it is only as good as the field data behind it.

The analysis models the pole itself: its height, class, material, and setting depth. It then adds every load the pole carries, including power conductors and equipment, each communications cable and its strand, streetlights, and guys, along with the wind pressure on all of them. Your proposed cable and strand go in last, using their weight, diameter, and attachment height.

The result is a pass, a pass with conditions such as a new guy, or a fail that calls for make-ready or a pole replacement. Clearances to power and to other attachers are reviewed at the same time, so a pole can pass on strength and still need make-ready for separation.

Our role is the inputs. We supply measured heights, accurate cable data, span lengths, and photographs so the owner models the pole that is actually in the ground. When a result looks wrong, those measurements and photographs are what let you question it with evidence.

How Should You Read a Make-Ready Estimate?

A make-ready estimate is a bill and a schedule at the same time, and the schedule half is usually the one that hurts. The line items that matter most are pole replacements, because they drive both cost and duration and they pull in transfers by other attachers that the estimate itself does not schedule.

It is worth reviewing whether every flagged item is genuinely required for your attachment or is pre-existing work being bundled into your project. Sometimes a design change removes a replacement entirely: adjusting the attachment height, shortening a span, adding a pole, or taking one short section underground with a bore.

We review estimates with you, and where a redesign is cheaper than the make-ready, we show you what that redesign looks like and what it costs to build, so the comparison is a real number instead of a hunch.

Transfers, Tickets, and the Waiting Game

After make-ready is approved and paid, the physical work usually happens in sequence: electrical make-ready first, then each communications attacher transfers in order. Transfers move through the ticketing systems the pole owners use, and the pace of the whole route is set by whoever is slowest to respond.

Tracking is the actual job at this stage. We keep a live status by pole, follow up on stalled tickets, and flag the ones that are going to threaten your in-service date early enough for you to escalate, redesign around them, or reset expectations with your own customer.

We also sequence construction so the route is built in the order approvals arrive rather than in the order the drawings happen to be numbered. Production continues while the hard poles work through the queue.

What Happens After the Attachment Is Built?

When the attachment is built, the pole owner generally wants a post-construction record, and you want the same information in a form your maintenance group can use. Those should be one data set, collected once, not two documents assembled separately from memory.

That data set is organized by pole, so anyone can open it at a specific pole number and see what was built there and how it was measured. It is what protects you in a future attachment audit, and it is what saves the next crew a day of field verification before they can start work.

Attachment records also matter commercially. Pole owners audit attachments and bill for what they find, and an undocumented or misrecorded attachment is difficult to dispute years later. A dated, photographed, pole-by-pole record is the cheapest insurance available on an aerial route, and it is also what a new attacher asks for when they want to overlash your strand.