A reporting worksheet for checking an award’s identity, money fields and transaction history before turning federal spending data into a story.
Write down which dollar figure you mean
A contract story can change meaning when the headline drops the name of the money field. “Award value,” “obligated” and “paid” need separate treatment.
USAspending’s Analyst’s Guide to Federal Spending Data distinguishes an obligation, a government commitment to spend, from an outlay, a payment. The site’s About the Data documentation describes contract attributes and transaction records, including potential value and obligations.
For a B2B or government-technology publisher, the first editorial task is deciding which question the record can answer. How large could this award become? What has the government committed? What payments are reported? Keep the field label attached to the answer.
Start with one award, then its history
Search USAspending for a specific award or recipient. Save the award identifier, awarding agency, recipient identity and the record URL before collecting amounts.
Then inspect the transaction history. A later action may change funding, dates or descriptive information. Compare the relevant action with the award-level total; adding a cumulative total to a transaction amount can count the same commitment twice.
Read the data documentation for the fields you use. Coverage, reporting schedules and corrections limit what a search can establish. A missing recent action is a reason to check the underlying record and agency, rather than infer that no action occurred.
Our defense-award guide focuses on reading an announcement. This worksheet follows the award’s structured record and its changes over time.
An award-record worksheet
Copy this table into the story file. Put the exact export field name beside each amount in your working version.
| Check | What to save | Claim it helps you test |
|---|---|---|
| Award identity | Identifier, agency, recipient and record URL | Are we discussing the same award? |
| Potential value | Field label, amount and record date | What potential value does this record show? |
| Obligations | Award total and relevant transaction amount | What commitment changed in this action? |
| Outlays | Amount, reporting period and availability | What payments are actually reported? |
| Transaction history | Action dates, modification identifiers and descriptions | Is this new work, funding or another update? |
| Contract structure | Parent vehicle or order relationship where present | Are we comparing a vehicle with an individual order? |
| Verification | Agency response and underlying award material | What remains uncertain after reading the data? |
Leave a field blank when it’s unavailable and explain the gap. Substituting a different money field can make a polished table inaccurate.
A hypothetical modification worth investigating
Suppose a vendor announces an expanded contract, and the award record shows a later funding action. This is an illustrative reporting exercise, not a real award.
The useful next question is what changed. Compare the action’s obligation amount with the cumulative total, check the description and review the performance dates. Ask the agency and company whether the action funds existing scope, exercises an option or adds work.
Your initial sentence can identify the dated action and the amount under its actual field label. A claim about new capability or revenue growth needs more evidence. A funding action alone won’t establish that a contractor has earned, received or recognized the same amount as revenue.
And a negative transaction deserves the same discipline. Check whether it reflects a funding adjustment, closeout or correction before describing it as a program cancellation.
Keep the query with the finding
For a recurring beat, save the query, retrieval date and export. Compare like periods and keep contract awards separate from other award types unless the story explicitly covers both.
Describe the bounds in the published piece: selected agencies, period, category and money measure. When an award’s recorded end date prompts a follow-up, ask what the agency plans next. The date itself doesn’t establish a future competition.
Use the record to build a short list of questions you can take to sources. The best output from a scan may be a single discrepancy worth resolving.
Niche’s briefings can help you follow the field’s reported developments. Keep the award-level check in your own reporting file, with the export that supports your claim.
Related reading
- Read defense contract announcements
- Read SBIR and STTR research awards
- Test four data-story angles
- How a Niche briefing is checked
Frequently asked questions
Are obligations the same as money paid?
No. An obligation commits the government to spending. An outlay records a payment. Preserve the distinction when reporting federal award amounts.
Does a contract’s end date confirm an upcoming recompete?
The recorded end date gives you a question to ask the agency. Future work might be extended, changed, competed or discontinued, so verify the acquisition plan separately.