Joint Use and Pole Attachment: Why You Are Billing Rent on Poles That Are Gone and Missing the Ones That Are Not

Why joint use is a revenue system that most utilities run like a filing cabinet

It is the annual joint use invoice. The pole owner bills a cable operator for 61,400 attachments. The cable operator responds with a spreadsheet asserting 57,100 and a list of poles they say do not exist, were replaced, or never carried their plant. Nobody can settle it because both inventories are derived from records rather than from the field, and the last joint audit was six years ago and was itself sampled. So the two companies split the difference, book a reserve, and repeat next year. Meanwhile the same pole owner is receiving permit applications from three fiber builders at a volume the joint use team has never seen, each one carrying a regulatory clock with consequences.

Both of those are the same underlying failure. There is no authoritative record of what is on each pole, maintained continuously, that both parties trust. Attachment records get created at permit time and never verified again. Poles get replaced and the new pole inherits the old identity, or does not, depending on who filed the paperwork. Attachers overlash without notifying, which is often permissible and still means your record of the pole is now wrong about loading. Contractors attach without a permit and the discovery happens years later during an unrelated field visit.

The tools are real. Alden One is a genuine system of record for joint use communication between parties and is used across the industry. Katapult Pro is strong on permitting workflow and make-ready data collection, particularly from the attacher and engineering firm side. IKE Office handles field measurement. O-Calc Pro and SPIDAcalc do structural loading analysis properly and should not be reimplemented by anyone. What none of them do is hold your specific joint use agreements, your state's rental formula, your billing cycle and your permit clock in one object that both the engineering group and the accounting group work from. That gap is why joint use runs on spreadsheets at a scale that would be unacceptable anywhere else in the utility.

Problem 1: two inventories that have never matched and never will by argument

Pole identity is the root problem. Your GIS knows a pole by an asset identifier. The attacher knows it by their own tag number, sometimes by a photo and a cross street. A pole replacement creates a new physical object that may or may not inherit the old identifier. Multiple poles sit at one intersection. Field crews tag poles with metal plates that fall off. When the two parties compare lists, they are comparing keys that were never designed to join.

The reflex is a full field audit, which is expensive and produces a snapshot that starts decaying the day it is delivered. Utilities that have done one know the pattern: the audit finds unauthorized attachments and missing records, both parties negotiate a settlement, and four years later the inventories have drifted again because nothing changed about how records are maintained.

What a custom build does: make reconciliation continuous rather than periodic. Every permit, every make-ready job, every field visit, every inspection photo becomes an observation attached to a pole with a timestamp and a source. The record is then a current state derived from observations, with a confidence level, rather than a row somebody typed once. Match attacher-supplied identifiers to your asset identifiers through a persistent crosswalk that improves with every joint job, so the next comparison starts from the last agreed position instead of from scratch. Audits still happen, but they update a living record rather than creating a new one.

Problem 2: the permit clock is a legal object, not a service level target

Under the FCC's pole attachment rules a pole owner has defined windows: review an application for completeness, survey the poles, provide a make-ready estimate, and complete make-ready inside 60 days in the communications space or 90 days above it, with a one-touch make-ready path for simple communications attachments and a self-help remedy available to the attacher when deadlines slip. Many states have taken back regulatory authority over pole attachments and set their own timelines, so a utility operating across state lines is tracking more than one clock.

The practical failure is not refusal. It is that an application sits in a shared inbox for eleven days because the engineer who handles that district was on vacation, and the clock started when it arrived, not when someone opened it. Then a self-help notice arrives, an attacher's contractor is working on your poles under a remedy you did not intend to trigger, and the conversation escalates to lawyers over a scheduling failure.

What a custom build does: start the clock automatically at intake, per jurisdiction, with the completeness review as an explicit gated step that either accepts or returns the application with reasons inside the review window. Every downstream step carries a due date derived from the rule set rather than typed by a person. Escalation is automatic and goes to a named supervisor before the deadline, not after. The rule set is data, because these rules change and you should not be redeploying software when a state commission issues an order.

Problem 3: make-ready sequencing, and the double wood problem nobody owns

A new attachment on a congested pole means existing attachers move. Communications plant is rearranged in a defined order, sometimes the pole is replaced entirely, and every existing attacher has to transfer their own plant to the new pole. That sequencing is coordination across companies that do not report to each other, and the failure mode is visible from any road in the country: the old pole still standing next to the new one, held up by whichever attacher has not transferred, months after the electric facilities moved.

Double wood is not just cosmetic. The pole owner cannot retire the asset, cannot stop maintaining it, and in many agreements cannot bill for it either. The industry runs transfer coordination through notification systems such as NJUNS, which does the notification job, but the follow-through is a person chasing companies by email.

What a custom build does: model the transfer as a multi-party workflow with per-attacher tasks, dependencies and due dates from the agreement, and an escalation path that produces the documentation you need if you eventually charge for delay. Photographic evidence attaches to each transfer step from the field, which is what actually resolves the argument about whether a transfer was completed. Then the pole retirement gets triggered by the last completed transfer rather than by someone noticing.

Problem 4: the money is calculated differently for every counterparty

Rental revenue is where inventory error turns into a real number. The FCC's rate formulas rest on published presumptions about pole height, usable space and space occupied per attachment, and the applicable rate depends on the type of attacher and the jurisdiction. States that regulate attachments directly apply their own formulas. On top of that sit individual joint use agreements, some decades old, with their own rates, escalators, audit provisions and unauthorized attachment penalties. A pole owner with eight attachers may be running eight different calculations.

Make-ready billing is a second, messier stream. Estimates are provided, actuals differ, contractor invoices arrive on their own schedule, and reconciling estimate to actual to invoice to the attacher's payment is done in a workbook that one person understands.

What a custom build does: express each agreement as a versioned rate rule with effective dates, so an annual bill is generated rather than assembled and can be reproduced exactly two years later when it is questioned. Unauthorized attachments discovered in the field become a workflow with an evidence package, a notification, a cure period and a back-rent calculation from your agreement terms, instead of a note in an inspection report that nobody actions. Make-ready costs track from estimate through actual to invoice on one job object, so the variance is visible while it can still be explained.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this category has a repeatable shape. A first release covering permit intake with jurisdictional clock tracking, the attachment inventory with observation-based reconciliation, and make-ready job and transfer sequencing runs $70,000 to $150,000 and ships in 12 to 16 weeks. A full platform adding multi-agreement rental billing, unauthorized attachment workflow, contractor coordination, field capture with photographic evidence and reporting built for complaint proceedings runs $180,000 to $450,000 phased over 6 to 12 months.

What drives it up: operating across several states with different attachment rules, since each is a rule set to encode and maintain. The number of distinct joint use agreements, because each old agreement is its own billing logic. Integration with pole loading analysis, which is worth doing since geometry should flow into O-Calc Pro or SPIDAcalc rather than being retyped, but is genuine integration work. And whether you are the pole owner, the attacher, or both, because a telecom builder's workflow is a mirror image of the owner's and building for both doubles the surface.

What keeps it down: start with permitting and the clock. It is the piece with legal exposure, it is where volume is growing fastest under current broadband deployment programs, and it generates the observation data that makes inventory reconciliation possible later.

Build versus buy, and when buying is right

Buy the loading analysis. O-Calc Pro and SPIDAcalc are the standards, engineering firms know them, and nobody should be writing their own structural analysis of a wood pole. Buy the collaboration layer too if it fits: Alden One is a legitimate system of record for joint use and if your attachers already work in it, fighting that is expensive. Katapult Pro is a sensible answer for an attacher or an engineering firm running permitting volume.

Build when two or more of these are true. You own more than roughly 100,000 jointly used poles. You have more than four attachers on materially different agreements. Your last inventory dispute ended in a negotiated settlement rather than an agreed number. You operate in more than one state with different attachment rules and clocks. Or your permit volume has multiplied because of fiber buildouts and your team is now tracking regulatory deadlines in a shared mailbox, which is the specific condition that turns an administrative problem into a legal one.

Our position: joint use is a revenue and compliance function that most utilities staff and tool as a records function. The tell is whether your joint use manager can produce, today, the rental invoice for one attacher with a defensible line for each pole. If that takes a week, the problem is not the invoice.

How to choose a developer for joint use and pole attachment systems

Ask how they model pole identity when a pole is replaced. If the answer does not distinguish between the asset, the position and the attacher's own identifier, their reconciliation will fail on exactly the poles that cause disputes.

Ask how the FCC and state clocks are represented. The answer you want is configurable rule data with effective dates, not conditional logic in application code. Commissions issue orders and you should not be paying for a release each time.

Ask what their system does about double wood. A developer who has worked in this space will immediately talk about per-attacher transfer tasks and evidence. One who has not will describe a status field.

Ask who owns the code and get it in writing before kickoff, along with a full export of the attachment inventory in an open format. At Digital Heroes the client owns the code from the first commit. Then give a candidate developer one contested pole with a real history, replacement, overlash, unauthorized attachment and a disputed invoice line, and ask them to model it. That single pole separates people who have done this from people who have read about it.