This practical checklist is designed for journalists, researchers, analysts and government-contracting teams who need a repeatable way to evaluate an individual defense contract award or a set of related actions. It is a research worksheet, not a certification or guarantee of complete federal coverage.
Before you trust a contract-award number
- Define the claim: Is it about a specific award, a contractor total, market concentration, a government agency or a possible future opportunity?
- Capture the record: Record the exact source identifier, transaction or modification number and accessible source location.
- Check the parties: Identify recipient, reported legal identifiers, awarding agency and funding agency without guessing parent ownership.
- Check the amount: Distinguish current action, cumulative obligation, ceiling value, budget authority and outlay.
- Check the dates: Note fiscal year, effective/action date, source publication date and current database coverage date.
- Check the record unit: Are rows transactions, contracts, contract vehicles, orders or aggregated rollups?
- Check corrections: Look for amendments, negative de-obligations, superseded actions or duplicates.
- Check category labels: Use the NAICS/PSC description and the underlying procurement description; distinguish official fields from derived market categories.
- Check coverage: Look at the Data Status page. A missing record is not proof that an award did not occur.
- Check your conclusion: Could another denominator, period, role definition or stale reporting snapshot overturn it?
Copyable case-note structure
| Research field | What to record |
|---|---|
| Research question | One factual question with scope and period |
| Bellum page | Exact URL used for evidence |
| Underlying record ID | Contract/award identifier and relevant action reference |
| Recipient | Reported legal name and verified identifier where available |
| Agencies | Awarding organization; funding organization recorded separately |
| Dates | Action date; fiscal year; access date; data freshness range |
| Financial measure | Transaction obligation, cumulative obligation, ceiling, outlay or budget amount |
| Industry grouping | NAICS; PSC; Bellum-derived market where applicable |
| Source and caveats | Primary-source location; missing data; classification or comparison limitations |
| Finding and uncertainty | Conclusions supported by the record; outstanding questions |
Illustrative verification failure
Hypothetical case. A dashboard shows three actions of $1.2 million, $300,000 and −$100,000 attached to the same contract. If these are action-level changes in obligations, their net change is $1.4 million. But if the $1.2 million value is already a cumulative total, summing all three will be wrong. First inspect the source field definitions, then calculate. A contract ceiling of $8 million must not be added to either total.
Red flags in published defense-contract analysis
- A claim about all U.S. defense procurement built from an undocumented subset.
- An article calling an obligated amount cash paid or contractor profit.
- Duplicated parent and subsidiary amounts counted as independent spending without documented entity relationships.
- Contract action rows counted as unique contracts without deduplication.
- Fiscal-year totals compared against calendar-year periods without explanation.
- A derived classification described as an official government category.
- A reported market total with no source date, denominator or known limitations.
A repeatable Bellum workflow
Open the Award Explorer, identify the record and capture its reported fields. Expand through Companies, Agencies and Markets. Consult the Financial Definitions and Methodology before calculating totals. Check Data Sources and Coverage. If the underlying evidence appears incorrect, use Corrections.
Frequently asked questions
What is the most important field for checking a defense contract?
The primary-source contract or award identifier is a good starting point, but a reliable interpretation also requires its action reference, transaction type, amount definition and reporting date.
Can I treat an unlisted contract as nonexistent?
No. The search could be affected by incomplete coverage, late reports, search terms, legal-name variants or access restrictions. Document the negative result and the limits of the search.
Does this checklist replace legal or procurement advice?
No. It is an evidence-verification aid for publicly reported data, not professional advice or an official determination of award status.