LuxBEAD as-built requirements: what subgrantees must hand over, by state
Written by
Lux Team
Category
Documentation
Date
Share this article
Where BEAD stands
There is no single federal BEAD as-built format: NTIA sets what states must report, and each state sets what its subgrantees must hand over, in the subgrant agreement and the state's reimbursement and reporting guides. In practice, many states, Montana and Wyoming among them, tie payments to milestones that you prove with as-built records of the plant placed and the locations it serves, and you should expect to keep location-level evidence from the first day of construction.
This page collects what a subgrantee needs to know, as of October 2026, with links to each state's own documents. It will be updated as states publish final guides. Lux is not BEAD compliance or reporting software and files nothing with NTIA or a state broadband office; the last section says what Lux does and does not do.
NTIA approved the last of the 56 state and territory Final Proposals in late August 2026, so every program has moved into the subgrantee phase: signing agreements, clearing environmental review and building (Benton Institute). That makes as-built documentation a near-term question for most subgrantees, not a 2029 one.
What NTIA requires at the federal level
NTIA's reporting requirements fall on the Eligible Entity, meaning the state or territory, which then passes them to subgrantees. NTIA's semi-annual report guidance describes what states report after their Final Proposals (NTIA SAR guidance v1.3), and the later Semi-Annual Technical Report form has separate sections for subgrantees, deployment projects and locations (NTIA SATR v2.0 form). Reporting is therefore location by location: which broadband serviceable locations a project has reached and when.
What NTIA's published guidance does not do is prescribe one as-built file format, a GIS schema or a drawing standard. Those come from the state. Read your subgrant agreement first; its reporting exhibit is the binding version.
State examples
The table lists what each state's own documents say. Percentages and forms change between versions, so open the linked document before relying on a row.
State | Milestone or report | Evidence asked for | Source |
|---|---|---|---|
Montana | Construction payments released at set shares of project locations (for example 20% of BSLs), after state verification | Placement of infrastructure and the associated as-built documentation for that share of locations; the state may request more documentation | |
Montana | Quarterly report (terrestrial) | A CSV of served locations for the state's semi-annual report, and a list of locations removed from the project, which the state must approve | |
Wyoming | Fixed-amount milestones, including a project plan milestone and completion of 50% of BSLs; no payment before a milestone is met | Milestone evidence, quarterly desk reviews, semi-annual and annual reports, closeout reporting | |
Alabama | Quarterly desk reviews and semi-annual performance reports through a state portal | Records that support every reported figure, provided to NTIA or the state on request; duties can change with the state's risk assessment | |
South Carolina | GIS data from application through closeout | As-built shapefiles showing where construction took place, following the state's template schema | |
New Jersey | Construction start | Final NTIA approval of the environmental and historic preservation documentation before any construction |
The common thread: payment depends on proving, location by location, that plant was placed and service is available, and the state can ask for the records behind any number. A shapefile delivered at closeout is not enough if the milestone payments along the way also need as-built evidence.
What a complete as-built package usually contains
States differ on format, but the content they ask for converges. Plan to be able to produce, for any milestone:
Location list. Every BSL in the project with its status: passed, service available, connected, or removed with the reason and the state's approval.
As-built GIS. Routes as built, with cable type and fiber count, aerial or underground, and the structures (poles, handholes, cabinets) placed. Keep it in the state's schema if there is one.
Construction records. Dated photos of the work, inspection results and change orders explaining where the build differs from the plan.
Test data. Optical test results for the plant, so that "service available" is backed by a measurement.
Permits and environmental clearances. Approved permits and the environmental decision documents for the areas built.
Cost records that support the milestone claimed, under the state's rules for fixed-amount or reimbursable awards.
Questions to settle with your state before construction
Disputes over milestone evidence are easier to avoid if these questions are settled at the start. Put these to your state broadband office in writing, and keep the answers with the agreement:
Which file formats and schema does the state accept for as-built GIS, and does it want one file per milestone or one cumulative file?
What counts as a location "passed" or "service available" for a milestone: plant placed past the location, a drop installed, or a test result?
Which test results does the state want, from which instruments, and in which file format?
How are locations removed from the project handled, and who approves the change?
How long must records be kept after closeout, and in what form?
Will the state field-verify a sample of locations, and how much notice is given?
Keep as-built evidence from day one
The expensive pattern is the one our article on as-built drift describes: crews redline paper, records are digitized weeks later, and the as-built is assembled at the end. Under milestone payments that delays cash, and under audit it is hard to defend. A better pattern:
Set the schema before construction. Map the state's as-built fields to your design data on day one, so each placed asset already carries what the report needs.
Capture at the job. Each work order closes with its photos and readings attached, checked against your standard before the crew leaves.
Compare continuously. Compare each as-built change with the design as it arrives, and record the reason for every difference.
Count from the record. Derive locations passed and connected from the network record, not a spreadsheet updated on Fridays.
Keep the trail. Record who approved each change and when; auditors ask.
How Lux handles it
Lux is not BEAD compliance or reporting software, and it files nothing with NTIA or your state broadband office. Your team prepares and files reports. What Lux can do is keep the records those reports draw on in one place. It can propose obligations from an uploaded subgrant agreement, quoting each clause, for a person to confirm, and then track them on a calendar. It counts locations passed and connected, and cable built, from the project record, and can load FCC broadband availability files as a map layer.
During construction, crews' required photos are checked against your rubric, as-builts are recorded on a separate branch and compared with the design difference by difference, and a supervisor accepts each merge, all on a tamper-evident audit trail. See Lux for BEAD and GIS, CAD and as-builts.
Frequently asked questions
Is there a federal BEAD as-built format?
No. No single federal format has been published. NTIA sets what states report, including location-level data, and each state sets the as-built format and evidence in its subgrant agreement and guides.
What evidence do BEAD milestone payments need?
It varies by state. Montana, for example, ties construction payments to infrastructure placed plus as-built documentation for a share of project locations, verified by the state. Check your agreement's reporting exhibit.
When can BEAD construction start?
After the subgrant agreement is signed and NTIA has approved the environmental and historic preservation review. New Jersey's guidance states that construction must not begin before NTIA's final approval of that documentation.
What format should BEAD as-builts be in?
Use the state's template if it has one. South Carolina, for example, asks for as-built shapefiles that follow its schema. Otherwise agree the format with the state broadband office before construction.
Does Lux file BEAD reports?
No. Lux is not BEAD compliance or reporting software. It keeps project records, obligations and construction evidence in one place; your team prepares and files reports.
Share Blog
