# OSP Detailed Design for Overbuilder Competition Areas: HLD to LLD Release

**Title tag:** OSP Detailed Design for Overbuilder Competition Areas 2026  
**Meta description:** OSP detailed design for overbuilder competition areas: serving areas, nodes, fiber assignments, make-ready states, and LLD release. Fabric stays challengeable.  
**Author:** Julio Martinez  
**Published:** October 8, 2026  
**Last updated:** October 8, 2026  
**Category:** ISP & Carrier Networks / Data Center  
**URL:** https://draftech.com/blog/osp-detailed-design-for-overbuilder-competition-areas  
**Primary keyword:** osp detailed design for overbuilder competition areas  
**Word count:** 2729  
**Read time:** 11 minutes

![Person seen from behind in a dark shirt drafts on a large plan sheet with a pencil and scale ruler at an office desk.](../../blog/img_osp_detailed_design_for_overbuilder_competition_areas.webp)

---

A competitive overbuild often arrives as a painted service area. The marketing map already has a fill color. The National Broadband Map already shows someone else's claimed availability. Neither layer is a construction baseline. Neither one names who can grant an attachment or a duct.

We convert a documented overbuild boundary and verified access evidence into HLD-to-LLD objects the operator can freeze. Serving areas and nodes get a named owner. Cable counts and fiber assignments wait on that same evidence. Alternate corridors stay in the package until the preferred path has authority behind it. A launch calendar is not one of those objects.

## What OSP Detailed Design for Overbuilder Competition Areas Must Freeze

**OSP detailed design for overbuilder competition areas** converts a documented competitive boundary and verified access evidence into controlled HLD-to-LLD objects. The Broadband DATA Act, Public Law 116-130, enacted March 23, 2020, requires location-specific availability reporting. That reporting is not proof of demand, constructability, ownership, spare capacity, attachment rights or competitor geometry.

The working file has to show which segments still depend on somebody else's pole or conduit. Verified access evidence arrives from [OSP fielding for overbuilder projects](/blog/osp-fielding-for-overbuilder-projects). Photographs without an owner process stay tagged as field proof. We will not promote them into an issued LLD sheet because a scheduler needs a date.

DA 26-630, released June 26, 2026 by the Broadband Data Task Force and the Office of Economics and Analytics, opened the Broadband Data Collection filing window on July 1, 2026 for data as of June 30, 2026. It also set September 1, 2026 as the Fabric-challenge deadline for the December 2026 Fabric. Those are map-revision clocks. They are not attachment grants.

### Reconcile FCC Availability Without Treating It as Plant

Licensed Fabric locations are a location inventory. They tell us which structures the current vintage treats as broadband serviceable. They do not tell us who owns the pole in front of that structure. They do not tell us whether a duct has spare capacity. A mid-size ISP in the Southeast can hold a Fabric extract covering an entire tract while the pole owner has not accepted a Regular Order on the lesser of 300 poles or 0.5 percent of that utility's poles in the state.

We date the Fabric vintage in the design record. Then we reconcile those points with lawful operator inputs. The operator's approved service objective and the locations it is authorized to serve have to match the plant it already owns or has a right to occupy. Where they disagree, both stay in the file. The disagreement is the design problem. Hiding it inside a green overlay is how LLD gets issued against a path nobody can attach.

The Commission's fixed availability challenge process gives a challenged provider 60 days to accept or deny after notification. That process can change what the National Broadband Map shows. It cannot change who owns a pole. We treat availability as reported and challengeable, then we design against access evidence.

> **Keep the map in its lane:** a Fabric point is a location record. Write the vintage on it. Do not let it vote on cable count or on an attachment right.

The limitation of our preferred freeze method is that it looks slower than a painted polygon. We used to let a Fabric export paint serving areas before access evidence existed. That produced LLD sheets that could not attach. We stopped doing it.

## Convert Boundary Evidence into Serving Areas and Nodes

HLD may arrive with a service-area blob and a handful of candidate nodes. LLD has to name the serving area that a specific cable and a specific node actually feed. The overbuild boundary is an input. It is not the serving-area geometry. If the operator's authorized footprint is smaller than the marketing fill, the design follows the authorized footprint. If access evidence cuts a hole in that footprint, the serving area follows the hole until an alternate corridor closes it.

Node placement follows the same rule. A cabinet or splice node that sits on a pole line the owner has not accepted is a candidate, not a baseline. We will relocate it before we will issue an LLD sheet that pretends the approach is settled. One thing I still catch in our own first-pass packages is a node that looks clean on the HLD because the fiber assignment still points at a duct nobody opened.

### Make Each HLD Object Earn an LLD State

**Table: Overbuilder HLD-to-LLD decision map**

| Decision object | HLD input | LLD evidence | Release state |
| --- | --- | --- | --- |
| Serving area | Documented overbuild boundary and operator service objective | Fabric locations reconciled with lawful operator inputs | Freeze, hold, or redraw |
| Node | Candidate hub, cabinet, or splice node | Access path and fiber assignment on the approach | Place, relocate, or defer |
| Cable count | Planning count by layer | Count tied to assigned fibers and a named spare pool | Freeze count or return to HLD |
| Fiber assignment | Intended working and reserved fibers | Cable ID, tube, fiber, splice path, and endpoint | Assign, reserve, or withhold |
| Alternate corridor | Second path parked at HLD | Authority evidence on the preferred path | Keep, drop, or promote |
| Pole or conduit ownership | Named owner and coverage call | Attachment or occupancy process record | Apply, reroute, or hold |
| Make-ready state | Screening quantity from fielding | Owner estimate and current process step | Screen, wait, or reroute |
| Permit state | Jurisdiction list | Application identity and current agency state | Package, hold, or redesign |

Usable is too coarse a status here too. A serving area can be geometrically complete while the node that would feed it still sits on an unauthorized approach. A cable count can be frozen while no fiber has an endpoint. The table buys the next permitted action against a named missing authority. One blended confidence color across those objects will never do that, because a node waiting on a duct key and a permit waiting on a county completeness letter are not the same kind of not-yet.

### Cable Counts and Fiber Assignments Stay Named Objects

Planning counts belong at HLD. LLD has to assign fibers. Cable ID, tube, fiber number, splice path, and endpoint have to survive from the schedule into the issued sheet. A reserved fiber that cannot name its cable is not reserved. It is a hope. We withhold assignment rather than invent a path through plant the owner has not opened.

If the competitive area sits on an incumbent copper footprint, the overlay sequence belongs to [copper-to-fiber migration engineering](/blog/copper-to-fiber-migration-engineering). This page does not own cutover. It owns whether a fiber in the overbuild cable is allowed to occupy the corridor the overlay would use. Where the two programs share a pole or a duct, both records have to name that dependency. Silence is not coordination.

## Keep Pole and Conduit Ownership Inside the Clock That Binds

47 U.S.C. 224, Pole Attachments, is the statute in force. Subsection (a)(1) excludes any person who is cooperatively organized, and any person owned by the Federal Government or any State, from the definition of utility. We identify the owner before we cite a federal timeline, because a clock filed against an owner it does not bind burns the only calendar the launch team thought it still had.

For owners the statute actually reaches, 47 CFR 1.1411, Timeline for access to utility poles, currently in the eCFR as of September 14, 2026, sets the access process. The Paperwork Reduction Act amendments adopted in the Fifth Report and Order, FCC 25-38, published at 90 FR 41726 on August 26, 2025, became effective May 7, 2026 under DA 26-446. Those amendments added defined Large Order timelines. They did not make the statute cover a cooperative pole.

A Regular Order, currently up to the lesser of 300 poles or 0.5 percent of the utility's poles in a state, still gives a covered utility 45 days after a complete application to complete the survey. We use that number as a process date. We do not use it as a construction start. Order size is checked after owner coverage, never before. Filing a Large Order clock against a municipal system is the same error as filing a Regular Order clock against it. The statute never attached.

### Make-Ready and Permit States Are Not Construction Dates

IEEE C2-2023, the 2023 National Electrical Safety Code, took effect on February 1, 2023 and is the loading and clearance edition we design to unless the pole owner specifies another accepted edition in writing. Make-ready itself is construction the pole owner controls. A fielding quantity is a screen until the owner's process produces the controlling estimate. We will not freeze an LLD hang count on a screening number.

Permit state is equally specific. A jurisdiction list is HLD. LLD needs the application identity and the current agency state for the segment being released. A neighboring segment with an approved encroachment does not lend that approval across a county line. Corridor comparison that selected those segments lives in our [fiber route analysis guide](/blog/fiber-route-analysis). We consume the selected corridor and the parked alternate. We do not rerun that comparison here.

Underground reuse has the same ownership test with a harder visibility limit. Continuity and usable capacity stay behind the vault wall until the owner provides access and a written capacity confirmation. A locked lid is not capacity. The alternate new-build alignment stays alive until that writing exists.

## Hold Alternate Corridors Until a Segment Earns Release

A competitive overbuild dies when the last remaining alignment is the one that still needs a third-party yes. We keep a second path in the LLD package until the first path has authority evidence, not just a cleaner lineweight. Dropping the spare so the issued set looks simpler is an irreversible act. So is ordering cable against a reuse claim that still lacks an owner letter.

We date each dependency from the next irreversible act, not from the date the GIS status turned green. Status dates lie. Decision dates do not. A pole marked in process in a tracker can still be several owner steps from an attachable state. The remaining steps are the real calendar, and they belong on the LLD cover sheet so a later designer cannot read a yellow icon as a notice to proceed.

> **Two corridors until one is authorized:** LLD that drops the spare to look finished is not finished. It is exposed. Keep the second path until the owner has spoken.

### Where OSP Detailed Design for Overbuilder Competition Areas Stops

This page owns competitive-area architecture and LLD release only. It does not walk the plant. Corridor scoring lives elsewhere. Copper migration is a different record. Mixing those jobs here is how a field photo becomes a serving-area freeze. The release package has to show the proven segments and the remaining dependencies. The surviving alternate stays written beside them. If those statements are missing, we do not release.

We also attach the NESC edition basis and the owner-coverage call on section 224, because a later designer who inherits only the green overlay will assume both were settled. They have to be written and dated. A coverage call that says "not 224" is a complete answer. It routes the segment to the owner's own process. It is not a defect in the federal clock.

## How to Choose an Overbuilder LLD Release

**Aerial-heavy competitive overbuild on investor-owned poles:** do not freeze attachment geometry until owner identity and the applicable section 224 coverage are in the record. Sight of open communication space is a screen, not access. Run loading against IEEE C2-2023 unless the pole owner has named another accepted edition in writing, and treat the 45-day 1.1411 survey clock as a process date rather than as a field measurement. Keep the spare corridor until that process has spoken.

**Overbuild on cooperative or municipal poles:** do not file a federal 1.1411 timeline against an owner that section 224 does not bind. Identify the owner's own attachment process first, then size LLD to the evidence that process actually consumes. A photograph of crowded attachments still does not authorize an attach. The spare alignment stays alive until that owner has spoken.

**Duct-reuse overbuild:** do not baseline capacity from a lid photo. Continuity plus ownership plus written capacity have to exist before the underground option displaces a new-build alternate. Fiber assignment through that duct waits on the same writing. A locked vault is not a path.

If the next irreversible act is a cable order or a node pad, that act still has to wait on whoever owns the pole or the duct, because a Regular Order clock filed against the wrong owner does not move a pad or a reel. Our [ISP network engineering service](/services/isp-network-engineering) writes the owner-coverage call onto the same revision as the current permit identity before that order goes out. The [Draftech partner team](/about) is accountable for that record. Active in 24 states. Available across all 50 U.S. states. Where an owner also buys construction, Draftech delivers full turnkey work through Draftech-managed subcontract crews under our QA/QC and safety program. Engineering stays inside the firm either way.

If osp detailed design for overbuilder competition areas 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](/free-design). The owner reviews each request before Draftech commits the package.
> **Stop the cable order if the owner still owns the clock.** [Talk to our OSP team about an overbuild package with mixed pole and duct ownership](/#dt-contact).

Send the owner-coverage call with the 1.1411 applicability note, then add the current permit identity and the fielding dependency map. Mail that package to [info@draftech.com](mailto:info@draftech.com?subject=Overbuilder%20LLD%20release). We will mark which of those acts still sit on someone else's process. Do that before the reel ships.

## Frequently Asked Questions

### Does FCC availability prove an overbuild LLD can be released?

No. FCC availability is provider-reported and challengeable. The Broadband DATA Act, Public Law 116-130, enacted March 23, 2020, requires location-specific reporting overlaid on the Fabric. A licensed Fabric location is a serviceable-location record. It is not a pole, a duct, spare capacity, or an attachment right. We will not release a competitive-area LLD sheet from a green map polygon.

### Does 47 CFR 1.1411 apply to every pole owner in an overbuild?

No. 47 U.S.C. 224, Pole Attachments, excludes cooperatively organized persons and persons owned by the Federal Government or any State from the definition of utility. 47 CFR 1.1411 is the Timeline for access to utility poles under that statute. A Regular Order, currently up to the lesser of 300 poles or 0.5 percent of a covered utility's poles in a state, has a 45-day survey clock after a complete application.

### When can a competitive-area segment be released?

A segment is released when geometry and fiber assignment point at the same revision. Ownership, make-ready, and permit state for that segment have to be written. Keep at least 2 corridors until the preferred path has authority evidence. We do not release on a marketing fill or on a Fabric export. The package names what is still held.

### How should Fabric locations enter serving-area design?

Licensed Fabric locations enter as a location inventory, dated to the Fabric vintage the operator is licensed to use. DA 26-630, released June 26, 2026, identified the June 2026 Fabric for the as-of June 30, 2026 Broadband Data Collection. Reconcile those locations with lawful operator inputs. Do not treat a Fabric point as demand or as competitor plant.

### What stays outside this design package?

This page owns competitive-area architecture and LLD release only. Field proof of reuse belongs to OSP fielding for overbuilder projects. Corridor comparison belongs to fiber route analysis. Copper overlay and cutover belong to copper-to-fiber migration engineering. Take rate, return on investment, a launch week, and competitive superiority are not design outputs. We do not restate those jobs here.

### Who has to speak before a pole or duct enters the LLD baseline?

The facility owner. Sight of open communication space is a screen. A lid photo is a clue. 47 CFR 1.1411 sets the access clock only for owners that 47 U.S.C. 224 actually covers, and only after we identify that owner. IEEE C2-2023 took effect on February 1, 2023 and is the loading edition we design to unless the pole owner names another accepted edition in writing.