Direct answer
A federal award record can tell a recruiter who received an award, from which agency, for what category of work, roughly where and when it is performed, and how much money has been obligated so far. It cannot tell you that the company is hiring, how many people the work needs, who is staffed on it, or whether anyone holds a clearance.
Read every field at its own level. An obligation is a commitment of money, not money spent [S3][S4]. A ceiling or potential value is not an obligation. A recipient address is not the place of performance. Recent Department of Defense awards can appear late because of a documented reporting delay [S1][S2]. Use the record to choose which companies to research, then build the actual search lanes with our donor-company mapping workflow.
The one rule: company evidence stays company evidence
Most errors in GovCon recruiting research come from moving up a level of claim without new evidence. "Example Systems LLC received an award for network operations work at an Army installation" is a supportable company fact. "Example Systems is hiring network engineers there" is a different claim that needs a job posting or a conversation. "People at Example Systems hold the clearance this work needs" is a claim no public award record can support.
Keep a label on every note: AWARD FACT (from the record), INFERENCE (your reasoning, stated as a hypothesis), or VERIFIED BY (a named source or conversation). The worksheet at the end of this guide has a column for exactly that.
Field by field: what the record says and what it does not
Field names vary slightly between USAspending.gov, SAM.gov and downloaded files, so check the field definitions in the system you are using. The meanings below are the recruiter-relevant interpretation; where a definition matters to your conclusion, confirm it in that system’s data dictionary.
| Field | What it tells you | What it does not tell you | Safe wording for a recruiting note |
|---|---|---|---|
| Recipient name and unique entity ID | The legal entity that received the award | The brand people use on professional profiles, or whether a parent company does the hiring | "Award recipient of record: [legal name]" |
| Parent recipient | A reported corporate parent, where available | Which subsidiary employs the people doing the work | "Reported parent: [name]; employing entity unconfirmed" |
| Awarding agency vs funding agency | Who contracted, and whose money pays for it; they can differ | Which office the work is physically for | "Awarded by [agency]; funded by [agency]" |
| Obligated amount | Money the government has legally committed so far [S3] | Money actually paid out (that is an outlay [S4]) or the total the contract may reach | "Obligations reported to date: [amount] as of [date]" |
| Potential or ceiling value | An upper bound under the award’s terms | Expected spending, work volume or headcount | "Reported potential value; not an obligation" |
| Period of performance | The reported start and end of the work | Whether it will be extended, recompeted or ended early | "Reported period: [start] to [end]" |
| Place of performance | Where the work is reported to be performed | Where the company’s staff live, or remote versus on-site arrangements | "Reported performance location: [city, state]" |
| Recipient location | The address on the recipient’s record | Where the work happens; it is often a headquarters | Do not use it as the work location |
| NAICS and PSC codes | Industry and product or service category for the award | The specific job titles or skills involved | "Classified as [code and title]" |
| Award type (contract, IDV, order) | Whether this is a vehicle or an order placed under one | That a vehicle by itself carries funded work | "Indefinite-delivery vehicle; see orders for funded work" |
| Subawards | First-tier subcontracts the prime has reported, above the reporting threshold [S5] | Every subcontractor, or any below-threshold or unreported work | "Reported first-tier subaward: [name]" |
Timing caveats that change what "recent" means
- Department of Defense procurement data entered into the federal procurement data system is subject to a 90-day public availability delay, according to the system’s own notice [S1]. A 2017 DoD Inspector General audit found DoD award data was not publicly available until 91 days after award [S2]. If your search window is the last quarter, expect defense awards to be missing.
- Subcontract data is reported by the prime, not the government. Prime contractors under FAR clause 52.204-10 report first-tier subcontract awards valued at or above the threshold in FAR 4.1403(a) by the end of the following month. The first-tier subcontract reporting threshold increased from $30,000 to $40,000 effective October 1, 2025 [S5][S8]. This threshold applies to federal procurement contracts, not every federal grant or assistance subaward. SAM.gov now handles FSRS subaward reporting following the March 2025 transition [S9]; confirm the reporting channel and effective rule applicable to the award date.
- Public contract award search moved to SAM.gov: GSA states FPDS ezSearch was decommissioned on February 24, 2026 [S6]. Older tutorials that send you to FPDS search screens are out of date.
- Obligations accumulate through modifications. A single snapshot of an award’s totals is only true as of the date you looked, so record that date.
Five misreadings, corrected
Each example uses a fictional company, Example Systems LLC, and fictional figures. They are written the way they often appear in recruiting notes, followed by a version that only claims what the record supports.
| Misreading | Why it is wrong | Supportable rewrite |
|---|---|---|
| "Example Systems just won a $480M contract, so they will need hundreds of engineers." | The figure is a ceiling on an indefinite-delivery vehicle; headcount is not in the record | "Example Systems holds a vehicle with a reported $480M potential value; funded orders and staffing levels are unknown." |
| "The work is in Reston, VA." | Reston is the recipient address; the reported place of performance is Huntsville, AL | "Reported performance location: Huntsville, AL. Recipient address: Reston, VA." |
| "Their people are cleared for this program." | Award records contain no personnel or clearance data | "The award’s category suggests cleared work may be involved; clearance requirements must come from a posting or the employer." |
| "No new DoD awards for this office in the last two months." | Recent DoD awards may not be public yet because of the reporting delay [S1] | "No public DoD awards found for the last 90 days; data may be delayed. Re-check after [date]." |
| "Example Systems is the only subcontractor." | Only reported first-tier subawards above the threshold appear [S5] | "Reported first-tier subaward: Example Systems. Other subcontractors may exist." |
A ten-minute reading routine for one award
- Copy the award identifier, the source system and today’s date into the worksheet before reading anything else.
- Record recipient, parent and the employer brand you will search under, and mark the employer brand "unconfirmed" until you have seen it on the company’s own site.
- Record obligations and potential value in separate columns. Never add them together.
- Record place of performance separately from recipient location.
- Note the classification codes and write the work category in plain words.
- Check for an IDV or parent award and look at the orders under it, which is where funded work usually shows up.
- Check reported subawards and note that the list may be incomplete.
- Write one INFERENCE line, stated as a hypothesis, about what kind of talent the work might involve, and one line naming what would verify it, such as a current posting.
Boundaries for cleared and federal recruiting
Treat incumbent-capture or recompete research the same way. A period-of-performance end date is a public fact. "Their staff will be looking for work" is speculation about people, and it should not appear in outreach.
Federal award reading worksheet
One row per award. The columns force obligations, ceilings, recipient address and performance location apart, and give every claim a label: AWARD FACT, INFERENCE or VERIFIED BY. Pair it with the donor-company map in the federal contract data guide.
Download the CSV worksheet (plain text, opens in any spreadsheet tool; contains no candidate data).
| Column | What to record |
|---|---|
award_id | Award or order identifier exactly as shown |
source_system_and_date | USAspending.gov or SAM.gov, plus the date you looked |
recipient_legal_name | Recipient of record |
employer_brand_to_search | Name people use on profiles; marked unconfirmed until checked |
awarding_agency | Agency that awarded it |
obligated_to_date | Obligations as reported on that date |
potential_or_ceiling | Kept separate from obligations |
place_of_performance | Reported performance location |
recipient_location | Address of record, not the work site |
award_type | Definitive contract, IDV or order |
reported_subawards | First-tier subawards found; note possible gaps |
claim_label | AWARD FACT, INFERENCE or VERIFIED BY |
what_would_verify | The posting, page or conversation that would confirm an inference |
Related guides
Source ledger
The October 2025 FAR threshold table (S8) and official SAM.gov FSRS retirement announcement (S9) were directly reviewed on October 25, 2026. Remaining federal award and source-system claims are search-result summaries or inherited from an existing guide and still need direct per-claim verification before publication. Separate procurement subcontracts from federal grant assistance reporting.
| ID | Source | Claim it supports | Accessed / method | Human re-check |
|---|---|---|---|---|
| S1 | Federal Procurement Data System: DoD data availability notice | DoD data entered into FPDS is subject to a 90-day delay in availability | 2026-10-25 · WebSearch summary; page not opened | Confirm the notice is still current after the SAM.gov transition |
| S2 | DoD Office of Inspector General: Report DODIG-2018-021 | DoD procurement award data was not publicly available until 91 days after award (2017 finding) | 2026-10-25 · WebSearch summary; page not opened | Historic audit; confirm the page and figure, and do not present it as current practice |
| S3 | Government Finance Officers Association: Using USAspending.gov to track federal award obligations and outlays | An obligation is a legally binding commitment that results in outlays now or later | 2026-10-25 · WebSearch summary; page not opened | Secondary explainer; prefer the USAspending glossary wording if it differs |
| S4 | U.S. Department of the Treasury: Federal spending transparency (PDF) | An outlay is a payment that liquidates an obligation | 2026-10-25 · WebSearch summary; page not opened | Confirm the definition text and document date |
| S5 | FSRS / GSA: FFATA Subaward Reporting System | FAR 52.204-10 references FAR 4.1403(a) for first-tier subcontract reporting; the threshold rose from $30,000 to $40,000 effective Oct 1, 2025. Verify contract-vs-grant and award date before applying it | 2026-10-25 · WebSearch summary; page not opened | Confirm transition and exact reporting mechanism; S8 independently verifies the threshold |
| S8 | Acquisition.gov: Threshold Changes — October 1, 2025 | First-tier subcontract reporting threshold $30,000 → $40,000 effective October 1, 2025, FAR 4.1403(a); distinct from federal assistance grants | 2026-10-25 · Official primary source directly opened 2026-10-25 | Verify rule wording and current threshold before publication; retain contract/grant distinction |
| S9 | SAM.gov: Subaward Reporting is live on SAM.gov | FSRS.gov retired March 8, 2025 and subaward reporting moved to SAM.gov, according to the official SAM announcement | 2026-10-25 · Official primary source directly opened 2026-10-25 | Verify announcement path and latest subaward reporting requirements before publishing |
| S6 | SAM.gov / GSA: FPDS transition to SAM.gov | Public FPDS functionality moved to SAM.gov; FPDS ezSearch decommissioned February 24, 2026 | 2026-10-25 · Carried from an existing SourcingOS guide; not re-opened | Re-open and confirm the date |