Congressionally-identified projects — CFDA 11.617 obligation totals

A $530.4M listing tagged as congressionally identified

USAspending.gov records $530.4M in obligations on assistance awards tagged 11.617. SpendingVault reprints that catalog total. The listing title names congressionally-identified projects. That title is a catalog label, not a vote tally and not a list of bill sections. The extract does not split the $530.4M by project type. This guide will not invent that split.

No fiscal year is attached. If a local press note cites a different “community project funding” total, match the CFDA number before adding that note to $530.4M. Other agencies’ congressionally directed listings are other catalog rows. Keep 11.617’s obligation sum on its own line. One hundred seventy-eight awards at this dollar scale is a mid-volume file of discrete projects rather than a formula run with tens of thousands of rows.

The packet has no median award size. Do not divide $530.4M by 178 and publish the quotient as a typical identified project. Amount-sort on the hub is the check. Project purpose — facility, research, or other — is not in the four-field extract. Award titles on the table are the place to see what USAspending stored.

178 awards on 135 recipient identifiers

One hundred thirty-five recipients hold 178 awards. That pairing is compatible with some organizations receiving more than one identified project or modification. The packet does not classify the 135 as cities, universities, or nonprofits. Award count is a row count; recipient count is distinct identifiers, not a count of ribbon-cuttings.

A 135-name list is large enough that search on the program hub helps. Repeat identifiers mean the same organization received more than one recorded award. Repeat appearance is not a finding about political preference. This page does not assign projects to members of Congress; those names are not in the packet.

40 states on the 11.617 extract

The file counts 40 states. That is wide coverage without claiming every jurisdiction in a 50-plus extract. The packet does not name the 40 or split the $530.4M among them. Place of performance may be a recipient headquarters even when the project site sits elsewhere. This packet does not say which location field fed the count.

Forty states is a coverage statistic, not a map of appropriations politics. Missing states are not listed, so their absence is not explained here. Use award-level place fields on the hub if a particular state is the question. This rollup will not rank jurisdictions by identified-project dollars.

Identified-project obligations are not outlays

Committee tables, explanatory statements, and local matching pledges are different ledgers. CFDA 11.617’s $530.4M is USAspending assistance-award obligations. Mixing a bill-text dollar figure into $530.4M, or treating $530.4M as cash already spent at a construction start, would mix ledgers. SpendingVault keeps the assistance-award definition.

Outlays are payments. Obligations are commitments. Directed projects can obligate and then draw over several years. This extract does not report outlays or completion status. Cite $530.4M as recorded commitments on 178 awards. Do not describe the sum as money already in a city’s construction account.

Not a government-wide earmark census

Congressionally directed spending appears under more than one CFDA number across agencies. CFDA 11.617 is this listing only. Adding its $530.4M to another agency’s directed-project CFDA would build a homemade “all earmarks” total the packet does not support. Keep congressionally-identified projects on their own row on the all-programs index.

Opening the 11.617 table

The Congressionally-Identified Projects program page lists the 178 awards and 135 recipients behind $530.4M. Filter by location if a state is the question; the 40-state count will not name them. Agency pages are a different USAspending cut; this packet does not name the awarding agency, so the $530.4M stays on the CFDA card. Member press releases remain a different file than this obligation rollup. Cite $530.4M only as the CFDA 11.617 obligation total on SpendingVault. Member press releases are not this USAspending obligation rollup. Cite $530.4M only as the CFDA 11.617 total on SpendingVault.

Questions

How much is obligated under CFDA 11.617?

CONGRESSIONALLY-IDENTIFIED PROJECTS show $530.4M in USAspending.gov obligations in SpendingVault’s extract. The figure is a commitment total, not outlays and not a member-by-member earmark table. The packet does not name requesting offices. USAspending.gov obligations on CFDA 11.617 are recorded commitments, not Treasury outlays.

How many congressionally-identified awards are in the file?

The extract lists 178 awards and 135 recipients. Award count is a row count; recipient count is distinct identifiers. The packet does not classify those recipients as cities, universities, or other entities. USAspending.gov obligations on CFDA 11.617 are recorded commitments, not Treasury outlays.

Which states appear on the 11.617 listing?

The file counts 40 states but does not name them or split the $530.4M by state. Location follows USAspending’s recorded fields. Use the 178-row table for award-level geography. USAspending.gov obligations on CFDA 11.617 are recorded commitments, not Treasury outlays.

Is $530.4M the amount already spent on those projects?

No. Obligations are commitments. Outlays are payments. The $530.4M on CFDA 11.617 is the obligation total. Completion status and local match are not in this packet. USAspending.gov obligations on CFDA 11.617 are recorded commitments, not Treasury outlays.