Safe Streets and Roads for All — CFDA 20.939 obligation totals

A $537.0M safety-grant file with 797 rows

USAspending.gov records $537.0M in obligations on assistance awards tagged 20.939. SpendingVault reprints that catalog total. An obligation is a federal commitment on the award. It is not a police-overtime ledger, not a construction-draw register, and not a Vision Zero scorecard. The listing title names Safe Streets and Roads for All; the extract does not split action-plan awards from implementation awards inside the $537.0M. This guide will not invent that split.

No fiscal year is attached. If a city safety plan cites a different federal total, match the CFDA number before adding that plan to $537.0M. Other highway-safety listings are other catalog rows. Keep 20.939’s obligation sum on its own line. Seven hundred ninety-seven awards at this dollar scale is a high-volume competitive file relative to the 16-row railroad listing a reader may have seen nearby on the index — nearby in dollars, not in purpose.

The packet has no median award size. Do not divide $537.0M by 797 and publish the quotient as a typical Safe Streets grant. Amount-sort on the hub is the check for a tail of large implementation awards. Countermeasure type — speed, pedestrian, or other — is not in the packet.

797 awards and 763 recipients, nearly one-to-one

Seven hundred sixty-three recipients hold 797 awards. The two counts are close, which is compatible with many local governments or MPOs receiving a single recorded award. The packet does not publish that as an official ratio and does not classify the 763. Award count is a row count; recipient count is distinct identifiers, not a count of intersections treated.

A 763-recipient list is large enough that search on the program hub helps. Repeat identifiers among the extra 34 award rows, if they exist, mean the same organization received more than one recorded award. Repeat appearance is not a safety-performance finding. Crash diagrams and project as-builts are not in this extract.

50 states on the Safe Streets extract

The file counts 50 states. That is nationwide coverage in this extract’s sense, without the extra jurisdictions some other CFDA lines show. The packet still does not list the states or split $537.0M among them. A 50-state count is not proof of equal per-capita safety aid, and it is not a league table of cities.

Place of performance for a county award may be the county seat. Place of performance for an MPO award may be the host city. This packet does not say which location field fed the count of 50. Use award-level geography on the hub if a particular city is the question. Do not read 50 as a guarantee that every municipality received an award.

Safety-grant obligations are not lives-saved outlays

Fatality Analysis Reporting System counts, state crash files, and local Vision Zero dashboards are different datasets. CFDA 20.939’s $537.0M is USAspending assistance-award obligations. Mixing that sum with a predicted-lives-saved model would claim results this file does not contain. Match the metric before comparing this CFDA line to a safety-plan appendix.

Outlays are payments. Obligations are commitments. Implementation projects can draw after the obligation date. This extract does not report outlays or crashes reduced. Cite $537.0M as recorded commitments on 797 awards. Do not describe the sum as money already in a public-works construction account.

Not a combined highway-safety catalog

Other traffic-safety and highway listings can sit near 20.939 on the all-programs index because their obligation totals occupy a similar band. Similar scale is not similar purpose. Do not add this $537.0M to a different CFDA to build a homemade “all road safety” figure. Keep Safe Streets and Roads for All on its own catalog row.

Opening the 20.939 table

The Safe Streets and Roads for All program page lists the 797 awards and 763 recipients behind $537.0M. Filter by location if a state is the question; the 50-state count will not name them. Agency pages are a different USAspending cut; this packet does not name the awarding agency, so the $537.0M stays on the CFDA card. Crash-reduction factors remain a different file than this obligation rollup. Cite $537.0M only as the CFDA 20.939 obligation total on SpendingVault.

Questions

How much is obligated under Safe Streets and Roads for All?

CFDA 20.939 shows $537.0M in USAspending.gov obligations in SpendingVault’s extract. The figure is a sum of assistance-award commitments, not Treasury outlays and not a count of crashes avoided or streets rebuilt. USAspending.gov obligations on CFDA 20.939 are recorded commitments, not Treasury outlays.

How many Safe Streets awards are in the extract?

The file lists 797 awards and 763 recipients. The two counts are close. Award count is a row count; recipient count is distinct identifiers. The packet does not classify those recipients as cities, MPOs, or other entities. USAspending.gov obligations on CFDA 20.939 are recorded commitments, not Treasury outlays.

Does CFDA 20.939 appear in every state?

The extract counts 50 states. It does not name them or split the $537.0M by state, and it does not prove that every city received an award. Use the 797-row table for award-level geography. USAspending.gov obligations on CFDA 20.939 are recorded commitments, not Treasury outlays.

Is $537.0M the amount already spent on safety projects?

No. Obligations are commitments. Outlays are payments. The $537.0M on CFDA 20.939 is the obligation total. Construction draws and crash-outcome metrics are not in this packet. USAspending.gov obligations on CFDA 20.939 are recorded commitments, not Treasury outlays.