Pole attachment schedules fail when a project team treats the owner's response as one undivided wait. The chain starts with a complete application and merits review. Survey and estimate come next; existing-attacher notice and make-ready follow. Any self-help election comes last. Each event needs evidence tied to an owner, plus a trigger date that establishes the escalation condition. We plan that chain before a construction date is allowed to depend on it.
The governing regime comes first. Federal timelines apply only where 47 U.S.C. 224 and the FCC's rules control the utility and jurisdiction. Other pole owners may follow a state program or tariff. For some routes, an agreement or owner procedure controls. We identify that source before pasting a federal clock onto every structure. That matters.
Pole Owner Response Time for Make-Ready in 2026
Pole owner response time for make-ready is the documented sequence that starts with completeness review and continues through the pole survey. The estimate and notice follow before physical preparation of a pole. Under current 47 CFR 1.1411, a standard-order survey has a 45-day deadline, although order size and the controlling jurisdiction can alter the usable schedule for that route.
The direct answer is therefore a chain, not a promised completion date. The current federal rule gives a utility 10 business days to determine whether an application is complete. After completeness, the standard-order merits response and survey periods run for 45 days. A detailed estimate is then due within 14 days after the survey, subject to the distinct treatment the rule gives Large Orders under the tier provisions.
Physical make-ready has another clock. For communications-space attachments, the notice sets completion no later than 30 days after notice under the current federal standard-order timeline in 47 CFR 1.1411. Work above the communications space uses 90 days, and the utility may assert the additional control period allowed by the rule for the affected poles on that order. These are regulatory stages, not a guarantee that every pole on every route will clear on one date or that an owner has promised one route-wide release.
The official source is the current eCFR text of 47 CFR 1.1411. We read the definitions and tier thresholds with the operative paragraphs, because a timeline copied without its order category can be materially wrong when setting each milestone. We also separate simple communications-space work from complex make-ready and supply-space work. Those labels affect contractor eligibility and remedies.
One-touch make-ready is a separate path for qualifying simple work. It is not a universal shortcut. Notice duties and contractor controls remain. Damage or restoration obligations do too. Our one-touch make-ready guide explains the eligibility question. For response-time planning, we flag OTMR candidates but keep them out of the conventional transfer schedule until the utility accepts the classification in the application record.
How the Federal Response Clock Is Built
A useful schedule begins with the order tier. The current rule applies the standard timeline through the lesser of 300 poles or 0.5 percent of the utility's poles in a state for the request. Mid-Sized Orders and Large Orders use higher thresholds and added time. Orders beyond the rule's Large Order ceiling require good-faith negotiation rather than pretending the standard clock still controls.
Advance notice now matters for larger submissions. The rule calls for at least 15 days of advance notice for a Mid-Sized Order and 60 days for a Large Order, with a meet-and-confer process for the latter. Filing first and discovering the advance-notice requirement later can keep the operating timeline from starting when the project schedule expected it to start.
Completeness is a separate gate from technical approval. The owner must identify all reasons for a timely incompleteness finding, and a bona fide resubmission addressing those reasons receives its own 5-business-day review rule. We log each reason against the field record or calculation that resolves it. A generic response such as “updated plans attached” is not enough for traceable closure.
| Clock event | Standard order | Larger-order effect | Evidence to retain |
|---|---|---|---|
| Completeness review | 10 business days | Same initial gate | Receipt and written decision |
| Merits response | 45 days | 60 or 90 days by tier | Grant or specific denial |
| Pole survey | 45 days | 60 or 90 days by tier | Survey record and notices |
| Detailed estimate | 14 days after survey | 29 days for Large Orders | Itemized basis and date |
| Communications-space work | 30 days after notice | 75 or 120 days by tier | Notice and completion status |
| Above-space work | 90 days after notice | 135 or 180 days by tier | Notice, control period, status |
Application and survey controls
The table is a reading aid for the federal rule, not a substitute for it. We first determine whether the application is standard or Mid-Sized. A Large Order is marked separately, as is any request beyond the defined tiers. We also check whether multiple requests can be treated as one request. Pole attachment rate calculations address a different issue: recurring attachment rates should not be confused with make-ready timing or make-ready charges.
Estimate and notice controls
An estimate should be tied to the survey that supports it. The current rule calls for enough detail to determine projected material and labor costs. Related costs remain visible, including a pole-by-pole presentation where requested and subject to treatment of fixed costs. After accepted payment, written notices identify affected work and attachers. Each notice also states the applicable completion date. Retain the copies. A spreadsheet forecast is not the record.
Make-ready and remedy controls
The communications-space date begins with the written notice sent after payment, not with application intake. Supply-space and other above-communications-space work uses a different period and may involve the utility's right of control. We keep those work classes separate at the pole level. A route-level status called merely “make-ready pending” hides which event is late. It also obscures the responsible party and available remedy.
Self-help also follows a sequence. The deadline must pass, the attacher must provide the required notice, and the contractor must meet the applicable qualification and owner-selection rules. Utility and existing-attacher attendance rights remain intact. We treat damage notification and service protection as release conditions, not cleanup language, because a schedule recovery step cannot create an uncontrolled operating risk.
Why Pole Owner Response Time for Make-Ready Still Varies
A rule-based date can move for lawful reasons. A utility may issue a detailed deviation when good and sufficient cause makes timely make-ready infeasible. That writing must identify the affected poles. It must also provide a new completion date. Complex make-ready carries specific safety and service-interruption treatment as well, so we record the cited basis and affected structures instead of replacing the original milestone with an unexplained date.
A route can also mix governing regimes. Municipal and cooperative ownership may sit beside federally regulated poles; state-certified programs or contract-specific processes can govern another segment. We do not average those clocks. We segment the route by owner and authority, then schedule each segment against its controlling source. That source may be a rule or tariff; for another owner, an agreement or published procedure may control. The slowest dependency stays visible to the overall build plan. Our state service-area map shows where Draftech can support that owner-by-owner engineering work.
Owner comments are another source of apparent delay. Some comments correct genuine application defects; others request clarification without making the package incomplete. We keep the category clear. Pole ID, proposed attachment height, span association, loading model, photographs, and make-ready notation should all point to the same structure. When one identifier drifts, a reviewer cannot safely approve the rest of the record.
Existing-attacher coordination is not an invisible utility task. Under the federal rule, the new attacher receives notice copies and contact information and is responsible for coordinating to encourage timely completion. That makes a contact log, notice date, response, work status, and unresolved constraint part of schedule control. Our make-ready engineering timeline shows how these dependencies fit beside design and construction release.
Pole replacement deserves a distinct status from attachment transfers. Replacement can affect supply facilities and communications attachments. Equipment or permits may move on separate tracks, while traffic control and restoration create their own dependencies. We show the controlling owner decision and all dependent transfers instead of assigning one generic completion percentage. That approach does not predict crew production. It tells the project manager which accepted prerequisite still prevents the new attachment from moving forward.
Weather and emergency restoration can affect actual performance, but they should not become an all-purpose explanation. If the utility invokes a permitted deviation, the written record should name the affected poles and explain the reason. It should also give the new date. If no formal deviation applies, the issue remains an overdue milestone for coordination. Clear status language protects both parties by separating documented exceptions from an application that simply lost its owner.
Draftech timing rule: We use 6 schedule fields for every owner event: authority; triggering record; trigger date; deadline; evidence; escalation path. This is a Draftech review framework, not an industry performance statistic.
One limitation in our own framework is blunt: six fields improve visibility, but they cannot make a pole owner respond or turn a planning assumption into a regulatory deadline. We still have to distinguish engineering control from owner control. No dashboard fixes that.
Application Controls That Protect the Clock
The best schedule defense is an application that can be reviewed without reconstructing the field survey. Our in-house engineers reconcile map coordinates with owner pole numbers; pair photographs with attachment heights; verify span geometry against proposed cable and equipment; and confirm the loading basis before issue. We do not release a structure with an undocumented critical assumption merely to make the submitted count look complete. Evidence first.
- Owner basis: Name the controlling rule, tariff, agreement, and current owner procedure for each route segment.
- Structure identity: Match the pole ID to coordinates and photographs; then reconcile the model with the drawing callout before submission.
- Proposed attachment: Reconcile attachment height and cable with the span hardware; check clearance separately; confirm make-ready notation across all files.
- Comment closure: Tie every owner reason to the revised evidence and preserve the transmittal date.
- Schedule trigger: Store the event that starts each clock instead of relying on a manually entered due date.
Field evidence deserves its own gate because a model cannot repair an ambiguous photograph or a mismatched pole. Our utility pole loading field measurement framework preserves traceability from observation to engineering input. Where the owner requires structural review, the evidence must carry into the accepted modeling method and owner-specific deliverable. No shortcut survives owner review.
Batching should follow the current rule and the actual deployment, not an attempt to manipulate clocks. The regulation addresses advance notice and order thresholds. It also explains when multiple requests may be treated as one. We therefore map the planned order against those provisions. The deployment relationship stays documented, and larger-order coordination begins early. A smaller file is not automatically a better file if its separation obscures one network deployment.
Quality control should reproduce a sample from source evidence rather than only checking that fields are populated. We select ordinary poles, then add cases with replacement or complex make-ready. Owner-comment cases and missing-access records also enter the sample. The reviewer traces each from the photograph and survey into the model. The review continues through drawing and application before it reaches the schedule. If one stage uses a different identifier or revision, the response-time record is not ready for release.
A weekly owner report should distinguish these states: submitted; incomplete; complete; surveyed; estimated; paid; noticed; in make-ready; ready for attachment. Those states mirror decisions that can be evidenced. Percent-complete estimates without those records are weak controls because two routes at the same percentage can face entirely different remaining work. We prefer fewer statuses with objective entry and exit conditions over a long list of subjective progress labels.
A Practical Response-Time Decision Framework
ISP or CLEC with a federally regulated standard order: Build the milestone schedule from the completeness decision through the merits response and survey. Add estimate plus payment, then preserve each notice through make-ready completion. Use the federal periods only after confirming that 47 U.S.C. 224 and 47 CFR 1.1411 control the owner and jurisdiction. This is the cleanest case.
Program manager carrying a Mid-Sized or Large Order: Start with advance notice and the proper tier before assigning survey or work dates. The submission plan must preserve the deployment relationship while applying each tier-specific period, because an artificial file split does not create a better clock and can obscure the request the utility actually has to process. Coordinate early.
Applicant outside the FCC regime: Replace every federal assumption with the exact state program or tariff that governs the facility. An executed agreement may control instead; an owner procedure may also set the trigger. Capture acceptance and survey status, then tie estimate payment to transfer notice before completion confirmation. Never label an internal forecast as an owner commitment.
Attacher facing a missed federal deadline: Read the applicable self-help provision before acting. Contractor qualification and notice still matter; attendance rights and damage response remain intact. Supply-space restrictions require separate attention. Self-help is a controlled remedy. It is not permission to send an unfamiliar crew onto a joint-use pole. We will not release physical work until the legal basis and engineering controls are resolved.
The service bridge is specific: uncertain ownership and incomplete field records create untrustworthy clocks, while inconsistent models or untracked notices hide the next responsible party. Those are the exact problems our make-ready engineering workflow removes. Engineering remains 100% in-house. When construction is included, full turnkey delivery uses Draftech-managed subcontract crews under our QA/QC and safety oversight, while power work stays within distribution and make-ready scope.
If your attachment schedule does not show what started each clock, email our engineering team. We can review the owner matrix against the application evidence. We then trace open comments into the notice record without inventing one universal response time. The next action should have one owner. It belongs to engineering or owner coordination; when a deadline has passed, it may instead be existing-attacher coordination or a properly supported remedy.
Talk to our make-ready team about your pole-owner schedule. Bring the owner list and application receipts. Add current survey status plus any estimates; include open notices. We will identify the controlling clock and the missing evidence.
