Why "Close Enough" Isn’t Good Enough: Defensible Data in Utility Pole Engineering

Utility pole engineering has reached the point where an approximate record costs more than an accurate one, because every number in a make ready package now has to hold up in front of a pole owner, a funding reviewer, and eventually a construction crew. The Fiber Broadband Association reported that fiber deployments reached a record 11.8 million U.S. homes passed in 2025, and much of that aerial fiber rides on poles already carrying power and 3rd party attachments. NOAA's National Centers for Environmental Information counted 27 separate billion-dollar weather and climate disasters in 2024, 17 of them severe storms, and those storms are working on the same distribution poles we keep asking to carry more.

Legacy workflows tend to degrade data as it moves. A reading from a hot stick goes onto a clipboard, gets retyped into a spreadsheet, is emailed to a consultant, and is reinterpreted by a designer who never saw the pole, so every handoff works like a game of whisper-down-the-lane. By the time a pole owner and an attacher compare notes, they are often holding two versions of the same pole, and that gap turns into application kickbacks, truck re-rolls to re-measure what someone already measured, and weeks lost while both sides argue about facts instead of engineering.

Compliance is the goal every party shares. Running our own production engineering crews on this work every day has shown us that compliance holds up when it rests on defensible data across four operational pillars: spatial accuracy, clearances, provenance, and the work plan through as-built. The sections below walk through each one, what it asks of your workflow, and how the work gets done in Katapult Pro.

What defensible data means in pole engineering

Defensible data in utility pole engineering is a field record that can show what was on a pole, where that pole sits on the map, who captured and edited the information, and when, without anyone driving back out to re-measure. In practice it means calibrated photo measurements traceable to a reference of known length in the frame, every photo geo-located to a specific pole, and every annotation and attribute change recorded with the user and time. When a pole owner, attacher, or funding reviewer questions a number, the evidence behind it is already in the record.

Pillar 1: Spatial Accuracy (XYZ), Placing Assets in 3D Space

For an OSP engineering consultant, spatial accuracy shows up as one question from the pole owner's reviewer: does the model match the pole? Pole loading analysis runs on geometry, meaning attachment heights, span lengths, the directions lines leave the pole, and the pole's own class, height, and species. When any of those inputs come from an estimate or a retyped field sheet, the loading result inherits the error, and the reviewer has no way to tell a sound design from a lucky one.

Why estimates and uncalibrated photos fall short

A ground-level photo without a scale reference documents that a pole exists, but it can't tell an engineer whether the lowest communications cable sits at 18 or 19 feet. Manual methods carry their own limits, since a height read off a hot stick extended to the attachment depends on the reader and the conditions, and raising a stick toward the neutral for a number puts a person in a hazardous position at every pole. Neither method leaves behind anything a third party can check later, which means an honest disagreement about a height has no tiebreaker.

What gets captured, and how it reaches your loading tool

In the method our own crews run, a two-person team photographs each pole with a calibration stick held flush against its base, and office engineers then calibrate the image against that reference and mark heights directly on the photo. Our published system specifications put absolute accuracy at ±3 inches at 50 feet above ground with the approved setup (a Canon EOS R100 body, RF24-105mm lens, and 17-foot leveling rod), with relative accuracy of make ready measurements between bolted attachments held to +/- ¼ inch. Our post on why utility pole field data collection starts at the pole walks through the method step by step.

Those specifications also list a 98% expected pole capture rate without data re-collects, alongside 30 seconds to a minute and a half per pole in the field and 125 or more poles in an 8-hour day for a two-person crew, because the photo set carries enough context that engineers rarely need to send a crew back.

A complete record for each pole typically includes:

• The pole's location as a node on the map, from which span lengths and the bearings of lines leaving the pole are calculated
• Calibrated heights for attachments in the communications and power space, plus midspan heights at critical crossings
• Pole attributes such as tag, class, height, and species where they are readable or recorded, along with birthmark, grounding, guys, and anchors
• Proposed attachments and make ready moves, drawn against the existing conditions

That record exports into SPIDAcalc, O-Calc Pro, and PoleForeman, so engineers aren't re-keying heights into the loading tool a utility mandates. Katapult Pro also runs an integrated pole loading engine during make ready design that covers most scenarios, and when a pole owner requires a specific program, the export carries the same field measurements into it. You can see how that loading and design work fits together on our engineering design platform page.

Replacing the right poles, and only the right poles

Pole replacements are among the most expensive lines in a make ready estimate, which makes them the place where inaccurate geometry costs the most. A height error of a few inches can push a proposed attachment into an apparent violation that only a taller pole seems to solve, while an accurate measurement might show that a simple rearrangement will do. A replacement also starts a chain of transfers that has to finish before the old pole comes down, and transfers that stall become the double wood that blocks the next attacher's access. The reverse matters just as much to the pole owner, because accurate geometry and loading also catch the poles that genuinely lack capacity, so a pole that should be replaced doesn't take on an attachment it can't carry.

The cost side has regulatory weight too. As our breakdown of the FCC pole attachment timeline changes explains, the Fifth Report and Order (FCC 25-38) upheld the rule that a utility's own change to its construction standards can't shift pole replacement cost onto a new attacher, with one clarification: when the existing pole lacks capacity under both the old and the new standards, the attacher pays. Showing which standard the existing pole was actually built to now supports a cost-share position, which puts the weight back on the quality of the existing-conditions record. For a broader primer on how those calls get made, our guide to what make ready is and what drives its cost covers the fundamentals.

Pillar 2: Clearances and NESC Compliance, Protecting Safety and Assets

Clearance problems are the most common reason make ready exists, and they are also where disputes over responsibility get heated. Every clearance rule is a measured distance, so the quality of the height data decides whether a violation call is a fact or an opinion.

The clearance concepts that drive most make ready calls

The National Electrical Safety Code sets the framework in most of the country. Because the code itself is copyrighted by IEEE, the figures below come from published utility and cooperative summaries, and each pole owner's standards and the code's own exceptions govern the final call:

• Clearance above ground (NESC Rule 232, Table 232-1): the NRECA guide to clearances on joint use poles lists 15.5 feet for insulated communication cables and messengers over roads and streets subject to truck traffic, and 9.5 feet over spaces subject only to pedestrians, with clearance maintained at 120°F with no wind and when iced.
• The communication worker safety zone (NESC Rules 235C4 and 238E): the same NRECA guide describes this zone as starting above the communication space and extending up the pole 40 inches, which communication workers commonly call the "40-inch rule."
• Midspan separation (NESC Rule 235C2b): Chelan County PUD's pole attachment standards apply the requirement that clearance anywhere in the span be at least 75 percent of the at-pole value, which works out to 30 inches for voltages up to 8.7 kV.
• Communication-to-communication spacing (NESC Rule 235H): Chelan PUD's standards cite 12 inches between communication messengers at the pole and 4 inches between different communication utilities anywhere in the span, except by agreement of the parties.

California runs on its own rules under CPUC General Order 95. GO 95 Rule 37, Table 1 sets 18 feet for communication conductors crossing or running along thoroughfares in urban districts, and GO 95 Rule 38, Table 2 sets 48 inches of vertical separation between communication conductors and supply conductors up to 7,500 volts, 72 inches for supply between 7,500 and 20,000 volts, and 12 inches between communication conductors. GO 95 Rule 87.4 also requires cables and messengers attached to joint poles to sit at least 6 feet below supply conductors, reducible to 4 feet below conductors of 0 to 750 volts when a guard arm is installed.

Separating existing violations from proposed ones

Calibrated heights matter most when the question is who caused a violation. Under 47 CFR 1.1411, a utility may not deny a new attacher access based on a preexisting violation the new attacher did not cause, and the FCC's 2018 pole attachment order also bars charging the new attacher to bring poles or existing attachments into compliance when the noncompliance came from someone else's earlier work. Those rules only work when the existing condition is documented well enough to establish which violations were there before the application arrived, which means a dated, calibrated photo of the pole as it stood is what lets both sides allocate cost fairly.

In Katapult Pro, clearance rules are configured to NESC or GO 95 and adjusted to each pole owner's standards, and the platform flags violations across an entire project so engineers aren't checking every pole from memory. Attacher filters on the engineering side help teams evaluate preexisting violations and see where earlier construction went wrong, which gives the pole owner a clear basis for asking the responsible party to correct it.

Protecting the people who work on the pole

The communication worker safety zone exists so that people installing and maintaining communication facilities have room to work below energized conductors, and every clearance call ultimately protects a lineworker or technician. Ground-based photo collection keeps field crews out of that hazard during the survey itself, because the calibration stick is held against the base of the pole rather than raised into the power space, and our crews treat it as the non-rated tool it is by lowering the top section whenever there is any chance of contact with live wires. When construction crews later arrive with a package built on photo-backed existing conditions, they know where the violations, crowded crossarms, and tight midspans are before anyone climbs.

Pillar 3: Provenance (Who, What, Where, When), The Audit Trail Behind Every Record

A measurement is only as defensible as its origin. When a joint use manager reviews an application, the useful questions are who captured this, who changed it afterward, which pole it belongs to, and when it was true, and a spreadsheet passed between three firms can rarely answer any of them.

Who and what

Katapult Pro records user and time-stamped actions on field data, so every data point carries an audit trail showing who collected or edited it and when. Project managers use that history to give feedback to crews and subcontractors, spot training needs, and hold teams accountable for the data they submit, and the platform keeps a full change history on engineering work as well. On the joint use side, in-app discussion threads attach to individual poles and attribute changes, and each workflow stage records entry and exit timestamps, which makes time-in-stage visible for every attacher in the queue.

Where and when

Every photo is geo-located to the pole it documents, and the platform gets there in two ways depending on how the crew is collecting. With Katapult Pro's mobile assessments, each photo is geo-located and time-stamped at the point where it was taken, so no one goes back to the office to work out which picture belongs to which pole. With our camera-based collection method, the crew lead marks each pole done on a wrist-mounted mobile device, the app creates time buckets, and on upload each photo is matched by capture time to its pole node on the map, which means the record doesn't depend on coordinates embedded in the image file and crews can shoot with replaceable, off-the-shelf mirrorless cameras. Either way, every photo in the record carries its pole location, its capture time, and the user who uploaded it.

The TrueNet Communications fielding team, which runs as-built documentation through mobile assessments, described what that means for their compliance reviews in our TrueNet as-built case study:

"With Katapult, we definitely know where it is because we can see the time stamp. There’s no question."

Michael Daniels, Senior Project Manager, TrueNet Communications

Ending arguments over facts

Pole owners and attachers have legitimate, different interests, and neither side benefits when a review turns into a debate over whose field notes are right. FCC rules already recognize that the process involves multiple parties, since 47 CFR 1.1411 requires a utility to let the new attacher and any existing attachers on the affected poles be present for any field inspection during its survey, with advance notice of not less than 3 business days. A shared, photo-backed record lets each of those parties review the same calibrated evidence from their own desk, which is what makes a virtual rideout possible in place of scheduling a truck so several people can meet under the pole to settle a question the photos already answer.

For a joint use manager handling thousands of attachments with a small staff, that record protects the utility as much as it helps the applicant, because approvals rest on current, attributable data rather than on whichever version arrived last. Our joint use management platform is built around that single record, from application intake through post-construction inspection, with the utility, attacher, and contractors seeing the same thing.

Pillar 4: Work Plan and As-Builts, Closing the Loop from Design to Construction

The approved design is a promise, and the as-built is the proof that the promise was kept. For a broadband engineering manager running a federally funded build, that proof is tied directly to money, because deployment milestones and reimbursements depend on showing that what was permitted is what got built.

What funding programs expect

NTIA's General Terms and Conditions for the BEAD Program require states to fund deployment projects on a reimbursable basis, to include clawback provisions in subgrant agreements, to mandate timely subgrantee reporting, and to monitor subgrantees, with NTIA pursuing clawback from grantees that fail to hold subgrantees accountable. Federal award records generally must be kept for three years from the final financial report under 2 CFR 200.334, and, as our FCC timeline post notes, NTIA's January 2026 update to the BEAD terms brought BEAD subgrantee-owned poles under the FCC pole attachment framework for the federal interest period where those poles weren't already regulated.

RDOF carries its own verification pressure. The Universal Service Administrative Company advises support recipients to understand what evidence they may need to supply for its compliance team to verify buildout, and it lists non-compliance measures that can include additional reporting requirements, reduction of support, or a draw on the carrier's letter of credit. Those milestones are staged, with Davis Wright Tremaine summarizing required RDOF deployment of 40, 60, and 80 percent of locations by the end of years three, four, and five.

Verifying the build against the baseline

A time-stamped photo confirms something was there, but confirming that what got built matches what was permitted takes a baseline captured before construction. Our Katapult Pro Broadband Deployment workflow freezes a named snapshot of each job when construction starts, marks the existing field photos as the pre-construction baseline, and calibrates post-construction photos against that baseline pole by pole. We want to be precise about maturity here: TrueNet configured this approach for BEAD compliance documentation on their own, and the as-built verification step is being packaged as a default going forward.

Post-construction inspection then becomes a photo review, where reviewers click through each location and see the photo, the capture time, and the pole it belongs to, instead of waiting for paper markups to come back and be keyed in. The same review can surface construction that drifted from the design, which TrueNet found when terminals and drop heads turned up on different poles than the design indicated.

What the turnaround looked like in one program

We don't publish a universal as-built turnaround, because it depends on route size, crew count, and each funder's package requirements. What we can share is one program's experience. In our TrueNet case study, the team described a paper-based process where a four-step compliance validation could take nine to twelve months, with each step averaging two to three months and roughly 5% of documentation photo-validated. The first three steps of that process, which had taken six to nine months, took less than a month on their first project in Katapult Pro, and every location in the as-built documentation now carries a geo-located, time-stamped photo.

"Instead of taking six to nine months, it took us a little less than a month to completely turn around and have their packages validated."

Carl Gross, Project Manager, TrueNet Communications

The schedule risk on the other side is real. Our Broadband Deployment post puts the cost of idle crews and equipment at $50,000 to $200,000 a month while pole access clears, which is why a record that moves cleanly from permit to as-built protects both the build schedule and the funding behind it.

Legacy approach vs. defensible data approach

How to evaluate your own workflow against the four pillars

These questions work as a quick audit for an engineering program manager, a joint use department, or a broadband team preparing for a funding review.

Spatial accuracy

• Can you state the measured accuracy of the heights in your current packages, and could you show a reviewer how that accuracy was achieved?
• Do field measurements reach SPIDAcalc, O-Calc Pro, or PoleForeman by export, or does someone retype them?
• When a replacement is called, can you show the geometry that proves the pole lacks capacity?

Clearances

• Are clearance rules for each pole owner's standards applied the same way by every engineer, including new hires?
• Could you prove whether a violation existed before your application, using a dated record of the pole as it stood?
• Do construction crews receive existing-condition photos with the package?

Provenance

• For any attribute on any pole, can you see who entered or changed it, and when?
• Are photos geo-located to the correct pole through the workflow, or matched by hand after the crew returns?
• When a pole owner and attacher disagree, can both review the same evidence without a site visit?

Work plan and as-builts

• Is a pre-construction baseline captured and preserved before crews start building?
• Can you produce a photo-backed record for every funded location, organized the way your state broadband office or USAC will ask for it?
• Will the record still be retrievable three years after your final financial report?

Frequently asked questions

What does defensible data mean in utility pole engineering?

Defensible data is a field record that can prove what was on a pole, which pole it was, who captured and edited it, and when. It combines calibrated photo measurements, photos geo-located to specific poles, and user-attributed, time-stamped annotations, so disputes and reviews can be settled from the record instead of another field visit.

How accurate are photo-based pole measurements, and how does calibration work?

Each height photo includes a calibration stick of known length held against the base of the pole, and engineers calibrate the image against those markings before marking attachment heights. With the approved setup named in our system specifications (a Canon EOS R100 body, RF24-105mm lens, and 17-foot leveling rod), we publish ±3 inches of absolute accuracy at 50 feet above ground, with relative accuracy of make ready measurements held to +/- ¼ inch.

Can photo-based field data be used in SPIDAcalc, O-Calc Pro, or PoleForeman?

Yes. Katapult Pro exports pole data into SPIDAcalc, O-Calc Pro, and PoleForeman, so the analysis runs on the measured field conditions without re-keying. The platform also includes an integrated loading engine for design work and feeds the mandated tool whenever a pole owner requires one.

What documentation do BEAD or RDOF reviewers expect for pole attachment work?

Requirements vary by state broadband office and program, but reviewers generally look for evidence that funded locations were built as proposed and on schedule. BEAD subgrants are paid on a reimbursable basis with reporting and clawback provisions, and USAC verifies RDOF buildout against deployment milestones, so photo-backed, geo-located, time-stamped as-built records organized by location are the most direct way to support those reviews.

How does a virtual rideout differ from a field inspection?

A field inspection brings the parties to the pole, while a virtual rideout brings the pole to the parties by letting everyone review the same calibrated, time-stamped photos from their own desks. It resolves most questions about existing conditions and clearances without a truck roll, although a site visit still makes sense when conditions have changed since the photos were captured.

Building the workflow around defensible data

Scoping a program across spatial accuracy, clearances, provenance, and the work plan through as-built gives a team a practical way to design a workflow built for long-term compliance, instead of assembling proof after someone asks for it. Each pillar builds on the one before it, because accurate geometry supports clearance calls, attributable records make those calls hold up in review, and a preserved baseline lets the as-built prove the design was executed.

In Katapult Pro, those pieces live in the same record: calibrated photos traceable to a reference in the frame, geo-located and time-stamped to the pole they document, user attribution on every data point, clearance rules that flag violations against NESC or GO 95, and QC built into the model your team configures. We run our own production crews on the same platform every day, which is why the workflow reflects the way this work actually happens in the field and the office.

If you want to see how your current process measures against the four pillars, book a workflow review with our team and bring a recent project we can walk through together. If you'd rather start with the field side first, explore how Katapult Pro data collection captures calibrated, geo-located pole records from ground level.