Guide
Read SBIR and STTR Awards as Research Records
Use award data to investigate a technical question while separating awarded funding, research goals and demonstrated commercial results.
What does an SBIR or STTR award tell you?
An award record can connect a small business, a funding agency and a described research effort. It can help a startup or defense writer identify technical problems agencies are supporting. It does not establish that the research succeeded, that the company has a production contract or that a commercial product is available.
Start with SBIR.gov's data resources and award search. Check the dataset's coverage, definitions and update information before making a count. A missing record is not proof that a company received no support, especially when the reporting period may be incomplete.
Build an award record before building a narrative
| Field | What to capture |
|---|---|
| Company and identifier | Match the recipient across records carefully |
| Agency and program | Identify the funding context |
| Award year, date and phase | Describe the particular award without assuming a complete sequence |
| Amount | State the field and record you are using |
| Topic and abstract | Separate the research goal from an achieved result |
| Related records | Find agency notices, company disclosures and follow-on documentation |
| Outcome evidence | Identify what would demonstrate actual progress |
Correct names and entity matching matter. Similar company names, acquisitions and affiliates can distort totals. Preserve the original identifiers and document any grouping you apply. Check for duplicate records before adding amounts.
Follow the technical question
Imagine a hypothetical award abstract proposing a method for detecting corrosion in difficult-to-inspect equipment. That is a useful lead about an engineering constraint. It is not evidence that the method now detects every defect or that the agency has adopted it operationally.
Read the topic description, ask the company about available results and seek an independent specialist's explanation of the technical difficulty. Look for public testing, publications or subsequent procurement records. Attribute company statements and distinguish a proposal, a prototype, a test result and a deployed system.
Do not infer that every later-phase award followed the same earlier path. Read the particular program and award context. Likewise, the absence of a later award in your search does not establish failure; the work may have continued through another funding route or outside your dataset.
Make comparisons reproducible
If you compare awards, state the period, filters, download date, treatment of duplicates and unit of analysis. Counting awards is different from counting companies. Awarded amounts are not automatically revenue recognized or cash already spent.
A strong article can explain which technical questions appear in a defined set of awards and what further reporting reveals about them. Keep claims about broader market direction proportional to the sample. Use the defense-contract guide for separate procurement records and the standing-file template to track outcomes over time.
Keep reading