PIIDs, related notices, and award transaction data
Terms for following numbers, related-notice links, , and modifications across and .
1 / 2
Award data sources
Award data sources are the current public destinations for and spend reconstruction. Public search has transitioned to .gov Contract Awards and ; USAspending remains the official open source for federal spending analysis and receives procurement data derived from that reporting stream. Treat FPDS as lineage vocabulary, not as the current public destination. Start every incumbent or spend reconstruction with SAM.gov award search / reports, then USAspending for transaction and spending analysis.
Watch for
Don't confuse SAM.gov with pre-award only, USAspending with grants only, or Data Bank with forecasts that have no awards or modifications.
2 / 2
Related notices and transaction chain
A related-notice chain connects , presolicitation, solicitation, , justification, and award for one acquisition story in SAM.gov. A transaction chain follows PIIDs, parent IDVs, task orders, award and modification records, net including deobligations, and potential value as a ceiling rather than revenue. Use the notice chain for requirement evolution when building binders; use the / modification trail for dates and money. Distinguish historical facts from assumptions about the next procurement — ceiling is not spend; continuity is not customer sentiment.
Watch for
Don't treat the awardee's legal name alone as a reliable identity key, assume an award notice holds the full and every amendment, or count potential value plus every child order as incumbent revenue. Negative obligations are not automatic proof of failed performance.