NSF Translation to Practice 2026–2027: Up to $2 Million to Move STEM Innovations into Use

NSF Translation to Practice 2026–2027: Up to $2 Million to Move STEM Innovations into Use

The U.S. National Science Foundation’s Translation to Practice (NSF TTP) program is an active funding route for U.S.-based research organizations that have a credible STEM discovery or innovation and need to turn it into something people can use. The program is broader than a startup grant and more practical than a basic-research award: it supports the work between a laboratory result and a usable product, process, service, standard, open-source effort, licensing outcome, or other real-world application.

The current solicitation, NSF 25-540, has three tracks matched to different stages of translation. TTP-Explore extends an eligible existing NSF award for early, high-risk use-inspired work. TTP-Translate supports teams that need to mature and validate a solution. TTP-Partner supports translation and deployment work that requires an external partner. The next full-proposal deadline for TTP-Translate and TTP-Partner is November 17, 2026, at 5 p.m. in the submitting organization’s local time; the next listed 2027 deadline is May 18, 2027. TTP-Explore requests are accepted anytime, subject to its separate eligibility and prior-approval rules.

This guide reflects the official solicitation and program page checked on July 29, 2026. It is a preparation guide, not a substitute for the current NSF TTP solicitation, the applicable NSF Proposal & Award Policies & Procedures Guide, or institutional sponsored-research review.

Key details

What NSF TTP is designed to support

NSF describes translation to practice as moving findings, knowledge, or theoretical concepts from the laboratory into real-world impact. In this program, that can lead to commercial activity, but commercialization is not the only valid outcome. The solicitation expressly contemplates products, processes, services, open-source projects, standards-setting work, licensing, startup or small-business formation, nonprofit or for-benefit entities, and collaborations that make an innovation usable at scale.

The project still needs a STEM foundation and a practical reason to exist. A proposal should identify a concrete problem faced by consumers, industry, government, or another defined group; explain the underlying discovery or innovation; and show how the proposed translation activities close a real gap. A polished business narrative cannot replace the research and development case, while a strong technical result without an intended user, deployment context, or measurable benefit will not show the program fit.

The program is not a fit for medical research or clinical trials; NSF says those may be returned without review. Health-related engineering, data, or technology projects may need special care to distinguish a technology-translation plan from medical research. When scope is uncertain, contact the program rather than trying to stretch a clinical study into this solicitation.

Choose the right track before you write

TTP-E, TTP-T, and TTP-P are not steps that every applicant must take in sequence. NSF says proposers should enter at the track that fits the maturity of the technology or innovation. The choice changes eligibility, funding scale, partnership requirements, and preparation work.

TTP-Explore (TTP-E) is for a current, eligible NSF awardee who wants to extend foundational research toward adventurous, high-risk use-inspired and initial translation activities not covered by the original award. It can support activities such as interdisciplinary collaboration, community engagement around an open-source product, student internships with industry, and work to mature technology readiness. The award is estimated at about $600,000 for up to 24 months. It is not an open competition for any promising project: the underlying NSF award needs at least one year remaining, approved annual reporting, and eligibility under the solicitation. EAGER, RAPID, and RAISE awards cannot receive TTP-E funds.

TTP-Translate (TTP-T) is the usual route for a team that already has use-inspired research or an early translational result and needs to make it more mature, reliable, scalable, or accessible. Prior NSF funding is not required. NSF gives examples such as iterative prototype testing, industrial-process optimization, patent-supporting work, open-source design and implementation, and standards development. A strategic partner is encouraged but not required. TTP-T can request up to $1.2 million for up to 36 months.

TTP-Partner (TTP-P) is for translation efforts where one or more outside partners are essential to technology development or deployment. The required NSF-Catalyzed Partner may be from industry, government, philanthropy, an international organization, or another relevant organization. The proposal must name a co-PI or senior/key person who is a member or employee of that partner, and a collaboration letter is required. TTP-P strongly prioritizes non-academic partners able to help bring the solution into practice. It can fund up to $2 million for up to 48 months.

Who can apply

The proposal must come from an eligible U.S. organization. NSF permits accredited two- and four-year institutions of higher education, including community colleges, that have a U.S. campus and apply for their faculty members. It also permits U.S. nonprofit, non-academic organizations directly associated with educational or research activities, including independent museums, observatories, research laboratories, and professional societies.

An individual cannot submit independently. By the deadline, the PI must hold either a tenured or tenure-track appointment, or a primary full-time paid research or teaching appointment as determined by the submitting institution. A PI or co-PI may have only one NSF TTP proposal under review at a time across all three tracks, and must wait for NSF’s determination before submitting another. There is no stated organization-wide limit.

TTP-E adds two key gates. The proposer needs an active eligible NSF research award and must send the cognizant NSF program officer a three- to five-page description of the planned future translation activities. The program officer must approve that request by email before the TTP-E proposal is submitted. Include the invitation email in the supplementary documents; NSF says a TTP-E request without it will be returned without review. A team without this route is not shut out: it may apply directly to TTP-T or TTP-P if it meets their terms.

What a competitive proposal needs to establish

Start with the real-world driver. The official instructions ask applicants to identify the societal or market need, the potential users or stakeholders, the intended outcome, and why the proposed translation is necessary. State the comparison point plainly: what does the current process, product, or service fail to do, and what specific improvement would adoption produce? Avoid defining the problem only through the novelty of the research.

Then make the development path testable. TTP-T and TTP-P project descriptions may be up to 15 pages and need an executive summary, research motivation, and development-of-solutions sections. NSF expects a concrete account of technical barriers, the experiments or work needed to overcome them, validation before full implementation, a timeline of critical milestones, success measures, alternatives if objectives fail, and risk mitigation. This is the core of the application. A claim that a prototype is “ready to scale” should be supported by the remaining engineering, integration, cost, compliance, supply-chain, interoperability, intellectual-property, and user-adoption work.

Finally, give the team and partner plan equal weight. Explain who owns the technical work, stakeholder discovery, validation, intellectual-property decisions, and deployment relationship. TTP-P needs a partner whose role is material to translation, rather than a logo on a slide. Letters of support are not allowed for any track, but letters of collaboration are required for TTP-P and encouraged for TTP-E and TTP-T. A collaboration letter must be on the organization’s letterhead, signed by an appropriate representative, and say how the relationship adds value.

Application process and required materials

For TTP-T and TTP-P, the first operational decision is whether to submit through Research.gov or Grants.gov. NSF permits either, but separately submitted multi-organization collaborative proposals must use Research.gov. Importantly, all TTP proposals must be submitted by one institution. Linked collaborative proposals in which several organizations each request a separate award for the same project will be returned without review. Set the lead institution and any subaward or partner arrangement early.

The cover-sheet title must begin with the appropriate track label: NSF TTP-E:, NSF TTP-T:, or NSF TTP-P:. The project summary is written in third person and must include an overview, intellectual merit, and broader impacts. Its overview should identify the need, application area, potential stakeholder, and possible outcomes. Do not put proprietary information in that summary.

For TTP-T and TTP-P, make the executive summary specific about the driver, innovation, value proposition, differentiator, and how the team will measure it. The project description must show the existing state of the art, the route to the end goal, barriers and validation, milestones and metrics, risk plans, team capability, and, for TTP-P, the merits of the partner collaboration. NSF also requires a substantive, project-specific data-management and sharing plan of no more than two pages. If the work may create valuable intellectual property, explain its protection and management there rather than offering only generic data-sharing language.

The solicitation permits up to $50,000 over the project duration for the applicant institution’s allowable TTP-related patent expenses. It does not permit voluntary committed cost sharing. These are budget rules, not reasons to add a speculative patent line; work with the technology-transfer and sponsored-programs offices to ensure the budget matches the project’s actual translation plan.

Timeline and a disciplined preparation plan

For the active TTP-T and TTP-P cycle, the practical target is November 17, 2026, at 5 p.m. local time of the submitting organization. The next listed full-proposal date is May 18, 2027. Because NSF sets these as recurring third-Tuesday deadlines in May and November, verify the program page before relying on any future date. TTP-E proposals are accepted anytime, but that does not eliminate planning time: prior program-officer approval is mandatory.

Use the first preparation phase to create a one-page translation hypothesis. Identify the research outcome, target user, decision-maker or buyer where relevant, unmet need, required proof, endpoint, and the biggest reason the idea could fail. This document should let the research lead, technology-transfer office, and external partner agree on what will be built or changed during the award.

Next, turn that hypothesis into a milestone map. Each milestone should have a deliverable, method, decision criterion, owner, date, and fallback. For example, a prototype milestone should say which use condition will be tested, what comparison will be made, what result permits the next investment, and what the team will do if it misses. A date-only work plan does not give reviewers evidence that the team knows when to pivot.

For TTP-P, complete partner due diligence early. Establish the partner’s contribution, the named employee who will serve as co-PI or senior/key personnel, authority to sign the collaboration letter, any data or equipment access, and intellectual-property expectations. For all tracks, let the institutional sponsored-research office review registrations, budget mechanics, and the applicable PAPPG before the final submission window.

How NSF will review the application

All NSF proposals receive review under the National Science Board’s Intellectual Merit and Broader Impacts criteria. TTP-T and TTP-P also receive solicitation-specific scrutiny. Reviewers will ask whether the proposal identifies a compelling unmet need, clearly identifies stakeholders and expected impacts, and explains the innovation’s potential commercial, economic, or other value.

They will also examine whether the team has described the technical barriers before translation and deployment. NSF specifically calls out safety, compliance, scalability, integration, compatibility, sustainability, cost, and intellectual property or licensing as examples. The proposal should make its validation plan, milestones, success metrics, risk mitigation, resource needs, and time to deployment credible. If an innovation depends on a partner, reviewers assess whether the partnership is strategic, complementary, and likely to accelerate translation.

The practical drafting lesson is simple: write the proposal so a reviewer can trace every claimed benefit to a technical or implementation activity, a measurable milestone, and a capable person or partner. Do not rely on enthusiasm, an untested market assertion, or vague language about impact.

Common mistakes to avoid

The most common mismatch is choosing a track based only on its dollar ceiling. TTP-E is not a general seed grant; it is an extension of an eligible active NSF award with prior program-officer approval. TTP-P is not simply a larger TTP-T award; it requires a genuine NSF-Catalyzed Partner and qualifying named personnel. Choose the track that matches the evidence and relationship you already have.

Another error is treating the external partner as an endorsement. NSF does not allow ordinary letters of support. A TTP-P collaboration letter must explain the partnership’s substantive contribution. Make the proposed work impossible to misunderstand: what does the partner contribute, why can it not be replaced by a generic adviser, and how does it help get the solution into use?

Do not hide the hard parts. A credible TTP proposal names the technical, regulatory, production, integration, access, and adoption uncertainties and then provides mitigation. Reviewers have been instructed to consider those obstacles. A transparent plan with decision points and alternatives is more convincing than a smooth narrative that assumes every prototype test will succeed.

Frequently asked questions

Can a startup apply directly?

Not under the listed submitting-organization categories unless it is applying through an eligible organization. TTP is designed around qualifying U.S. higher-education institutions and certain nonprofit non-academic research or education organizations. A company can be an important NSF-Catalyzed Partner, especially for TTP-P, but that is different from being the submitting organization.

Does TTP-T require prior NSF funding?

No. The solicitation says TTP-T and TTP-P proposals may build on NSF or other federally funded discoveries and innovations, but prior federal funding is not required. TTP-E is the exception because it extends an eligible active NSF research award.

Are partnerships mandatory?

They are encouraged for TTP-E and TTP-T. TTP-P requires an NSF-Catalyzed Partnership, including a co-PI or senior/key person employed by or a member of that partner, plus a collaboration letter.

Is there a letter of intent or preliminary proposal?

No. The solicitation states that neither is required. That does not remove the need for early internal review, especially because TTP-E has its own advance-approval requirement.

Where should applicants ask questions?

NSF lists the TTP Program at [email protected] and (703) 292-4800. Use the official solicitation and program page as the controlling sources for changes, program webinars, and any NSF-Direct Partnership notices.

Official links and next step

• NSF 25-540 full solicitation
• NSF Translation to Practice program page
• NSF proposal-submission guidance

If the innovation has a defined use case, a clear technical gap between today’s result and a usable outcome, and an eligible institutional home, NSF TTP is a timely 2026–2027 option. Start by selecting the correct track, writing measurable milestones, and ensuring that the submitting organization and any partner arrangement meet the solicitation’s terms before investing in full proposal drafting.