# Overbuild: Planning a Second Broadband Network in a Served Area

**Published:** November 16, 2026  
**Last updated:** November 16, 2026  

**Meta description:** Overbuild explained for broadband entrants: existing service, network differentiation, pole and duct access, and how BEAD and ReConnect eligibility differs.

By Omar Molina | November 12, 2026 | 11 min read

![A person seen from behind at an office desk highlights a route on a printed aerial map beside a monitor showing it.](/blog/img_overbuild.webp)

#### IN THIS ARTICLE

- [What overbuild means for a broadband entrant](#meaning)
- [Who pursues an overbuild, and why?](#entrants)
- [What changes for the entrant's route](#access)
- [How BEAD and ReConnect treat served locations](#funding)
- [Choose the next step for your overbuild](#decisions)

## What overbuild means for a broadband entrant

An overbuild is a second broadband network built where another provider already serves the same addresses, usually fiber passing copper, coax or older fiber. Existing service can vary widely: the FCC's 2024 Section 706 Report adopted a fixed broadband benchmark of 100 Mbps downstream and 20 Mbps upstream.

The addresses already have a choice. That changes the entrant's starting question from whether a connection exists to whether a different network offers something people will choose. An ISP planning new fiber needs a reason for subscribers to switch, while a cooperative may be responding to member needs that the existing service does not meet.

**Coverage alone leaves much unanswered.** A map can show service at a building without explaining the customer's experience inside it. Our starting point is the intended service area and the service the entrant wants to deliver there. Where the proposed advantage depends on upload performance, the design brief should say so explicitly rather than leaving the engineering team to infer it from the word fiber.

### Competition and eligibility answer different questions

The FCC benchmark provides useful context for the word broadband, but a funding program applies its own rules. The report, released March 18, 2024 as FCC 24-27, does not make every competing fiber proposal eligible for a grant. A privately financed entrant can evaluate a served neighborhood on its own merits. Public support needs a separate eligibility review.

Keep those decisions separate. For our engineering work, the practical benefit is a clear instruction about which addresses belong in the proposed network and which assumptions still need an owner decision. Otherwise, a footprint drawn for commercial expansion can quietly become the footprint used in a funding discussion, even though nobody has checked whether the locations qualify.

A route can also pass through a served area to reach a different destination. Passing a property does not necessarily mean the proposed network will offer it a connection. Our review therefore distinguishes the physical route from the intended service footprint. That distinction matters when a line on a map crosses a neighborhood that lies outside the owner's customer plan.

### Define what the entrant will offer

The service brief should describe the customer handoff. A household connection and a business connection may share part of the route while requiring different treatment at the premises. If building access remains unresolved, the address should retain that condition in the planning record; an attractive route past the front door does not settle how service reaches the tenant.

This is where our preference for address-level planning has a limitation: available records can still be wrong, and an orderly map can make uncertain information look settled. The remedy is to preserve the evidence behind the address and mark the unresolved condition. A blank field deserves attention. It should not silently become an affirmative answer.

## Who pursues an overbuild, and why?

An entrant needs a reason to build that survives comparison with the service already available. The FCC's 100/20 Mbps benchmark helps describe existing capability, but it cannot explain whether customers want a new provider. Our design discussion starts with that intended difference. The owner supplies the commercial case; engineering tests whether the proposed footprint can support it.

### ISPs compete on a defined service proposition

An ISP can pursue customers whose requirements differ from what the incumbent offers. For example, a business may value upload performance or a separate physical entrance more than a higher advertised download tier. Neither advantage follows automatically from installing fiber. The proposed service must be described clearly enough for our design team to identify what the route needs to support.

**Route diversity needs physical evidence.** A competing network could occupy the same corridor as the existing provider and share exposure to the same excavation or damaged structure, even though its ownership is different and its retail service is sold separately. Trace the actual paths. A second provider alone cannot establish that the customer's connection has an independent physical route.

The address list also needs to distinguish market interest from an instruction to serve. Our survey scope follows the owner's proposed footprint, so uncertainty about a building can affect which access questions get investigated. Keep a prospective extension visible without letting it appear as part of the committed design. This gives the owner a deliberate choice when the engineering information becomes available.

| Entrant | Reason to consider a build | Question to resolve first |
| --- | --- | --- |
| Independent ISP | A service proposition customers may prefer | What physical design supports that difference? |
| Cooperative | Member broadband needs | Which members and premises belong in the footprint? |
| Municipality | A defined public connectivity objective | Who owns the network and operates the service? |
| Utility | Communications infrastructure with a broadband role | Which facilities may support commercial access? |

### Cooperatives start with the member footprint

A cooperative's existing relationship with members can clarify why a competing network is being considered. It does not settle the broadband boundary. Some premises may sit beyond the proposed fiber route, and some structures on that route may belong to another owner. Our engineering scope needs the intended coverage boundary before an existing electric service territory becomes a presumed broadband service territory.

Member service remains the starting point. A cooperative should decide how to treat outlying premises before comparing route alternatives, because an option that omits those premises answers a different question from an option intended to reach them. Document that choice in the brief so the eventual design comparison reflects the same coverage obligation on both sides.

### Municipalities and utilities need a clear operating model

A municipality may want another retail choice or infrastructure that lets service providers reach residents. Ownership and operation must be explicit. The party that owns the fiber may differ from the party responsible for subscriber service, and that separation affects the handoff requirements our engineering team receives. A public objective becomes a usable design instruction only when someone defines who will operate what.

A utility considering broadband should distinguish operational communications from facilities intended to support a commercial network. Shared ownership does not remove the need to examine access rights. The useful input for us is the owner's approved use of the proposed facilities, with any restrictions carried into the survey scope rather than discovered after a route has become the preferred option.

HFC combines fiber with coaxial distribution toward subscribers, while FTTH extends fiber to the home. That architectural difference helps explain why an entrant may propose fiber beside an established cable network, but the incumbent's actual service remains the relevant comparison. The HFC-versus-FTTH article in Related Articles examines that choice in detail.

## What changes for the entrant's route

An occupied corridor requires fielding to establish what is present. Pole or duct access needs separate confirmation, and the proposed work needs permits. Under 47 U.S.C. 224, *Pole attachments*, federal access provisions have defined limits: cooperatively organized and government-owned utilities are excluded from its utility definition, and state regulation can displace FCC jurisdiction. Our route assessment must therefore identify the infrastructure owner and applicable rules before treating existing plant as usable.

### Resolve access before treating reuse as settled

The [fielding workflow for overbuilder projects](/blog/osp-fielding-for-overbuilder-projects) connects observed conditions to proposed reuse so our survey findings can distinguish a workable path from an assumption that still needs confirmation.

For covered poles, the FCC's 47 CFR 1.1411, *Timeline for access to utility poles*, sets conditional attachment clocks that must be checked against the applicable application and make-ready process, rather than treated as a promised project completion date.

The [HLD to LLD release for competitive areas](/blog/osp-detailed-design-for-overbuilder-competition-areas) should carry the accepted route and unresolved access conditions into detailed design so our drawings do not conceal a dependency behind finished linework.

**Keep conditional access visible.** A route option that relies on another owner's facility should retain that dependency in its label until the relevant access question has been resolved.

These questions belong together. Our [ISP network engineering services](/services/isp-network-engineering) cover survey, HLD and LLD, permit drawings, pole loading and utility coordination. The point is to give the entrant a consistent engineering basis for choosing a route, with unresolved access carried forward where the next person reviewing the drawing can see it.

## How BEAD and ReConnect treat served locations

Funding eligibility depends on the program and the location evidence. NTIA's BEAD framework distinguishes unserved locations lacking qualifying 25/3 Mbps service from underserved locations lacking qualifying 100/20 Mbps service. Its BEAD Restructuring Policy Notice, issued June 6, 2025, changed program requirements, including technology treatment. An existing network therefore does not, by itself, answer whether a location remains eligible.

### BEAD follows the program's eligible locations

The relevant starting point is the administering broadband office's current eligible-location record and applicable award requirements. A location with qualifying served status is ordinarily outside BEAD deployment funding for unserved or underserved locations. The commercial appeal of a fiber competitor does not change that classification. Our recommendation is to settle the eligible footprint before asking a design to satisfy both a grant boundary and a broader market plan.

Check the location identity. An address string and a mapped building can appear to describe the same place while referring to different records, particularly where a property contains multiple premises or the address has changed. Our engineering brief should identify which location record controls the proposed footprint and who will resolve a disagreement, instead of letting each drawing revision inherit a different interpretation.

Our [BEAD challenge-process mapping guide](/blog/bead-challenge-process-mapping) explains how location evidence and challenge outcomes should remain traceable when the program's records and the proposed route are reconciled.

**A served crossing needs its own explanation.** A line that traverses an area on the way to eligible premises raises a different question from a proposal to fund new service at every property along that line. The applicant should resolve that treatment with the administering office. Keep the physical connection and the funded service obligation distinguishable in the proposal.

**Record the map version.** Retain the date and source of the eligibility layer used for a route decision, so a changed location status can be traced to the affected design.

### ReConnect uses its own area test

USDA's ReConnect service-area guidance states that at least 90% of households in the proposed funded service area must lack sufficient broadband access, with the applicable funding notice defining that term. For the Round 5 notice published February 21, 2024, USDA used 25 Mbps downstream and 3 Mbps upstream for sufficient access. That is a round-specific rule, not a universal definition of an acceptable overbuild.

The same Round 5 material requires the proposed network to support 100 Mbps symmetrical service to every premises in the funded area simultaneously. Existing-service eligibility and proposed-network capability are separate tests. USDA also applies rural-area and protected-service-area requirements. A household percentage alone cannot establish that an application qualifies, so applicants must use the governing notice for the round they pursue.

Do not transfer a BEAD classification into a ReConnect application by changing the label. The unit being assessed and the governing evidence can differ. Our engineering input begins with the footprint the applicant has established under the relevant program; a commercial expansion outside that footprint should remain identifiable as a separate owner decision.

### Make the funding assumption visible to the owner

A blended route can be technically sensible while containing different funding assumptions. The owner needs to know which segment depends on an award and which portion belongs to the broader competitive plan. That distinction lets our route work remain useful if the funded boundary changes. Without it, an eligibility revision can look like an unexplained engineering change.

Uncertainty should have an owner. Identify the person responsible for resolving a disputed location and record the decision with the supporting evidence, so the next design review can distinguish an open question from a change that has already been accepted. A clean drawing helps people understand a route. It cannot supply the missing eligibility determination.

## Choose the next step for your overbuild

**Independent ISPs:** Define the customer advantage before commissioning a detailed route. Where the proposition includes physically separate connectivity, request evidence of that separation rather than treating another provider name as sufficient. Give our engineers the intended handoff and a settled service boundary so the proposed route can be assessed against the actual service being offered.

**Cooperatives:** Confirm the member coverage obligation before selecting the preferred route. Keep premises beyond the initial footprint visible as explicit decisions, and identify facilities whose ownership differs from the cooperative's own system. This avoids comparing alternatives that appear equivalent only because their coverage assumptions differ. The member boundary should lead the engineering brief.

**Municipalities:** Establish the ownership and operating model before the network layout becomes detailed. A plan for retail service and a plan for infrastructure used by outside providers can require different handoffs. Assign responsibility for those interfaces in the brief. That gives our design team an operating requirement instead of a general instruction to increase competition.

**Utilities:** Confirm which facilities may support the broadband proposal and carry their use restrictions into route selection. Operational infrastructure can offer a starting point, but the commercial service boundary still needs an owner decision. Where a proposal relies on public funding, establish the eligible footprint separately before combining it with the utility's wider communications objectives.

The first discussion with us should center on the proposed footprint and the decisions still open. Existing drawings can help explain the intent even when they are incomplete. Mark their uncertainty. The [Draftech partner profiles](/about) identify the people behind our work, and the [contact page](/contact) provides a direct way to describe the route and its access questions, or email us at [info@draftech.com](mailto:info@draftech.com).

Draftech International's engineering is 100% in-house. Our survey and design work connects the proposed customer footprint to the physical route, with permit drawings and utility coordination addressing the access dependencies that otherwise remain buried in a planning map. The useful next deliverable is a route the owner can evaluate with its unresolved conditions in view.

For an entrant ready to examine a candidate route, our [free-design offer](/free-design) covers the first 20,000 linear feet of a qualifying route at no cost, from feasibility and field survey through permit approval. The owner reviews each request before Draftech commits the package. Bring the proposed service boundary and the access questions that could change it.

## Frequently Asked Questions

### Does overbuild mean the existing broadband network is removed?

No. A competitive overbuild adds another network serving addresses where a provider already operates, so removal of the incumbent network is not implied. Our planning distinguishes that competitive entry from an owner replacing its own plant. The FCC's 100/20 Mbps benchmark describes broadband capability; it does not tell the entrant whether existing facilities will remain or become available for reuse.

### Can an overbuild qualify for BEAD funding?

The word overbuild cannot establish eligibility by itself. NTIA's framework uses qualifying-service thresholds of 25/3 Mbps and 100/20 Mbps, and the administering office's eligible-location records determine which premises remain in the deployment footprint. Our recommendation is to resolve that footprint before detailed route design, with any proposed commercial expansion identified separately from the locations covered by the funding decision.

### Does ReConnect use the same served-area rules as BEAD?

No. USDA's published service-area guidance applies a 90% household test for lack of sufficient access, and the governing funding notice supplies the applicable definition and other conditions. Round 5 used 25/3 Mbps for sufficient access. Our advice is to verify the relevant round before carrying a BEAD location classification into a ReConnect proposal or treating a whole route as eligible.

### Can a new entrant use poles that already carry broadband?

Existing attachments do not establish the entrant's permission or the structure's ability to support another attachment. Federal access provisions under 47 U.S.C. 224 have jurisdictional and ownership limits, and state rules can govern instead. Our route review therefore separates observed facilities from confirmed access, with the infrastructure owner and applicable process identified before reuse becomes a settled design assumption.

### What does Draftech need to review a proposed overbuild?

Start with the intended service footprint and available route information, identifying access questions that remain unresolved. Our engineering is 100% in-house and covers survey, HLD and LLD, permit drawings, pole loading and utility coordination. Draftech's free-design offer concerns the first 20,000 linear feet of a qualifying route, from feasibility and field survey through permit approval, subject to owner review before commitment.
