PAR-25-338 academic industrial R01 eligibility Guide
Updated 6 official sources
Quick Answer: PAR-25-338 is an NIH R01 for academic-industrial teams translating technologies, methods, assays, devices, or systems into a usable state for diagnosis, treatment, monitoring, or research needs.
Full answer and how we checked it
It is clinical trial not allowed and should be compared with PAR-25-337 when clinical-trial work is planned. The 2026 decision turns on 7 checks.
Who this is for: Academic labs, company partners, engineering teams, clinical technology groups, diagnostic developers, imaging teams, research-tool builders, and sponsored-research offices deciding whether an academic-industrial R01 fits.
Data note: This guide uses NIH PAR-25-338, companion NIH PAR-25-337, correction notice NOT-CA-25-032, Grants.gov listing 357962, and USAspending award data. NIH dates were rechecked on October 10, 2026.
In this guide
- Source Check
- 6 PAR-25-338 Eligibility Stop Checks
- 5 Funding, Timing, and Mechanism Rules
- 5 Route Choices Before Drafting
- What NIH Doesn't Tell You
- 7 Evidence Assets That Make This R01 Stronger
- 7 Source-Backed Search Questions
- 21-Day R01 Routing Plan
- 6 Reviewer-Risk Signals to Fix
- 5 Applicant Types and Best Next Move
- 8 Applicant Memo Lines to Include
- 6 Common Route Mistakes
- 9 Review-Ready Proof Points
- 7 Route Checks
- Sources
PAR-25-338 is not a standard investigator R01. According to NIH PAR-25-338 (opens in a new tab), the route expects academic and industrial partners to adapt, optimize, validate, and translate a technology, method, assay, device, or system toward a useful state.
Some applications describe a partnership that sounds good but leave the roles unclear. For this route, the partnership is not decoration. It is part of the fit argument.
Use this guide with the live NIH Academic-Industrial Translation R01 program record. Then compare NIH grants complete guide, NIH R01 R21 R03 K awards comparison, what is a NOFO, NCI Assay Screening R01 guide, and the Grantsights grant database.
Source Check
Checked October 2026.
As of October 10, 2026, PAR-25-338 is active. The June 5 and October 5, 2026 new-application dates have passed. The next renewal, resubmission, and revision date is November 5, 2026. New applications next use February 5, 2027, then June 5 and October 5, 2027. Later renewal, resubmission, and revision dates are March 5, July 5, and November 5, 2027. We compared the NOFO's due-date table with the October 2026 calendar: a new application that missed October 5, 2026 should change the timing to February 5, 2027 rather than rush. NIH lists January 8, 2028 as the expiration date and a 5 p.m. local submission rule.
The March 31, 2025 update says applicants should reread the full opportunity and adjust applications before submission. The January 10, 2025 correction, NOT-CA-25-032, changed the goal statement to the broader NIH mission rather than a single institute-specific mission. For searchers, that means the first screen should not overstate this as only an NCI cancer technology route.
Get grant deadline alerts by email
About once a week, we email a short list of open grant calls with real deadlines from different funders. It isn't limited to the programs in this guide.
No spam. Unsubscribe anytime.
6 PAR-25-338 Eligibility Stop Checks
6 stop checks decide whether this R01 fits. The project should have both academic and industrial partners, a translational product or method, a specific problem, and non-trial scope.
| Stop check | Strong R01 signal | Red flag |
|---|---|---|
| Partnership | Academic and industrial roles are real | Industry partner is only advisory |
| Translation | Technology moves toward end-user use | Basic biology dominates |
| Product type | Method, assay, device, system, or tool is defined | Output is vague |
| Trial status | No NIH-defined clinical trial | Clinical-trial work is planned |
| Budget | Up to $499,000 direct costs per year fits scope | Budget is product-scale |
| End user | Use setting and validation needs are clear | No user or setting is named |
| Timing | February 5 or June 5, 2027 cycle fits | Application uses stale timing |
Don't use this route if the project is only basic research, commercial production, or a clinical study. Those are different paths.
5 Funding, Timing, and Mechanism Rules
5 public rules should appear before drafting. According to NIH, PAR-25-338 is an R01 clinical trial not allowed opportunity. NIH lists the opportunity's expiration date as January 8, 2028.
| Rule | Source-backed read |
|---|---|
| Funding number | PAR-25-338 |
| Mechanism | R01 research project grant |
| Clinical trial status | Not allowed |
| Budget | Up to $499,000 direct costs per year |
| Companion route | PAR-25-337, R01 clinical trial optional |
| Next new dates | February 5, 2027 and June 5, 2027 |
According to USAspending.gov (opens in a new tab) data, assistance listing 93.395 had about $1.14B in FY2024 obligations across 3,308 awards active that year.
5 Route Choices Before Drafting
5 route choices matter because technology translation can sit between NIH, SBIR/STTR, and company-funded development.
| Route | Better first read when... | Why |
|---|---|---|
| PAR-25-338 R01 | Academic-industrial team has non-trial translation work | Program fit is strong |
| PAR-25-337 R01 | Clinical-trial work is part of the plan | Companion route fits |
| SBIR/STTR | Company-led commercialization is central | Small-business route may fit |
| Parent R01 | Basic research is central | Partnership route may be wrong |
| Device or diagnostic route | Regulatory path dominates | More product-focused route may fit |
The best first move is a partner-role table. If the table cannot explain who owns development, validation, samples, data, end-user input, and project management, the partnership is not ready.
What NIH Doesn't Tell You
4 hidden readiness questions decide whether PAR-25-338 is worth pursuing.
First, NIH does not make a company name equal partnership. The company should bring tools, know-how, production capability, validation capacity, end-user insight, or data that the academic side lacks.
Second, NIH does not make translation the same as commercialization. The project should move a method or system toward use, but it is not meant to fund commercial production.
Third, NIH does not allow clinical trials here. If the project tests an intervention in humans to evaluate a health outcome, compare PAR-25-337 or another route.
Fourth, NIH does not make every technology project fit. The proposed output should address a specific research, clinical, diagnostic, treatment, risk, or monitoring problem.
Route choice in the active cycle matters most. A serious applicant needs the 2027 due dates, $499,000 annual direct-cost limit, no-trial boundary, companion PAR-25-337 route, and partner-role proof before building a budget.
7 Evidence Assets That Make This R01 Stronger
7 evidence assets help the application stand out.
First, define the target problem. The proposal should say exactly what research or clinical gap the technology will solve.
Second, show partner complementarity. The academic partner should not duplicate the company, and the company should not simply provide a letter.
Third, define the translated output. Method, assay, device, system, software, imaging approach, diagnostic tool, or measurement platform should be concrete.
Fourth, name end users. A tool for pathologists, imaging labs, rural clinics, research cores, or trial sites has different validation needs.
Fifth, include validation milestones. One university in California working with a diagnostics company on a low-resource pathology assay could state technical validation, user testing, sample handling, and reproducibility milestones.
Sixth, handle conflict and IP issues early. Academic-company partnerships need clear data rights, publication rules, and financial-conflict management.
Seventh, compare the companion route. If clinical-trial work is needed, PAR-25-337 may be more appropriate.
7 Source-Backed Search Questions
7 search questions should be answered directly. The first is whether an industry partner is required. NIH says each partnership should include at least one academic and one industrial organization.
The second is whether clinical trials are allowed. They aren't under PAR-25-338. PAR-25-337 is the companion clinical-trial-optional path.
The third is what the project should translate. NIH names technologies, methods, assays, devices, systems, diagnosis, treatment, monitoring, risk assessment, and related research or clinical needs.
The fourth is what budget applies. NIH lists a $499,000 direct-cost-per-year limit.
The fifth is whether foreign organizations are eligible. NIH lists foreign organizations as eligible, but applicants still need active registrations and institutional support.
The sixth is whether commercial production fits. The honest read is no. The route is for translation and validation toward use, not production.
The seventh is whether basic research fits. If the core question is biology and the technology is already established, a parent R01 may be better.
21-Day R01 Routing Plan
21 days is enough to decide whether the team should draft. Days 1 through 3 should confirm source status, deadline, trial status, budget, and companion route.
Days 4 through 7 should write the partner-role table: academic role, industry role, shared milestones, data rights, IP, and management.
Days 8 through 12 should define the technology translation path: current state, validation gap, end user, setting, and target problem.
Days 13 through 16 should build the milestone plan and compare SBIR/STTR, parent R01, and PAR-25-337.
Days 17 through 21 should prepare the program-staff memo and budget checks.
6 Reviewer-Risk Signals to Fix
6 risk signals should be fixed before submission. First, the industry role should not be vague.
Second, the project should not be basic research with a company letter attached.
Third, the clinical-trial status should be clear.
Fourth, end-user validation should be specific.
Fifth, the budget should match the translation path.
Sixth, data rights, IP, and publication rules should not wait until award.
5 Applicant Types and Best Next Move
5 applicant types commonly ask about PAR-25-338.
| Applicant type | Best next move | Why |
|---|---|---|
| Academic lab with company partner | Build partner-role table | Route may fit |
| Company-led team | Compare SBIR/STTR | Business route may fit |
| Clinical-trial team | Compare PAR-25-337 | This route bars trials |
| Basic research PI | Compare parent R01 | Translation may be weak |
| Sponsored-project office | Check IP, budget, and trial status | Compliance issues can block |
The best answer is: use PAR-25-338 when academic and industrial partners can translate a defined technology toward end-user use without a clinical trial.
If the company role isn't real, the end user isn't named, or the project is basic research with a partner letter, don't force it into this route.
8 Applicant Memo Lines to Include
8 memo lines help determine whether PAR-25-338 is a real fit. According to NIH, application budgets are limited to $499,000 in direct costs per year, so the partner plan should be realistic. Line 1 should name the target problem in research, diagnosis, treatment, monitoring, or risk assessment.
Line 2 should name the technology, method, assay, device, system, or tool and describe its current state.
Line 3 should state the academic partner's role. That role might include biology, specimens, clinical context, measurement science, algorithm development, or validation.
Line 4 should state the industry partner's role. That role might include manufacturing know-how, engineering, software, quality systems, platform access, regulatory insight, or deployment planning.
Line 5 should identify the end user and setting. A technology meant for pathology labs, imaging centers, rural clinics, research cores, or trial sites needs different validation.
Line 6 should state why the project is not a clinical trial. If clinical-trial work is part of the plan, PAR-25-337 should be reviewed instead.
Line 7 should define milestones that move the technology toward use, such as validation, reproducibility, performance, or cross-site testing.
Line 8 should explain data rights, IP, publication, and conflict management before the application goes in.
6 Common Route Mistakes
6 mistakes can make an otherwise strong technology project miss this route. First, a company letter is not the same as an industry partner. The partner should have work, budget, and responsibility.
Second, the project should not be basic research with a product label. Reviewers need to see adaptation, validation, and movement toward use.
Third, the user setting should not be vague. Translation depends on where and how the technology will work.
Fourth, clinical-trial work should not be hidden inside validation language. Trial status is a source-check issue and a review issue.
Fifth, the budget should not read like commercial production. NIH is funding research and translation work, not market launch.
Sixth, the application should not ignore the companion route. The clinical-trial-optional version exists for a reason, and the team should show it chose the correct one.
9 Review-Ready Proof Points
9 proof points should be visible before a team commits to PAR-25-338. First, the technology should be named. Second, the problem should be specific. Third, the academic role should be essential. Fourth, the industry role should be essential. Fifth, the end user should be named. Sixth, the validation setting should be clear. Seventh, the trial-status decision should be explicit. Eighth, the budget should fit the $499,000 yearly direct-cost limit. Ninth, the next route after validation should be stated.
According to NIH, each partnership should include at least 1 academic and 1 industrial organization. That requirement is not just eligibility language. It should shape the aims, budget, letters, milestone plan, and management structure.
7 Route Checks
Added June 2, 2026.
Checked on June 2, 2026 against PAR-25-338 (opens in a new tab), PAR-25-337 (opens in a new tab), NOT-CA-25-032 (opens in a new tab), the Grants.gov listing (opens in a new tab), and Grants.gov (opens in a new tab).
| Check | Public answer |
|---|---|
| Eligibility | Confirm the applicant, institution, and route rules for PAR-25-338 academic industrial R01 eligibility. |
| Source status | Verify the official listing, notices, due date, and expiration status. |
| Budget | Check award size, cost limits, match, or budget logic when the source provides it. |
| Evidence | Name the data, preliminary work, partner role, or implementation proof needed. |
| Bad fit | Stop if the project belongs in a nearby NIH or federal route. |
| Review criteria | Tie the first page to significance, approach, team, environment, and source-specific criteria. |
| Next action | Decide whether to draft, ask a program contact, or redirect to a nearby route. |
Final public checklist
- Confirm whether R01 is the right route or whether a nearby program fits better.
- Check budget, partner, match, or data-readiness constraints.
Sources
4 sources anchor this guide: the NIH R01 NOFO, the companion clinical-trial-optional NOFO, the correction notice, and the Grantsights public database record.
- NIH PAR-25-338 R01 NOFO: grants.nih.gov (opens in a new tab)
- NIH PAR-25-337 companion R01: grants.nih.gov (opens in a new tab)
- NIH NOT-CA-25-032 correction notice: grants.nih.gov (opens in a new tab)
- Grants.gov listing 357962: grants.gov (opens in a new tab)
- Grantsights grant database: Search NIH technology translation routes
Next steps
Where to go next
These next pages help you move from research into a specific grant choice.
Open PAR-25-338 record
Check active June and October 2026 timing, no-trial status, partner structure, and $499,000 cap.
Compare nanotechnology R01
Use when NCI technology translation or nanotechnology route choice controls fit.
Compare assay route
Use when assay development or screening fit may be stronger than the academic-industrial route.
Find grants that fit you
Free eligibility check: answer 9 questions and see ranked matches with deadlines and fit reasons.
Frequently Asked Questions
What does PAR-25-338 fund?
NIH says the R01 supports academic-industrial partnerships that adapt, optimize, validate, and translate technologies, methods, assays, devices, or systems for diagnosis, treatment, monitoring, or research needs.
Are clinical trials allowed?
No. PAR-25-338 is clinical trial not allowed. PAR-25-337 is the companion clinical-trial-optional route.
Is an industry partner required?
Yes. NIH says each partnership should include at least one academic and one industrial organization.
What is the annual budget limit?
NIH states that application budgets are limited to $499,000 in direct costs per year.
Who should skip this route?
Skip it if the project is basic research without translation, commercial production, or a clinical study.
Last updated October 10, 2026. Corrected October 10, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.
Related Guides
PAR-25-106 Cancer Nanotechnology R01 Eligibility Guide
NIH PAR-25-106 guide: NCI cancer nanotechnology R01 eligibility, clinical-trial-not-allowed fit, nanoscale criteria, and review checks.
PAR-24-280 clinical observational R01 eligibility Guide
PAR 24 280 clinical guide: 7 checks for eligibility, source status, budget, evidence, route fit, and review criteria in 2026.
PAR-25-317 family health R01 eligibility Guide
PAR 25 317 family health guide: 7 checks for eligibility, source status, budget, evidence, route fit, review criteria, and next steps in 2026.
PAR-25-112 language development R01 eligibility Guide
PAR 25 112 language development guide: 7 checks for eligibility, source status, budget, evidence, route fit, review criteria, and team readiness in 2026.
PAR-25-379 Native Health R01 Eligibility Guide
NIH PAR-25-379 guide: Native health intervention R01 eligibility, clinical-trial optional fit, community engagement, R01 versus R34, and review checks.
PAR-25-153 NCI Assay Screening R01 Eligibility Guide
NIH PAR-25-153 guide: NCI assay-development and screening R01 eligibility, clinical-trial-not-allowed fit, stages, and review checks.