Reading Federal Spending Data

Federal spending data can be confusing because of the multiple ways the government measures and reports financial activity. This guide explains the key terms and concepts you need to understand the data presented on PlainFedContract and on the source platform, USAspending.gov.

Obligations vs. Outlays

The most common source of confusion in federal spending data is the difference between obligations and outlays. An obligation is a binding commitment by the government to pay for goods or services. It occurs when a contract is awarded or modified. An outlay is the actual disbursement of funds — when the check is written. Obligations typically occur before outlays, and there can be a gap of months or years between the two.

PlainFedContract primarily shows obligations, which is the standard metric used in federal procurement data. This is what USAspending.gov reports for contract awards. Obligations are a better measure of current procurement activity because they reflect when the government commits to spending, not when it pays.

Budget Authority

Budget authority is the legal authority provided by Congress that allows an agency to incur obligations. It represents the ceiling on how much an agency can commit to spend. Budget authority comes from annual appropriations acts, authorizing legislation, or borrowing authority. An agency's budget authority may differ from its actual obligations because not all authorized funds are obligated within a fiscal year.

Total Award Amount

The total award amount for a contractor represents the cumulative sum of all contract obligations across all agencies. This includes the base contract plus all modifications. Note that modifications can be positive (adding funds) or negative (de-obligations). The total amount shown on a contractor's page reflects the net sum of all contract actions.

Fiscal Year

The federal fiscal year runs from October 1 to September 30 of the following calendar year. FY2024 covers October 1, 2023 through September 30, 2024. This is important when interpreting annual spending trends on our data — the FY2024 figure covers a period that straddles two calendar years.

NAICS Codes

Each contract is classified by a North American Industry Classification System (NAICS) code that describes the products or services being procured. A single contractor may have contracts across multiple NAICS codes. Our industries page shows total spending by NAICS code. For more detail, see our guide on NAICS codes explained.

State-Level Data

Contract spending by state reflects the place of performance, not the contractor's headquarters location. A company headquartered in Virginia may perform work in multiple states, and each contract action is attributed to the state where the work is performed. Our state data uses this place-of-performance attribution.

Data Limitations

Federal spending data is reported by agencies with varying levels of timeliness and accuracy. Some limitations to keep in mind:

• Data may lag behind actual contract actions by several weeks to months
• Classified contracts (primarily in defense and intelligence) may not appear
• Grants, loans, and other forms of financial assistance are not included in contract data
• Subcontract data is limited — only prime contract obligations are shown
• Interagency transfers can cause apparent double-counting in some cases

For the most current data, check USAspending.gov directly. PlainFedContract aggregates and simplifies this data to make it more accessible.

Quick reference: the federal spending vocabulary

Federal procurement data uses a handful of overlapping terms that often get used interchangeably in news coverage even though they refer to distinct stages of the spending lifecycle. Distinguishing between them is essential when comparing two numbers from different sources or different reporting periods. The table below organizes the most common terms by where they sit in the spending pipeline:

Definitions per USAspending.gov Data Element Dictionary (usaspending.gov/data-dictionary) and OMB Circular A-11.

Why "obligation" is the right metric for procurement analysis

Journalists, academics, and procurement analysts almost universally use obligations (not outlays) when discussing contract spending, because obligations capture the government's current commitment behavior — the decisions being made today — rather than payments that might reflect commitments made years earlier. A contract for a multi-year Air Force fighter jet program might be obligated in full in year one but pay out across five fiscal years; an outlay-based view would smear that signal across the lag. PlainFedContract follows this convention and reports obligations unless explicitly stated otherwise. Comparing PlainFedContract numbers to outlay- based reports (such as those in some Congressional Budget Office documents) will show systematic differences explained by this lag.

How USAspending.gov gets refreshed and why some numbers move retroactively

USAspending.gov refreshes contract data daily from the underlying Federal Procurement Data System (FPDS) and the Award Submission Portal (ASP) for financial assistance. Agencies can submit corrections to past records, which means historical totals are not strictly immutable — a major correction to a multi-billion-dollar award in a prior fiscal year will retroactively shift the totals reported for that year. This is one reason analysts who track federal spending always cite their data extract date alongside the numbers. PlainFedContract refreshes its mirror periodically from the USAspending.gov bulk-download API; small differences between PlainFedContract and the live USAspending.gov web interface usually reflect the lag between extracts rather than methodological differences. When precision matters, cross-check against a same-day USAspending.gov pull.

Place-of-performance vs. recipient-location: two different state pictures

State-level federal spending totals can be reported by either the recipient's headquarters location or the place where the work is actually performed. These two attributions can produce dramatically different state-level totals for the same contracts. A defense contractor headquartered in Virginia may perform 60 percent of the work on a major program in California, Texas, and Florida factories. Reporting the full contract value against Virginia overstates Virginia's economic impact; reporting it against the performance states understates the headquarters services that Virginia provides. PlainFedContract follows the USAspending.gov convention of using place-of-performance, which is the more meaningful attribution for economic impact analysis but can understate the apparent role of headquarters states like Virginia, Maryland, and the District of Columbia in the federal procurement system.

Worked example: tracing a five-year defense program through the data

Consider a hypothetical Department of Defense IT modernization contract awarded in October 2023 (FY2024) with a $200 million ceiling and an initial obligation of $40 million. Over the following twelve months the agency adds two modifications: a $25 million scope expansion and a $5 million negative de-obligation as a small task is descoped. By the end of FY2024 the contract has $60 million in net obligations against the $200 million ceiling. In FY2025 the agency obligates an additional $80 million and the contractor invoices roughly $70 million in costs; Treasury issues outlays of $65 million by year-end. Querying USAspending.gov for this contract at the end of FY2025 returns: ceiling $200 million, total obligations $140 million, total outlays $65 million. The same contract therefore appears with three very different dollar figures depending on which metric the analyst pulls — a frequent source of confusion in news coverage when reporters cite "the size of the contract" without specifying which stage they are measuring.