Skip to content
Inerxia

BEAD reporting for ISPs What BEAD asks you to prove, and where the data comes from.

BEAD subgrantees report to their state or territory broadband office, not directly to NTIA. The office rolls those reports into its own semiannual reports to NTIA. What you report covers deployment progress, the locations you serve, your low-cost service option, and annual network performance tests. Almost all of it comes from the operational data you already keep: subscribers, service addresses, speed tiers, installs and outages.

Updated · By the Inerxia team

What is BEAD?

The Broadband Equity, Access, and Deployment (BEAD) Program is a $42.45 billion federal program created by the Infrastructure Investment and Jobs Act and administered by NTIA. It funds broadband deployment to unserved and underserved locations. NTIA awards the money to Eligible Entities, meaning the 56 states, territories and the District of Columbia. They select providers, called subgrantees, to build the networks.

The rules changed materially in June 2025, when NTIA issued the BEAD Restructuring Policy Notice. The notice made subgrantee selection technology-neutral, so fiber is no longer the only way to qualify as a Priority Broadband Project. It required a new “Benefit of the Bargain” selection round. It removed several NOFO requirements, including the labor, climate and middle-class affordability provisions. It also stopped states from setting the price of the low-cost service option.

BEAD guidance is still being revised. NTIA's FAQ reached version 22 in June 2026. Treat this guide as orientation, not legal or compliance advice, and confirm every obligation with your state broadband office and your subgrant agreement.

Who has to report, and to whom?

Reporting runs in a chain. Your subgrant agreement with the state sets what you report and when. The state broadband office must monitor its subgrantees and submit a Semi-Annual Report (SAR) to NTIA. Performance-testing results, for example, reach NTIA once a year, in the SAR covering July 1 to December 31, which is due January 30. Each state sets its own subgrantee deadline ahead of that date.

  1. 1.You (the subgrantee) keep records, run the required tests and submit reports on the schedule in your subgrant agreement.
  2. 2.Your state broadband office (the Eligible Entity) reviews them, checks compliance and consolidates them into its SAR.
  3. 3.NTIA oversees the Eligible Entities and receives summarized results.

Separately, you keep filing with the FCC. Facilities-based providers submit Broadband Data Collection (BDC) filings twice a year, with data as of June 30 and December 31. BEAD performance testing samples from the locations in those filings.

What data do subgrantees typically report?

The exact list comes from your state, but the obligations published by NTIA fall into these areas:

Data areaWhat it coversWhere it lives in your systems
Deployment progressBuild milestones toward offering service across the project area within four years of the subgrantConstruction and network records, provisioning status per location
Locations servedWhich BEAD locations (BSLs, identified by FCC Fabric ID) have service available and active subscribersSubscriber and service-address records, BDC filings
InstallationAbility to complete a standard installation within 10 business days of a requestOrder, scheduling and install records
Low-cost service optionA subgrantee-proposed plan of at least 100/20 Mbps and 100 ms latency for Lifeline-eligible subscribers, offered through the 10-year federal interest periodPlan catalog, eligibility records, billing
Network performanceAnnual speed, latency and availability tests on a random sample of active subscribers, per speed tier and technologyCPE management (e.g. TR-069/TR-369), test results, outage logs
Financial and complianceCosts, match, letter of credit or performance bond, and certifications required by the grant termsAccounting, grant files

Performance testing is the most data-heavy requirement. According to NTIA's September 2025 primer, speed tests run once an hour for a week between 6 PM and midnight local time. At least 80% of measurements must reach 80% of the committed speed tier. Latency tests run once a minute for an hour, and 95% of results must be at or below 100 ms. Cumulative outages over 48 hours in a year must be reported. Results go to the state in the USAC CSV format, one file per technology and speed tier, with each test tied to a location's BSL Fabric ID and your subscriber ID.

Why do your billing and subscriber records matter?

Almost every BEAD report depends on one thing: an accurate record of which address has which service, at which speed tier, since when, on which equipment. That is not separate grant data. It is the same data your billing, provisioning and support systems produce every day.

  • Testing samples are drawn from locations with active subscribers, so your subscriber-to-location mapping has to be right.
  • Each test is tied to a BSL Fabric ID and a subscriber ID, so every service address needs a Fabric ID.
  • Results are split by speed tier and technology, so plans in billing have to match what is provisioned on the network.
  • Availability reporting counts outages from the first customer report, so support tickets and outage records have to carry timestamps and locations.
  • Installation and low-cost-plan obligations are proven from orders, installs and eligibility records.

When those records live in separate spreadsheets, every reporting cycle turns into a reconciliation project. When they sit on one subscriber record, a report becomes a query.

Operations · last 24 hoursSep 23 · 14:32
IDEventStatusValue
#48201Auto-suspendSuspended−1 service
#48202Auto-reconnectReconnected2 min
#48203Cycle invoicingIssued2,418 docs
#48204Payment reconciledCleared+$74.00
Service changes, installs and payments as timestamped events on one subscriber record, the raw material behind location-level reporting.

How do you get your data BEAD-ready?

Check
Every service address carries its FCC BSL Fabric ID
Tests, locations served and BDC filings all key on it.
Each subscriber's plan matches the speed tier provisioned on the network
Performance compliance is measured per committed speed tier.
You can pull active subscribers per project area, tier and technology
The testing sample comes from active subscribers in each state.
CPE can run or report tests remotely
NTIA lists TR-069/TR-369, gateway software or on-site measurement devices as testing methods.
Outages and customer reports are timestamped and tied to locations
Availability reporting starts the outage clock at the first customer report.
Installs record request date and completion date
Standard installation means service within 10 business days of a request.
Low-cost plan enrollment and eligibility are tracked
The low-cost service option runs through the 10-year federal interest period.

Keep the documentation of your testing methods as well. NTIA requires subgrantees to document methods and parameters, publish their measurement report on their website, retain the data for inspection and certify its accuracy.

Where does Inerxia fit?

To be direct: Inerxia is not a BEAD reporting tool, and it does not generate BEAD or SAR reports. Sonar has deeper US grant and BEAD reporting tooling today, and we say so on our comparison page. If your main constraint is grant reporting, weigh that seriously.

Inerxia's role is upstream. It keeps the data those reports are built from clean and in one place. The Operating System holds subscribers, service addresses, plans, installed equipment, tickets and OLT/GPON, RADIUS and TR-069 provisioning on one subscriber record. Subscriber Intelligence clusters calls and tickets by service location, which shows where outages and service problems concentrate.

Sources

BEAD reporting, answered.

Do BEAD subgrantees report directly to NTIA?

No. Subgrantees report to their state or territory broadband office under the terms of their subgrant agreement. The broadband office monitors its subgrantees and submits Semi-Annual Reports to NTIA, including an annual summary of performance-testing results in the report due January 30.

What speeds and latency must a BEAD-funded network meet?

Performance is measured against the committed speed tier, which cannot be lower than 100/20 Mbps. Under NTIA's September 2025 primer, 80% of speed tests must reach 80% of the committed speed, and 95% of latency tests must be at or below 100 milliseconds. Your subgrant agreement may add stricter terms.

Do BEAD subgrantees still have to offer a low-cost plan?

Yes. The statute requires at least one low-cost service option, and the June 2025 Restructuring Policy Notice kept that requirement. States can no longer set its price: subgrantees propose it themselves. It must offer at least 100/20 Mbps with latency of 100 ms or less, and eligibility follows the FCC Lifeline program.

How long do BEAD obligations last?

Deployment must allow standard installation across the project area within four years of receiving the subgrant. The low-cost service option and the federal interest in funded assets run for 10 years after the year the subgrant is closed out. Performance testing continues annually through the period of performance.

Does Inerxia produce BEAD reports?

No. Inerxia does not generate BEAD or Semi-Annual Reports, and Sonar has deeper grant reporting tooling today. Inerxia keeps the underlying operational data on one subscriber record: service addresses, plans, provisioning, installs and tickets. That is the data reporting draws on.

See it running on your own data.

Thirty minutes on your own subscriber data, and a straight answer about where Inerxia fits your operation.