BEAD subgrantees are learning something the hard way: winning the award was the easy part. The compliance requirements that come with it — environmental review, buy America, construction documentation, quarterly reporting, post-construction verification — are more operationally demanding than most ISPs and construction firms expected when they submitted their applications. And states aren't waiting for the final closeout to check your work.
We've been working alongside BEAD subgrantees in several states as their engineering partner, and the compliance gaps we're seeing are consistent. They're not coming from bad intentions. They're coming from organizations that are good at building fiber networks but weren't set up to run a federally funded construction program. This checklist is based on what Utah, Alabama, and North Carolina are actually auditing — not the abstract requirements in the NTIA Final Rule. Specific. Actionable. Organized by phase so you know what's due when.
BEAD Pre-Construction Compliance Requirements Before You Break Ground
BEAD pre-construction compliance requirements include approved network design deliverables, completed NEPA environmental review, SHPO Section 106 clearance, executed ROW permits, PE-stamped construction plans, and documented subcontractor qualifications — all required before a shovel enters the ground. States are enforcing these requirements before issuing construction authorization, not accepting post-hoc documentation at closeout.
This is where most subgrantees fall behind before they've pulled a single permit. The pre-construction compliance window is narrow — states have aggressive build timelines — and the documentation burden is front-loaded. Miss a step here and you either delay construction or start building without the compliance documentation you'll need at closeout.
Environmental and Historic Preservation (EHP) Review
BEAD grants are subject to federal environmental review under NEPA and Section 106 of the National Historic Preservation Act. States are handling this at the program level to varying degrees, but subgrantees are responsible for providing the site-specific information that feeds into the state's environmental review. That means: project description with maps, construction method details (aerial vs. underground, bore or trench), identification of any resources within or adjacent to the project area — wetlands, floodplains, historic properties, tribal lands — and documentation of any design modifications made to avoid or minimize impacts.
North Carolina's BEAD program, administered through the Department of Information Technology, requires subgrantees to submit a project-level EHP questionnaire before any ground-disturbing activity is approved. The questionnaire asks specifically about National Wetland Inventory areas crossed by the route, presence of any structures over 50 years old within 100 feet of proposed ground disturbance, and whether any project activity occurs within a 100-year floodplain. Getting these answers requires actual GIS analysis against federal and state environmental datasets — not a checkbox from memory.
Utah's approach through the Utah Broadband Center follows a similar structure but adds a requirement for coordination with the Utah State Historic Preservation Office (SHPO) on any ground disturbance in areas identified as having elevated archaeological sensitivity. In practice, that means subgrantees in rural Utah building through agricultural or undeveloped land need a SHPO coordination letter before the environmental review is considered complete.
Pre-Construction EHP Checklist
- Project route map with GIS coordinates submitted to state program office
- National Wetland Inventory crossings identified and flagged
- FEMA floodplain layer reviewed; any floodplain crossings documented
- Section 106 coordination initiated with SHPO for any ground disturbance
- Tribal consultation completed where required by state program guidance
- EHP questionnaire or equivalent submitted and approved before ground-breaking
- Any required design modifications (horizontal directional drill instead of open trench, aerial re-route, etc.) documented in the engineering package
Buy America Build America (BABA) Requirements
The Build America Buy America Act applies to BEAD-funded infrastructure. For fiber construction, that means iron and steel products, manufactured products, and construction materials used in the project must be produced in the United States — to the extent required by the applicable waivers and covered product categories as interpreted by NTIA and OMB guidance. This is not a procurement preference. It's a compliance condition. Failure to comply can result in disallowed costs and repayment obligations.
Alabama's BEAD program through the Alabama Department of Economic and Community Affairs (ADECA) requires subgrantees to submit a BABA attestation form before procurement that certifies compliance and identifies any products for which waivers are being claimed. The attestation requires documentation of the country of origin for conduit, fiber cable, and drop wire at minimum. Getting this wrong at procurement — buying conduit from a foreign manufacturer because it was 11% cheaper — creates a closeout problem that can't be easily fixed after the fact.
Fiber optic cable, specifically, has a complicated BABA profile. The fiber itself is often manufactured domestically, but the cable sheathing materials and buffer tubes may not be. The rule requires tracing the supply chain, not just the point of purchase. Subgrantees need to get written BABA compliance certifications from their primary material suppliers as part of the procurement process — not as a closeout documentation exercise.
Waivers are not automatic: NTIA has published a list of covered products and a waiver framework, but waivers must be requested and granted before the non-compliant procurement occurs. Retroactive waivers are not guaranteed. If your splitter hardware or optical network terminal equipment has a foreign content issue, get the waiver filed before you order — not after it arrives on the jobsite.
During Construction: Active Monitoring and Documentation
States are deploying field monitors on BEAD projects. Not universally, and not on every project simultaneously — but the monitoring function exists and is being used. Alabama has contracted with third-party inspection firms to conduct random construction site visits on active BEAD projects. Utah's program office has indicated it will require photographic documentation of construction progress at defined project milestones. North Carolina's program requires construction inspection reports signed by a licensed PE or equivalent for certain project tiers.
What inspectors are looking for — based on what we've seen and what the program documents specify — falls into several categories:
Construction Compliance Checklist (Active Phase)
Permitting and ROW Documentation
- All required permits (municipal, county, state DOT, railroad crossing, USACE Section 404 if applicable) obtained and on-site or electronically accessible
- Permit conditions being actively followed (burial depth, restoration requirements, work window restrictions)
- Right-of-way documentation for any private easements required by the project route
- Any utility crossing notifications completed per state one-call requirements (811 tickets current and documented)
Construction Progress Documentation
- Daily construction logs with route segment, linear footage placed, and crew count
- Photographic documentation at each key milestone: bore entry/exit points, splice enclosure installations, cabinet and hut installations, pole attachment points
- Material tracking records: fiber cable lot numbers, conduit footage by type, splice enclosure serial numbers — traceable to BABA compliance documentation
- As-built redlines being maintained concurrently with construction (not reconstructed after the fact)
- Any design deviations from the approved engineering package documented with reason and engineering approval
Labor Standards and Workforce Documentation
- Davis-Bacon wage determination posted at the work site (if applicable to your state's program requirements)
- Certified payroll records submitted per the program office's schedule
- Subcontractor documentation on file: licenses, insurance certificates, subgrant flow-down conditions acknowledged in writing
- Any workforce development commitments (local hire requirements, apprenticeship ratios) being tracked and documented
The as-built documentation requirement during active construction deserves specific attention. States are not accepting end-of-project as-built submissions reconstructed from memory and GPS traces. The standard that's emerging across Utah, Alabama, and North Carolina is that as-built records must reflect actual construction conditions as they occur — photo documentation of each buried conduit segment before backfill, GPS coordinates taken at each splice location, depth measurements at defined intervals. As we detail in our guide to fiber network as-built documentation, the difference between acceptable and rejected as-builts almost always comes down to whether documentation was captured during construction or assembled after.
Quarterly Reporting: What States Are Actually Requiring
Quarterly progress reports under BEAD are not narrative summaries. They're structured data submissions with specific fields that feed into state and federal tracking systems. Getting this wrong — submitting narrative-only reports, missing quantitative fields, or reporting against different metrics than your approved project plan uses — is one of the fastest ways to trigger a compliance review.
North Carolina's quarterly reporting template, which NCDIT circulates to subgrantees, requires the following quantitative data fields at minimum:
- Linear miles of infrastructure deployed by construction method (aerial, underground direct bury, underground conduit) during the reporting period
- Number of locations passed by service tier (25/3 Mbps, 100/20 Mbps, 1 Gbps/1 Gbps)
- Number of locations serviceable (drop complete and ONT installed) vs. passed (route in place but drop not yet connected)
- Cumulative grant expenditures by budget category, with supporting documentation
- Any EHP issues encountered and how they were resolved
- Schedule variance — if behind plan, explanation and corrective action
Utah's reporting structure through the Utah Broadband Center adds a geographic verification requirement: progress must be mapped and submitted as a GIS layer each quarter, showing actual construction extent. The layer must match the linear footage numbers in the narrative report within a defined tolerance. If your GIS shows 47.3 miles of fiber placed but your narrative reports 51 miles, that discrepancy will generate a question at minimum and a site audit if it can't be quickly explained.
Alabama's ADECA currently uses a hybrid spreadsheet submission that tracks milestone completion against the approved project timeline. But the agency has signaled it's moving toward a GIS-based progress tracking portal for larger projects — similar to what North Carolina and Virginia are doing — so subgrantees should be building their documentation systems with GIS-integrated progress tracking from the start.
BEAD Post-Construction and Closeout Documentation Requirements
BEAD closeout requirements include verified as-built GIS records, final network documentation, photographic construction evidence, PE-certified completion certifications, and final cost reporting tied to the approved project budget. Missing documentation at closeout can delay or prevent final disbursement payments, even when physical construction is complete. Starting as-built documentation concurrent with construction — not after — is the only reliable path to clean closeout.
Closeout is where the documentation gaps that were manageable during construction become expensive problems. As we've covered in our broader breakdown of BEAD engineering requirements for 2026, the federal program's closeout provisions require a level of documentation specificity that most subgrantees haven't historically had to produce.
Post-Construction Compliance Checklist
As-Built Documentation Package
- GIS feature dataset with network geometry accurate to within 1.5 meters of actual field position (some states require sub-meter accuracy on key network nodes)
- Complete attribute data: fiber cable type, count, manufacturer, installation date, burial depth, conduit type and size, splice enclosure make and model
- Splice record documentation: fiber assignments by tube and fiber position, splice loss values from OTDR traces, closure type and GPS location
- Photo documentation index cross-referencing construction photos to specific network segments
- OTDR test records for all fiber spans — not just the backbone, but distribution and drop fiber where testing was feasible
Service Verification and Eligibility Certification
- Final serviceable location list reconciled against the approved project area and the BEAD eligible location list
- Speed test records or network performance documentation confirming that deployed equipment meets the funded service tier (minimum 100/20 Mbps, typically 1 Gbps symmetrical for most BEAD awards)
- Documentation for any locations that were in the funded area but could not be served, with engineering justification
- Subscriber take rate data for the first 90 days of service (some state programs require this)
Financial Closeout Documentation
- Final expenditure report by budget category reconciled to actual invoices and payroll records
- Match fund documentation: source, amount, documentation that match was actually spent on allowable costs
- Final BABA attestation confirming all covered materials in the completed project were compliant or covered by approved waivers
- Disposition of any equipment purchased with grant funds that may have been removed or replaced during construction
Common BEAD Engineering Compliance Failures Across Projects
A few patterns that are showing up consistently across the BEAD projects where we're supporting subgrantees:
EHP documentation gaps discovered post-construction. A subgrantee in a Midwestern state — not one of the three mentioned above, but a state with similar requirements — completed a significant portion of underground construction before discovering that two of their route segments crossed areas flagged in the state's SHPO database as having potential archaeological sensitivity. The construction had already disturbed those areas. The remediation process — retroactive SHPO consultation, potential archaeological monitoring, revised construction methods for the remaining segments — added 11 weeks to the project timeline and put the subgrantee at risk of disallowance on the affected segments.
As-built redlines reconstructed after the fact. This is almost universal on first-time BEAD subgrantees. Construction crews don't naturally carry GIS-enabled documentation workflows. They build and move on. Going back to document what was built — depth measurements, exact bore paths, splice locations — after the conduit is buried and the pavement is patched is an exercise in estimation, not documentation. States are starting to reject as-built submissions that don't show adequate field-level specificity, and the bar is only going to get higher.
Subcontractor flow-down compliance gaps. The BABA and Davis-Bacon obligations flow down to subcontractors. If your prime contractor is compliant but your directional boring subcontractor is using non-compliant conduit purchased through a foreign distributor, that's still your compliance problem. Subgrantees need to include BABA compliance certification requirements in every subcontract and verify compliance before materials are ordered — not at closeout.
Our permitting and compliance support services include a BEAD subgrantee compliance tracking framework that covers all of the above — pre-construction through closeout — with the GIS documentation capabilities to support state reporting requirements. If you're a subgrantee who's already in construction and feeling behind on documentation, the time to catch up is now, not at closeout. Reach out at info@draftech.com and we'll tell you honestly where you have gaps and what it will take to close them.