BEAD broadband obligations in Washington

One prime award carries Washington’s BEAD allocation

This tie keeps USAspending assistance where CFDA 11.035 meets Washington place of performance. The dollar book is $1,227,742,066. The award count is 1. BEAD state allocations typically post as a single large award to the designated state recipient. One prime record does not mean one ISP was selected, and it does not isolate the Olympic Peninsula from the Palouse.

The join does not prove that Washington’s unserved-location count, rural density, or a particular middle-mile map caused $1,227,742,066. Those are other series. This packet has no project list. Correlation is not causation. Packet facts stop at $1,227,742,066, 1 award, WA, and 11.035.

11.035 is not FCC High Cost USF

Universal Service Fund High Cost (CFDA 32.002) is a different catalog. Mixing USF into $1,227,742,066 would invent a broader telecom total than this cell contains. Facts available: Washington, CFDA 11.035, $1,227,742,066, 1 award. FCC map locations and ISP subawards are not in the facts.

With one award, the implied mean equals $1,227,742,066. Downstream subawards to ISPs are not additional prime awards in this extract. Unique recipients are unpublished. 1 is not a count of passing addresses.

Washington geography on the BEAD tag

WA is the place-of-performance code. A statewide BEAD award can still appear as one record tagged to Olympia or another in-state address. Awards coded to Oregon, Idaho, or Alaska stay outside $1,227,742,066 even when a network plan crosses those borders. The code does not convert $1.23 billion into a fiber map.

Washington federal spending is the all-program parent. 11.035 is one row on Washington programs. $1.23 billion is not the state’s complete federal footprint. Open Broadband Equity, Access, And Deployment Program in Washington for the filtered table, CFDA 11.035 for 11.035 without a Washington filter, and All spending ties for other pairs. Do not add those parents into $1,227,742,066.

Reading n = 1 under Washington BEAD

One award under $1,227,742,066 implies a mean of $1,227,742,066. With a single row, mean and total are the same number. Construction draws can lag the federal obligation by years. The figure is still an obligation aggregate, not an outlay.

Treat 1 as a record count in an aggregate, not as 1 finished last-mile project. Later ingests can restate $1,227,742,066 without changing the join key of 11.035 and WA. Without a transaction register, you cannot see whether the row is a continuation, renewal, or correction.

What the BEAD–Washington pair does not prove

A large 11.035 total tagged to Washington does not measure whether unserved locations fell, and it does not equal miles built. FEC donations do not fund this USAspending cell. Correlation is not causation. The headline remains $1,227,742,066 on 1 award for BEAD in Washington.

Keep both sides of the join: Broadband Equity, Access, and Deployment and Washington, obligations only. Do not annualize $1,227,742,066 without a year field—this packet publishes none. Quote USAspending.gov and the overlay path rather than a construction story.

Using the BEAD–Washington overlay

The overlay target is the Washington × CFDA 11.035 table. Open Broadband Equity, Access, And Deployment Program in Washington when you want the same $1,227,742,066 / 1-award cell in the site’s data chrome. CFDA 11.035 drops the Washington filter. Washington federal spending drops the CFDA filter. Washington programs lists other catalogs beside BEAD. All spending ties indexes other pairs.

This page exists because two tables meet: a CFDA program and a place-of-performance state. It does not exist to argue that Washington won or lost federal money, that donations paid for the awards, or that obligations equal cash. The pair is 11.035 plus WA. Obligations of $1,227,742,066 are not outlays. Cite Broadband Equity, Access, And Deployment Program together with Washington whenever you reuse $1,227,742,066. 1 remains an award-record count on USAspending.gov, not a person, facility, or project census. Obligations of $1,227,742,066 are not outlays. The overlay path is the live table for this 11.035 × WA cell. Later bulk files can restate $1,227,742,066 without changing the join key.

Questions

How much BEAD spending is in Washington?

USAspending.gov shows $1,227,742,066 in CFDA 11.035 obligations coded to Washington across 1 award. The join uses the program number and Washington place of performance. The total is obligations, not outlays. Keep Broadband Equity, Access, And Deployment Program and Washington together when citing $1,227,742,066.

Why is there only 1 award for about $1.23 billion?

BEAD state allocations often post as a single large prime award to the designated state recipient. The extract counts 1 record tagged to CFDA 11.035 and Washington. With one award, the implied mean equals the total: $1,227,742,066.

Is $1.23 billion Washington’s full federal spending?

No. $1,227,742,066 is only the BEAD cell. Other CFDA programs with Washington place of performance sit on the statewide hub. Nationwide 11.035 is not limited to Washington. Obligations of $1,227,742,066 are not outlays.

Do these obligations equal broadband construction completed?

No. $1,227,742,066 is an obligation sum. Outlays are a different USAspending series. Construction draws can lag the federal obligation by years. This packet has no fiber-mile count. Original filings remain on USAspending.gov for this 11.035 × WA pair.