How Should We Compare a State's BEAD Allocation With Its Approved Build?
NTIA's original allocations include Texas ($3.313B), California ($1.864B) and Missouri ($1.736B). Those figures describe the funding allocated to each state, rather than its approved deployment total. Each state guide separates these amounts in its opening BEAD panel and identifies funded locations, technology mix and subgrantees. Use those deployment details to understand the approved build's scope.
Can We Scope a Build Outside Draftech's Current Active States?
Yes. We can review a proposed build in any U.S. state, including one where we do not currently have an active project. Bring the awarded location list, grant requirements and available infrastructure records to the scoping discussion. We assess field survey needs, permitting jurisdictions and pole attachment work before establishing the engineering deliverables and schedule.
Which Providers Can Bring an Awarded Fiber Build to Draftech?
We support independent ISPs, electric cooperatives, municipal broadband providers, tribal providers and cable operators expanding into fiber. A BEAD subgrantee can engage us for route engineering, make-ready and pole attachment packages, permit coordination, construction drawings and closeout records. For tribal service areas, we include tribal permitting coordination in the route planning discussion so it informs the scope from the start.
What Should a Subgrantee Check Before Scheduling BEAD Engineering?
Confirm the awarded locations and agreement status with the state broadband office. NTIA's July 14, 2026 request called for removing satellite locations shown as served or non-residential on the new FCC map. Its September 3, 2026 Supplemental Deployment Policy Notice opened a second round for missed or newly unserved locations using roughly $21 billion in savings; other uses await NTIA guidance. Establish which locations belong in your design scope before scheduling surveys.
How Do State GIS Requirements Shape the Closeout Package?
The state's required fields and submission format determine how we organize the network data. We prepare attributed shapefiles and geodatabases covering the specified route, fiber, conduit, splice and hub information, then check the package internally against those requirements. Aligning the records with field changes gives the broadband office and network owner a consistent account of what was constructed.
