An approved OTMR application answers one question: the utility has acted on the simple-work package, and it has not authorized a crew to climb. The FCC order Accelerating Wireline Broadband Deployment by Removing Barriers to Infrastructure Investment, FCC 25-38, took effect on May 7, 2026 under the Federal Register implementation notice of that date. After that date, the attacher-side clock is a notice-and-record problem.
This guide starts after technical approval. Survey evidence and simple-work classification belong in the paired engineering article. The record that matters here is the pole history. Authorization has to sit beside the field event, the notice file and any open inspection or remedy, so a later reviewer can reconstruct the pole without hunting through email.
How OTMR pole attachment services start the field clock
OTMR pole attachment services run the approved attacher's field sequence: contractor assignment, pre-work notice, simple make-ready, completion records and inspection. Current 47 CFR 1.1411, as amended effective May 7, 2026, requires 15 days of written notice before approved work and a 15-day window after work on each pole to send completion notice.
An approval date answers only that the utility has acted on the submitted simple-work package. Mobilization requires more. We open the field ledger with the exact approved poles and the assigned contractor pathway, then calculate notice dates from actual delivery records rather than from a reserved crew slot. Crew availability can shape the forecast. It never supplies the regulatory event that the forecast depends on.
If the approved pole list changes after notice has already been prepared, the scheduler has to recalculate the affected workfront from the revised utility record rather than carrying an earlier delivery date onto structures the utility did not approve. Recalculate those dates. A leftover notice file is worse than a late one, because recipients will treat it as the work that is coming.
Put the approval record beside the construction calendar
FCC 25-38 is the order already named above. Current 47 CFR 1.1411 now carries the completeness, order-size and advance-notice provisions used here. The pole loading and make-ready service connects those procedural events to the approved pole record. We cite the current rule once in full, then later mentions use the section number.
A useful calendar shows why a date exists. Application completeness and merits action come from the utility record, while notice delivery lives in the attacher's communication file. Contractor readiness is a third event, taken from the selected pathway rather than from a reserved crew slot. If one of those events moves, the scheduler can revise the affected workfront without rewriting the history of the others, which is the only way a later review can tell whether the delay belongs to application review or to field preparation. We keep those events separate.
We do not label every missed forecast as utility delay. A defect notice may require resubmission, and an unavailable contractor demands another qualified assignment. Those conditions have different cures. The ledger names the event that failed and retains the old planned date, which gives the project manager an honest schedule variance instead of a polished calendar that cannot explain itself. Variance needs a named cause.
Field-date test: open one scheduled pole and find the approval record, notice delivery and contractor assignment without leaving its ledger entry. If any item exists only in email or in a planner's memory, the mobilization date is not ready to issue. We will not issue it.
The FCC rule assigns rights to the utility and affected existing attachers. Draftech does not replace those roles. We coordinate technical inputs and the construction record, while the new attacher still controls its election and notices. That separation lets an internal schedule remain useful without presenting it as consent from another party. A bar on a Gantt chart cannot authorize work. We will not pretend it can.
Keep route gaps visible when poles leave OTMR
A route rarely reaches the field as one uniform class. Some poles may remain eligible for simple make-ready while a replacement, an above-space condition or supported complex work follows another process. We let the clean group move only if the excluded location stays connected to its network consequence. A splice plan cannot quietly assume that a held pole has cleared because nearby work advanced. The held pole still controls the span.
| Event | Current rule timing | Controlled record |
|---|---|---|
| Application completeness | 10 business days | Utility disposition and defect list |
| Ordinary merits review | Generally 15 days | Approval or supported denial |
| Pre-work notice | 15 days before make-ready | Covered poles, contractor and work date |
| Completion notice | Within 15 days after work | Pole completion record |
| Inspection opportunity | At least 90 days from receipt | Inspection status and any remedy |
Sequence work without disguising the federal order
Current 47 CFR 1.1411 defines Mid-Sized Orders as greater than the lesser of 300 poles or 0.5 percent of the utility's poles in a state, and Large Orders as greater than the lesser of 3,000 poles or 5 percent, up to the lesser of 6,000 poles or 10 percent. 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. The pole owner response-time guide explains the broader schedule. Our route board preserves the actual deployment relationship even when field crews receive smaller operational batches. Batch size is not order class.
Breaking work into practical crew packages can reduce idle time. It does not change the applicable federal order merely because fewer poles appear on a daily assignment. We record the reason for each batch and show the common route that joins it to the rest of the deployment. That record keeps operations flexible while preventing schedule convenience from becoming an unsupported order classification. Convenience is not a classification.
The table is a map, not a promise that every row applies identically to every order. The scheduler first confirms jurisdiction and order treatment, then we link each applicable timing event to its source instead of copying a default 15-day cell onto a Large Order that the rule treats differently. A held complex pole receives a standard-make-ready status on the same route board, and its downstream effect remains visible even while the eligible work proceeds around it. Keep the gap on the board.
The route-gap entry should identify the blocked span and its next process so activation planning can continue without treating nearby OTMR completion as evidence about the excluded structure. A project manager should be able to answer which route segment remains unusable because of the excluded pole. It is not enough to show the pole in a red color. We attach the actual continuity consequence and the next responsible process. A green production total cannot hide a network gap. The gap remains.
Name the contractor before the notice leaves
Contractor selection is a work-class decision, not a procurement shortcut. Simple work can follow a different pathway from complex or above-space self-help. We verify the utility's applicable list treatment and the firm's qualifications before naming it in a notice. The contractor on the record must be the contractor scheduled to perform the approved movement. Names have to match.
Match qualifications to the classified work
Current 47 CFR 1.1412, as amended effective May 7, 2026, addresses contractor selection and requires a reasonably sufficient utility list for certain complex and above-space self-help. It also gives the utility 30 days to respond to a request to add a contractor and states qualification categories. The OTMR engineering services guide covers the technical package that the selected contractor receives. We send that package only after the pathway is supported. We start any add-contractor request before advertising a field date so recipients never receive a notice tied to a firm that no longer fits the applicable pathway under current 47 CFR 1.1412.
If list status changes while notice is being prepared, the attacher pauses that assignment and updates the contractor record before recipients receive a date tied to a firm that no longer fits the pathway. Otherwise the schedule can reach the notice point while the firm remains outside the applicable pathway. Simple-work handling may differ under the rule and utility procedure, but the new attacher still needs a real assignment rather than a placeholder company name. A placeholder invites last-minute substitution. The resulting notice no longer describes the crew expected at the pole. We will not send that notice.
- Work date: the date and time of the approved make-ready, taken from actual notice delivery.
- Work description: the simple movement already approved, written tightly enough that a supervisor cannot treat the visit as a redesign session.
- Contractor identity: the firm actually assigned under current 47 CFR 1.1412, with list status or qualification evidence attached to the pole package.
- Observer window: a reasonable opportunity for the utility and existing attachers to be present, as current 47 CFR 1.1411(k)(4) requires.
Contractor check: the credential card names the approved work class and utility-list status, then identifies the qualification record that supports the assignment and travels with the pole list. Availability by itself proves nothing about authorization. We hold the date until it does.
Our own schedule pressure can make an available firm look interchangeable with a qualified one. That is a limitation of the process we recommend: we will hold a lawful start even when an unqualified crew could mobilize sooner. Eligible work can be resequenced, or another approved firm can be chosen. We cannot broaden a contractor's authority through optimistic wording. The trade-off is a later start against a lawful one.
Notice content should describe the approved work without inviting a field redesign. Existing attachers and the utility receive the opportunity the current rule provides, and a supervisor receives only the movement that engineering approved. If the actual configuration differs, the supervisor stops and reports it rather than converting a coordination visit into an informal design meeting. The pole controls the decision. We write that on the card.
Give the supervisor one usable stop rule
The field package must tell a supervisor when simple work has ceased to be simple. A newly discovered complex condition stops affected make-ready on that pole. If the new attacher or the utility determines that make-ready classified as simple is actually complex, current 47 CFR 1.1411(k)(4) requires that specific make-ready to halt and the determining party to give immediate notice of the impacted poles. Upon receiving notice of damage or of an outage reasonably likely to interrupt service, the utility or existing attacher may complete the remedial work and bill the new attacher for the reasonable costs related to fixing the damage, or it may require the new attacher to fix the damage at its expense immediately following that notice. The crew protects the facility and records what it observed. It does not decide liability. Work on that pole stops.
Capture the notice event with the pole evidence
A photograph in a group message can help explain a condition. It does not establish who received the required notice. We preserve the image beside delivery evidence and the pole identifier so the responding party can act while commercial responsibility waits. Speed matters here. A fast message with no recipient record is fragile evidence. We keep both.
The stop card is deliberately brief. It identifies the approved movement and the project contact, then leaves room for the observed condition and notification time so the supervisor can protect the pole and start escalation without inventing a design change. Design alternatives belong with engineering after the site is stable. The card does not ask a field lead to interpret an agreement while equipment is open or service is at risk. Keep the card short.
Stop-card rehearsal: before mobilization, the supervisor locates one approved pole identifier, describes the departure from simple work and sends the notice through the assigned channel. If that exercise exposes an outdated contact or an ambiguous movement, we move the date. Finding the defect in an office review is cheaper than discovering it on the structure.
The rehearsal is complete only when the same pole identifier appears in the approved movement, the field report and the delivered notice, so engineering can respond without first reconciling three versions of the location. An exception remains open until the appropriate party issues technical direction and the resulting work is documented. The record does not overwrite the first observation with a clean final photograph. It shows the original condition, the delivered notice, the direction and the correction as separate events. That history is what supports a later inspection response or reasonable-cost record. The first photograph stays.
Choose the next step from the inspection status
For an attacher with one utility: require a pole ledger that proves notice delivery and leaves the inspection horizon open until the utility acts or the period ends. Do not accept a route summary as a substitute for pole history. That buyer needs clean custody more than another schedule dashboard. We will not close on a percentage.
For a mixed simple and complex route: buy the operating discipline that keeps qualified poles moving while preserving the held pole's network effect and standard-process status. A provider that reports only OTMR production will hide the location most likely to control activation. Keep that gap on the release board. We will show it there.
For an overbuilder on a 2026 attachment schedule: let completion notice start the inspection clock pole by pole under current 47 CFR 1.1411(k)(5), and do not treat silence during the 90-day inspection opportunity as acceptance. The downstream splice plan should wait on inspection-open poles the same way it waits on held complex poles. We do not recommend a release that converts an open inspection into a claimed complete route.
Completion begins the last control period. Current 47 CFR 1.1411(k)(5) requires notice within 15 days after the work on a pole and gives the affected utility at least 90 days from receipt for inspection. If the utility or an existing attacher notifies the new attacher of damage or code violations and provides adequate documentation, that party may complete the remedial work and bill reasonable costs, or it may require the new attacher to fix the damage or code violations at its expense within 14 days following that notice. We therefore keep completed, inspection-open and remedied statuses distinct. Silence while the inspection opportunity remains open is not an acceptance event. Silence is not acceptance.
How OTMR pole attachment services close an inspected pole
Sampling starts with delivery proof. A reviewer picks one worked pole, confirms when completion notice reached the correct recipients and follows any supported finding into corrective action. The original evidence remains available after remedy. Route percentages can summarize volume. They cannot replace this pole history, because two neighboring structures may occupy different inspection states. Where inspection identifies work outside the approved movement, the correction record must preserve the first finding and the utility direction. The attacher can then explain why completion status changed after notice delivery.
The pole attachment application process guide shows why utility-specific workflow belongs beside the federal baseline. Draftech's in-house engineers own technical dispositions. When full turnkey make-ready construction is procured, the Draftech-managed subcontract crew model remains subject to the approved contractor pathway and utility operating requirements. Engineering remains in-house. Separately purchased construction is delivered through Draftech-managed subcontract crews under QA/QC and safety controls. The performing contractor stays visible in the field record.
Send the first unresolved notice or inspection event to the attachment team. If it controls the route, scope the work around that open pole rather than asking for a generic calendar. Bring the pole identifier. We will start with that pole.
