TRL Milestone Planning Guide
Technology Readiness Levels (TRL) are the standard framework for communicating R&D maturity — used by NASA, the EU's Horizon Europe program, NSERC, Mitacs, and IRAP as the primary mechanism for milestone gating and funding disbursement.
This guide covers the nine TRL levels, the three major milestone gates, common governance failures that invalidate TRL claims, and execution principles for aligning funding agency requirements with actual technology development progress.
Where TRL Governance Fails
TRL Inflation
Teams self-assign TRL levels without external validation or defined exit criteria. A TRL 5 claim based on laboratory bench results — not a relevant environment — misrepresents technology maturity to funders, partners, and program managers, leading to schedule and budget shocks downstream.
Missing Exit Criteria
TRL gates are stated as level numbers without associated evidence requirements. When the next milestone is 'demonstrate at TRL 6' without specifying what constitutes demonstration, the gate becomes a negotiation rather than a verifiable achievement.
Disconnected Risk Register
TRL progression is managed independently of the program risk register. Technology maturation risks — material properties, manufacturing yield, qualification test failures — are not surfaced until they become schedule-critical, at which point recovery options are expensive.
Funding Misalignment
Funding agency milestone requirements (Mitacs, NSERC, IRAP) are mapped to calendar dates rather than TRL gates. When technical progress is slower than the funding timeline assumed, milestone reports describe outputs that don't correspond to the stated TRL — creating compliance exposure.
Technology Readiness Levels 1–9
Each level is defined by the evidence that must exist to claim that level — not by the activities underway. A TRL claim is only valid when the corresponding evidence package can be produced.
Basic Principles Observed
Basic ResearchScientific research identifies fundamental principles that could underpin a new technology. At this stage there is no application concept, no prototype, and no demonstration. Output: peer-reviewed literature, research hypotheses, and initial experimental results.
Technology Concept Formulated
Basic ResearchApplication of basic principles to a specific problem domain is described. Preliminary analytical and theoretical studies confirm feasibility. Output: technology concept document, feasibility analysis, initial specification of key parameters.
Experimental Proof of Concept
Applied ResearchActive R&D begins. Key functions are demonstrated analytically and experimentally. Proof-of-concept experiments validate that the underlying technology can perform the required function. Output: experimental data, proof-of-concept reports, early performance characterization.
Technology Validated in Lab
Applied ResearchComponent or system is validated in a laboratory environment. Individual components are integrated and tested together for the first time. Output: laboratory test results, integration architecture, preliminary performance against technical parameters.
Technology Validated in Relevant Environment
DevelopmentTechnology is validated in a simulated or representative operational environment. Fidelity increases significantly. Output: integrated system performance data in relevant environment, updated risk register, revised development timeline.
Technology Demonstrated in Relevant Environment
DevelopmentPrototype or representative model is demonstrated in a relevant environment. This is the transition from development to system integration. Output: prototype demonstration results, system integration requirements, qualification test plan baseline.
System Prototype Demonstrated in Operational Environment
DemonstrationPrototype is demonstrated in an operational environment — the actual deployment context, not a laboratory approximation. This is a significant program milestone: the technology must survive real operating conditions. Output: operational prototype test data, system qualification report draft, production readiness assessment.
System Complete and Qualified
DemonstrationTechnology is proven to work in its final form and under expected conditions. All qualification testing is complete. Manufacturing processes are defined and stable. Output: qualification test report, manufacturing readiness assessment, regulatory submissions (where applicable).
Actual System Proven in Operational Environment
OperationsTechnology is deployed in its actual operational environment and performing as specified. Full-rate production is underway or approved. Post-deployment monitoring and continuous improvement are active. Output: operational performance data, lessons-learned documentation, technology transfer package.
The Three Milestone Gates
Milestone gates are formal decision points where continued investment is justified by verified technical achievement — not by schedule. Gate criteria must be documented before the gate review, not assembled retroactively.
Research to Development Transition (TRL 3 → 4)
- Proof-of-concept experimental data reviewed and accepted by technical authority
- Key technology parameters identified and preliminary performance targets established
- Development risk register initialized with critical uncertainties quantified
- Development phase scope, resources, and schedule baselined
Development to Demonstration Transition (TRL 5 → 6)
- Laboratory validation results meet or exceed performance thresholds in relevant environment
- System integration architecture finalized and build-to specification released
- Qualification test plan baselined and reviewed by stakeholders
- Manufacturing readiness assessment initiated — early yield and process capability data
Demonstration to Operations Transition (TRL 7 → 8)
- Prototype demonstration results in operational environment documented and reviewed
- All qualification testing complete — no open waivers without disposition authority approval
- Manufacturing process stable and documented — first article inspection passed
- Regulatory submissions filed or received (where applicable)
TRL Execution Principles
TRL governance is only as reliable as the processes used to assess and validate each level. These principles apply across technology domains — from semiconductor process development to AI model deployment to quantum hardware characterization.
Every TRL gate should have a written evidence package requirement agreed by technical leadership, the PM, and the funding agency before the phase begins. Retroactive definition of exit criteria produces disputes, not governance.
Funding agency deliverable dates should be anchored to TRL evidence production events — data collection complete, report finalized, prototype demonstration scheduled. Calendar-anchored milestones with no technical event behind them are liabilities.
Each identified technology risk should have a TRL gate at which it must be resolved. If a thermal dissipation problem must be resolved before TRL 6 demonstration, that is a gate condition — not a general risk to 'monitor.'
Starting TRL should be assessed by a technical authority external to the development team — not self-reported. Disagreements about starting TRL are easier to resolve at program initiation than mid-program when schedule pressure is high.
TRL in Canadian R&D Funding Programs
Canadian federal and provincial funding agencies use TRL as both an eligibility criterion and a milestone reporting mechanism. Understanding how each agency operationalizes TRL is essential for compliant program management.
- NSERC Alliance Grants
Requires TRL 2–5 at application. Progress is reported against stated TRL targets in annual progress reports. TRL claims must be substantiated by referenced experimental outputs.
- Mitacs Accelerate and Elevate
TRL is used to scope internship deliverables. Internship research outputs must correspond to a defensible TRL claim. Mitacs reviewers assess TRL plausibility at application and during cluster reviews.
- IRAP (NRC Industrial Research Assistance Program)
TRL is central to IRAP's eligibility determination. Projects targeting TRL 6+ are eligible for IRAP ITS contributions. IRAP advisors conduct their own TRL assessment — independent of the applicant's self-assessment.
- Horizon Europe
Uses TRL definitions from the European Commission's Horizon Europe Work Programme. Proposal submissions must specify starting and target TRL per objective. TRL targets are evaluated against project budget and timeline plausibility.
Related Services and Resources
Managing a TRL-gated R&D program?
PMOVA provides senior PM leadership for R&D programs governed by TRL milestone frameworks — including Mitacs, NSERC, IRAP, and Horizon Europe funded projects. Gate-ready governance artifacts produced as standard delivery outputs.