NJUNS Pole Attachment Application Process: The OSP Engineer's Field Guide

The first time I filed a NJUNS pole attachment application, I missed a Dynamic Attributes field and the ticket sat in limbo for three weeks before anyone told me why. That was on a 73-pole run in northern Virginia in Dominion Energy territory. Three weeks of a project timeline gone because of one blank field.

That's the kind of thing nobody tells you upfront about the NJUNS pole attachment application process. The system works — it genuinely does — but it punishes sloppy submissions and rewards engineers who understand what pole owners actually need to see before they'll move a ticket forward. This guide is what I wish someone had handed me early on.

What NJUNS Is and Why the Industry Uses It

NJUNS stands for National Joint Use Notification System. It's the shared platform that most major electric utilities and telecom pole owners in the United States use to manage joint-use pole attachment requests and track pole-related work between multiple parties. Think of it as the clearinghouse where an attacher — your ISP, CLEC, or cable company — formally notifies the pole owner that you want to place equipment on their infrastructure.

Before NJUNS, every utility had their own paper-based or proprietary submission process. Some still do, frankly. But for the large regulated utilities — Dominion Energy, Duke Energy, Georgia Power, Oncor, AEP, and many others — NJUNS is the standard. AT&T uses it for their pole inventory as well, which matters if you're attaching to AT&T-owned poles rather than electric utility poles.

The system creates a traceable, time-stamped record of every action on a ticket. That matters for FCC timeline compliance, for dispute resolution when make-ready costs balloon, and for managing the coordination between a new attacher and the existing attachers already on the pole.

The PA Ticket Workflow: Seven Stages, No Shortcuts

A NJUNS pole attachment application moves through a defined set of stages. Miss a requirement in any stage and the ticket either stalls or gets pushed back. Here's how the workflow actually runs in practice.

Stage 1: Create

You create the PA ticket in NJUNS. This is where most new applicants make their first mistakes. The ticket requires your organization's information, the pole owner's information, and — critically — a complete list of poles. Each pole gets entered individually with its NJUNS pole ID or the utility's own pole tag number. If the pole isn't in NJUNS yet, you may need to initiate a pole record addition first, which adds time.

Dynamic Attributes fields are required at creation and they're not optional even if the system lets you skip them. These fields capture specifics like attachment height, equipment type, conductor size, and whether you're proposing an aerial or underground transition. Leaving them blank triggers rejection. Fill them out wrong — listing a strand attachment as a cable/equipment attachment, for example — and you'll hear about it during survey.

Stage 2: Open

Once submitted, the pole owner accepts the ticket and moves it to Open status. This signals that they've received it and it's in their queue. Don't mistake Open for approval — it just means someone at the utility has acknowledged the request. In practice, Open status can last anywhere from a few days to several weeks depending on the utility's backlog.

Stage 3: Validate

Once the pole owner reviews the submission for completeness and accuracy. This is the stage where rejections come back if your Dynamic Attributes fields are wrong, if your pole list contains poles already covered by another active ticket, or if your attacher profile in NJUNS is missing updated contact or licensing information. Getting through Validate quickly means submitting clean data the first time.

Stage 4: Survey

After validation, the pole owner sends out a field crew to survey the requested poles. They're measuring actual attachment heights, documenting existing equipment, flagging safety violations already present on the pole, and collecting the data your make-ready engineer will need.

The FCC's shot clock gives pole owners 45 days to complete surveys after a PA ticket is accepted. That's the maximum, not the target. In territories with heavy deployment activity — parts of the Southeast, rural Texas — I've seen that 45-day window get used in full every single time. Plan around it. Rushing doesn't help; the field crews have routes and they run them when they run them.

This is also the stage where Katapult data becomes valuable. If your field team collected pole data with Katapult Pro before you filed — capturing attachment heights, equipment IDs, and GPS coordinates — you've given your make-ready engineer a head start that reduces back-and-forth with the pole owner's survey team. We tie pole loading analysis with O-Calc Pro directly into this workflow, so by the time survey data comes back, we already have preliminary load calculations running.

Stage 5: Make-Ready Design

Survey results come back into NJUNS and the pole owner's engineer — or a third-party make-ready engineer they've contracted — reviews what work is needed before you can attach. This is the stage that controls your timeline more than any other. Simple poles with room to attach and no violations move fast. Poles that need transfers, replacement, or complex rearrangements of existing equipment can sit in design for months.

The 60-day make-ready notice is the FCC's requirement: after issuing the make-ready design, the pole owner must give existing attachers 60 days notice before the new attacher can proceed with One-Touch Make-Ready (OTMR) work. We'll come back to OTMR in a moment.

During this stage, you may receive a pole loading analysis requirement. The pole owner wants to see that your proposed attachment doesn't push the pole over its allowable loading threshold under NESC standards. That's where NESC pole loading compliance work comes in — and it needs to be completed before you'll clear make-ready design on loaded or borderline poles.

Stage 6: Construction

Make-ready work gets done. Who does it — the pole owner's crews, existing attachers' contractors, or your OTMR contractor — depends on the make-ready type, the utility's policy, and whether OTMR applies. Once construction is complete, the pole owner updates NJUNS to reflect the as-built conditions.

For large projects, you'll have dozens of tickets in various construction stages simultaneously. That requires systematic tracking. We use spreadsheet-based dashboards tied to NJUNS ticket numbers, updated weekly, that show exactly which poles have cleared construction and which are still waiting on other attachers to move their equipment. Without that kind of tracking, batches fall through the cracks.

Stage 7: Closeout

After construction and your actual attachment work, the ticket gets closed in NJUNS. Closeout requires that you document your as-built attachment — actual height, equipment placed, GPS coordinates in some utility territories. Missing closeout documentation is one of the reasons utilities start rejecting future PA tickets from the same applicant. Keep a clean record.

NJUNS Pole Attachment Application Process: Common Rejection Triggers

I've reviewed hundreds of rejected NJUNS tickets over the years. The same patterns come up over and over.

• Incomplete Dynamic Attributes: The most common reason. Every field that the pole owner's system marks as required must be filled — even fields that seem irrelevant to your attachment type.
• Pole ID mismatches: Your pole list uses the utility's internal tag number but the NJUNS record is under a different ID format. Always verify pole IDs against the utility's current records before submitting.
• Attacher profile not current: Your NJUNS attacher profile is missing updated insurance certificates, contact information, or licensing — some utilities check this before moving past Validate.
• Poles already in an active ticket: Another attacher filed for the same poles recently. NJUNS will flag this, but some utilities reject instead of notifying. Check NJUNS for active tickets before you submit your list.
• Equipment description doesn't match OSP design: Your submission says fiber optic cable but your design spec shows coax. These discrepancies create audit problems for the pole owner.

The fixes are straightforward. What's frustrating is that rejection notifications in NJUNS can be sparse — a one-line comment that says "incomplete submission" tells you almost nothing. Having a direct contact at the utility's joint-use department speeds up the clarification process considerably.

How OTMR Changes the NJUNS Pole Attachment Workflow

One-Touch Make-Ready was designed to solve the coordination problem that made traditional make-ready so slow. Under the old model, every existing attacher on a pole had to schedule their own crew to move their own equipment before a new attacher could proceed. In practice, that meant waiting months for AT&T, Comcast, and the electric utility to each independently schedule field work — none of them with any urgency to move fast for your project's benefit.

OTMR allows the new attacher to hire a single qualified contractor to perform all simple make-ready in one visit. The 60-day notice window still applies — existing attachers get that window to respond and either do their own work or consent to OTMR. If they don't respond, the new attacher can proceed.

In the NJUNS workflow, OTMR eligibility is flagged at the make-ready design stage. If poles are OTMR-eligible, the ticket tracks the 60-day notice clock. When that clock expires without response from existing attachers, you're clear to proceed with your OTMR contractor.

The catches: OTMR doesn't apply to complex make-ready, not all utilities have adopted OTMR policies uniformly, and your OTMR contractor must hold certifications from each existing attacher on the poles. Getting those certifications takes time upfront. But on projects where OTMR is available and the majority of work qualifies as simple make-ready, it can cut 90 to 120 days off the timeline compared to traditional sequential make-ready.

We've seen this play out on a 340-pole rural broadband deployment in central Georgia — traditional make-ready would have taken 7 to 8 months. OTMR got the same route cleared in just under 5 months. That kind of difference matters for project financing, grant compliance deadlines, and the ISP's customer commitments.

Typical Timelines by Utility

These are rough numbers based on what we've seen across multiple projects. Individual project results vary based on pole count, make-ready complexity, and seasonal factors.

• Dominion Energy (Virginia, North Carolina): Survey runs close to the 45-day maximum. Make-ready design adds 6 to 10 weeks for complex poles. Total PA-to-construction authorization: 5 to 8 months for complex make-ready.
• Duke Energy (Carolinas, Indiana, Florida): Similar to Dominion in the Carolinas. Their joint-use team in Indiana runs faster. Plan 4 to 7 months.
• AT&T (as pole owner): Highly variable by state. Texas territories move faster than the Southeast. Their dynamic attributes requirements are strict and they will reject incomplete submissions without much detail. Budget 3 to 6 months for straightforward attachments.
• Smaller rural electric cooperatives: Some run faster because they have fewer active tickets in the queue. Others are much slower because they have limited joint-use staff. We've seen co-op survey windows extend well beyond 45 days — technically a violation of FCC timelines, but enforcement is limited for small co-ops.

Tracking these timelines carefully matters for make-ready engineering timelines on projects with hard completion deadlines. BEAD grant projects, for example, carry milestone commitments where a slow utility can directly threaten compliance.

Using Katapult and O-Calc Data in the NJUNS Process

The pole data you collect in the field doesn't exist in isolation from the NJUNS workflow — or at least it shouldn't. When field crews use Katapult Pro to capture pole conditions, attachment heights, and GPS coordinates, that data can feed directly into your NJUNS application and your make-ready design package.

Practically speaking: Katapult exports can populate the Dynamic Attributes fields in NJUNS with actual measured values rather than estimated ones. That reduces the chance of rejection at Validate and often reduces the scope of corrections required after survey. The pole owner's surveyor is less likely to flag discrepancies when your submitted data matches what they find in the field.

O-Calc Pro load calculations tie in at the make-ready design stage. When a pole comes back from survey flagged as requiring a loading analysis before attachment authorization, having a pre-run O-Calc model ready to submit speeds up that review. The pole owner's engineer can verify your work rather than starting from scratch. On borderline poles — where the load calc comes back at 97% or 98% of allowable — having the model already built also lets you explore mitigation options quickly: adjusting your attachment height by 18 inches, reducing equipment weight, or flagging the pole for replacement.

Managing these ROW permitting delays requires integrating the NJUNS timeline with all other permit streams — municipal ROW permits, railroad crossings, environmental reviews — so that field crews don't arrive at a corridor that's only partially clear.

Tips for Faster NJUNS Pole Attachment Application Approval

Most of these come down to submitting complete, accurate data the first time and building relationships with utility joint-use contacts.

• Run a pre-submission checklist on Dynamic Attributes fields before every ticket batch. Build a template for each major utility you work with — their requirements vary.
• Verify pole IDs against current utility records, not your own GIS. Discrepancies are common after utility consolidations and system migrations.
• Establish a named contact at each utility's joint-use department. This doesn't shortcut the process, but it gives you a direct line for clarification when rejections are vague.
• Stage your submissions to align with your construction sequence. Don't submit 300 poles in one batch if construction is going to happen in four phases — you'll have tickets closing out while others are still in survey, and the coordination overhead is significant.
• Keep your NJUNS attacher profile current. Expired insurance certificates will get you rejected at utilities that check, and updating your profile mid-project causes delays.
• Track the 45-day survey clock in your project schedule. If a utility is approaching that deadline without scheduling survey, send a formal written follow-up. It creates a record and sometimes accelerates scheduling.

None of this is glamorous. But on a 500-pole deployment, the difference between clean submissions and sloppy ones is often 60 to 90 days of project schedule — which in a competitive broadband market is a very real competitive disadvantage.

When the NJUNS Process Breaks Down

It does break down. Utilities lose survey data. Tickets get stuck in Validate for no apparent reason. A make-ready design comes back requiring a pole replacement on a structure that clearly doesn't need one. Existing attachers don't respond to the 60-day notice and then dispute the OTMR work anyway.

When the process breaks down, documentation is your only protection. Time-stamp every communication. Export your NJUNS ticket history regularly. Keep records of when you submitted, when survey was completed, when design came back, and when you followed up on stalls. The FCC's complaint process exists, but it's slow — most disputes get resolved through direct negotiation with utility joint-use teams, and having a clean paper trail makes those conversations much more productive.

Our permitting services include managing this process end-to-end for clients who don't want to build the internal expertise or staffing to handle high-volume NJUNS submissions. For a 200-pole project, that's manageable in-house. For a 2,000-pole multi-county deployment, managing the NJUNS workflow, tracking timelines, and coordinating construction authorization across dozens of active tickets becomes a significant operational burden.

If you're dealing with a high-volume NJUNS pole attachment application process or running into repeated rejections on a specific utility, our team has handled this across 22 states. Reach out at info@draftech.com — sometimes a fresh set of eyes on a stalled ticket batch is all it takes.