Technology Readiness Levels (TRL) Explained: A Field Guide for Federal R&D

Technology Readiness Levels — TRLs — are the single most consequential acronym in the federal R&D ecosystem. They determine which solicitations you can respond to, whether a program manager will return your call, and whether your Phase II proposal reads as ambition or fantasy. Misjudge your TRL by even one level, and reviewers will stop reading.

This guide is the field reference we hand to our own SBIR/STTR clients. It defines each level as DoD, NASA, and DOE actually evaluate them — and tells you how to defend your assigned level when a reviewer pushes back.

What Is a Technology Readiness Level?

A Technology Readiness Level is a standardized 1-to-9 scale used by federal agencies to assess the maturity of a technology — from initial scientific principle (TRL 1) through proven operational deployment (TRL 9). The scale was originated by NASA in the 1970s, formalized by the Department of Defense in the 1990s, and is now embedded in every major federal acquisition framework, including DARPA, AFWERX, the Army SBIR Catalyst program, and the DOE's national laboratory ecosystem.

TRL is not a measure of how good a technology is. It is a measure of how proven it is in a relevant operating environment. A TRL 3 lab demonstration can be world-changing science; a TRL 8 system can be incremental engineering. Reviewers care about the difference because federal funding mechanisms are tier-matched to TRL bands.

The Nine Technology Readiness Levels Defined

TRL 1: Basic Principles Observed

Scientific research begins translating into applied research. There is no application yet — only a phenomenon, a principle, a paper. If your evidence is a peer-reviewed publication and a hypothesis, you are at TRL 1.

TRL 2: Technology Concept Formulated

Practical applications are now being invented. Speculative — but the use case is named, the architecture is sketched, and the analytic case for feasibility exists. You can describe what the technology will do, even if you cannot yet show it doing anything.

TRL 3: Experimental Proof of Concept

Active R&D begins. Analytical studies and laboratory experiments validate the analytical predictions of separate elements of the technology. This is the typical entry point for an SBIR Phase I proposal — the level at which DoD, NSF, NIH, and DOE expect a Phase I awardee to begin.

TRL 4: Component Validation in Laboratory

Basic technological components are integrated to establish that the pieces will work together. The fidelity is low compared to the eventual system, and the environment is the lab — but integrated function exists. Most successful Phase I projects exit at TRL 4.

TRL 5: Component Validation in Relevant Environment

Fidelity of the breadboard increases significantly. The components are integrated with reasonably realistic supporting elements, and they are tested in a relevant environment — meaning conditions that simulate, but do not yet replicate, the operational environment. Phase II SBIR projects typically begin here.

TRL 6: System Demonstration in Relevant Environment

A representative model or prototype system is tested in a relevant environment. This is a major step up. TRL 6 is often the gate for transition into Phase III, Direct-to-Phase-II awards, and follow-on contracting through programs like AFWERX, SOFWERX, NavalX, and DIU.

TRL 7: System Prototype Demonstration in an Operational Environment

A prototype near, or at, planned operational system. Demonstration occurs in an operational environment — actual flight test, field deployment, end-user evaluation. Crossing TRL 6 to TRL 7 is the single most credibility-building transition in the readiness ladder.

TRL 8: Actual System Completed and Qualified

The technology has been proven to work in its final form and under expected conditions. Development is essentially complete. For DoD systems, this is typically the end of system development and demonstration — the technology is ready for Low-Rate Initial Production.

TRL 9: Actual System Proven Through Successful Mission Operations

The technology is in its final form and operating under the full range of expected mission conditions. TRL 9 is fielded. Most SBIR firms never personally drive a technology to TRL 9 — they transition it to a prime, a program of record, or a commercial integrator who does.

How DoD, NASA, and DOE Differ on TRL

The scale is shared. The application is not. Each agency applies the TRL framework with subtle but consequential differences:

• DoD TRLs are codified in DoDI 5000.02 and the Defense Acquisition Guidebook. The DoD treats TRL 6 as the de facto threshold for transition to a program of record, and emphasizes Manufacturing Readiness Levels (MRLs) alongside TRL.

• NASA TRLs are defined in NASA Procedural Requirements (NPR) 7123.1 and NPR 7120.8. NASA interprets 'relevant environment' more strictly than DoD — for spaceflight hardware, that often means thermal-vacuum and vibration testing. NASA also uses TRL gates inside formal Key Decision Points.

• DOE TRLs largely mirror DoD definitions but emphasize scale-up readiness for energy systems, where moving from a working bench prototype to a pilot-scale plant frequently spans multiple TRL levels and substantial capital.

Defending Your TRL in a Federal Proposal

Reviewers reject self-assigned TRLs that read as aspirational. Three principles separate proposals that get funded from those that get flagged:

1. Anchor every TRL claim to evidence. Cite the specific test, the conditions, the data, and the document of record. 'We have completed bench-scale testing under representative thermal load (see Appendix B, Test Report 22-04)' — not 'we are at TRL 5.'

2. Underclaim, then overdeliver. Reviewers respect a defensible TRL 4 over a contested TRL 6. Inflation reads as inexperience.

3. Map your TRL trajectory to the funding instrument. A Phase I proposal that ends at TRL 6 is unrealistic. A Direct-to-Phase-II that begins at TRL 3 is unfundable. Match the level to the mechanism.

Where TRL Fits in Your Capture Strategy

TRL is a sequencing decision before it is a writing decision. The right capture strategy treats your current TRL as a known position on a map and your next funding instrument as the route to the next gate. We help R&D firms move from TRL 3 to TRL 7 across the SBIR/STTR lifecycle — through capture planning, proposal development, Phase III transition, and commercialization.

If you are uncertain where your technology sits on the readiness scale, or how to argue for the level you have earned, that uncertainty is not a writing problem. It is a strategy problem — and it is solvable.