All BEAD news
BEAD UpdateSouth CarolinaJuly 7, 2026

South Carolina cuts planned BEAD subgrantees from 16 projects to 8

South Carolina announced that eight of the 16 BEAD projects it originally planned will instead be funded using existing state and federal ARPA resources rather than BEAD dollars, halving the program's subgrantee list. The move reflects the state's determination that it no longer needs the full slate of BEAD awards it had planned.

What this means for BEAD compliance

ISPs originally slated for the 8 South Carolina BEAD projects now to be funded via state/ARPA sources, and the remaining 8 providers still on the BEAD subgrantee list.

Providers whose projects shift to state/ARPA funding exit the BEAD compliance regime entirely, meaning federal BEAD-specific obligations such as SCRM equipment certification, NEPA/environmental screening, and NIST CSF cybersecurity controls no longer apply to those projects, though state ARPA reporting and cost-documentation rules likely still govern them. The 8 providers remaining on the BEAD list continue toward subgrant agreement execution, so pre-award requirements around environmental compliance, internal controls, and covered-equipment certification remain in force and unaffected by this reduction. Compliance officers for affected providers should confirm which funding source now governs their project and adjust internal tracking accordingly, since dual-track (BEAD vs. ARPA) recordkeeping errors could create audit exposure.

Phase 2 · Award ReadinessSCRM-008ENV-001-6FIN-005-16

Analysis by BeadComply Compliance Intelligence, grounded in the BEAD requirements registry.

Read the source: Web search sweep

Won a BEAD award in South Carolina? See South Carolina's program status and compliance requirements →

Get BEAD news like this in your inbox