Pole Attachment Management Software: Custom Build or Off the Shelf

What the off the shelf joint use products actually do well

The annual joint use invoice goes out for 61,400 attachments. The cable operator replies asserting 57,100 and a list of poles they say do not exist, were replaced, or never carried their plant. Neither side can settle it, so both book a reserve and repeat next year. That is the situation, and it is worth knowing which parts of it software already solves.

More than most utility people assume. Alden One is a genuine system of record for joint use communication between parties and is used across the industry, which matters enormously because a shared record only works when both sides are in it. Katapult Pro is strong on permitting workflow and make-ready data collection, particularly from the attacher and engineering firm side. IKE Office from ikeGPS handles field measurement properly. Osmose O-Calc Pro and Bentley SPIDAcalc do structural loading analysis correctly and nobody should ever reimplement them. NJUNS does the notification job for transfers across companies.

Buy the loading analysis without hesitation. Engineering firms know those tools, the calculations are standardised, and writing your own structural analysis of a wood pole would be a serious error of judgement. Buy the collaboration layer too if your attachers already work in it, because fighting an incumbent shared platform is expensive and you will lose.

Below roughly 30,000 jointly used poles with two attachers and stable volume, buy and enforce your agreement. The problem at that size is contractual discipline rather than software, and a build will not supply discipline.

Where they stop: the clock, the identity and the money

Three specific workflows, and none of them is a feature gap in the products above.

The first is the permit clock, which is a legal object rather than a service target. Under the FCC pole attachment rules a pole owner has defined windows to review an application for completeness, survey the poles, provide a make-ready estimate and complete make-ready, with a shorter period in the communications space than above it, a one-touch make-ready path for simple communications attachments and a self-help remedy available to the attacher when deadlines slip. More than twenty states have certified to regulate attachments themselves under Section 224 of the Communications Act and set their own timelines, so a utility across state lines is tracking several clocks at once. The practical failure is never refusal. It is an application sitting in a shared inbox for eleven days because the engineer for that district was on vacation, and the clock started when it arrived rather than when somebody opened it. Then a self-help notice lands, an attacher's contractor is working on your poles under a remedy you did not intend to trigger, and lawyers get involved over a scheduling failure.

The second is pole identity. Your geographic information system knows a pole by an asset identifier. The attacher knows it by their own tag, sometimes by a photo and a cross street. A replacement creates a new physical object that may or may not inherit the old identifier. Multiple poles sit at one intersection and metal tags fall off. When the two parties compare lists, they are joining keys that were never designed to join, which is why a full field audit produces a snapshot that starts decaying the day it is delivered.

The third is money. Rental rates depend on the applicable regulatory formula with its published presumptions about pole height and occupied space, on the class of attacher, on the jurisdiction, and on an individual joint use agreement that may be decades old with its own escalators, audit provisions and unauthorized attachment penalties. A pole owner with eight attachers is running eight different calculations, and make-ready billing from estimate to actual to contractor invoice is a second, messier stream that one person understands.

The arithmetic: per pole subscriptions against a fixed build

Joint use platforms are generally priced against your pole count or your permit volume, so the buy side scales with exactly the thing that is growing. Run your own quote through the sum, because current broadband deployment programmes have pushed permit volumes to levels most joint use teams have never seen.

Then price the parts no subscription removes. The disputed inventory that gets settled by splitting the difference each year, which you can take straight from your reserve. The make-ready reconciliation nobody can defend line by line. The poles you are billing that are gone, and the ones you are not billing that are carrying plant. Utilities that have run a joint audit know the shape of that gap and it is rarely small.

A build sits flat. A first release at $110,000 with migration and support amortised across five years lands near $45,000 a year regardless of how many attachments you carry.

The crossover sits near 100,000 jointly used poles for a single state owner with straightforward agreements. It drops to roughly 40,000 poles once you carry four or more attachers on materially different agreements, and lower again once you operate under two or more state rule sets, because each jurisdiction is a separate clock and a separate rate formula rather than a bigger version of the same one. Attachers cross earlier than owners on schedule exposure, since their cost is a delayed build rather than a disputed invoice.

What a custom build actually costs

These are Digital Heroes delivery bands. A first release covering permit intake with jurisdictional clock tracking, the attachment inventory reconciled from timestamped observations, and make-ready job and transfer sequencing runs $70,000 to $150,000 over 12 to 16 weeks. A full platform adding multi agreement rental billing, unauthorized attachment workflow with evidence packages, contractor coordination, field capture with photographs and reporting built for complaint proceedings runs $180,000 to $450,000 phased across 6 to 12 months.

Data migration runs 10 to 25 percent of the build and it is not a records transfer. It is building the crosswalk between your asset identifiers and each attacher's own identifiers, seeded from every joint job you have records for, so the next comparison starts from the last agreed position rather than from scratch. Budget it as a joint exercise with your largest attacher, because a crosswalk one party built alone is a crosswalk the other party disputes.

Year two and each year after runs 15 to 20 percent of build cost annually. Here that figure buys rule maintenance. State commissions issue orders and the FCC revises its rules, so timelines and rate formulas must be configurable data with effective dates rather than conditional logic in application code. If you are paying for a software release every time a commission acts, the design was wrong.

The four situations where building wins

Two together. One alone is a subscription and a stricter contract manager.

• Regulatory fit. The strongest case in this category. Clocks start at intake per jurisdiction, completeness review becomes an explicit gate that either accepts or returns the application with reasons inside the review window, and every downstream due date derives from the rule set rather than being typed by a person. Escalation goes to a named supervisor before the deadline rather than after. If you operate across states that have certified their own regimes, no product will hold all of them the way your counsel reads them.
• Scale economics. More than roughly 100,000 jointly used poles, or permit volume that has multiplied because of fiber buildouts while your team still tracks deadlines in a shared mailbox. That specific condition converts an administrative problem into a legal one.
• A workflow that is your competitive advantage. Transfer sequencing and the double wood that follows it. Model the transfer as a multi party workflow with a task per attacher, dependencies, due dates from the agreement, automatic escalation and photographic evidence at completion, and pole retirement triggers from the last completed transfer rather than from somebody noticing the old pole still standing. That is the work no notification system does for you.
• Integration sprawl. Count what one pole touches: the geographic information system, the asset and work management system, the loading analysis tool, the field capture app, the joint use collaboration platform, the billing ledger and the contractor's invoices. Three or more with a person reconciling, and that person is the reason your invoice takes a week to defend.

Pole count alone is not on the list. A large single state owner with two disciplined attachers and one agreement template is well served by a subscription.

How to decide in a week

Two tests. The second one also screens developers.

Monday and Tuesday, measure the intake lag. Take last quarter's permit applications and record, for each, the date it arrived and the date somebody first worked it. Then compare against the review window for that jurisdiction. The distribution will tell you immediately whether your exposure is capacity, routing or visibility, and only the third of those is a software problem.

Wednesday and Thursday, run the contested pole test. Pick one pole with a real history: a replacement, an overlash somebody did not notify, an unauthorized attachment found in the field, and a disputed invoice line. Try to assemble its complete history from your existing systems and time it. Record every place you had to open a spreadsheet, an email thread or ask a named person.

Friday, hand that same pole to any developer or vendor you are considering and ask them to model it in front of you. A team that has done this work will immediately separate the asset, the position and the attacher's own identifier, and will ask which one persists through a replacement. A team that has not will describe a status field. That single pole separates people who have done this from people who have read about it, and it costs you nothing.

If you proceed, take a paid discovery phase rather than a build. At Digital Heroes that means a signed product requirements document before code: the pole identity model, the jurisdictional rule sets as configurable data with effective dates, the observation based reconciliation approach, the transfer workflow, the rate rules with versioning, and acceptance criteria at a fixed price. You own the document whether or not you build with us, and it works as a specification for a product vendor too.

We are wrong for an owner under 30,000 jointly used poles, for anyone who wants structural loading analysis rebuilt, and for a utility unwilling to work the identifier crosswalk jointly with its largest attacher. We hold India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law, and we would insist on a full export of the attachment inventory in an open format because that inventory is evidence in rate disputes that outlast software vendors. More than fifty specialists, over 2,000 projects, in house products including ShopScore, HeroCheckout and Section Vault, and a named team you meet before signing. Verify us on Clutch, Trustpilot, Fiverr Vetted Pro and our D-U-N-S record.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.