An ISP project manager often treats the joint-use call as the work. The stall is usually a missing dated file. A utility desk will not price a pole that the application cannot identify, and counsel cannot argue from a screenshot that never entered the revision history.
This guide is engineering-record preparation for an ISP's authorized negotiator. It is not legal advice or bargaining representation. Dispute advocacy is also out of scope. Counsel and the client control rights and terms. We build the dated files those people can take into a utility meeting without asking an engineer to argue price.
Pole Attachment Negotiation Tips for ISPs: Start With Authority
Pole attachment negotiation tips for ISPs start with a dated engineering record, not a talking point. Draftech's 6-file package is inventory; application record; make-ready evidence; cost-question log; revision history; and issue matrix. Access and price stay with counsel under 47 U.S.C. 224 plus 47 CFR Part 1 Subpart J, and with the state file plus the executed agreement.
Start with the owner, not the spreadsheet. 47 U.S.C. 224, Pole attachments, current through September 3, 2026 on the U.S. Code, is the federal statute. Subsection (a)(1) defines utility and then excludes any railroad, any person who is cooperatively organized, or any person owned by the Federal Government or any State. That exclusion is statutory, so we copy it as written rather than collapsing owner classes. The Congressional Research Service report Pole Attachments in Broadband Deployment: Selected Issues, R48992, dated June 16, 2026, restates the same owner-class limit: investor-owned utilities can sit inside the federal regime, while municipalities and electric cooperatives do not.
Attacher class is a second gate. Current 47 CFR 1.1411(a)(1), on eCFR as of September 14, 2026, defines an attachment as one by a cable television system or a provider of telecommunications service. Counsel decides whether this ISP is inside that class for this owner. We record the conclusion we were given. We do not invent one from a portal login.
Jurisdiction is the third gate. 47 U.S.C. 224(c) keeps the Commission out of pole attachments in a State that regulates those matters and certifies that it does. The Wireline Competition Bureau public notice DA 26-579, released June 11, 2026, states that 23 states and the District of Columbia have filed such certifications. California is on that certified list. For a California IOU route, the CPUC file and the executed agreement are the first clock sources we copy. Current 47 CFR 1.1411 is not.
Name four facts before any clock is copied
Every timing sentence in the issue matrix has to answer four questions. If one answer is missing, the date is a forecast, not a regulatory event.
- Owner type: investor-owned utility or municipality. A cooperative or another class named in the agreement also belongs here.
- Attacher class: the classification counsel assigned for this relationship, written beside the date it was assigned.
- Jurisdiction: FCC Subpart J. A reverse-preemption state commission or the contract alone may control instead.
- Controlling instrument: the tariff, agreement, owner standard, or commission order actually in force on the application date.
Authority card: open one pole and find the four facts on its matrix row without leaving that row. If any of them lives only in email, the meeting is not ready.
The pole loading and make-ready service is where those four facts get tied to a structure. Loading outputs and clearance notes belong on the make-ready evidence sheet. They do not decide who may attach. They do not set rent.
Build the Six-File Engineering Record
We keep six files because mixing them is how a negotiator inherits an argument nobody can reconstruct. The table is Draftech's recommended package. It is not a statute and it is not an error rate.
| File | What it establishes | Source family | Failure if missing |
|---|---|---|---|
| Inventory | Which structures are in the request | Owner GIS, field IDs, billed IDs | The meeting argues about a pole nobody can find |
| Application record | What was submitted and when | Portal receipt, completeness letter, revision | A clock starts from a date the owner never accepted |
| Make-ready evidence | Physical work proposed or observed | Survey, loading, owner standards | A cost line has no structure behind it |
| Cost-question log | Which charges are still open | Estimate lines and source notes | Price talk mixes with engineering talk |
| Revision history | What changed after the first submittal | Dated packages and owner comments | Two people argue from two versions |
| Issue matrix | Open items by pole or job line | The five files above | Counsel is asked to work from a thread |
Inventory first, then the application record
Inventory is identity work. Owner prefixes and replacement-pole suffixes can make one structure look like three records, and a local alias can do the same. We keep billed ID and owner ID in separate mapped fields, then GIS ID and field ID beside them. A match rule should be reviewable. Concatenating values in the source column is how later disputes become unprovable.
The application record is a custody file. Current 47 CFR 1.1411(d)(1), as amended effective May 7, 2026 under the Federal Register implementation of FCC 25-38, Accelerating Wireline Broadband Deployment by Removing Barriers to Infrastructure Investment, released July 25, 2025, gives a covered utility 10 business days to decide completeness. A resubmission that addresses the stated defects is deemed complete in 5 business days unless the utility specifies what remains open. Those two numbers belong on the application row only after the authority card is filled. The NJUNS pole attachment application process guide shows why a portal workflow still needs that same receipt trail.
A complete-looking PDF is not a complete application. The owner's written procedures, the master agreement, or the publicly posted requirements at the time of submittal define completeness under current 47 CFR 1.1411(d)(1). We keep a copy of the procedure that was in force on the submittal date. A later rewrite of the portal help text does not quietly replace it.
Make-ready evidence a negotiator can actually use
Make-ready evidence is the physical file: survey notes; photographs with pole IDs; loading outputs; proposed movements; and owner standard citations. It answers what exists on the structure and what the design asked to change. It does not answer whether the ISP may elect one-touch make-ready.
Current 47 CFR 1.1411(k) is the OTMR option for simple make-ready on covered utilities. We record whether the application elected that path. We do not decide whether the work is simple. The OTMR pole attachment services guide owns that sequence. This package stops before eligibility so a negotiator cannot treat an engineering flag as a grant.
If the survey and the application list disagree, both values stay visible. A replacement pole that received a new owner ID is a revision event, not a delete. The issue matrix names the blocked span and the next process. A green production total cannot hide a network gap.
Map Every Clock to Owner Type
Federal clocks are a baseline for covered utilities in states that have not reverse-preempted. They are not a national promise. Current 47 CFR 1.1411(d)(2) gives a covered utility 45 days from a complete application to grant or deny access on a standard-order request. A Mid-Sized Order gets 60 days. A Large Order gets 90 days. The survey period in current 47 CFR 1.1411(d)(3) uses those same three windows. Copy them only onto poles whose authority card says Subpart J applies.
Order class is a threshold fact, not a crew-batch convenience. Current 47 CFR 1.1411(a)(4) defines a Mid-Sized Order as greater than the lesser of 300 poles or 0.5 percent of the utility's poles in a state, up to the lesser of 3,000 poles or 5 percent. Current 47 CFR 1.1411(a)(5) defines a Large Order as greater than that band, up to the lesser of 6,000 poles or 10 percent. Breaking work into daily assignments does not change the class of the application that produced those poles.
Advance notice is a separate event. Current 47 CFR 1.1411(c) requires written advance notice no less than 15 days before a Mid-Sized Order and 60 days before a Large Order, and the Large Order notice must request a meet-and-confer within 30 days. We record the delivery proof. A reserved crew slot is not that proof.
Pole attachment negotiation tips for ISPs after the first utility reply
The first utility letter is a source document, not a verdict. A completeness defect list is an application event. A merits denial has to be specific under current 47 CFR 1.1403(b) and 1.1411(d)(2) where those rules apply, and it has to rest on capacity or safety. Reliability or engineering standards can also be the stated ground. We log the stated reasons next to the poles they name. We do not rewrite them into a friendlier summary.
One thing I have always found easy to over-service is copying a 47 CFR 1.1411 clock onto a cooperative pole file because the spreadsheet already had the column. That habit is ours. It is also wrong. A rural electric cooperative is outside the federal utility definition in 47 U.S.C. 224(a)(1). The executed joint-use agreement and the cooperative's published standards are the instruments we copy. If the state commission has its own cooperative-pole program, that program is a fourth source, not a reason to paste the FCC 45-day cell.
Municipal poles take the same discipline. The city or public-power tariff, the occupancy agreement, and any local ordinance the counsel file identifies are the controlling texts. DA 26-579 does not pull those owners into Subpart J. Our joint-use pole attachment work is the place those owner-specific contacts and notice records get kept beside the pole list. Coordination is not consent from the other party.
A reverse-preemption state can still contain a cooperative or municipal owner that the state never brought under its pole-attachment rules. The issue matrix has to say so pole by pole. A California CPUC clock copied onto a city-owned pole is the same defect as an FCC clock copied onto a co-op pole. Wrong authority. Wrong date.
Keep Cost Questions Off the Rate Sheet
Cost questions are line items. They are not a rate. Current 47 CFR 1.1411(e) requires a covered utility to present a detailed itemized estimate. Where requested it is pole-by-pole. The clock is 14 days from completing the survey, or 29 days on a Large Order. The estimate has to carry documentation sufficient to determine the basis of the charges. We log each unsupported line. We do not convert the log into an annual attachment formula.
The pole attachment rate calculation guide owns governing formulas. Carrying charges and usable-space treatment live there too. This file stops before that workbook. A negotiator who argues rent from a make-ready estimate is mixing two instruments. A negotiator who argues make-ready from a rent invoice is doing the same thing in reverse.
Current 47 CFR 1.1411(e)(4) says a covered utility may not charge a new attacher to bring poles, attachments, or third-party equipment into compliance with current published safety, reliability, and pole-owner construction standards when the noncompliance was caused by work performed by a party other than the new attacher before the new attachment. That sentence is a question for the log, not a finding we stamp onto the estimate. We attach the field evidence that shows the preexisting condition. Counsel decides what the sentence does for this owner.
Log rule: one open charge, one pole or job line, one source document, one date. An unexplained total is not a question. It is a missing file.
Final invoices follow the same split. Current 47 CFR 1.1411(e)(3) requires a detailed, itemized final invoice of actual make-ready charges when the final cost differs from the estimate, again pole-by-pole where requested. We reconcile the invoice to the estimate and to the work record. Recurring rent stays in its own column. Make-ready labor stays in another. Blending them into one effective unit rate is how a later true-up becomes unanswerable.
Self-help and complaint procedure sit outside this package on purpose. Current 47 CFR 1.1411(j) describes self-help after specified deadlines on covered utilities, including survey work and make-ready. Current 47 CFR 1.1404 and 1.1415 address complaints and the Rapid Broadband Assessment Team. Those paths belong to counsel and the client. We will not walk them here. The engineering job is to keep the evidence those paths would need, if someone later opens them, from dissolving into email.
Recommendation: Who Should Carry Which File
For a single-state ISP on an investor-owned utility in a state that has not reverse-preempted: require the 6-file package with the Subpart J authority card filled before anyone copies a 10-business-day or 45-day cell. Do not accept a route dashboard as a substitute for pole history. That buyer needs custody more than another talking-point memo.
For a multi-state overbuilder with reverse-preemption mix: buy the operating discipline that keeps a separate authority card per owner and per state. DA 26-579's count of 23 certified states plus the District of Columbia is a reminder to classify, not a license to average clocks. A provider that reports one national make-ready duration will hide the location most likely to control activation.
For an ISP attaching to municipal or cooperative poles: drop the FCC timeline columns unless counsel has identified a state program that actually applies to that owner. Carry the executed agreement and the owner standards. Keep the application receipt with them. We do not recommend a meeting that treats those poles as if 47 U.S.C. 224 had already decided the terms.
Draftech's in-house engineers own the six files. When full turnkey make-ready construction is later in scope, Draftech-managed subcontract crews deliver it under our QA/QC and safety program. Engineering remains in-house. The performing contractor stays visible in the field record. We do not claim a self-perform construction crew today, and we do not undersell the construction role as oversight-only.
The last useful test is reconstruction. A reviewer who did not prepare the package opens 1 pole and finds inventory identity; the application event; the make-ready evidence; the open cost question; the revision that changed the row; and the matrix status. If that test fails, the authorized negotiator is being sent in with a story. Send the first unresolved pole to the attachment team.
If pole attachment negotiation tips for isps is part of a qualifying route, Draftech engineers the first 20,000 linear feet at no cost, from feasibility and field survey through permit approval. Request the free design package. The owner reviews each request before Draftech commits the package.
Talk to our make-ready team about the open pole on your issue matrix. Bring the pole identifier and the authority card. We will start with that pole.
