# State Broadband Offices: What BEAD Subgrantees Need to Submit

**Title tag:** State Broadband Offices: BEAD Submission Guide 2026
**Meta description:** State broadband offices guide: BEAD subgrant agreements, environmental review, progress reports, payment evidence, GIS formats and engineering closeout.
**Author:** Ashish Kumar Meena
**Published:** November 13, 2026  
**Last updated:** November 13, 2026  
**Category:** BEAD & Grants
**URL:** https://draftech.com/blog/state-broadband-offices
**Primary keyword:** state broadband offices
**Plan reference:** plan-2026-10-31
**Word count:** 2928

![A person at a window-side desk traces a road on an aerial map with a yellow highlighter beside a laptop and binder.](/blog/img_state_broadband_offices.webp)

### In This Article

- [What state broadband offices do for BEAD](#office-role)
- [Turn selection requirements into a subgrant record](#selection-agreement)
- [Prepare the route for environmental and permit review](#review-release)
- [Make progress reports and payment evidence agree](#progress-payments)
- [Why state broadband offices shape design and as-builts](#formats-closeout)
- [Choose the next submission your team needs](#next-submission)

A state broadband office is the office or authority that administers BEAD for its state or territory, often alongside other broadband programs. Its name and department vary. For an ISP, cooperative or municipality, the practical question is which office can explain the requirements attached to the proposed subgrant.

We approach that relationship through the engineering record. A route drawing needs to match the project the office selected, and the eventual as-built needs to explain what changed. This guide follows the submissions that connect those endpoints, so your engineering team can prepare evidence in the receiving office's format.

## What state broadband offices do for BEAD

For BEAD, state broadband offices administer the program on behalf of the state or territory that NTIA calls an Eligible Entity. NTIA identifies 56 Eligible Entities, including the states, territories and District of Columbia. The office manages the subgrantee relationship, while NTIA retains federal program oversight.

**The office's organizational home does not define your submission.** It may sit within an economic development department, a public utility agency or a separate authority. We start with the program named in the solicitation and identify the unit responsible for its engineering review. That program's instructions govern the submission; another grant handled by the same staff may use different evidence.

### Find the current contact and submission channel

NTIA's BroadbandUSA State and Territory Map is the starting point for finding the relevant office and its broadband program information. Confirm the listed contacts against the office's current website before sending material. Because staff assignments change, we also check whether technical questions belong in a procurement portal, a designated mailbox or a formal clarification process before an engineer emails a drawing directly.

Ask for the current application instructions and the technical attachments that will accompany the subgrant agreement. Request the office's accepted deliverable formats early enough to shape production. A public presentation can explain the program, but your document register should identify the actual version used for a submission and the person responsible for checking updates.

### Keep the office's authority separate from other approvals

The office oversees subgrantee selection and the resulting subgrant agreement. Its continuing responsibilities include environmental review coordination, permit and construction monitoring, progress reporting, payment review and formal subgrant closeout. NTIA's BEAD Final Proposal Guidance for Eligible Entities describes the monitoring relationship. We use that relationship to organize the engineering handoffs without assuming that every office has the same review workflow.

**Award selection does not release a route.** Road authorities still control their permits, pole owners control attachment permissions, and federal environmental requirements remain part of the project conditions. By tracking those decisions separately, we give a project manager a way to see the precise restriction on a segment without interpreting a general award announcement as permission to begin construction.

NTIA's June 6, 2025 BEAD Restructuring Policy Notice changed requirements affecting selection and subgrantee obligations. An older presentation may therefore describe a process that no longer governs the award. Our [BEAD technical assistance guide](/blog/bead-subgrantee-technical-assistance) explains how to distinguish governing award documents from supporting guidance and escalate an apparent conflict for written clarification.

The BEAD sequence moves from selection and federal approval through the subgrant agreement to authorized deployment, reporting and closeout. For a particular project, get milestone dates from the applicable award documents and current NTIA notices. We would not infer a construction start from a national announcement.

## Turn selection requirements into a subgrant record

**Start with the office's requested evidence.** The table groups its review responsibilities by the handoffs an engineering team must support. These are preparation categories, not a universal submission specification. Your agreement determines the required attachments, and an office may separate the reviews across different staff or systems.

| Office responsibility | Evidence to prepare | Engineering consequence |
| --- | --- | --- |
| Subgrantee selection | Proposed project area and technical design basis | Keep the proposal tied to its location set |
| Subgrant agreement | Accepted scope and milestone attachments | Establish the design baseline |
| Environmental review coordination | Project description and proposed disturbance footprint | Track the route revision submitted for review |
| Permit and construction monitoring | Permit status and field progress evidence | Show where work is authorized and documented |
| Progress and payment review | Period-specific quantities and supporting records | Reconcile claimed progress with the design |
| Closeout approval | Final engineering records and resolved exceptions | Preserve accepted as-builts and decision history |

### Selection: preserve what the proposal promises

The application establishes what the applicant proposes to deliver. Expect the office to request evidence of technical capability and a network plan tied to the proposed service area. Our submission record keeps the location dataset, its source version and the proposal drawings together. Otherwise, a revised route can become the working plan without anyone checking whether it still serves the locations in the application.

Our preferred starting point is a traceable relationship between each proposed service location and the network design. The location identifier should survive routine CAD and GIS exports, even when the drawing sheet number changes during production. An address alone is a fragile reference. A spelling correction should never silently disconnect a location from the project record used for review.

### Agreement: establish the accepted baseline

Before issuing construction drawings, compare the accepted project scope with the engineering assumptions made during the application. The subgrant agreement may incorporate attachments that define milestone evidence or technical acceptance requirements. Reading those attachments together helps us flag differences for the subgrantee's responsible team rather than treating the original proposal as the final authority for every downstream drawing.

**Assign ownership of changes.** A design lead should know who can authorize an amendment and how the office wants a proposed change submitted. Our revision process preserves the original baseline so each change can explain which locations it affects. The limitation of this approach is that careful version control cannot resolve an ambiguous award condition; the subgrantee still needs a written determination.

## Prepare the route for environmental and permit review

Environmental review needs a description of the work that can be compared with the proposed construction footprint. NTIA's BEAD Frequently Asked Questions and Answers, version 19, describes Eligible Entity environmental screening and preparation of draft decision documents for NTIA approval. We supply engineering inputs within the agreed scope. The responsible environmental team determines what studies or consultations are needed.

### Environmental review: identify the footprint being assessed

A centerline alone may leave essential work outside the reviewer's view. Ask the responsible team what it needs to represent access and temporary disturbance, and distinguish proposed methods where they change the affected area. With the reviewed revision identified on the drawings, a later route movement is easier to recognize, and the subgrantee needs to know whether that movement requires additional review before work proceeds.

For that comparison, we use a change record connecting the revised geometry to the previous submission and explaining why the change is proposed. Avoid leaving that explanation in a meeting note that the drawing recipient never receives. The record should identify the affected segment and refer the approval question to the responsible party, without presenting an engineering update as an environmental clearance.

**Carry the review boundary into production.** Mark the exact route revision covered by each approval, so a field instruction cannot inherit clearance from a drawing that describes a different footprint.

### Permits and construction: show the release condition

Permit monitoring works best when each permit is associated with the part of the network it covers. Our permit mapping compares the permitted limits with the construction issue set and records restrictions that affect field release. A permit application receipt proves submission. The actual authorization, including its conditions, tells the project team what work it can perform.

Construction monitoring then needs evidence of what happened within those limits. A field record should identify the segment and the drawing revision used for the work, with observed departures routed back to the design lead. The distinction between proposed and installed work matters to us when a progress report reaches the office before an updated drawing has completed engineering review.

For teams whose drawings and milestone records need to fit those handoffs, our [BEAD engineering consulting packages](/services/bead-engineering-consulting) cover design, milestone evidence, as-builts and closeout documentation in the receiving office's format. Engineering is 100% in-house. We establish the required engineering outputs with the subgrantee before production, so the office's submission structure is reflected in the records from the beginning.

## Make progress reports and payment evidence agree

Progress reporting explains the project's status against its accepted scope. Payment review evaluates a request under the agreement's payment terms. Those reviews may draw on the same field evidence, but they answer different questions. Before the first reporting period, we work through the meaning of each reported status with the team, especially where installed work still awaits testing or acceptance.

### Progress reports: define what each status means

A route marked complete can mean that placement has ended, that testing has passed or that the owner has accepted the segment. The office's definitions determine which meaning applies; where the reporting form leaves room for interpretation, ask the subgrantee to obtain clarification and retain it with the reporting instructions. We then map production statuses to those definitions instead of changing their meaning between submissions.

**Use the reporting cutoff consistently.** Field changes received after the cutoff belong in the next update unless the office directs a correction. The report needs to remain reproducible even as the live GIS database changes. Our retained submission files let the team recover the network it reported at that cutoff, rather than reconstructing it from later edits.

We favor an exception note that identifies the affected scope and explains the remaining dependency. A generic percentage cannot tell the office whether the unfinished portion awaits permission or needs engineering correction. Our [BEAD engineering compliance checklist](/blog/bead-subgrantee-engineering-compliance-checklist) provides a separate audit-oriented check of the engineering evidence supporting those submissions.

### Payment review: connect the request to supported work

The subgrantee's financial team owns its payment request and supporting financial records. Engineering supports the physical-work claims with the evidence required by the agreement. Our quantity reconciliation starts with the claimed work: if a request refers to installed route length, the supporting measurement should use the same scope boundary and measurement basis as the accepted milestone definition.

When quantities differ, retain the reason for the difference before correcting the submission. A design centerline measurement and an installation record can describe different things, especially where field routing departs from the original plan. We identify the engineering discrepancy for resolution. The office and the subgrantee's authorized team determine the payment treatment under the agreement.

**Payment attachments need their export history.** For each payment package, we retain the exact engineering files and their export version with the submission record described above. That history distinguishes a corrected attachment from the original and preserves the evidence sent for payment review.

## Why state broadband offices shape design and as-builts

The receiving format affects how engineers organize the underlying records. A portal may ask for a location-level attachment while the construction team works by route segment, so the design must maintain a reliable relationship between them. We establish that relationship before final drafting. Rebuilding it from PDF sheets at closeout introduces interpretation precisely where the office needs a reproducible record.

### Use the prescribed structure from the first export

Request the current schema and an accepted sample if one is available. Check the required coordinate reference system against the design environment, and confirm how the office expects location identifiers to be stored. A sample export lets us check for problems that simply opening the file will not reveal, such as a truncated identifier or a lost relationship between a record and its attachment.

Validation outside the production workspace tells us whether the exported files are ready for someone else to use. Confirm that a recipient can identify the intended revision without accessing the designer's folders. Our [BEAD GIS deliverables guide](/blog/bead-gis-deliverables) covers GIS formats and attributes in detail; this office-facing workflow uses the format specified for the actual subgrant.

**Preserve the reason for a field change.** An as-built should describe the installed network, while the accompanying change record explains its departure from the accepted design. We keep those purposes distinct. If a route detour changes the relationship to a service location, the record needs to show how the obligation remains addressed or where an approved scope change applies.

### Closeout: reconcile the final engineering package

Engineering closeout should leave the recipient able to trace the completed network back to the accepted project, so resolve open drawing comments and reconcile the final location set with the applicable scope. Our handoff record distinguishes acceptance from upload: a file in the portal can still have unresolved review comments, and its upload receipt alone cannot establish that the office accepted its contents.

Formal subgrant closeout remains the office's decision under the applicable award conditions. NTIA's BEAD Restructuring Policy Notice discusses closeout separately from service initiation and continuing federal obligations. While we resolve the final technical exceptions, the subgrantee needs to identify remaining administrative obligations with its grant team; delivery of the engineering package does not end the subgrant.

For handover, organize the accepted engineering records so the operator can retrieve the correct file without the original designer explaining it. The final drawing should remain linked to its supporting evidence and approval history, so the operator can follow the decisions behind the installed network. The subgrantee should confirm retention requirements from its governing documents and preserve access to the engineering package for as long as those requirements demand.

## Choose the next submission your team needs

**ISPs entering selection:** establish the proposed location set and preserve the submitted design basis. Request the office's technical attachments before expanding the design package. In our preparation work, questions about the receiving format belong at this stage, while the proposal is still editable and its structure can accommodate the award conditions as they become clear.

**Cooperatives and municipalities preparing delivery:** name the person responsible for obtaining written office decisions and connecting them to the engineering baseline. Separate that responsibility from drawing production. Your internal approval process should make it clear who can commit the organization to a scope change and who records the resulting technical revision.

**Engineers supporting an active subgrant:** test a sample submission against the required format, then keep the exported records synchronized with field changes. As part of that check, resolve identifiers before closeout. To find the right person to work with us, review the [Draftech partner responsibilities](/about) when selecting an engineering counterpart, and use our [contact page](/contact) to describe the package that needs support.

Draftech International delivers turnkey telecom and power infrastructure, with 100% in-house engineering and full turnkey construction delivered by Draftech-managed subcontract crews under Draftech's QA/QC. For this office-facing scope, we prepare the design and milestone-evidence packages that carry forward into as-builts and closeout. If inconsistent revisions are blocking that handoff, write to [info@draftech.com](mailto:info@draftech.com) with the required engineering format.

For an eligible route at the start of that work, the [free design offer](/free-design) provides engineering for the first 20,000 linear feet of a qualifying route at no cost, from feasibility and field survey through permit approval. The owner reviews each request before Draftech commits the package. That gives the initial engineering record a defined scope before it develops into the office-facing submission.

## Frequently Asked Questions

### How do I find the right state broadband office?

Start with NTIA's BroadbandUSA State and Territory Map, then confirm the contact on the office's current program website. NTIA identifies 56 BEAD Eligible Entities, so the relevant recipient can be a territory or the District of Columbia. Before sending project files, we confirm the technical submission channel: a public contact may direct questions to a separate program reviewer.

### Does the broadband office approve environmental review?

The office coordinates its responsibilities under the award, while NTIA retains the federal environmental decision role described in BEAD guidance. NTIA's BEAD Frequently Asked Questions and Answers, version 19, explains Eligible Entity screening and draft decision preparation for NTIA approval. For our engineering handoff, the project team needs to identify the specific clearance covering the proposed footprint before treating a segment as released.

### What should engineers request before preparing a submission?

Request the current technical attachments and the receiving office's file specifications before producing the submission package. Checking 1 sample export against those instructions helps us find identifier or coordinate problems while they are easy to correct. The sample is a production check, not an office approval, and the complete package still needs the review required by the subgrant agreement.

### Can the same engineering file support reporting and payment?

It can support both when its contents match the evidence each submission requires, but the subgrantee must apply the agreement's reporting and payment rules separately. Our approach is to retain 1 exact snapshot for each submitted package so a later database update cannot overwrite its basis. Engineering should identify the physical work supported by that snapshot while the responsible financial team handles payment certification.

### Is delivery of as-builts the end of a BEAD subgrant?

Delivery of as-builts completes an engineering handoff only when the required technical review and acceptance are satisfied. NTIA's June 6, 2025 BEAD Restructuring Policy Notice addresses formal closeout and continuing obligations separately from network service initiation. The subgrantee should confirm the remaining grant obligations with its responsible team while we finish the engineering records needed for its closeout package.