How to prove your TRL: the evidence grant reviewers and investors expect

Every grant form and most investor decks ask for your technology readiness level. Many teams write a number and move on. Reviewers do not. They read your claimed TRL, then look for the evidence behind it, and a gap between the two costs you credibility on the rest of the proposal.

This guide is for researchers and startup founders who need to show, not just state, where their technology stands. If you are new to the scale itself, start with TRL levels explained, which covers what each of the nine levels means. This post is about proof.

The one rule: claim the highest level where nothing is missing

A technology sits at the highest TRL for which every requirement, at that level and all levels below it, is backed by evidence. Not the level you expect to reach by the end of the grant. Not the level of your best single experiment.

Two consequences follow:

• One strong result does not lift you a level. If your prototype worked once in the lab but you cannot show it works repeatably, you have not finished TRL 4.
• A gap at a lower level caps everything above it. A field trial (TRL 6 style evidence) on a design that was never validated as an integrated system in the lab invites hard questions.

What reviewers actually check

Across sectors, reviewers look at the same five things in your evidence:

1. The environment. Lab bench, simulated conditions, relevant environment or real operation. This single factor separates TRL 4, 5, 6 and 7 more than anything else.
2. The scale. Gram or litre scale, pilot scale, production scale. A result at 100 ml does not prove a process at 100 litres.
3. Integration. Did you test components one by one, or the assembled system?
4. Repeatability. How many runs, batches or units, and how consistent were the results?
5. Independence. Who ran the test? Your own team, a partner, an accredited lab, a user in the field?

If your documents answer these five questions clearly at each level, your TRL claim will stand up.

How BIRAC defines readiness, as an example

The Biotechnology Industry Research Assistance Council (BIRAC) publishes sector-specific TRL documents. It adapts the nine-level NASA scale and defines the levels separately for ten areas, including drugs, vaccines, biosimilars, medical devices and diagnostics, industrial biotechnology, agriculture, and AI, IoT and software. BIRAC says it uses TRLs to judge the maturity of core technologies during selection and later monitoring, and its definitions include the regulatory approvals and quality certifications relevant to each stage.

The industrial biotechnology document shows how concrete the expectations are. It describes TRL 3 as a concept proven and optimised at flask scale, TRL 4 as demonstration from lab scale to a bioreactor under 100 litres, with approvals such as RCGM or GEAC where GMOs are used, and TRL 5 as process development at that bioreactor scale including downstream processing. Scale and approvals, not just results, decide the level.

If you work in a BIRAC-funded area, download the document for your sector from the BIRAC website and use its wording. India's draft National Technology Readiness Assessment Framework (NTRAF) from the Office of the Principal Scientific Adviser points the same way: its detailed verification questions need supporting documents.

What evidence fits each level

The table below is a general guide. Your sector document, if one exists, takes priority.

The band from TRL 4 to TRL 6 is where most claims are challenged, because the environment and scale change at each step. Be most careful here.

Build a TRL evidence pack in five steps

An evidence pack is a short folder you can attach to a proposal, share with an investor under NDA, or hand to a licensee. It turns a number into something a reviewer can check in twenty minutes.

1. Define what you are assessing. A diagnostic kit has a reagent, a device and software. Each can sit at a different TRL. The product is only as ready as its least ready critical part, so say which part your claim refers to.

2. Pick the framework. Use your funder's sector document where one exists. Otherwise use a general nine-level scale and say which one.

3. Map each level to documents. For every requirement at every level, list the document that proves it: notebook pages, data files, test reports, photos or videos of the prototype, calibration records, third-party lab reports, user trial reports, regulatory submissions. Note the date, scale and conditions.

4. Mark the gaps honestly. Stop at the first level where a requirement has no document. That is your TRL. The gaps above it become your work plan.

5. Write a one-page summary. State the claimed TRL, the three or four strongest pieces of evidence, the next level you aim to reach, what it will take and what it will cost. This page is what most reviewers read first.

A structured tool helps keep this consistent across projects. TRL Pro assesses readiness from TRL 1 to 9 using Zernyx's own copyrighted methodology, which covers more than 60 technology domains and subdomains, and records the evidence behind each answer so you can reuse it in proposals.

Matching your TRL to the funding you ask for

Funding schemes and investors are built for different stages. BIRAC's Biotechnology Ignition Grant (BIG), for example, gives early-stage support of up to ₹50 lakh over 18 months to help take an idea to proof of concept, with calls usually announced on 1 January and 1 July. A proposal for a scheme like that should show a credible concept and a clear plan to prove it, not claim a field-ready product.

The common error runs both ways. Teams overstate their TRL to look investable, and reviewers see the gap. Or they understate it and ask for money to repeat work already done. Read the scheme's own guidelines for the stage it funds, then match your claimed TRL and your milestones to it. Patent timing matters too: if you plan to publish results, file first. Our guide to low-cost patent filing for startups covers the route.

Common mistakes

• Claiming the target, not the status. Write where you are today, and put the target in the milestones.
• Lab results described as field results. "Tested on real samples" is not the same as "tested in the field". Say where and how.
• No dates or scale on the evidence. A graph without conditions proves very little.
• One TRL for a whole product with uneven parts. Assess each critical part.
• Ignoring approvals. In regulated sectors, missing approvals cap your TRL however good the data.

FAQ

Do grant applications in India require a specific TRL?

It depends on the scheme. Many describe the stage they fund, such as proof of concept or validation, rather than a single TRL number. Read the scheme guidelines and, for BIRAC schemes, the TRL document for your sector.

What documents prove TRL 4?

Typically a description of the integrated lab prototype, test protocols, repeated test results with dates and conditions, and photos or videos of the prototype working. In some sectors, approvals or scale limits also apply at TRL 4.

Can I claim a TRL based on someone else's published work?

Only for the levels where the published work covers your exact technology. Your own TRL depends on what you have built and tested. Cite earlier work as background, not as proof of your readiness.

How often should I reassess my TRL?

At every major milestone, and before each grant application, investor round or licensing discussion. Update the evidence pack at the same time.