NSF's Translation to Practice Window Closes May 19: The Three-Track $30M Solicitation That Forces Researchers to Pick a Lane

The third proposal cycle of NSF's Translation to Practice solicitation (NSF 25-540) closes at 5:00 p.m. submitter local time on Tuesday, May 19, 2026 — and the way the program is structured, the deadline is doing more work than a typical NSF cutoff. TTP is a single solicitation with three tracks that look superficially similar but, on close reading, function as three different programs targeting three different stages of translational maturity. The agency's roughly $30 million in anticipated FY2026 funding is split across approximately 29 awards. The split is not advertised, but the per-award caps — $600,000 for Translation to Practice-Explore (TTP-E), $1.2 million for Translation to Practice-Translate (TTP-T), and $2 million for Translation to Practice-Partner (TTP-P) — combined with the mandatory $50,000 line item for I-Corps Teams training in TTP-T and TTP-P proposals, tell investigators exactly what kind of translation story NSF wants to fund at each price point.

The most consequential aspect of TTP is that it forces a binary decision researchers historically tried to defer. In the old translational-funding stack at NSF — Partnerships for Innovation, the I-Corps program, the Innovation Corps Teams supplement, and the early SBIR Phase I pathway — a PI could plausibly write a proposal that left the question of who would commercialize the technology, when, and through what mechanism somewhat soft. The original solicitation could be about "exploring translation opportunities," and the team could maintain optionality between licensing, startup formation, open-source distribution, or standards work. TTP eliminates that soft option. The track you choose declares your translation thesis publicly, on paper, to NSF reviewers who will hold you to it.

What Each Track Actually Is

TTP-E is the cheapest track and the only one that requires you already have an active NSF research award with at least one year remaining when the supplement is requested. The cap is $600,000 over up to 24 months. NSF describes the track as supporting "adventurous, high-risk" use-inspired research that extends an existing award toward initial translational activities. In practice, TTP-E is a supplemental funding mechanism: it does not start a new project, it bolts translational scope onto a project NSF is already paying for. Because TTP-E proposals are accepted any time rather than tied to the May/September cycle, the May 19 deadline does not apply to TTP-E. The track exists for current awardees who realize, partway through a research project, that the work has produced something the world might use.

TTP-T is the new-money track for solo translators. The cap is $1.2 million over up to 36 months. Prior NSF funding is not required, which means TTP-T is open to investigators whose translational thesis matured outside NSF-funded research — a critical opening for university faculty who built early-stage technology on internal seed funds, foundation grants, or DoD contracts and now need NSF-scale resources to mature the work. TTP-T does not require a formal partner organization, though the solicitation strongly encourages NSF-Catalyzed Partnerships and reviewers will evaluate "partnership strategic value" even when no partner is mandatory. TTP-T is the right track for technologies that need substantial additional engineering, prototype development, or systems-optimization work before any external partner can meaningfully engage.

TTP-P is the partnered track and the most aggressive. The cap is $2 million over up to 48 months. Like TTP-T, prior NSF funding is not required, but TTP-P does require at least one NSF-Catalyzed Partner from outside higher education to participate as Co-PI or Senior Personnel. The partner organization must contribute substantively to technology development and deployment — not just provide letters of support — and the proposal must articulate a clear path from the partnership's work to a product, process, service, open-source ecosystem, or standards adoption. TTP-P is the track for teams that already know who is going to commercialize their technology and can name them.

The $50,000 I-Corps Mandate

Hidden in the budget section of the solicitation is a constraint that materially changes proposal economics: TTP-T and TTP-P proposals must include $50,000 for an I-Corps Teams training cohort in Year 1, unless the PI completed I-Corps within the past two years. Up to an additional $50,000 may be allocated to patent-related expenses over the full award duration. The I-Corps requirement is not optional and is not waivable; it is the price of admission to TTP-T and TTP-P.

The implication is that a $1.2 million TTP-T award is really an $1.15 million research-and-translation award plus a forced customer-discovery exercise that NSF believes will catch translational teams who have not yet talked to the people they intend to serve. The same math applies to TTP-P at a $1.95 million effective ceiling. For investigators who completed I-Corps within the prior two years, the $50,000 is freed up for additional research scope — a meaningful advantage that quietly rewards teams already inside the NSF translational pipeline.

Why The May 19 Deadline Matters

May 19 is the second of two annual TTP-T/TTP-P deadlines, the other being the third Tuesday in September. The May cycle has historically been the larger of the two and the one where NSF program officers expend the bulk of their annual TTP allocation. Missing May 19 does not kill a proposal; it pushes it to September 15, 2026, and the September cycle from the prior fiscal year will not be reviewed until winter, with awards typically announced the following spring.

For teams whose technology has a competitive clock — venture-capital fundraising on a parallel timeline, an industry standards-body meeting in mid-2027, a strategic partner whose budget cycle resets in October — the deadline difference is the difference between funded translation activities running through 2027 and funded activities not starting until summer 2027 at earliest. The May 19 deadline is a forcing function that many translational teams will need to honor whether or not the proposal is fully polished.

How to Pick a Track

The track decision is not aspirational. NSF reviewers evaluate proposals against the track-specific criteria, and a proposal that fits poorly in its chosen track will fare worse than one that fits well in a less ambitious track. The decision rubric for principal investigators is roughly:

If you have an active NSF research award with more than a year of performance remaining and the translation activity extends that work rather than starting new work, TTP-E. The supplemental nature of TTP-E and its rolling submission window make it the lowest-friction entry into the program for current NSF awardees.

If you do not have current NSF funding, your technology needs additional internal engineering or systems-optimization work, and you do not yet have a partner organization willing to commit to development and deployment, TTP-T. The track is forgiving on prior funding history but unforgiving on translation specificity — the project description must clearly articulate the technical barriers between the current state of the technology and a market-relevant prototype.

If you do not have current NSF funding, you already have at least one external partner organization willing to take on substantive technology development and deployment responsibility as Co-PI or Senior Personnel, and the partnership can plausibly deliver a product, process, service, open-source ecosystem, or standards outcome within four years, TTP-P. The $2 million cap is substantial, and the four-year performance period is the longest of the three tracks, but the partner-organization requirement is real and binding — reviewers will scrutinize the partner's commitments and capability.

What Reviewers Are Reading For

Beyond the standard NSF merit-review criteria of Intellectual Merit and Broader Impacts, TTP proposals are evaluated on research motivation and compelling innovation description, identification of technical barriers and mitigation strategies, development timeline and path to market, team capability and expertise, and — for TTP-P — partnership strategic value. The "path to market" criterion is the one that most often catches academic teams unprepared. A vague endorsement of "potential commercialization" will not pass; reviewers want a specific articulation of who will buy, license, deploy, or adopt the technology, what evidence supports that, and what the team will do during the award period to validate or refine that hypothesis.

Medical research and clinical trials are explicitly out of scope. Investigators working on diagnostics, devices, or therapeutics intended for human use should be looking at NIH translational mechanisms, ARPA-H program calls, or BARDA solicitations — not NSF TTP. The exclusion is policed during the merit-review stage and is one of the most common reasons NSF returns TTP proposals without review.

The May 19 deadline is the moment the FY2026 translation portfolio at NSF takes shape. Proposals submitted on or before Tuesday will compete for roughly half of the $30 million the agency expects to award this fiscal year across the three tracks; the rest will go to teams whose work is ready for the September 15 cutoff. For investigators sitting on translation-ready research, the question is not whether to apply — it is which track most honestly describes the work, and whether the proposal can articulate a path to market specific enough that a reviewer will believe it.