TRL 2 meaning: technology concept formulated, and how to show it
TRL 2 meaning in plain terms: technology concept formulated, how NASA and India's NTRAF define it, lab examples, the evidence checklist and how to reach TRL 3.
Part of the guide TRL levels explained: what TRL 1 to 9 really mean, and how to place your technology
TRL 2 means a technology concept or application has been formulated: a practical use for an observed principle is proposed, but no experiment yet proves it. NASA's exit criterion is a documented description of the application that addresses feasibility and benefit. India's NTRAF names TRL 2 research to prove feasibility and asks for a technical solution formulation document.
At TRL 1, a scientist has seen something and written it up. At TRL 2, someone has asked the next question: what could this be used for? The lab notebook moves from "we observed" to "we propose", and a specific application appears on paper for the first time.
Nothing has been built yet. There is no experimental proof that the application works. What exists is a concept, a set of calculations and predictions, and a reasoned case that it should work. This post explains how the main frameworks define TRL 2, what it looks like at the bench, what evidence a reviewer expects, and what it takes to move to TRL 3. If you are starting from the observation itself, read TRL 1 meaning first.
What does TRL 2 mean?
TRL 2 means technology concept and/or application formulated. Three things are true:
- A practical application of an observed principle has been identified.
- The application has been worked through on paper: calculations, models, literature, design sketches.
- There is no experimental proof yet that the application works as predicted.
NASA puts the key limitation plainly: the application is "speculative, no experimental proof or detailed analysis is available to support the conjecture."
How do NASA and NTRAF define TRL 2?
| Framework | Name or definition | What it says | Evidence asked for |
|---|---|---|---|
| NASA ESTO | Technology concept and/or application formulated | "Invention begins, practical application is identified but is speculative" | A documented description of the application or concept that addresses feasibility and benefit |
| India, NTRAF | Technology concept formulated; stage: research to prove feasibility | "Once basic principles are observed, practical applications can be invented. Applications are often speculative" | A technical solution formulation document, with the critical checklist items below |
Sources: NASA ESTO technology readiness levels and the National Technology Readiness Assessment Framework, published by the Office of the Principal Scientific Adviser.
NASA gives a separate description for software at TRL 2: basic properties of algorithms, representations and concepts are defined, basic principles are coded, and experiments are performed with synthetic data. NTRAF places TRL 2 inside the proof-of-concept stage, its TRL 1 to 3 band.
TRL 2 in the proof-of-concept band
What does NTRAF ask for at TRL 2?
NTRAF's TRL 2 checklist has eighteen items, each marked critical or not. The critical ones are the ones a reviewer will not let you skip:
| Critical item in NTRAF | What it looks like in a lab file |
|---|---|
| Potential applications for the system or component identified | A one-page note naming the application and who would use it |
| Paper studies show the application is feasible | Calculations, simulations or a literature review that supports the idea |
| An apparent theoretical or empirical design solution identified | A sketch, schematic or formulation outline |
| Expected performance of each technological element predicted | Numbers: expected sensitivity, yield, efficiency, strength, with the basis |
| Qualitative idea of risk areas (cost, schedule, performance) | A short list of what could go wrong |
| Rough idea of how to market the technology | Who is interested and how they will hear about it |
The non-critical items include identifying a customer, a customer expressing interest, a preliminary function analysis, a system architecture, analytical studies reported in journals or technical reports, an investment strategy sheet, knowing what experiments are needed, and an assessment of researchers and facilities. None of these is mandatory. Each one you have strengthens the case.
I like that the marketing question sits at TRL 2. Researchers often postpone it, and it is far cheaper to ask now than after a prototype has been built in a form nobody wants.
What does TRL 2 look like at the bench?
Three examples of the kind of work that sits at TRL 2:
| Field | TRL 1 observation | TRL 2 concept |
|---|---|---|
| Materials | A polymer film swells sharply when pH drops below a value | Proposal: use the film as a pH-triggered valve in a drug-release patch, with predicted response time from swelling data |
| Biotech | An enzyme from a soil isolate stays active at high temperature | Proposal: use it in a detergent formulation for hot washes, with predicted activity at wash temperatures from published kinetics |
| Electronics | A nanomaterial's resistance changes with humidity | Proposal: a low-cost humidity sensor for grain storage, with predicted range and drift from reported data |
In each case the TRL 2 file holds the same pieces: the observation and its source, the proposed application, the design idea, predicted performance with calculations, the main risks and the first experiment to run. None of it involves building the device. That comes at TRL 3.
Is a TRL 2 concept patentable?
It can be. Under the Patents Act, 1970, patentability depends on novelty, inventive step and industrial application, not on readiness. Section 3(c) excludes the mere discovery of a scientific principle, which is why a TRL 1 observation alone is hard to patent. A specific, workable application, which is what TRL 2 adds, can cross that line.
The practical risk is disclosure. A specification must describe the invention well enough to perform it, and at TRL 2 you may not yet know what works. Many researchers file a provisional specification once early data exist; under section 9(1) the complete specification must follow within twelve months of the provisional. Do not publish the concept in a paper or poster before you decide.
From TRL 2 to TRL 3
How do you move from TRL 2 to TRL 3?
TRL 3 is experimental proof of concept. To get there, choose the single function your concept depends on and test it in the lab: the film opens the valve at the right pH, the enzyme cleans at wash temperature, the sensor responds to humidity in the predicted range. Set the pass mark before you run the experiment, repeat it, and record conditions and raw data. When the results match your predictions, you have the core of a TRL 3 claim. Our guide on how to prove your TRL shows how to package the evidence.
Common mistakes
- Calling a concept TRL 3 because a related paper reported a similar result. Your own experiment is what counts.
- Writing an application so broad ("for healthcare") that no prediction can be tested.
- Skipping performance predictions. Without them, the TRL 3 experiment has nothing to confirm.
- Ignoring the market question until much later.
- Publishing the concept before deciding about a patent filing.
My view: most researchers spend too little time at TRL 2. A careful concept file with honest predictions saves months of unfocused experiments. I cannot say how long TRL 2 should take, because that varies widely by field, but the file itself is usually a few weeks' work.
If you want a structured check of where your work stands, TRL Pro gives an assessed level: you answer questions about your technology and its evidence, and get back a readiness level from TRL 1 to 9, assessed with Zernyx's own copyrighted framework (ZTRAF) covering more than 60 technology domains and subdomains.
Common questions
What is the difference between TRL 2 and TRL 3?
TRL 2 is a formulated concept supported by paper studies and predictions. TRL 3 is experimental proof of concept: the critical function has been shown in a lab experiment. If you have run the key experiment and it worked, you are moving into TRL 3.
What evidence proves TRL 2?
NASA asks for a documented description of the application or concept that addresses feasibility and benefit. NTRAF asks for a technical solution formulation document, and lists critical items such as identified applications, paper studies showing feasibility, an apparent design solution, performance predictions, a qualitative idea of risk areas and a rough idea of how to market the technology.
Can a TRL 2 invention be patented?
Often, yes. Patentability under the Patents Act, 1970 depends on novelty, inventive step and industrial application, not on readiness. A specific, workable application of a principle can be patentable, while the mere discovery of a scientific principle is excluded by section 3(c). Enablement can be hard at TRL 2, so get advice before filing.
Can software be at TRL 2?
Yes. NASA's software description for TRL 2 says basic properties of algorithms, representations and concepts are defined, basic principles are coded, and experiments are performed with synthetic data. Real data and integrated testing come at higher levels.