Every state broadband office, every BEAD subgrantee agreement, every Treasury Circular 570 surety is operating under the same NTIA Letter of Credit Waiver Notice — a programmatic waiver dated October 23, 2023 that lets a 100% performance bond substitute for the 25% bank LOC originally required by the BEAD NOFO. As of May 2026, 54 of 56 Eligible Entities have NTIA-approved Final Proposals. Subgrantee agreements are being signed now.
Telecom Performance Bonds: BEAD, FCC & OSP Contracts
This is not the IT performance bond you read about for SaaS rollouts or data-center SLAs. Telecom performance bonds underwrite physical infrastructure — outside-plant fiber pulls, tower erection, last-mile wireless, undersea landings, and NGSO satellite milestones. In 2026 the dominant question on this desk is BEAD, but the FCC NGSO milestone bond under 47 CFR § 25.165 and the state PUC continuous carrier bond (e.g., California PUC § 1013(f)) remain on the desk every week.
- BEAD
- 100% performance bond in lieu of 25% LOC; 54 / 56 states NTIA-approved
- FCC NGSO
- $1M initial, daily escalation, $5M cap at D=2,192 (47 CFR § 25.165)
- State PUCs
- Continuous carrier bonds — greater of $25K or 10% of intrastate revenue (CA)
Start your bondability letter
Three Federal Sources That Govern Telecom Bonds
Telecom bonding is not a single regulatory regime — it is a stack of NTIA, FCC, and Treasury rules that apply to different parts of the build. Here are the three primary sources every prospective bond principal should read before approaching a surety.
Official Federal (NTIA / BEAD) Requirements
"An Eligible Entity may accept a performance bond, valued at no less than one hundred percent (100%) of the subaward amount, in lieu of the letter of credit required by the BEAD NOFO, provided that the performance bond is issued by a company holding a certificate of authority as an acceptable surety on federal bonds, as identified in the Department of Treasury's Circular 570."NTIA BEAD Letter of Credit Waiver Notice — October 23, 2023 • BEAD NOFO Programmatic Waiver
Official Federal (FCC — Satellite) Requirements
"The bond amount shall be the sum of $1,000,000 plus $4,000,000 multiplied by the lesser of D/2192 and one, where D is the number of days that have elapsed since the date the application or petition was granted. Each licensee shall maintain on file with the Commission a surety bond in the proper amount payable to the United States Treasury."Code of Federal Regulations — 47 CFR § 25.165 • 47 CFR § 25.165 (NGSO Satellite Milestone Bond)
Official California (CPUC) Requirements
"Each holder of a Certificate of Public Convenience and Necessity (CPCN), Wireless Identification Registration (WIR), Interconnected VoIP registration, or Non-Dominant Interexchange Carrier (NDIEC) registration shall maintain a continuous performance bond in an amount equal to the greater of $25,000 or ten percent (10%) of the carrier's California intrastate revenues for the preceding calendar year."CPUC Decision D.10-09-017 & D.13-05-035 — California Public Utilities Code § 1013(f) • Cal. PUC § 1013(f)
State Broadband Offices: Who Is Issuing Bond-Required Subgrantee Agreements Right Now
NTIA writes the framework; each state runs the actual contracting. Four reference states with verified Final Proposal status — every one of them has accepted the surety-bond alternative under the NTIA waiver. (We deliberately omit unverified state-by-state bond mechanics here. If your state is not below, ask us and we will pull the broadband-office template directly.)
BEAD Active-Contracting Status — Reference States (May 2026)
Allocation, approval date, current phase, and bond pathway
| State | BEAD Allocation | Final Proposal Status | Bond Pathway |
|---|---|---|---|
| Texas (BDO, Comptroller) | $3.3 billion (up to) | NTIA-approved Dec 4, 2025 | 100% bond accepted in lieu of 25% LOC; 6-month execution window |
| California (CPUC) | $1.86 billion | Submitted to NTIA Dec 19, 2025; NIST pending | 100% bond accepted; subgrantee bond in addition to PUC § 1013(f) carrier bond |
| Virginia (DHCD Office of Broadband) | $1.48 billion | NTIA-approved November 2025 | 100% bond accepted; DHCD contract template public Aug 4, 2025 |
| Washington (WSBO, Dept. of Commerce) | $736.3M federal + $112.4M state | NTIA-approved Feb 27, 2026 | 100% bond accepted; construction expected to break ground 2026 |
Allocation figures from NTIA's June 30, 2023 Notices of Available Amounts and subsequent state press releases. Bond pathways follow the NTIA LOC Waiver Notice of Oct 23, 2023 and the BEAD Restructuring Policy Notice of June 6, 2025.
Sources: ntia.gov, broadbandusa.ntia.gov, comptroller.texas.gov, cpuc.ca.gov, dhcd.virginia.gov, commerce.wa.gov
The other 52 Eligible Entities (territories and remaining states) operate under the same NTIA framework. If your state is not listed above, the bond mechanics are identical — what varies is the milestone-reduction schedule each office writes into its own subgrantee agreement.
Who Actually Posts the Bond — ISP, OSP Contractor, or Both
BEAD has been live long enough that NASBP and the Surety & Fidelity Association of America published a formal Surety Bond Information Kit with two distinct bond forms. Picking the wrong one stalls your subgrantee agreement.
Form 1 — Single Obligee (ISP-Posted)
The BEAD subgrantee — the ISP that signed the award letter — furnishes the performance bond directly to the state broadband office. The state is the sole obligee. This is the cleanest structure and the default where the ISP itself qualifies for the full 100% of subaward bond. Underwriting hinges on the ISP's balance sheet, intrastate revenue history, and the technical team\'s build-out track record. Recurring revenue and the ETC or CPCN authority itself function as soft collateral.
Use when: The ISP has audited financials supporting the bond amount, an established surety relationship, and is doing the construction with in-house crews or a single tier-one subcontractor.
Form 2 — Dual Obligee (OSP-Contractor-Posted)
The outside-plant construction contractor — the firm actually pulling fiber, setting poles, or trenching — furnishes the bond. The obligees are both the ISP and the state broadband office. This form exists because the BEAD recipient (often a smaller regional ISP) does not always have the bonded capacity for a 100% subaward bond, but its general-contractor fiber partner does. The OSP contractor carries the construction risk anyway, so writing the bond on the contractor\'s paper is underwritably cleaner than forcing the ISP to qualify on someone else\'s job.
Use when: The ISP is a regional, EBITDA-positive but not investment-grade carrier, and the construction is being delivered by a national fiber contractor with established construction bonding.
The bondability letter step. Before either form is executed, the state broadband office expects a bondability letter from a Treasury Circular 570 surety committing to issue the bond and naming the dollar amount. State offices have made this a prequalification gate — applications without one have been ruled non-responsive. We issue these for qualifying applicants in 5-10 business days using the NASBP template.
FCC NGSO Satellite Bond — The Daily-Escalating Bond Nobody Else Covers
If your company has been granted authority to launch a non-geostationary satellite system — or has filed for U.S. market access on a foreign-licensed NGSO — 47 CFR § 25.165 requires a surety bond filed with the FCC within 30 calendar days of the grant. The bond is payable through the FCC to the United States Treasury and increases daily on a formula until milestones are met or you hit the $5 million ceiling at day 2,192.
47 CFR § 25.165 — NGSO Milestone Bond
47 CFR § 25.165. A = bond penal amount. D = days elapsed since grant of space station application or petition for U.S. market access. Capped at D=2,192 days (≈ 6 years), yielding the maximum $5,000,000.
What the formula actually means for your filing
The FCC built the daily-escalation mechanism to make spectrum warehousing economically painful. A licensee who sits on an authorization without launching watches its surety obligation climb every morning. The bond is required to be on file within 30 days of grant — most operators arrange the bond before grant so the filing is a same-day formality.
Two practical points the regulation does not advertise: first, you can satisfy the escalation either with a bond that contains an automatic-increase rider or with annual amended bonds — most sureties prefer the latter because it gives them an annual reunderwriting touchpoint. Second, the bond does not extinguish at milestone completion automatically; you have to formally request release once the FCC accepts your milestone certification.
This bond does not apply to ground-station builders, gateway antenna contractors, or terrestrial fiber crews working for the NGSO operator — they post standard contract bonds to private obligees.
BEAD Takes a Surety Bond. RDOF and CAF II Do Not.
The most expensive misconception in this corner of the market is that "all federal broadband programs accept surety bonds now." They do not.
BEAD — Surety Bond Accepted
NTIA issued a programmatic waiver on October 23, 2023 substituting a 100% performance bond for the 25% LOC originally required by the BEAD NOFO. The June 6, 2025 BEAD Restructuring Policy Notice preserved that pathway unchanged and only relaxed the LOC bank-rating standard (from Weiss B- to "well capitalized" or NRSRO BBB-). Any Treasury Circular 570 surety can write the bond.
RDOF / CAF II — Bank LOC Only
The FCC's Rural Digital Opportunity Fund (Auction 904, 2020) and Connect America Fund Phase II (Auction 903) both require an irrevocable standby letter of credit from an eligible bank — and the FCC has specifically declined to permit surety bonds in lieu. FCC Order 24-127 (December 13, 2024) modified LOC mechanics but did not open the door to surety. Same ISP, same fiber crew, two programs, two security instruments.
An ISP that won both an RDOF Auction 904 census-block-group award and a state BEAD subaward maintains a bank LOC on the RDOF buildout and a surety performance bond on the BEAD subaward simultaneously. Do not let a broker tell you the BEAD bond covers your RDOF obligation — it does not, and substituting it will trigger a USAC support suspension.
What a $10M BEAD Subaward Bond Actually Costs by Credit Tier
BEAD subgrantee bonds and OSP fiber-contractor bonds are underwritten the same way every other contract performance bond is — penal sum, then credit tier, then financial-statement strength. The rate bands below are industry-typical for Treasury Circular 570 carriers writing telecom infrastructure work at the $5M-$50M penal-sum range. The principal's personal-credit tier is one input; the corporate balance sheet, working-capital position, and bonding history move the final rate within (and occasionally outside) these bands.
Telecom Performance Bond — Annual Premium by Principal Credit Tier
Based on a $10,000,000 bond amount
- Investment-grade ISP / national OSP contractor (700+)Rate: 1.0% – 1.5%$100,000 – $150,000
- Regional carrier, audited financials (680–699)Rate: 1.5% – 2.0%$150,000 – $200,000
- Mid-size OSP contractor, reviewed financials (650–679)Rate: 2.0% – 2.75%$200,000 – $275,000
- Standard market — smaller carriers (620–649)Rate: 2.75% – 3.5%$275,000 – $350,000
- Sub-standard / SBA-backed (580–619)Rate: 3.5% – 5.0%$350,000 – $500,000
- Distressed credit / collateralized program (<580)Rate: 5.0% +$500,000 + (collateral typical)
Industry rate-band data for Treasury Circular 570 sureties writing BEAD subgrantee bonds and OSP fiber-contractor bonds in the $5M-$50M penal-sum range. Not a statutory or NTIA-published rate schedule. Actual quoted premium depends on the corporate balance sheet, working-capital ratio, bonded backlog, prior loss history, and the specific milestone-reduction schedule in the subgrantee agreement. The bond is annual; first-year premium is sometimes earned in full on multi-year obligations.
The principal's personal credit is a smaller input on a $10M BEAD bond than on a $50K license bond, but it never disappears entirely. Sureties pull personal credit on the owner(s) of any closely-held ISP or OSP contractor and roll it into the corporate underwriting tier. Where it matters most is at the breakpoint between tiers — a 695 score sliding to 698 in a soft-pull cycle can be the difference between a 1.75% and a 1.5% rate on a $25M subaward bond, which is real money over a four-year build.
From the Producer's Desk
How a Dual-Obligee BEAD Bond Actually Gets Drafted
A BEAD dual-obligee bond is a more involved drafting exercise than most contract performance bonds because the obligation runs in two directions at once. The principal is the outside-plant construction contractor. The obligees — both of them — are the BEAD subgrantee ISP and the state broadband office. The bond has to satisfy the construction contract between the ISP and the contractor and the subgrantee agreement between the ISP and the state at the same time. That means the penal sum is sized to the subaward (100% of federal BEAD funds flowing to the project), not the construction contract value — even though the construction contract is usually a smaller number once the ISP's own match and overhead are netted out.
What state broadband offices typically ask for during prequalification is narrower than people expect. They want three things in a bondability letter: (1) the surety's Treasury Circular 570 listing reference, (2) the dollar amount the surety is committing to write, and (3) the form — single-obligee or dual-obligee — the surety is willing to use. They do not, in the prequalification stage, ask for an executed bond. The executed bond is a closing condition on the subgrantee agreement, not an application requirement. Confusing the two slows projects down by weeks while ISPs ask for documents the state did not actually request.
The structural difference from an FCC milestone bond is worth naming explicitly. The 47 CFR § 25.165 satellite bond is a single-obligee instrument running to the U.S. Treasury through the FCC, escalates daily on a formula until launch milestones land, and never names a private party. A BEAD dual-obligee bond is essentially the opposite: fixed penal sum at 100% of subaward, two named obligees, and a milestone-reduction schedule keyed to the subgrantee agreement's deployment phases — which vary state-by-state. The bond rider that satisfies a calendar-quarter reduction in one state's template will not satisfy a percent-locations-passed reduction in another's. Read the milestone clause in your state's template (Virginia's is publicly posted on dhcd.virginia.gov as of August 2025) and have the surety draft the rider to mirror that exact mechanism before you sign. Drafting the rider after execution is dramatically more expensive than drafting it before.
Eric Drummond
Surety Bond Producer — Telecom & Infrastructure
- Nevada: License #pending issuance (May 2026) (Property & Casualty (all bond lines))
- ✓NASBP BEAD Working Group Participant
All content is researched from official state and federal sources (.gov) and reviewed by surety bond specialists. We maintain direct integrations with Treasury-certified surety carriers rated A- or better by AM Best.
Need a bondability letter this week?
Submit your subaward letter or RFP, and we will return a Treasury Circular 570 surety\'s written commitment for the prequalification round.
State PUC Continuous Carrier Bonds — The Other Telecom Bond
If you operate as a CLEC, MVNO, interconnected VoIP provider, or NDIEC carrier in California, you carry a permanent bond at the state — separate from anything BEAD-related. Most state PUCs have analogous requirements; California is the most fully documented and serves as the operational template.
California CPUC — Continuous Performance Bond
- Bond Amount
- Greater of $25,000 per Utility ID Number or 10% of prior-year California intrastate revenues (per CPUC User Fee Statement).
- Filing Deadline
- March 31 each year, via Tier 1 advice letter to CDcompliance@cpuc.ca.gov.
- Bond Type
- Continuous bond (no termination date), issued by a corporate surety authorized to transact business in California.
- Statutory Authority
- California Public Utilities Code § 1013(f), implemented by CPUC Decisions D.10-09-017, D.11-09-026, D.13-05-035, and D.24-11-003.
- Who Files
- All CPCN holders, WIR registrants, Interconnected VoIP carriers, Nomadic registrants, NDIEC holders.
- Obligee
- California Public Utilities Commission.
Other state PUCs have similar continuous-bond requirements for telecom carriers, but amounts and filing mechanics vary materially. We do not publish unverified state amounts on this page — call us with your operating-state list and we will pull the current requirement directly from each PUC for you.
BEAD, FCC, and state PUC bond questions our desk gets weekly
Will the October 2023 NTIA waiver apply to my state's BEAD subaward?
Why does the bond have to be 100% of the subaward when the original LOC was only 25%?
Is my SpaceX or Kuiper ground-station construction subject to the FCC milestone bond?
What is a "bondability letter" and why is my state asking for one before I have a subaward?
My company holds a CPUC CPCN — do I post a separate bond for that on top of any BEAD bond?
Can I use a single surety bond for an RDOF buildout or only for BEAD?
Related Bonds & Cross-References
Telecom bonding sits at the intersection of federal contracting, FCC licensing, and state utility regulation. These are the adjacent pages on this site.
Official Government Sources
The foundational document authorizing 100% performance bonds as an alternative to the 25% LOC.
Most recent BEAD policy update — retains the bond alternative, relaxes LOC bank-rating standard.
The NGSO milestone-bond regulation, including the $1M initial / $5M cap escalation formula.
California carrier continuous-bond requirements under PUC § 1013(f); annual March 31 filing.
The annually-published list of acceptable sureties for federal bonds, including BEAD bonds.
Next steps — this week
Four moves between you and a signed subgrantee agreement
Bondability letters are not slow because surety underwriting is slow. They are slow because BEAD applicants send the wrong documents or skip a prerequisite. Run these four in order and a Treasury 570 carrier can be back on your application in five to ten business days.
- 1
Pull your state broadband office's subgrantee agreement template
Texas, Virginia, Washington, and California have all published draft or final templates. The milestone-reduction schedule and bond rider language live inside that document, and they are not standardized state-to-state. Read the bond-form section before you size the bond.
- 2
Decide single-obligee or dual-obligee — before the surety call
If the ISP self-performs, the bond is Form 1 (single-obligee, ISP-posted). If a national OSP contractor does the build, the bond is almost always Form 2 (dual-obligee, contractor-posted, ISP + state broadband office as co-obligees). Picking before the underwriting call cuts a full week.
- 3
Send three years of audited (or reviewed) financials
Treasury 570 carriers will underwrite a BEAD bond on three-year audited financials in five to seven business days. Reviewed financials add three to five days. Compiled-only financials at the $10M+ penal-sum range require either SBA backing or a personal-indemnity-plus-collateral structure.
- 4
Request the bondability letter — not the executed bond
State broadband offices require a bondability letter at prequalification. The executed bond is a closing condition on the subgrantee agreement, not an application requirement. Asking the surety for the bond too early stalls the file; asking for the letter early is exactly the right move.
Ready to start step 4?
Treasury Circular 570 sureties only. Letters in 5–10 business days for qualifying ISPs and OSP contractors.