How To Map Utility Poles For Attachment Applications

You're scoping a new fiber build. The route runs along an existing distribution line, you know roughly which poles you need, and construction is breathing down your neck. The pole owner just sent over their attachment application requirements, and the first deliverable they want is a pole map.

That map is going to be the foundation of every conversation with the pole owner from this point forward. If it's wrong or incomplete, the application bounces back, the FCC clock pauses, and your construction schedule starts compounding delays you can't recover. If it's right, the next step is verification, then make ready, then permission to attach.

Every pole attachment application starts with a pole map. The level of detail varies by jurisdiction and pole owner, but the universal requirement is the same: show us the poles you want to attach to, with enough detail that we can review the request. With over $42 billion in BEAD funding pushing FTTx deployments into territory that hasn't seen a fresh pole audit in decades, the quality of that first map is determining how fast (or whether) thousands of projects make it through the approval process.

This guide walks through what pole mapping means in practice, the difference between CAD and GIS pole maps and why that distinction matters more than it used to, what goes into a pole map for an attachment application, the workflow we use at Katapult, and the common reasons applications get bounced back.

See how Katapult Pro supports pole attachment workflows from first design through construction.

What Is Utility Pole Mapping?

Utility pole mapping is the process of identifying, locating, and documenting utility poles along a planned route, then turning that information into a deliverable that pole owners, joint users, and engineers can use to evaluate an attachment request.

At its simplest, a pole map shows which poles your project will touch, where they are in the real world, and enough attribute data for the pole owner to know what they're being asked to approve. The deliverable can be a PDF print, a spreadsheet of GPS coordinates, a GIS shapefile, or a KMZ overlay, depending on what the pole owner accepts.

That definition holds across every flavor of attachment work. Whether you're running fiber for a BEAD-funded ISP, scoping make ready for a small wireless deployment, or auditing existing attachments as part of a joint use program, the work starts with knowing which poles are in scope and having a defensible record of where they are. The variation comes in what counts as "enough" detail, and that's where the process gets messy.

Why Pole Mapping Matters For Attachment Applications

A complete, accurate pole map does three things at once.

It defines the scope. Until the pole owner knows which poles you're asking about, no review can start. The FCC's 10-day completeness review window doesn't begin until your application is considered complete, and a missing or inadequate pole map is one of the most common reasons that window resets. We covered the broader timeline mechanics in our breakdown of the FCC pole attachment timeline.

It establishes the basis for engineering. Once the poles are identified, the rest of the work (pole loading analysis, make ready design, joint use coordination) flows from that record. If the map shows the wrong poles, every downstream deliverable inherits the error. The same pole map that opens an application is the one feeding pole loading analysis and make ready engineering weeks or months later.

It becomes the audit trail. For federally funded projects, especially anything touching BEAD subaward documentation, the pole map is part of the permanent record of what was deployed where. The same map that gets an application approved is going to be referenced years later when a subgrantee has to prove what they built.

The cost of getting it wrong is real. Idle field crews run $50,000 to $200,000 per month depending on the deployment size. A rejected application that has to be re-collected and resubmitted can push a project deadline past a federal funding milestone. Pole owners receiving hundreds of applications per quarter triage by quality first. Sloppy maps go to the bottom of the stack.

CAD Versus GIS: Two Different Standards Living Side By Side

The industry is in the middle of a slow but real shift in how pole locations are recorded, and the pole owner's standard determines what they expect from you.

The older model is cartographic. Cartographic pole maps are CAD-style prints that present an artistic interpretation of real-world conditions, optimized for human legibility. Pole symbols are offset slightly so they don't overlap. Conductors are drawn as clean parallel lines even if they fan out in the field. The print is designed to be read by a field crew or a construction supervisor, not to be queried by software. In a lot of telecom construction, CAD prints are still the default deliverable for make ready packages and construction prints.

![Yates Engineering Services sample CAD print, showing cartographic pole layout for telecom construction]

The newer model is geospatial. GIS pole maps are databases of real-world design elements tied to their true geolocations, intended to be queried, filtered, and integrated with other systems. Many pole owners that historically maintained their asset records in offset cartographic layers are migrating to master GIS databases that house pole, conductor, and equipment data as it exists in the world. A growing number of BEAD subgrantees and state broadband offices are also moving toward GIS-first deliverables because the data has to be portable across the funding lifecycle.

![Esri Mobile GIS mapping sample, showing geospatial pole data tied to true geolocations]

The two formats coexist on most projects today. Your field crew might be collecting GIS-true coordinates on a tablet, the pole owner might want a CAD print for their construction team, and the joint use coordinator might want a shapefile for their database. Doing the work once and producing multiple format outputs is the practical answer to that mismatch, but it requires a data model that can support both.

The shift to GIS is being pushed by three forces at once. Federal funding documentation requirements expect portable geospatial data, utility GIS modernization programs are accelerating (Esri's ArcGIS Utility Network adoption is growing across investor-owned utilities), and joint use management software can only function with accurate, queryable pole records. The CAD-only workflow is not going away tomorrow, but it's getting harder to defend on projects that need both a make ready deliverable and a long-term asset record.

What Goes Into A Pole Map For An Attachment Application

The exact requirements vary by pole owner, but the data layers that show up on almost every attachment application include the following.

Pole identification. The pole owner's pole number or tag, plus GPS coordinates accurate enough to identify the right pole on the right cross street. Pole owners with mature GIS records expect coordinates that land within their internal tolerance, which varies by jurisdiction but typically resolves the pole to the right location with minimal ambiguity.

Pole owner and joint users. Who owns the pole and who already has equipment on it. This is what determines which joint use parties get notified during the application review.

Existing attachments. What's already on the pole. For applications that require pole loading analysis, this becomes the basis for the loading calculation. For simple notification applications, it confirms the pole has capacity for the new attachment.

Proposed attachment. What you're asking permission to add. Cable type, weight, tension, and proposed attachment height all factor in.

Route and connectivity. How the poles connect, where the spans are, and which poles are anchor or guying locations. This matters for tension calculations and for understanding the engineering footprint of the application.

Verification metadata. When the field data was collected, who collected it, and how confident the team is in the reading. For BEAD-funded work, this is increasingly required documentation, not optional.

The deeper your team's responsibility goes (from a notification application through full make ready engineering and pole loading analysis), the more attribute data the pole map needs to support. A simple application might require nothing more than tags and GPS coordinates. A full make ready package requires every measurable attachment height, midspan clearance, equipment classification, and guying detail. We broke down the minimum dataset in more detail in our post on utility pole data for telecom attachments.

The Pole Mapping Workflow, Step By Step

There is no single right way to map pole locations. The right way is whatever gets your team permission to attach safely as fast as possible. Here's the workflow we use at Katapult, which handles the full range of pole owner requirements we've encountered.

Step 1: Route Determination

Before any field work, the team identifies the candidate route using Katapult Pro's Google-based maps and street view. This first pass establishes which poles are in scope, where the route enters and exits the pole owner's territory, and whether any obvious obstacles (waterway crossings, dense overhead congestion, conflict zones with other utilities) will affect the design.

The output of this step is a candidate pole list with preliminary locations, ready to hand off to the field. For pole owners that allow application submission based on preliminary mapping, this can sometimes be the deliverable that starts the FCC clock. For most others, it's the input to the next step.

For a deeper look at how this works in practice, our pre-design manual walks through the office-side workflow our team uses.

Step 2: Field Verification

The next pass moves the work into the field. A field crew uses Katapult Pro's mobile maps to walk the route, confirm each candidate pole exists where the office map shows it, capture verification photos, and update the record with field-confirmed GPS coordinates and verification timestamps.

For teams whose responsibility ends at submission (because another firm will handle make ready engineering), field verification is often the last step. The deliverable is a verified pole list with confirmed locations and basic existing-conditions photos. For attachments that don't require full pole loading analysis, this is often enough to get an application accepted and the review clock started.

Our field manual covers the field-side methodology in detail.

Step 3: Data Collection

If your team is responsible for make ready engineering, pole loading analysis, or full attachment design, the field work expands into a complete photo-based data collection pass. This is the layer that turns a pole map into an engineering record.

Our two-person crew methodology captures measurable photos of every pole, with attachments, equipment, and spans documented to the level of detail required for back-office annotation. A calibratable height stick in every shot provides the measurement reference for heights up to 50 feet with plus or minus 3 inch accuracy. All identification of attachments, height measurements, and equipment classification happens back at the office during photo annotation, not in the field. That separation is deliberate. It lets field crews move faster without losing accuracy, and it puts the most error-prone work in front of trained annotators with the time and tools to do it right.

The deliverable from a complete data collection pass is a pole map that doubles as an engineering record: every attachment identified, every clearance measured, every span documented, ready to feed into pole loading analysis software or a make ready design package. We covered the full data collection methodology on the product page.

Pole attachments are messy. We know the mess firsthand because we run this workflow on our own customer projects every day.

Katapult Pro is built around the pole map: one shared, real-time database that handles route determination, field verification, photo-based data collection, and make ready engineering on the same record. Field crews, office annotators, engineers, and project managers all work from the same map without the spreadsheet patchwork.

Schedule a Demo | See Katapult Pro

Tools And Software For Pole Mapping

The tooling landscape for pole mapping falls into a few categories, and most teams running serious volume use some combination of all of them.

Field collection apps capture pole data and photos in the field. The best ones handle offline operation, GPS calibration, time-based photo association, and direct sync to a back-office workspace. Older paper-based or generic survey apps still work, but they require a lot of manual processing on the back end.

GIS desktop and web platforms (ArcGIS, QGIS, Esri Utility Network) handle the long-term asset record. Most pole owners that have moved to GIS-first standards are running some version of the Esri stack, which is also where most third-party joint use management tools integrate.

CAD platforms still dominate make ready prints and construction deliverables. Most engineering firms producing make ready packages for investor-owned utilities are exporting from a design tool into AutoCAD or MicroStation-compatible formats for the final deliverable.

Pole loading analysis software (SPIDAcalc, O-Calc Pro, PoleForeman, and Katapult Pro's integrated pole loading) handles the structural calculation side. These tools need clean attribute data from the pole map to run reliably.

Integrated engineering platforms combine field collection, GIS data management, photo annotation, and make ready engineering on one record. This is where the work has been heading for several years, because the alternative (separate tools for each phase, with data passed by export and reimport) is where most errors and delays come from.

Katapult Pro is one of those integrated platforms. We built it because we needed to run our own pole attachment work without the spreadsheet patchwork, and we still run our engineering services team on it for every project we deliver. The same database that holds the field data feeds pole loading analysis, engineering design, and joint use management, so the pole map you start with is the same record you end with.

Common Reasons Pole Map Submissions Get Rejected

After a few hundred projects across a range of pole owners and PUC jurisdictions, the rejection patterns start to repeat. These are the most common.

GPS coordinates that don't match the pole owner's record. Pole owners with mature GIS records expect your coordinates to land within their defined tolerance. If your field GPS was uncalibrated or pulled from a low-accuracy device, the pole owner's system will flag the application as ambiguous and bounce it back for verification.

Missing pole tags or tag numbers that don't match. Pole tags are how the pole owner connects your application to their internal record. A field crew that photographed a pole without capturing the tag, or transcribed a tag incorrectly, creates an immediate rejection trigger.

Inadequate existing-conditions documentation. Pole owners reviewing your application need to know what's already on the pole. A pole map that shows the pole but doesn't document existing attachments, equipment, or guying is incomplete for any application that requires loading analysis or make ready engineering.

Format mismatch. The pole owner expected a shapefile and you sent a KMZ. They expected CAD prints and you sent a PDF export of a web map. Format mismatches don't usually result in outright rejection, but they routinely cause the application to be set aside until the right format arrives, which is functionally the same delay.

Outdated route data. A pole map collected six months ago in an active growth area is going to miss new attachers that have joined the pole since the field work. Pole owners in BEAD-active markets have started requiring verification timestamps and refusing applications based on data older than a defined window.

No verification record. "Trust us, we walked it" is no longer accepted by most pole owners running a serious application portal. They want to see when the data was collected, by whom, and using what method. The verification metadata isn't optional anymore.

Inconsistent unit conventions or attribute schemas. A pole map with heights in feet on some poles and meters on others, or with attachment types coded differently across the dataset, will get bounced for normalization before any engineering review.

Avoiding these rejection reasons is mostly a workflow question, not a technology question. Field crews need calibrated equipment, the back office needs a defined data schema, and the deliverable needs to match the pole owner's stated format. None of it is exotic engineering. It's discipline at the data layer.

Frequently Asked Questions About Pole Mapping

What is pole mapping?

Pole mapping is the process of identifying, locating, and documenting utility poles along a planned route, then producing a deliverable that pole owners, joint users, and engineers can use to evaluate an attachment request. The deliverable can be a CAD print, a GIS shapefile, a KMZ overlay, or a spreadsheet of GPS coordinates, depending on the pole owner's requirements.

Why is pole mapping required for broadband deployment?

Pole owners and joint use coordinators cannot review an attachment application without knowing which poles are in scope and where they are. A pole map is the universal first deliverable in nearly every pole attachment application across both FCC-regulated and state-PUC-regulated jurisdictions. For BEAD-funded broadband deployment, pole mapping also feeds federal documentation requirements that extend beyond the immediate application review.

What's the difference between CAD and GIS pole mapping?

CAD pole maps are cartographic prints designed for human readability, with offset symbols and clean drafting conventions. GIS pole maps are geospatial databases tied to real-world coordinates, designed to be queried and integrated with other systems. Most projects today produce both, with the GIS data acting as the source of truth and the CAD prints serving as construction deliverables.

How accurate does a pole map need to be?

Accuracy requirements vary by pole owner and application type. For pole identification, most pole owners with mature GIS expect coordinates that resolve the pole to the right location within their internal tolerance. For full make ready engineering, attachment height measurements need to be accurate to within a few inches. Katapult Pro's photo-based measurement system supports measurements up to 50 feet with plus or minus 3 inch accuracy.

Who is responsible for producing the pole map?

The applicant is almost always responsible for producing the initial pole map as part of the attachment application. Some pole owners that operate full engineering departments will produce their own make ready engineering once the application is accepted. Others require the applicant or their engineering firm to deliver a complete make ready package as part of the application. Knowing where your responsibility ends is one of the first things to confirm with the pole owner.

How long does it take to map poles for an attachment application?

For a route with a clear path and reasonable existing pole owner records, an experienced two-person crew using a modern field collection platform can verify and document a substantial volume of poles per day. Routes with dense overhead congestion, poor existing records, or complex joint use situations move slower. Office annotation adds additional time after field collection, depending on the level of attribute detail required for the application type.

Can pole mapping be done from existing pole owner data alone?

Sometimes, but rarely as the complete deliverable. Pole owner records vary widely in quality, currency, and completeness. Using existing records as a starting point for office pre-design is common practice. Submitting an application based solely on existing pole owner data without field verification is generally not accepted by pole owners with mature application processes.

What software is used for pole mapping?

Teams use some combination of field collection apps, GIS platforms (Esri ArcGIS is the dominant utility GIS), CAD platforms for construction deliverables, pole loading analysis software (SPIDAcalc, O-Calc Pro, PoleForeman, or Katapult Pro's integrated pole loading), and increasingly integrated platforms that handle the full workflow on one record. Katapult Pro is one of those integrated platforms.

Ready To Get Your Application Through The Door?

Pole mapping is one of those parts of attachment work that looks straightforward until you've watched a few applications bounce back for reasons that come down to data hygiene. The cost of getting it right the first time is small compared to the cost of rework, missed shot clocks, and stalled federal funding milestones.

The teams we work with that move fastest on pole attachment applications are the ones that run one workflow from first design through final deliverable, on a platform that holds the map, the photos, the attribute data, and the engineering record in one place. That's what we built Katapult Pro to do, and it's what we use to run our own engineering services team's work every day.

If you're scoping a new build, planning a BEAD submission, or rebuilding your pole attachment workflow for higher volume, we'd be glad to talk through how the workflow can fit your team.

Schedule a call with our team to see how Katapult Pro can support your pole mapping workflow.