Awards and transactions are different records
Federal procurement data often contains an award-level view and a transaction-level history. An award identifies a continuing contract or assistance relationship; individual transactions capture reported actions and modifications over its lifecycle. Counting transaction rows as separate contracts overstates the number of awards. Conversely, collapsing every action into one award record can erase the history needed for audit and change analysis.
Preserve stable identifiers
Keep the source award identifier and the transaction or action identifier where available. Contract award identifiers may require agency context to distinguish otherwise similar values. Do not build a unique key from recipient name alone, because names can change and multiple recipients can have similar names. Store the awarding and funding agency context, recipient identifiers, source system and record lineage alongside the relevant action.
Understand dates and obligations
An action date describes when a reported modification or transaction takes effect or is recorded under the source definition. It should not automatically be treated as the original award date. Federal obligations are financial commitments, not necessarily cash payments or total contract ceilings. Modification actions can add funding, reduce obligations or change nonfinancial terms. A negative obligation can be legitimate and must not be discarded as a parsing error.
Reconcile award totals with action histories
For a transaction-based analysis, establish whether the source's award total is a current cumulative amount or a separately calculated sum. Summing all available actions may not reproduce a published award-level figure when records have corrections, different scopes or incomplete history. Keep the reconciliation method explicit, report discrepancies and preserve the original amounts so analysts can inspect differences rather than silently overwriting them.
Deduplicate carefully
Duplicate file deliveries are not necessarily duplicate economic actions. A stable deduplication key should combine authoritative source identifiers and the relevant action identity, with a documented fallback when a key is missing. Compare raw record fingerprints to detect exact re-ingestion, but do not collapse legitimate amendments or repeated amounts merely because they share a date and award identifier. Retain conflict records for review and make the published selection rule auditable.
Handle corrections and late updates
Public procurement sources may revise historical entries. An incremental pipeline should look back over an appropriate window and reconcile previously seen records, not assume that only today's actions can change. Preserve ingestion time separately from action date. Use versioned exports or change indicators so consumers can identify records that were added, updated or withdrawn between deliveries.
Quality controls for analysts
Validate identifier completeness, numeric precision, currency assumptions, date formats and agency references. Check whether a transaction belongs to an existing award, whether a modification creates a conflicting version, and whether a record has sufficient provenance to be reproduced. Report coverage limitations, including unavailable historical actions. For research, distinguish award counts, action counts and net obligations in every chart and summary.
Explore the related datasets
Review the Federal Contract Awards and Transactions datasets, quality controls and integration documentation. Dataset consumers should evaluate whether they need the current award snapshot, the full action history or both, because these answer different procurement questions.