Summary

  • NTIA’s October 20 dashboard says all 56 states and territories received final proposal approval and 55 returned signed federal award agreements.
  • A separate NTIA rule requires each subgrantee to submit a signed, machine-readable certification; missing it leaves BEAD funds unavailable from that subgrantee.

The dashboard says 55 of 56 states and territories have signed and returned their BEAD award agreements. It is a satisfying number: one state-level box remains, and the federal progress bar looks nearly finished. Then the paperwork descends a level.

Those 56 entities are the state and territorial recipients, not the local providers or other organisations that will build funded networks. NTIA’s April 2026 FAQ Version 20 puts a separate document between each subgrantee and access to its BEAD grant funds: a certification that stands on its own, is signed and dated, and arrives with the signed subgrant agreement.

The distinction is administrative, but the consequence is cash availability. FAQ 5.3 says a subgrant signature alone does not satisfy the condition. If the separate certification is missing, BEAD grant funds are held unavailable from that subgrantee until the Eligible Entity receives it. The completed federal award dashboard and the project-level funding gate are different ledgers.

NTIA has turned the certification into a small piece of payment plumbing. It must be a machine-readable PDF, use a consistent filename set by the state and include the subgrantee’s Unique Entity Identifier. The Authorized Organization Representative who signs the subgrant agreement must also sign and date it, have authority for the subgrantee’s affiliates, and include contact information. A state can standardise the filename; it cannot make the signature or the separate file disappear.

The certification concerns future federal support. The subgrantee says its application did not rely on speculative additional federal funding and that it will not need or accept additional federal broadband money to serve its BEAD-funded locations. NTIA requires each certification as a standalone submission and says it may publish them.

The dashboard does not show this lower-level receipt step. Its 55/56 figure answers whether states and territories returned federal award agreements. It does not tell readers whether a particular provider’s certification has reached its state, how many projects sit behind any missing document, or what amount is involved. No public subgrantee receipt ledger appears alongside the headline milestone.

That makes the title of the dashboard do more work than the dashboard can. It measures federal award progress; it does not certify that every downstream file needed for each subaward is in the folder. The paper gate is explicit in the FAQ, even if the public progress bar stops before it.

The two agreements sound similar because both sit inside one programme, but their parties and jobs differ. The federal award agreement runs between NTIA and a state or territory. A subgrant agreement runs between that Eligible Entity and the organisation selected to build a network. NTIA says NIST approval makes federal grant funds available to states; FAQ 5.3 then sets a separate condition that can hold funds from an individual subgrantee. A state-level green light is not a project-level receipt.

A useful operating register would keep the federal award in one record and pair each subgrantee UEI with its agreement, certification, authorised signer, receipt date and funds status. The FAQ does not prescribe a public dashboard design. It does name the two documents and the consequence of missing the second. What readers lack is a dated trail that shows whether the paper gate is routine processing or a specific hold.

For a provider, the operational checklist is blunt: align the signer with the agreement, verify affiliate authority, include contact details, use the state’s UEI-based filename convention, make the PDF machine-readable, and deliver it with the signed subgrant agreement. A checkbox called “agreement signed” cannot safely stand in for two documents when the rule names two.

Sources