NIH R25 Research Education Grant: How to Build a Training Program That Gets Funded

What the R25 Is and Who Actually Uses It

The R25 Research Education grant is NIH's mechanism for programs designed to educate, train, or retrain scientists — not to fund hypothesis-driven science itself. An R25 supports the structured activities that develop scientific capacity: intensive summer institutes, curriculum development for underrepresented undergraduates, workshops that teach early-career investigators a specialized technique, or re-training programs for mid-career researchers entering a new area. The mechanism spans nearly every NIH institute and spans a wide range of training populations, from high school students through established faculty.

Who actually applies? More PIs than you might expect. Department chairs building pipeline programs, established investigators launching career development workshops, research-focused nonprofits partnering with academic institutions, and center directors supplementing their P-grant infrastructure all use R25 regularly. If you've ever thought "I wish there were a better way to train people in this technique," you're probably thinking about an R25 application, whether you knew it or not.

One thing that surprises first-time R25 applicants: the R25 is not a research grant with a training component bolted on. Reviewers are explicitly evaluating the training program, not your research program. Your H-index and publication record matter far less here than your documented history of mentorship, education, and program development. That shift in emphasis catches a lot of very accomplished researchers off-guard.

Finding the Right R25 FOA — NOSIs and Institute Priorities

Unlike R01s, which can go to parent announcements with broad latitude, most R25 applications target institute-specific funding opportunity announcements that spell out exactly what kind of training program the institute wants funded. The NIGMS R25 portfolio looks nothing like NCI's or NIMH's. NIGMS runs R25s for research experiences for undergraduates and for building diversity in the biomedical workforce. NCI has FOAs for cancer education and for training data scientists. NIMH funds mental health services research training. Before writing a single page, identify the specific FOA you're targeting and read it cover to cover, not just the abstract.

The practical implication is that the FOA almost always dictates the training population, the program model, and the expected deliverables. If the FOA explicitly funds undergraduate research experiences and you propose a graduate-level curriculum, your application will likely come back administratively before it reaches review. Read the "Areas of Special Interest" section, then read the institute's current strategic plan, and only then decide whether your program idea actually fits.

One underused tactic: search NIH Reporter for currently funded R25 awards at your target institute. Read the abstracts of the most recent five to ten. You'll quickly learn what successful programs look like — their scale, scope, and framing — without having to guess from FOA language alone. The patterns across funded awards often tell you more than the FOA text itself.

The Program Plan: What Reviewers Actually Score

R25 applications don't use the five-criterion framework that governs research grants. Review criteria vary by FOA, but they typically cluster around three dimensions: the quality and feasibility of the proposed program, the qualifications of the leadership team, and the evaluation plan. Of these, the Program Plan is the document the whole application turns on.

Reviewers want a program that is operationally real. Specific activities, a clear timeline, named institutional partners, identified recruitment pipelines, and a training model grounded in something that has worked elsewhere. Vague programs score poorly. A proposal that says "we will offer workshops on relevant topics throughout the year" is essentially asking reviewers to fund a concept. A proposal that describes a 10-week intensive, names the techniques to be taught, identifies the faculty who will teach each module, and explains how trainees are recruited from partner institutions — that's a program reviewers can evaluate.

Training programs that have any track record have a significant advantage. If you've run anything at all — even informally, even a single pilot year — describe it. Participation numbers, informal feedback, career outcomes of people who went through the program. R25 reviewers treat a proof-of-concept pilot the way R01 reviewers treat preliminary data: it de-risks the proposal in a way that no amount of good writing fully replaces.

Budget and Personnel: What R25 Will and Won't Cover

R25 budgets are not modular. You write a detailed budget justification the same way you would for any research application with direct costs above the modular threshold. Budget caps and limits are set by the individual FOA and can vary widely — from around $150,000 in direct costs per year for small focused programs to well over $500,000 for large multi-institution efforts. Some institutes cap the total project period as well, so read the specific FOA budget section before building anything.

What R25 funds can cover: trainee stipends, program coordinator salary, supplies and materials directly tied to training activities, participant travel, and evaluation costs. What gets trickier is faculty salary support for program leadership. Some institutes restrict it significantly, others allow it at a reasonable level. These rules differ from standard NIH Research Policy Statement guidance, so "I assumed it works like an R01" is not a safe baseline here. The budget section of the FOA is usually explicit — if it isn't, contact the program officer before you draft numbers.

On personnel: the PI and any co-investigators or faculty mentors need biosketches that show relevant experience in education, training, or mentorship, not just research credentials. Reviewers score this separately from scientific expertise. A strong research record won't substitute for documented training experience. If your team is short on it, a well-chosen advisory board with external members who have program development and evaluation backgrounds can help close that gap.

The Evaluation Plan: The Section Most Applicants Phone In

This section separates strong R25 applications from mediocre ones, and it's where most researchers are least prepared. Reviewers for training-focused grants take program evaluation seriously, and many R25 FOAs now require it as a named section. The evaluation plan describes how you'll know whether the program worked: what data you'll collect, from whom, at what timepoints, and how you'll use those findings to improve the program during the award period.

Think of evaluation as the section that answers "how will you prove this was worth funding?" Strong plans name specific, measurable outcomes — degree completion rates, research publications from trainees, career trajectory tracking, self-reported skill gains using validated instruments — and include both a formative component (how you'll adjust mid-course when something isn't working) and a summative one (how you'll assess the program's overall impact at the end of each cycle).

If you've never designed a program evaluation, find a collaborator who has. A social scientist, education researcher, or someone with formal program evaluation experience listed as co-investigator or senior key personnel adds immediate credibility. Don't attempt to write boilerplate evaluation language and hope reviewers won't notice — the study sections that evaluate R25 applications often include members with deep expertise in education research, and they will notice.

R25 vs. T32 and R13: Choosing the Right Mechanism

Applicants sometimes conflate R25s with T32 training grants or R13 conference grants. They're different enough that the confusion usually produces applications that don't fit the mechanism. A T32 funds a structured program with predoctoral or postdoctoral trainees who receive stipends drawn directly from the award. The PI recruits trainees, supports them on the grant, and mentors them toward independent careers. T32s are larger, institution-administered programs that typically require substantial track records of trainee outcomes and demonstrated institutional commitment. If you're a junior PI thinking about a training program for the first time, an R25 is almost certainly the right starting point — not a T32.

An R13 funds conference and scientific meeting support. If your goal is to host a symposium or a multi-day workshop that doesn't involve a structured multi-year training pipeline, R13 is the right code. R13 applications are also exempt from the six-applications-per-year limit that took effect in late 2025 — so the mechanism has submission flexibility that R25s don't fully share. Worth noting if you're already close to your annual application ceiling.

The practical decision rule: if you're training a cohort of people over multiple years and measuring career outcomes, that's an R25. If you're running a discrete scientific event or a short concentrated series, that's an R13. If you need to support established predoc or postdoc trainees on stipends inside a large multi-mentor institutional program, that's a T32. When you can't tell which fits, call your target institute's program officer before you write — this is exactly the kind of scoping question they're happy to help with.

Frequently Asked Questions