BEAD vs RDOF vs ARPA — which federal broadband program fits your network?

Three federal programs have funneled hundreds of billions of dollars into rural broadband infrastructure over the last five years: BEAD (Broadband Equity, Access, and Deployment), RDOF (Rural Digital Opportunity Fund), and ARPA (American Rescue Plan Act). All three are active in some form in 2026. Each has a different source, timeline, reporting requirement, and operator profile.

Here's the breakdown of what each program is, who it applies to, and what it means for your fiber network management and compliance workflow.

BEAD — $42.45 billion, currently in sub-grant procurement

BEAD is the big one. Passed in the Infrastructure Investment and Jobs Act in 2021, the $42.45B program is administered by NTIA and distributed through State Broadband Offices. As of May 2026, every state has cleared NTIA's Initial Proposal phase and most are in active sub-grant procurement — selecting the providers who'll receive funding to deploy fiber to unserved and underserved locations.

• ·Status: Active sub-grant procurement in most states.
• ·Eligible operators: ISPs, electric coops, municipalities, tribal organizations — anyone who can commit to building to unserved/underserved locations.
• ·Reporting: Per-location build status, activation dates, GPS-linked evidence, audit trails. State-specific formats.
• ·Challenge process: 30–45 day challenge windows per state when eligibility fabric updates are published.
• ·Technology preference: Fiber is the preferred technology for BEAD. Fixed wireless may be used in specific cases.

BEAD requires the most sophisticated fiber GIS compliance workflow of the three programs. Eligibility maps, challenge process management, per-location build tracking, and quarterly state submissions all require structured, queryable, spatially-aware data.

RDOF — $20.4 billion, awarded in 2020, in active deployment

RDOF (Rural Digital Opportunity Fund) is an FCC program awarded in two phases. Phase I ($9.2B) was awarded in December 2020; Phase II was smaller and more targeted. RDOF recipients committed to serving specific Census blocks with defined service tiers by specific deadlines.

• ·Status: Active deployment. Most recipients are in mid-build or nearing milestone deadlines.
• ·Eligible operators: Winning bidders from the 2020 auction — a fixed, closed set of operators.
• ·Reporting: Quarterly milestone reports to the FCC. Location-fabric aligned deployment tracking.
• ·Deadlines: Phased deployment milestones (40%, 60%, 80%, 100% of locations) by specific dates varying by award.
• ·Risk: Some RDOF winners have defaulted on awards. Remaining award reallocations are possible.

If you're an RDOF recipient, your compliance workflow centers on FCC location-fabric aligned quarterly reporting. The penalty for missing milestones is financial — letter of credit draws — so the reporting timeline is non-negotiable.

ARPA — $350 billion total (with broadband-eligible portions), mostly awarded

ARPA (American Rescue Plan Act, passed March 2021) provided funding through multiple Treasury channels, most relevantly the State and Local Fiscal Recovery Funds (SLFRF) and Capital Projects Fund (CPF). States, counties, and cities could use SLFRF funds for broadband infrastructure; CPF provided $10B specifically for broadband.

• ·Status: Awards largely made in 2021–2022. Most recipients are in active construction or have completed builds.
• ·Eligible operators: Varied — ARPA flowed through state and local governments to sub-recipients, which could include ISPs, coops, and municipalities.
• ·Reporting: Quarterly Treasury reports. Project milestone tracking. Less complex than BEAD's per-location format.
• ·Deadline: ARPA funds must be obligated by December 2024 and spent by December 2026.

Side-by-side comparison: BEAD vs RDOF vs ARPA

• ·Total funding: BEAD $42.45B | RDOF $20.4B | ARPA $350B total ($10B broadband-specific)
• ·Status in 2026: BEAD active sub-grant procurement | RDOF active build-out phase | ARPA mostly deployed
• ·Eligible operators: BEAD — ISPs, coops, municipalities, nonprofits | RDOF — ISPs, coops | ARPA — municipalities, counties, states
• ·Coverage requirement: BEAD — unserved (<25/3 Mbps) + underserved (<100/20 Mbps) | RDOF — unserved (<25/3 Mbps) | ARPA — flexible
• ·Speed standard: BEAD — 100/100 Mbps minimum, 1 Gbps preferred | RDOF — 25/3 Mbps minimum, 100/20 Mbps preferred | ARPA — flexible, typically 25/3 Mbps minimum
• ·GIS requirement: BEAD — per-location FCC fabric matching, immutable audit trail | RDOF — location-level reporting | ARPA — flexible, NTIA-guided
• ·Challenge process: BEAD — formal 30-day window per state | RDOF — completed | ARPA — none formal
• ·Reporting: BEAD — quarterly per-location progress | RDOF — semi-annual | ARPA — annual Treasury reporting

Can you stack BEAD and RDOF? The overlap rules explained

BEAD and RDOF cannot fund the same location. An address that received RDOF funding is considered 'served' from BEAD's perspective and is generally excluded from BEAD eligibility — the RDOF award is treated as evidence that a provider committed to serve that location. However, if an RDOF recipient defaults or returns funding, those locations may become BEAD-eligible. This is an active issue in several states where early RDOF winners have returned or forfeited awards.

ARPA and BEAD can stack on a project level (different phases), but cannot fund the same location twice. Operators who used ARPA funding for fiber builds may face BEAD eligibility challenges for those locations unless the ARPA build was specifically scoped to exclude them. NTIA has issued guidance on this, but state programs vary in how they interpret the overlap rules.

GIS requirements by program: what your data must look like

• ·BEAD: Per-location FCC fabric IDs, GPS-accurate coordinates, per-location activation timestamp, immutable audit trail, state-specific polygon format, challenge-ready evidence (photos, GPS, dates)
• ·RDOF: Location-level build status reporting, FCC Form 477 census-block coverage data, subscriber-count reporting by area
• ·ARPA (Treasury): Address-matched coverage data, per-location service confirmation, annual progress reporting, income/demographic eligibility data for ARP equity requirements

Which program applies to your network?

The programs aren't mutually exclusive — an operator might have RDOF obligations from 2020 while simultaneously bidding for BEAD sub-grants in 2026. But the compliance priorities differ:

• ·If you won RDOF in 2020 and are in deployment: RDOF quarterly milestone reporting is your active obligation. BEAD may apply to locations your RDOF award didn't cover.
• ·If you received ARPA funding in 2021–2022: Your build should be in progress or complete. Treasury quarterly reports are ongoing. The December 2026 spend deadline is approaching.
• ·If you haven't yet received federal funding: BEAD sub-grant procurement is where the current opportunity is. Preparing structured fiber GIS data now — before the challenge process opens in your state — is the right move.

MapItRight supports all three programs with dedicated reporting templates. See /solutions/broadband-mapping-bead for the full BEAD compliance workflow, or book a demo if you want to see how the compliance module handles your specific program obligations.