USAspending Contracts obligations — $4.98 trillion
Federal contracts in USAspending.gov award files carry $4,975,819,796,721 in obligations. SpendingVault indexes that sum as an obligation total, not a Treasury outlay series. The same award_type_code group holds 11,255,726 contract records — a high row count relative to the dollar book, because procurement files stack orders and modifications. This packet does not name a fiscal-year window.
Key figures
- Contracts obligations in the indexed USAspending files total $4,975,819,796,721.
- The contract group contains 11,255,726 award records, about $442,070 per record as a scale check.
- The $4,975,819,796,721 is obligations, not Treasury outlays.
- The 11,255,726 count is award actions, including orders and modifications, not unique vendors.
- This packet does not name a fiscal-year window; cite the indexed roll-up, not an invented FY label.
What $4,975,819,796,721 of contract obligations measures
The contract headline is $4,975,819,796,721. USAspending.gov files that amount under the contract award_type_code family: procurement of goods and services. The government is the buyer. A vendor delivers a product, a construction job, a professional service, or another contracted output. That is a different legal instrument from a grant, a loan, a Direct Payment, or the residual other-assistance group. The $4,975,819,796,721 is the procurement family's obligation book, not a blended awards total.
An obligation on a contract is the amount the government has committed on the award action. It is not an invoice paid and it is not an outlay. Partial deliveries, options, and de-obligations can leave cash and commitment far apart. This page keeps $4,975,819,796,721 labeled as obligations from USAspending.gov. It does not recast the figure as money already spent.
11,255,726 contract records — volume vs dollars
Eleven million two hundred fifty-five thousand seven hundred twenty-six award records sit under the contract total. Procurement files generate many rows: delivery orders, task orders, modifications, and small purchases all increment the tally. Dividing $4,975,819,796,721 by 11,255,726 yields about $442,070 per record. That average is a scale check. It is not the price of a typical widget buy and not the value of a typical major system contract.
The 11,255,726 figure is not a vendor headcount. One contractor can hold thousands of actions. One parent vehicle can spawn many orders. This packet does not split the 11,255,726 by NAICS industry, awarding agency, or set-aside status. If the Contracts awards overlay shows those tables, read them there. This prose stays on the two facts.
Contract vs grant and the other USAspending families
USAspending groups awards into contract, grant, loan, direct payment, and other. A contract is a purchase. A grant is assistance. A loan expects repayment. Direct Payments and Other Financial Assistance are still other assistance families. Adding contract dollars to grant dollars and calling the mix 'awards' without naming the code group hides the split the source file is built around.
The $4,975,819,796,721 line is contracts only. Readers looking for formula grants, household assistance, or loan face amounts will not find those dollars inside this total. They will find procurement obligations. The all award types index compares families on the same obligation basis; this guide does not invent the other groups' sums.
Why the action count runs ahead of a simple purchase list
Contract reporting in USAspending.gov is action-based. A modification that adds funding, a modification that only changes a date, and a new order on an existing vehicle can each add a row. That is why 11,255,726 can look like 'eleven million contracts' when it is eleven million award records. Do not treat the count as a count of unique solicitations or unique vendors.
Because the packet has no modification flag and no unique-vendor total, this page does not estimate how many of the 11,255,726 rows are new awards versus changes. Use the overlay tables if they expose that grain. Keep the dollar side as $4,975,819,796,721 in obligations.
Reading the Contracts awards hub
Start on the Contracts awards overlay for the live procurement roll-up. Use all award types when the question is whether a dollar is procurement or assistance. Neither page is FPDS as a standalone system, and neither page is a budget justification. They are USAspending.gov award-file aggregates indexed on SpendingVault.
If a buy you expected is missing, it may be filed under a different award_type_code, sit below a reporting threshold, or appear only as an assistance action. This packet has contract facts only: $4,975,819,796,721 and 11,255,726 awards. Do not stretch those numbers to cover every federal purchase that exists in another dataset. Micro-purchases and intra-governmental orders that never become USAspending award rows will not appear in either figure.
How to cite federal contract obligations
A complete citation is $4,975,819,796,721 in Contracts obligations from USAspending.gov award files indexed on SpendingVault, covering 11,255,726 awards. Name the series as obligations. Do not call it Treasury outlays. Do not attach a fiscal year this packet does not supply. Do not describe it as grant assistance. If a later extract revises the indexed sum, cite the new dollar total with the new action count rather than blending file vintages.
If the question is about how many procurement records exist, lead with 11,255,726 awards, then the $4,975,819,796,721. Cite USAspending.gov as the source system. SpendingVault indexes the aggregates; it does not replace the award-level contract files.
Questions
- How much does the federal government obligate on contracts?
- USAspending.gov award files indexed on SpendingVault show $4,975,819,796,721 in Contracts obligations. That sum is an obligation total, not a Treasury outlay total. The same files record 11,255,726 contract awards. This packet does not name a fiscal-year window, so the dollars are the indexed procurement roll-up as loaded.
- Why are there more than 11 million federal contract awards?
- The indexed files count 11,255,726 contract records. Procurement files stack orders, task orders, and modifications, so the tally is a row count, not a count of unique vendors or unique solicitations. Dividing $4,975,819,796,721 by 11,255,726 yields about $442,070 per record as a scale check.
- Are contract obligations the same as spending?
- Not if spending means cash out the door. The $4,975,819,796,721 headline is obligations — legal commitments on contract award actions — not outlays. Invoices, options, and de-obligations can leave cash and commitment apart. This packet has no outlay column, so this page does not estimate amounts already paid.
- What is a USAspending contract versus a grant?
- A contract is procurement of goods or services. A grant is assistance for a stated purpose. USAspending files them as separate award_type_code groups. The $4,975,819,796,721 figure is Contracts only. Grant dollars live in a different group and are not included here.
Award types are USAspending award_type_code groups (contract, grant, loan, direct payment, other).