What counts as an unserved location under BEAD eligibility rules
If you've spent any time in a BEAD challenge window, you already know the term "unserved" carries a specific legal weight, not a general sense of "nobody out there has internet." The definition comes straight from NTIA's BEAD Notice of Funding Opportunity, and it hinges on two things: the speed a location can get, and whether that location sits in the FCC's broadband serviceable location fabric at all.
The speed thresholds that define unserved vs underserved
Under BEAD, a location is unserved if it lacks access to reliable broadband at 25 Mbps download / 3 Mbps upload, or has no wireline/fixed wireless service at all. A location is underserved if it gets at least 25/3 but can't reach 100 Mbps download / 20 Mbps upload. Anything at or above 100/20 counts as served and falls out of BEAD priority scoring.
That three-tier split matters because BEAD funds flow to unserved locations first, underserved second, and only after those are substantially addressed does money move to community anchor institutions and other eligible uses. If you're ranking areas for a subsidy bid, getting a location bumped from "underserved" to "unserved" (or the reverse) can change whether it clears the funding threshold at all.
A location also has to be "reliable" to count against it. A technology that's nominally capable of 25/3 but doesn't deliver it consistently (think oversubscribed fixed wireless or satellite with high latency) doesn't knock a location out of unserved status just because a provider claims coverage there.
Served vs underserved comes down to the location fabric, not the county
Older subsidy programs scored eligibility by census block: if one household in a block had service, the whole block could get marked served, even if the next ten houses had nothing. BEAD threw that model out. Eligibility is now assessed location by location, against the FCC's Broadband Serviceable Location (BSL) fabric, a dataset of individual structures built by CostQuest and licensed to the FCC.
That's a real improvement over census-block eligibility, but the fabric is still a snapshot. It gets updated on its own cycle, and it was built from parcel and address data that doesn't always keep pace with where people live now. New subdivisions, infill lots, manufactured home parks that went in after the fabric's last refresh, informal settlement clusters on unaddressed roads: these show up late, show up wrong, or don't show up at all. If a cluster of twelve households isn't in the fabric, it can't get scored as unserved, no matter how bad its service is.
Where this trips up coverage planners doing the ranking
This is the gap that matters when you're the one ranking areas for build priority or writing a challenge. The BDC data tells you what providers claim to serve. The fabric tells you where locations officially exist. Neither one tells you what's actually built on the ground right now, which is the thing a challenge process or a state's own prioritization model ultimately has to defend.
Planners end up stitching together the fabric, provider-reported coverage, and whatever parcel or imagery data they can get their hands on, then manually checking the areas that look off. That's slow, and it's easy to miss a cluster that grew up in the two years since the fabric's source data was collected.
A settlement layer built off a current high-resolution pass over the target region gives you something to check the fabric against: every cluster that's built, sized and located, independent of whatever address list fed the official fabric. That's the gap Settlement Mapping is built to close, by turning an annual satellite pass into a settlement-by-settlement view you can compare directly to the BSLs you're being asked to rank.
If your BEAD challenge or state prioritization work keeps running into locations the fabric missed, it's worth seeing what a current settlement layer for your region shows.