7 Ways BEAD Projects Stall Before Construction Starts

I've been doing OSP engineering for 17 years. I've watched fiber deployments of all sizes move from award to ribbon-cutting without a single unexpected delay. I've also watched well-funded BEAD subgrantees burn through 8 to 12 months of their project timeline before a single strand of fiber touched a conduit. The difference between those two outcomes is almost never money. It's almost always a set of pre-construction problems that were predictable — and that didn't get addressed because no one was tracking them early enough.

BEAD is not a typical commercial fiber build. The NTIA's grant structure, the state broadband office oversight, the environmental review obligations, and the documentation requirements create a project environment that punishes reactive engineering harder than any commercial deployment I've managed. By the time construction stalls, the subgrantee is already 90 days late — and the root cause was something that could have been caught in week three of HLD.

What follows are the seven stall patterns I see most often on BEAD OSP engineering projects. Not in any particular order of frequency — honestly, they tend to hit in clusters. But each one is real, each one is fixable, and each one starts doing damage well before the construction crew ever shows up.

1. Incomplete or Disputed Location Fabric Data

The NTIA Location Fabric is the foundation of every BEAD subgrantee project. It determines which locations are eligible for funding, what BSL counts the subgrantee committed to in their application, and ultimately what gets built. The problem is that the Fabric has errors. Not a few. On rural routes I've validated personally, I've found error rates of 12 to 18 percent — missing locations, duplicate entries, wrong address geocodes, and locations incorrectly classified as already-served on the FCC Broadband Map.

Subgrantees who don't validate their Fabric data before engineering starts are building on a cracked foundation. You might design a 22-mile aerial route targeting 340 locations, begin LLD, and then discover during QC that 40 of those locations either don't exist at the mapped coordinates or are already listed as served by another provider. That's a redesign — not a revision. And if you've already ordered cable sized to 340 locations with a 1:32 splitter ratio, you're looking at a BOM problem too.

The validation process isn't complicated, but it takes time. Cross-reference the Fabric against the FCC Broadband Map's challenge data, against county parcel records, and against satellite imagery on a spot-check basis. File Fabric challenges through the NTIA's official challenge process for any locations you dispute. Document every dispute with supporting evidence — this documentation becomes part of your BEAD compliance record. In my experience, getting this right before HLD is complete saves 3 to 6 weeks of mid-project rework. Our BEAD OSP engineering process includes a structured Fabric validation gate before route design begins for exactly this reason.

2. Permitting Backlogs Nobody Planned For

Every BEAD project schedule I've reviewed — every single one — treats permitting as a task that starts after LLD is complete. That assumption is why projects stall. State DOT encroachment permits, USACE Section 404 permits for wetland crossings, railroad crossing agreements, and SHPO reviews don't run in weeks. They run in months. VDOT routine encroachment permits average 60 to 90 days from submission. USACE Section 404 nationwide permit verifications routinely take 90 to 120 days. Railroad crossing agreements with Class I railroads — CSX, BNSF, Union Pacific — I've seen those take 180 days and longer.

If your LLD takes 10 to 14 weeks and you don't start permitting until it's done, you've built a 6-month gap into your construction timeline before you've ordered a single piece of hardware. That gap is your stall. It's not a permitting agency problem. It's a sequencing problem. So why do subgrantees keep doing it this way? Because their schedule was built by someone who'd never waited 90 days for a VDOT permit.

The fix is the engineering-permitting parallel track. At HLD, you have enough route definition to identify every permit-required crossing — road ROW, railroad, navigable waterway, federal land. Start those permit applications at HLD. Yes, the final LLD geometry may shift slightly. Most permit applications accommodate minor alignment changes during the review period, and a revised submission beats starting the review clock over from scratch. For a deep dive on managing this in practice, see ROW permitting delays in fiber deployment — it covers the agency-by-agency breakdown of realistic timelines. The subgrantees who hit their construction start dates are the ones running permits in parallel with design, not sequentially after it.

3. Pole Attachment Chaos

Utility pole attachment is the single most chaotic coordination task in an aerial fiber build. Pole owners — IOU electric utilities, cooperatives, municipalities — have 45-day statutory response windows under FCC rules for new attachment applications. In practice, many take 60 to 90 days. And that's after you've submitted a clean, complete application. If your application has errors, missing pole IDs, or incomplete make-ready estimates, the clock resets.

The deeper problem is missing pole records. I've worked routes where 20 to 30 percent of the poles on a given segment had no records in the utility's GIS, no NJUNS entries, and no joint use agreements on file. Poles that haven't been re-inventoried since the 1990s. Attachment heights that exist only in someone's hand-drawn field sketch from 2003. When you submit a pole attachment application for a pole the utility can't locate in their own system, the application stalls until they field-verify — and that field verification gets scheduled on their timeline, not yours.

Joint use agreements are their own category of problem. I've reviewed JUAs on rural routes that were last updated in 2001, that reference pole ownership structures that no longer exist, and that specify attachment rates superseded by two rounds of FCC rulemaking. An outdated JUA doesn't automatically block your attachment, but it does create a negotiation process that can take 60 to 120 days to resolve — usually right at the moment you need make-ready work to start.

The strategy that actually works is front-loading make-ready assessment before design commitment. Before you lock in your HLD route, walk the corridor with a field crew, identify every pole, pull NJUNS records, and flag every pole with missing data or a known make-ready issue. That assessment changes your route decisions in ways that save you weeks later. Our field survey services include a pre-design make-ready assessment specifically for BEAD aerial routes — because the cost of doing it before HLD is trivial compared to the cost of discovering a 45-pole make-ready dispute after LLD is committed.

4. Environmental Review Delays (NEPA/SHPO)

When federal money flows, NEPA applies. That's not optional, and it's not something your state broadband office will waive because the schedule is tight. The NTIA's Environmental Review obligations under the Infrastructure Investment and Jobs Act require that subgrantees complete environmental review before construction begins on any project using BEAD funds. For most rural aerial builds, you're looking at a Categorical Exclusion determination — the least burdensome NEPA pathway. But CEs still take 60 to 90 days in straightforward cases, and anything that doesn't cleanly fit a CE triggers an Environmental Assessment, which runs 4 to 6 months minimum.

SHPO reviews are their own timeline. State Historic Preservation Officers in rural states — where most of the unserved BEAD territory sits — are understaffed relative to the volume of reviews that BEAD is generating. I've seen SHPO Section 106 consultations run 4 to 6 months in states like Mississippi, West Virginia, and New Mexico, and that's for projects where there are no significant historic properties in the corridor. If you hit a potentially eligible site — a historic building, an archaeological resource, a traditional cultural property — the timeline expands to 9 months or more.

Tribal consultation is a separate obligation and the one I see subgrantees most unprepared for. If your route passes through or near lands with tribal connections — ancestral territories, traditional cultural properties, areas with treaty rights — the Section 106 process requires formal consultation with affected tribes. Tribes have no obligation to respond on your schedule. Meaningful consultation takes the time it takes. I've seen tribal consultation add 4 to 6 months to a SHPO review that was otherwise straightforward.

The only way to manage this without blowing your construction timeline is to initiate environmental reviews at HLD. You don't need LLD-level precision to file an APE (Area of Potential Effect) for Section 106. You need route geometry and project description. Get that from HLD and file immediately. If you wait for LLD, you've already given away 10 to 14 weeks of review time you needed. Review our guidance on BEAD funding and engineering requirements for 2026 for a full breakdown of the environmental documentation stack.

5. Material Lead Times vs. Project Timelines

The supply chain for fiber infrastructure is not what it was in 2019. It's better than the worst of 2022, but anyone planning a BEAD build assuming standard commercial lead times is going to get hurt. Fiber cable — specifically, high-count single-mode loose-tube and ribbon cable in the 288-fiber-and-above counts that BEAD routes typically require — is running 14 to 20 weeks lead time from major manufacturers as of early 2026. That number is for confirmed orders with a release date. Spot orders for large quantities often push toward the high end or beyond.

OLT hardware is worse. XGS-PON OLT chassis and line cards from Nokia, Calix, and Adtran are running 20 to 28 weeks on standard commercial orders. GPON equipment is somewhat shorter — 16 to 22 weeks — but most BEAD projects are specifying XGS-PON for the 10G symmetrical capability, which tightens supply. ONT quantities for large deployments can hit 12 to 16 weeks when you're ordering in the thousands.

Enclosures, pedestals, and splice closures are 8 to 12 weeks depending on manufacturer and configuration. Conduit and innerduct are generally available in 4 to 6 weeks, which is the least of your worries. Underground splice vaults — the precast concrete type that state DOTs often require for road crossings — can run 10 to 14 weeks from regional suppliers.

The mistake is waiting for LLD finalization before placing orders. By the time your LLD is reviewed, revised, and approved — typically 12 to 16 weeks from HLD completion — you've already eaten half or more of your lead time buffer. The right approach is using HLD outputs to place provisional orders. Fiber cable quantities can be estimated within ±15 percent at HLD based on route miles and design topology. That's enough precision to initiate a PO with a scope adjustment window. OLT hardware is even more straightforward — the headend design is largely set at HLD. For a complete breakdown of what BEAD compliance documentation should accompany procurement decisions, see our BEAD subgrantee engineering compliance checklist.

6. Field Survey Data That Can't Support Design

I've reviewed field survey packages from crews hired by subgrantees who needed to move fast and chose whoever was available. Some of those packages were fine. A lot of them were not. What does bad survey data actually cost? More than the survey itself — usually by a factor of five or six. And the ones that weren't — missing span lengths, wrong pole classes, GPS coordinates with 8-meter errors, attachment heights estimated visually rather than measured — those created problems that didn't surface until LLD QC. By then, the cost of a field resurvey is compounded by lost time, redesign labor, and in some cases, permit resubmissions because the corrected geometry moved crossing locations.

A proper OSP field survey deliverable for a BEAD aerial route includes: pole IDs cross-referenced to the utility's GIS or NJUNS records, measured span lengths (not estimated), measured or laser-ranged attachment heights for all existing communications attachments on each pole, pole class and height from the stamp or manufacturer record (not approximated), GPS coordinates accurate to 1 meter or better, existing make-ready conditions including down-guys and clearance issues, and photographs of each pole with a visible pole tag in the frame.

Surveys done by crews without telecom experience almost always miss attachment heights and make-ready conditions. A general contractor's survey team knows how to walk a route and GPS poles. They don't know that the height of the secondary power conductor above the proposed communications zone determines whether you need make-ready work — and they're not looking for it. The cost of a complete resurvey on a 15-mile aerial route runs $28,000 to $45,000. The cost of discovering a resurvey is needed during LLD QC, when design is already 60 percent complete and the schedule can't absorb it, is that plus 4 to 6 weeks of delay.

Our field survey services are designed specifically for BEAD broadband project requirements — OSP-trained crews, deliverables in CAD and GIS formats, and a QC gate before data is released to the design team. Every span measured. Every attachment height recorded. Every make-ready issue flagged in the deliverable so the design team knows before they commit to a route segment.

7. No Engineering Firm That Understands BEAD Compliance

This one is harder to see coming, because it doesn't look like a problem until you're already deep into design. A firm can do fiber engineering well — produce clean LLD packages, hit their schedules, deliver GIS-ready outputs — and still not know what a BEAD grant deliverable requires. These are genuinely different skill sets.

BEAD compliance documentation is not the same as a construction-ready design package. The NTIA requires subgrantees to document cost basis for their build — meaning your engineering team needs to produce cost estimates with methodology that can survive a federal audit. You need environmental review records that satisfy NEPA documentation requirements, not just a note that "environmental review was completed." You need as-built deliverables that close out to the BSL-level precision the grant requires — not just a red-line marked up by the construction foreman. You need a design package that explicitly demonstrates coverage of the committed BSL count, with the Fabric matching to show which locations the build serves.

General contractors who bridge into engineering — firms that build fiber and produce drawings in-house to save margin — almost universally can't produce this documentation. They're not set up for it. They don't have the grant compliance experience. I've seen a subgrantee hand their BEAD engineering to a contractor who had built 400 miles of fiber commercially, and that contractor produced a perfectly competent construction package that was completely inadequate for NTIA closeout. The subgrantee spent $185,000 in supplemental engineering fees to retrofit the compliance documentation after the fact.

When evaluating an engineering firm for BEAD work, ask these specific questions: Have they produced NTIA-compliant deliverables for a state broadband office? Can they show you a deliverable checklist mapped to BEAD subgrantee requirements? Do they have experience with Section 106 cultural resource documentation? Can they produce the cost basis summary in the format your state broadband office requires? If any of those questions produce hesitation, you need to keep looking. The difference between a firm that understands BEAD OSP engineering and one that doesn't is measured in months of delay and hundreds of thousands of dollars in remediation.

If you want to put this to the test before committing your project, start with our free design offer — we'll engineer your first 3.8 miles at no cost so you can evaluate the quality of our deliverables firsthand, including our BEAD compliance documentation package.