Stacking BEAD With RDOF, A-CAM, and State Grants: A Non-Duplication Field Guide for Small Carriers

By now most rural ILECs and small CLECs have at least one BEAD subgrant application open, in negotiation, or already under contract with a state broadband office. The pitch from the state offices is usually the same: BEAD will close the gap that earlier programs left behind. In practice, the gap is rarely empty. If you have been operating in your serving area for more than a decade, some portion of that footprint is already touching RDOF auction obligations, A-CAM model support, CAF-BLS broadband loop support, USDA ReConnect awards, or one of a dozen state matching programs that predate IIJA.

That overlap is where non-duplication clauses bite. Every BEAD program is operating under NTIA’s Notice of Funding Opportunity, and every state office has translated that NOFO into its own subgrant agreement. The clauses look similar but are not identical, and the consequences of getting the math wrong — claw-back, support reduction, or being declared ineligible mid-build — fall on the operator, not on the agency.

This is a peer-level overview, not regulatory or legal advice. Figures, deadlines, and cost-recovery mechanics in any of these programs change. Confirm specifics with NTIA, your state broadband office, USAC, and your tariff advisor before you sign anything or amend a filing. Pool participation rules and settlement outcomes vary by state and by your specific tariff.

The three overlap zones to map before anything else

Before you can answer “are we double-dipping?” you need a clean picture of what every existing dollar in your footprint already paid for. We see three overlap zones cause the most trouble.

The first is the locations layer. RDOF is location-based, BEAD is location-based, and the FCC’s National Broadband Map fabric is the source of truth for both — but the fabric updates on a cycle that does not match your application timing. A location that was unserved on the fabric vintage your state office used may now show as served on the version NTIA queried. Pull the exact fabric vintage referenced in your subgrant offer and reconcile it against your own GIS. Document the version number. If the state office and NTIA are working from different vintages, raise it now, not after award.

The second is the support layer. A-CAM and CAF-BLS support flows monthly through USAC. RDOF support flows monthly. BEAD pays out as a one-time capital subsidy against an approved buildout milestone schedule. The non-duplication question is not “do these dollars cover the same plant?” — it is “do they cover the same eligible cost element on the same location?” Many state subgrant agreements force you to net out the present value of expected ongoing high-cost support from the BEAD eligible cost basis. That nets your award down. It also means your model has to project A-CAM out to its term, which gets harder as the FCC continues working through the Enhanced A-CAM transition.

The third is the obligation layer. RDOF carries deployment milestones, performance tier obligations, and Letter of Credit requirements that survive a BEAD overlay. If you accepted RDOF for a census block group and now want to use BEAD to upgrade the same plant to a higher service tier, you cannot use BEAD to substitute for the buildout you were already obligated to complete under RDOF. You can use BEAD to upgrade beyond what RDOF required — but only if the cost split is defensible.

The honest limitation here: every state office is interpreting the overlap differently as of publication, and several have published draft policies that have not been finalized. Treat anything below as a starting point, not a final answer.

The non-duplication clause, in plain language

Read the actual subgrant agreement, but here is the pattern most state offices are using as of publication. A subgrantee may not receive BEAD funds for any cost that has been or will be reimbursed by another federal source for the same project at the same location, unless the funding sources are explicitly stackable per NTIA guidance. The subgrantee is responsible for tracking and disclosing all other federal, state, and private contributions used at any covered location, and must maintain records sufficient to demonstrate that no cost was paid twice from public sources.

Three operational implications fall out of that.

You need a per-location cost ledger, not a project-level one. If your engineering and accounting systems can only allocate cost at the project or work-order level, you will not be able to produce the records the agreement requires. Fixing this after a build is in flight is painful and expensive.

You need a defensible cost-allocation method when one piece of plant serves both a BEAD location and a non-BEAD location. Pro-rata by passings count is the most common approach state offices accept, but some require a more granular allocation for shared transport. Get the method approved in writing before construction starts.

You need to track in-kind contributions and tax abatements as if they were cash. Several states are treating local property-tax abatements and right-of-way fee waivers as program income that has to offset the BEAD basis. Your cooperative or municipal partners may not realize this when they offer the abatement, and the disclosure is on you.

Where small operators get tripped up

A few patterns we see repeatedly in conversations with small ILECs and CLECs working through subgrant offers right now.

Treating an LOI like an award. A letter of intent or preliminary award notice from a state office is not a binding obligation on either side and does not constitute “expected federal support” you can plug into your A-CAM or RDOF compliance models. Wait for the executed subgrant agreement before you adjust other filings.

Mis-mapping CAF-BLS lines into the BEAD project area. CAF-BLS supports the loop, not the location’s broadband service tier. A line that draws CAF-BLS support is not automatically a “served” or “underserved” location for BEAD purposes — but a sloppy crosswalk will make it look that way to a reviewer. Build the crosswalk explicitly and document the assumptions.

Overlooking the matching-fund treatment. NTIA and most state offices require a 25% match unless you qualify for a high-cost area waiver. Match dollars from another federal program generally do not count toward that 25%. Match dollars from a state program may or may not count, depending on the state’s rules and on whether the underlying state appropriation drew federal pass-through. This is a tariff-advisor question, not a vendor question.

Letting the engineering schedule drift past the four-year buildout window. The four-year deployment requirement is measured from subgrant execution, not from the day the state office sends an LOI. Sandbagging early activity to align with construction season is fine; assuming you have an extra winter on the back end is not.

Caveat: every one of these patterns has exceptions in specific state programs and specific NTIA waivers. Do not generalize from this list — use it as a prompt to ask the right questions of your own subgrant officer and your regulatory counsel.

A short pre-signing checklist

Before you countersign a BEAD subgrant, walk through this with your engineering, accounting, and regulatory functions in the same room. Anything you cannot answer in writing is something to push back to the state office before signature.

• What fabric vintage is this award based on, and how does it reconcile against our own GIS?
• For each location in the award, what other federal or state support touches it today, and through what date?
• What is the state’s required cost-allocation method for shared plant, and is our method approved in writing?
• What ongoing high-cost support, if any, must be netted against the BEAD basis, and what discount rate is the state prescribing?
• How will RDOF, A-CAM, or USDA obligations be treated where they overlap with the BEAD service tier?
• What is the buildout milestone schedule, and what triggers a draw versus a milestone certification?
• What records must we keep per location, and for how long after project closeout?

If the state office cannot give written answers to these questions, that is itself useful information — it tells you the subgrant team is working from policy that has not finished baking. Slow down. The honest limitation: even a state office that answers all of this confidently today may have to revise once NTIA issues additional guidance, so build amendment-friendly language into your internal models.

How OneCloud fits in

We provide wholesale origination and termination, tandem-side IP interconnection, and rural number-portability support to ILECs and CLECs across the lower 48. None of that replaces a tariff advisor or regulatory counsel — but if you are sizing a BEAD build and need to model the IP interconnect layer, the wholesale voice layer, or the LNP and LERG operations that come along with serving newly built locations, that is a conversation we have most weeks. Talk to our wholesale team or see our ILEC/CLEC interconnect options for what we offer at the operator tier.

If you are still mapping the basics of where you sit in the carrier landscape, our carrier services overview is a useful starting point, and our 2026 compliance checklist for LNP, E911, CNAM, and STIR/SHAKEN covers the operating obligations that ride alongside any new buildout. For peers working through the funding-and-modernization tradeoffs at the same time, the companion piece on NECA settlements and FCC filings during switch modernization lays out the regulatory mechanics on the legacy side that BEAD work tends to disturb.

Reach the wholesale desk at 844-450-3527 or via the form on the carriers page. Operator-to-operator only.