# Fiber Network HLD for USDA ReConnect Projects: Maps, Costs, and Design Review
**Title tag:** Fiber Network HLD for USDA ReConnect Projects 2026
**Meta description:** Fiber network HLD for USDA ReConnect projects: service area mapping, cost basis, design narratives, PE review, and application-to-award engineering handoffs.
**Author:** [Ashish Kumar Meena](/authors/ashish-kumar-meena)
**Published:** September 30, 2026
**Last updated:** September 30, 2026
**Category:** BEAD & Broadband Grants
**Reading time:** 11 minutes
IN THIS ARTICLE
- [Fiber Network HLD for USDA ReConnect Projects: Define the Scope](#hld-scope)
- [Make the Service-Area Map Explain the Build](#service-area)
- [Build the Estimate from the Mapped Scope](#cost-basis)
- [Prepare the Schedule and PE Review Together](#review-package)
- [Fiber Network HLD for USDA ReConnect Projects: Choose the Next Step](#owner-decision)
A fiber route can look settled on a map while the funding package still describes a different build. A boundary moves, but its remote premises remain in the estimate. An aerial segment becomes buried, yet the schedule still assumes attachment access. We treat those differences as engineering decisions that must be resolved before the application is assembled.
This guide covers the high-level design work behind a ReConnect network submission and the baseline an awardee should preserve afterward. We focus on service-area mapping and the cost basis, then explain how the narrative should connect them. USDA's ReConnect Loan and Grant Program page lists the application window as closed as of September 24, 2026. Planning work does not establish an open funding opportunity.
## Fiber Network HLD for USDA ReConnect Projects: Define the Scope
Fiber network HLD for USDA ReConnect projects is the planning design that connects a proposed funded service area to a technically feasible fiber build and defensible estimate. Under 7 CFR 1740.64, the network submission includes a capital investment schedule supporting construction within five years, with professional engineer certification of the required design materials.
**HLD is a working design stage.** Calling a package an HLD does not establish that it satisfies USDA's submission requirements. We use the term to describe the point where the architecture is developed enough to explain its physical route and support estimating. The required application materials still have to answer the agency's questions in their own right.
### Start with the RUS requirement
The Rural Utilities Service (RUS), within USDA, evaluates technical feasibility. Its Rural eConnectivity Program regulation, 7 CFR Part 1740, January 1, 2025 edition, addresses network design in section 1740.64. The agency's 2026 regulatory agenda also lists an update to Part 1740 under RIN 0572-AC69. An agenda entry is not an effective amendment; use the applicable funding notice and executed award to establish the project's controlling requirements.
For our engineering review, the key distinction is between a proposed corridor and a serviceable network. A corridor identifies where cable might run. A network design explains how the proposed equipment serves the premises assigned to that corridor, including the connection back to transport. If that connection depends on another party's plant, we want the dependency visible before the estimate becomes a funding request.
Keep the funding programs separate. Our discussion of [HLD requirements for BEAD subgrantees](/blog/fiber-network-hld-bead-subgrantee-requirements) addresses a different program context. Reusing geographic data can save work, but carrying over a BEAD submission checklist without checking the ReConnect instructions creates an avoidable mismatch. The same route can need different explanations for different reviewers.
### Set a practical limit on design maturity
We do not recommend paying for every construction detail before the service area is stable. Nor do we recommend pricing an entire network from an untested line on a basemap. Our preferred HLD approach has a weakness: clean GIS geometry can make uncertain access look resolved. We counter that by marking the underlying evidence and keeping unresolved corridors identifiable in the estimate.
A useful scope tells the owner what will be verified in the field and what remains a planning assumption. Where an attachment route depends on make-ready, the estimate needs to recognize that dependency even if the final pole analysis belongs to a later design task. For buried segments, the proposed method must fit the corridor well enough to support a credible quantity basis.
**Release status matters.** We label the HLD for its intended use and distinguish it from drawings released for construction. That prevents an estimator's route alternative from becoming a field instruction simply because it appears in the latest folder. The owner should be able to identify the accepted planning alternative without asking which designer last exported the map.
The following comparison describes the engineering package we recommend organizing around the application. It is not a USDA form list or a universal naming standard. Each component answers a different question, and the sections below explain the cross-checks that make the components useful together.
| HLD component | Application question | Engineering cross-check |
| --- | --- | --- |
| Service-area map | Which premises does the proposal cover? | Reconcile the boundary with the premises register. |
| Network narrative and diagram | How will the proposed fiber system deliver service? | Trace remote premises to the proposed serving equipment. |
| Quantity and cost basis | What physical scope supports the capital request? | Connect estimate quantities to mapped route segments. |
| Schedule and certification package | Can the proposed system be delivered as described? | Give the PE consistent design materials and stated dependencies. |
## Make the Service-Area Map Explain the Build
The proposed funded service area (PFSA) establishes the geography being presented for funding, and we keep its boundary separate from the cable centerline because those features describe different things. A route may pass through an area without making every nearby premises part of the proposal. Conversely, a premises inside the polygon still needs a plausible service path.
### Reconcile premises before polishing the map
USDA's ReConnect Service Area Map is an eligibility planning aid. We use agency mapping information as a starting point for review, while preserving its source and retrieval date in the project records. A screenshot cannot explain an inclusion. The engineering dataset should retain the relationship between each premises and the boundary used for the application.
We recommend a premises exception register for locations that do not match cleanly. A driveway entrance can sit outside the mapped parcel frontage, or an address point can fall on the wrong side of a road. Resolve the proposed connection against the actual approach to the structure. Do not let a convenient geocode decide which side of a crossing the estimate assumes.
The boundary review should also distinguish existing plant from proposed facilities so the owner can see where the project depends on capacity already in service and where new investment is required. If the map borrows a transport path outside the PFSA, explain that path's role and the basis for using it. Proximity to fiber does not establish available capacity.
### Keep the design narrative tied to the diagram
Explain the mapped architecture. We recommend using the same equipment identifiers in both, so a reader can follow a serving area back to its aggregation point without translating between naming systems. Describe the assumed service configuration at the remote end of the network, where reach or capacity can become the controlling design condition.
A statement about a product's advertised capability is not a network capacity assessment. We check the proposed configuration against the demand assumptions and the physical route, including any shared upstream constraint. The [difference between HLD and LLD fiber design](/blog/difference-between-hld-and-lld-fiber-design) matters here: the planning package needs a defensible architecture even though final splice assignments may come later.
We would reject a narrative that promises an alternate path while the diagram shows only a common corridor. That is a design claim, not a wording issue. Explain the actual arrangement and identify the limitation. The owner can then decide whether resilience improvements belong in the funded scope or in a separately supported expansion.
## Build the Estimate from the Mapped Scope
A cost total is only as useful as the quantities behind it. We start the estimate review at route-segment level and ask which design revision produced the measured length. Keep aerial and buried assumptions distinguishable. When the installation method changes, the estimate needs a traceable explanation of the affected scope rather than an unexplained adjustment to the grand total.
### Separate route length from material quantity
Route length is not cable quantity. Slack and vertical transitions can change cable requirements without extending the mapped corridor, while parallel facilities can make several material quantities depend on the same route segment. We recommend documenting those estimating rules explicitly so a reviewer can reproduce the quantity without having to assume that the map itself contains every allowance needed for construction.
Shared infrastructure deserves particular attention when several serving areas use a common feeder. Count the physical asset once in the project estimate and explain how its cost is allocated where the application requires a breakdown. Otherwise, separate area worksheets can each appear reasonable while the combined request pays for the same asset repeatedly.
**Cost support should be dated.** A supplier quotation should identify what it covers and remain distinguishable from an engineer's allowance for unresolved work. We ask the estimator to preserve that distinction through revisions. A new total cannot be evaluated sensibly if the owner cannot tell whether its increase came from more route or from a changed pricing assumption.
### Expose access assumptions that can move the budget
An aerial estimate that assumes usable attachment space needs a clear path to confirming that assumption. Underground alternatives also need enough investigation to identify major route constraints. We recommend assigning unresolved work to the person who can close it, with its effect on the estimate stated in plain language. The absence of a completed investigation is not evidence of a low-cost condition.
For owners coordinating the application with engineering, our [broadband grant engineering support](/services/bead-broadband-engineering/) connects the funding narrative to the route quantities. We keep that coordination within the design scope instead of asking the grant writer to infer construction methods from a GIS export. The financial model still belongs with the applicant's financial team; engineering supplies the physical basis it can test.
**Review the changed segment first.** When an access problem forces a reroute, compare the replacement corridor against the original estimate before accepting the revised project total. A cost difference is easier to explain when it remains attached to the design decision that caused it.
## Prepare the Schedule and PE Review Together
The build sequence needs to match the way service becomes available, so we work backward from the proposed operating network to identify which dependency controls each phase. A distribution area cannot enter service merely because its local cable is installed if its upstream connection is still unresolved. The schedule should make that relationship obvious to the owner and the certifying engineer.
### Give the certifying engineer a consistent package
Section 1740.64 requires certification by a professional engineer certified in at least one state where project construction occurs. The certification must address delivery to every premises in the PFSA at the required minimum service level. The submission also identifies required regulatory approvals and reliance on contractors or vendors. We recommend bringing the engineer into scope development early, so certification review tests the design decisions rather than discovering them after the application narrative is complete.
For that review, we would present the selected route and the matching estimate revision together. Open assumptions should remain visible. If a cost allowance depends on an access agreement that has not been secured, the reviewer needs to know that condition before judging feasibility. Replacing the assumption with a confident sentence does not improve the underlying design.
Match spending to the build sequence. We check whether spending assigned to a phase corresponds to the facilities needed for that phase to operate, particularly where a common feeder supports later distribution work. This is where the engineering schedule and financial model need an actual reconciliation instead of matching totals pasted into separate documents.
### Carry the accepted baseline into the award
After award, preserve the submitted design package and distinguish it from the evolving working design. We recommend recording the reason for each material route change and identifying which application assumptions it affects. The awardee should confirm the required agency action under its award before treating a changed scope as accepted. Engineering revision approval and agency concurrence serve different purposes.
That baseline supports later records without turning an HLD into a reporting instrument. Our guide to [USDA ReConnect construction progress reporting](/blog/usda-reconnect-construction-progress-reporting) addresses the reporting stage separately. Here, the handoff is the connection between what the application proposed and what the detailed design now intends to build. Preserve both versions when they differ.
## Fiber Network HLD for USDA ReConnect Projects: Choose the Next Step
**For a cooperative evaluating a future application:** settle the proposed service boundary before commissioning detailed route sheets. Put engineering effort into remote premises and uncertain corridors first, because those locations can change the scope the board is being asked to fund. Keep the planning schedule separate from any assumption about when USDA will open another application window.
**For an ISP preparing its network submission:** require a reconciliation between the diagram and the estimate before the PE review. Assign a person to resolve each mismatch. A polished narrative will not compensate for a feeder omitted from the budget, and the engineer should not have to guess which file represents the applicant's final proposal.
**For an awardee entering detailed design:** compare new field information with the accepted application baseline before releasing the affected work. Retain the original scope and explain the proposed change's effect on service. This gives the award administrator something concrete to review while the design team develops the replacement corridor.
**[Discuss your ReConnect design package with Draftech.](/#dt-contact)** Bring the proposed service-area map and the current estimate so the scope discussion starts with the physical network the funding request is meant to support.
When the application map and budget describe different builds, Draftech's [engineering and construction services](/services) connect the route decisions to delivery. Our engineering is 100% in-house, and full turnkey construction is delivered by Draftech-managed subcontract crews. Active in 24 states. Available across all 50 U.S. states. Send scope questions to [info@draftech.com](mailto:info@draftech.com).
If your proposed ReConnect route needs its planning assumptions worked through, consider [Draftech's free design offer](/free-design): Draftech engineers 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.
## Frequently Asked Questions
### Does a ReConnect HLD replace the required network design submission?
No. HLD describes a design stage, while 7 CFR 1740.64 specifies network design submission requirements. We recommend checking the actual package against the applicable application instructions rather than relying on its title. A usable HLD supports the submission by explaining the proposed network and its cost basis, but the applicant still needs the required certification and supporting materials.
### How detailed should the fiber route be before estimating?
The route needs enough definition to support its quantities and construction assumptions. The five-year capital schedule in section 1740.64 does not prescribe a universal drawing scale or make a preliminary corridor construction-ready. We recommend identifying uncertain segments separately so the estimate shows where additional fieldwork could change the selected method or the physical scope before the package is finalized.
### Who certifies the ReConnect network design?
Section 1740.64 calls for a professional engineer certified in at least one state where project construction occurs. Bring that engineer into the review while route assumptions can still be examined and corrected. We recommend providing a consistent design revision with its matching cost basis, so certification is grounded in the proposed system rather than a collection of independently updated files.
### Can an awardee replace the application HLD when field conditions change?
Keep the original and issue a traceable revision. The network design addressed by 7 CFR 1740.64 establishes application assumptions that later fieldwork may change, but an engineering edit does not itself establish agency acceptance. The awardee should confirm what action its award requires and preserve the comparison so reviewers can understand the effect on the proposed service and cost.
### Is the free design offer automatic for a ReConnect applicant?
No. Draftech engineers the first 20,000 linear feet of a qualifying route at no cost, from feasibility and field survey through permit approval, and the owner reviews each request before Draftech commits the package. A ReConnect funding plan does not establish qualification by itself. Submit the route for review so the engineering scope can be evaluated against the offer.
## About the Author
[Ashish Kumar Meena](/authors/ashish-kumar-meena), Managing Director & Partner, Draftech International. Leads BEAD engineering, GIS documentation, HLD deliverables, and broadband compliance programs. [info@draftech.com](mailto:info@draftech.com)
## Related Articles
- [BEAD Funding Engineering Requirements](/blog/bead-funding-engineering-requirements-2026)
- [BEAD GIS Deliverables: A 2026 Engineering and Records Guide](/blog/bead-gis-deliverables)
- [BEAD Compliance Documentation Requirements](/blog/bead-compliance-documentation-requirements)
- [BEAD PE Certification Requirements](/blog/bead-pe-certification-requirements)
- [7 Ways BEAD Projects Stall Before Construction Starts](/blog/bead-projects-stall-before-construction)
- [Fiber As-Built Services for Grant Compliance](/blog/fiber-as-built-services-for-grant-compliance)