Technology readiness level (TRL)

Definition (what it is)

Technology readiness level (TRL) is a standardized scale, originally developed by NASA and now widely adopted across government and industry, for estimating how mature a technology is—from basic principles observed to a system proven in operational use. The scale typically spans nine levels (TRL 1–TRL 9), providing a common way to describe progress, compare options, and plan transition from research to deployment. An assigned TRL is usually the outcome of a technology readiness assessment (TRA) that reviews requirements, demonstrated performance, and supporting evidence.

Function and purpose (key characteristics)

Common language for maturity: Enables consistent communication of development status across disciplines, organizations, and supply chains.
Stage‑gate decision support: Links technical milestones to program investment gates, informing go/no‑go decisions, schedules, and portfolio prioritization.
Evidence‑based criteria: Each level requires specific, auditable evidence (e.g., lab tests, prototype demonstrations, certification results) appropriate to the target application and environment.
Environment relevance: Distinguishes between laboratory, relevant, and operational environments—critical for technologies sensitive to thermal, mechanical, electrical, chemical, or radiation conditions.
Integration focus: Considers not only component performance but also interface control, system integration, safety, reliability, quality, and regulatory compliance appropriate to the intended use case.
Tailorable: Definitions are adapted by sectors (e.g., aerospace, defense, energy, automotive, healthcare) to reflect domain‑specific requirements and evidence.

The nine TRL levels (typical, summarized)

TRL 1: Basic principles observed and reported.
TRL 2: Technology concept and/or application formulated.
TRL 3: Analytical and experimental proof of concept (laboratory studies, bench‑scale validation).
TRL 4: Component and/or breadboard validated in a laboratory environment; initial interface and requirement definitions.
TRL 5: Component and/or breadboard validated in a relevant environment; preliminary reliability/safety evidence.
TRL 6: System/subsystem model or prototype demonstrated in a relevant environment; integrated testing, pilot builds.
TRL 7: System prototype demonstrated in an operational environment; near‑final interfaces and controls, limited trials.
TRL 8: Actual system completed and qualified through test and demonstration; conformity to specifications and applicable standards.
TRL 9: Actual system proven in operational use; sustained performance, reliability, and supportability demonstrated.

Typical evidence by stage (illustrative)

TRL 1–2: Publications, basic data, concept definitions, initial requirements and feasibility analyses.
TRL 3: Proof‑of‑concept experiments, simulations correlated with tests, early risk and hazard analyses.
TRL 4: Lab validation of components/subassemblies, verification plans, preliminary design for integration and test.
TRL 5: Testing in relevant conditions (e.g., temperature, vibration, duty cycles), initial safety/compliance checks, updated FMEAs.
TRL 6: Integrated prototype testing on relevant platforms, pilot‑line or pilot‑process runs, verification of interfaces and controls.
TRL 7: Operational‑environment demonstrations (e.g., field trials, fleet pilots), refined reliability growth and maintainability evidence.
TRL 8: Qualification/certification testing against standards, production‑intent designs and tooling, capability studies.
TRL 9: Operational performance data, field reliability and warranty data, continuous improvement metrics.

Relevance and applications

Cross‑sector use: Employed by agencies and industries (e.g., NASA, DoD, European Commission; aerospace, energy, automotive, advanced materials, health technologies) to reduce transition risk and align R&D with acquisition or commercialization timelines.
Systems engineering: Helps determine when a component or subsystem is ready to be integrated, and when a system is ready for fielding.
Example (materials and hardware): A new solid‑state battery electrolyte might progress from TRL 2 (concept formulated) to TRL 4–5 (cell‑level validation in relevant conditions), TRL 6 (module‑level prototype in vehicle‑relevant environment), TRL 7 (fleet trials), and TRL 8–9 (qualified and proven in production use).
Example (electronics): A wide‑bandgap power module may move from lab breadboard (TRL 4) to automotive‑relevant thermal/electrical cycling (TRL 5–6), to operational demonstrators (TRL 7), then qualification to standards and series deployment (TRL 8–9).

Related and complementary frameworks

Technology readiness assessment (TRA): The formal process used to assign a TRL based on evidence.
Manufacturing readiness level (MRL) and production readiness level (PRL): Assess producibility, yield, tooling, and supply‑chain readiness; commonly used alongside TRL.
Integration readiness level (IRL) and system readiness level (SRL): Assess maturity of interfaces and overall system readiness.
Commercial readiness index (CRI) or market readiness: Addresses business model, regulatory approval, customer adoption, and financing aspects.
Sector adaptations: NASA/DoD guidance, European Commission TRL definitions (Horizon programs), and industry‑specific checklists (e.g., those aligned with APQP/PPAP in automotive).

Notes and limitations

TRL is not a proxy for manufacturability, cost, supply‑chain robustness, cybersecurity, or business readiness; use with MRL/PRL, quality systems, and commercial readiness tools.
Definitions and evidence expectations vary by organization and sector; tailor criteria to the target application and environment to avoid over‑ or under‑estimating maturity.
A system’s TRL is constrained by both the maturity of its critical subsystems and the demonstrated integration of those subsystems; different elements can be at different TRLs.
Beware of “TRL inflation”: independent reviews and objective evidence reduce bias and improve comparability.
Mapping TRL to internal product‑development gates is useful but not one‑to‑one; maintain explicit entry/exit criteria at each gate.