How TRL levels are actually assessed differently by UKRI, EIC, and defence funders

TRL frameworks look universal. They aren't. The same technology, with the same evidence, can sit at different levels depending on who's assessing it — and mis-stating your TRL is one of the fastest ways to lose credibility in an application.

Innovate UK cares about your testing environment. For them, TRL 5 means validated in a relevant environment — and they mean it. A prototype tested in your own lab under controlled conditions, but not with real users or real operating parameters, is TRL 4 at best. The distinction between "laboratory" and "relevant environment" is where most over-claims happen, usually from genuine ambiguity rather than dishonesty.

The EIC Accelerator now requires TRL 5 completed before you apply. This is clarified in the 2026 Work Programme — "completed" means you have empirical evidence, not a plan to get there during the project. The new technical due diligence at Step 2 means a domain expert will challenge your claim directly. If you're genuinely at TRL 5, this protects you from competitors who overstate. If you're stretching, it's a problem.

Defence funders think in two dimensions. DASA and DTIL assess manufacturing readiness alongside TRL. A technology can be TRL 6 but MRL 2 — technically demonstrated but nowhere near producible. If you're applying to defence programmes, you need to address both or your credibility takes a hit regardless of your evidence.

Software TRL is the wild west. A working MVP is not TRL 7. If it hasn't been tested in its operational environment with representative users under realistic conditions, most funders would place it at TRL 5 at most.

The honest approach: state your TRL for the specific funder you're addressing, reference their definition, and provide evidence that maps to their criteria. If you're unsure where you sit, that's one of the most valuable pre-application conversations you can have.