The NIH R61/R33 Phased Innovation Award: Milestone-Driven Grant Strategy

What the R61/R33 Mechanism Is and Why NIH Uses It

The R61/R33 is a two-phase activity code. The R61 phase is designed for feasibility testing or early-stage development, typically one to two years with a budget cap set by the parent funding opportunity announcement. If the project meets its defined milestones at the end of the R61 phase, NIH transitions it to an R33 phase, which provides up to three additional years of support to carry the work through to its fuller research aims.

NIH introduced the mechanism to address a structural problem it had long recognized: early-stage translational projects often can't justify R01 budgets before a key feasibility question is answered, but they're also too ambitious and too progress-dependent for a standalone R21. The R61/R33 gives NIH a way to fund both phases under a single peer-review event, with a programmatic go/no-go decision built into the middle. That structure matters for NIH as much as it matters for applicants: it lets the agency commit resources to a validated plan rather than a speculative one.

That go/no-go decision is where the mechanism gets interesting, and where most applicants make strategic errors. The R61 phase isn't an R21 with an R01 attached to the back. It has its own logic, its own review criteria, and its own risks. Writing a strong R61/R33 application means understanding all three before you draft the first sentence.

How the Two-Phase Structure Works in Practice

At submission, you write a single application that describes both phases. Reviewers score the entire application, including aims, approach, and significance across both phases, but they also evaluate the feasibility of the R61 phase independently and the rigor of the milestone criteria you've proposed. The two phases share a budget section, and reviewers can comment on the balance between them.

The R33 phase doesn't get its own peer review. If you meet your R61 milestones, your program officer and grants management office process the R33 transition administratively. If you don't meet the milestones, the award ends. There's no re-review, no appeal process analogous to an A1 resubmission. The milestone structure is the contract, and it's interpreted by your program officer, not a study section.

That last point shapes how you should write this application. You're not just proposing interesting science. You're proposing a decision rule that NIH staff will use one to two years from now to decide whether the R33 phase activates. That decision rule needs to be binary, time-bound, and written in terms of outcomes your lab controls.

Budget planning across both phases also deserves more care than most applicants give it. The R61 phase is usually smaller than the R33, but the ratio isn't fixed. Reviewers will notice if the R33 budget is disproportionate to the R33 aims, and they'll question whether you've thought through what the work actually requires at each stage. In modular budget terms, think about whether the science justifies the module count before you finalize the numbers.

Writing Milestones That Actually Get Funded

Reviewers and program officers reading the funded application later want milestones that are binary, time-bound, and meaningful. These three properties sound obvious but are harder to achieve than most applicants expect, and the failure to get them right is the single most common weakness I see in R61/R33 applications.

One common mistake is setting milestones that are too easy, such as "complete recruitment" or "finish data collection," because applicants fear that rigorous milestones increase the risk of not triggering the R33. They do. But milestones that don't represent real decisions also reduce your chances of getting funded in the first place, because experienced reviewers can tell. Write two or three milestones, each mapping clearly to a specific R61 aim. The milestone statement itself should be one sentence, with one or two clarifying sentences on how it will be assessed and what constitutes passing.

The Stage Gate: Planning Your R61 to R33 Transition

The transition from R61 to R33 isn't automatic. It requires you to submit a milestone progress report, usually six months before the R61 phase ends. Your program officer reviews this report and recommends whether to proceed. NIH then issues documentation to continue the award under the R33 activity code. The specifics vary by funding opportunity announcement, so read the instructions for your FOA carefully before you plan your timeline.

Plan backward from this transition moment when you're writing the application. Ask yourself: what will I need to have in hand six months before my R61 ends? Work back from there to determine what your first-year activities need to accomplish. Applicants who don't think about the transition timeline until year two of the R61 often find themselves rushing milestone data collection while also managing progress reports and preparing new submissions. That's an avoidable situation, and it's one your reviewers are likely to flag if your timeline section doesn't show that you've planned for it.

The R33 phase has its own specific aims and approach, and these need to be written in the original application as a serious, scoped plan rather than a placeholder that assumes the R61 will succeed. Reviewers know the difference. A well-designed R33 section signals that your thinking is mature and that the milestones you set for R61 are grounded in a coherent downstream plan. A vague R33 section raises the question of whether you actually know where this work is going once the feasibility phase ends.

Your R33 aims should be written to stand on their own scientifically. The connection to R61 should be clear, but the R33 shouldn't read as contingent on a specific R61 outcome. If the R61 reveals that your assay needs a different approach, a well-written R33 can accommodate that — if the R33 is written narrowly around one expected R61 result, a partial milestone outcome will leave you in a difficult position with your program officer.

Which Institutes Use R61/R33 and for What

Not all NIH institutes use this mechanism. The most active users have historically been NHLBI, NCI, NIBIB, NIDDK, and NICHD, often for technology development, assay validation, device testing, and early-phase translational work. NIDCR has used R61/R33 for certain clinical studies. NCI uses variations of phased mechanisms across its precision medicine and early detection programs. This picture can shift by fiscal year, so treat these examples as a starting point, not a definitive map.

If you're unsure whether your target institute has active R61/R33 opportunities, search NIH Reporter for awards with the R61 activity code within the relevant institute over the past four fiscal years. This is more useful than reading general mechanism descriptions. You'll see actual budget ranges, the kinds of projects that get funded, and the program officers attached to awards in your area. When you find a funded R61 that looks close to your work, it's worth contacting that program officer before you submit to confirm that a new application in your area would be welcomed.

The R61/R33 is also used in certain Requests for Applications where NIH has a specific translational question and wants a gating structure built in. These RFA-driven awards tend to have narrower scientific scope than parent announcements and sometimes carry modestly higher budgets. If a relevant RFA exists when you're ready to submit, it's usually worth pursuing over the parent announcement, both for the scientific fit and for the more concentrated reviewer pool that comes with a targeted RFA.

R61/R33 vs. R21 vs. R01: Choosing the Right Mechanism

The mechanism question comes up early in project development and has real consequences for how reviewers read your application. Here's how to think through it.

The R21 is right for exploratory work where the main deliverable is a demonstration of feasibility or a new approach, and where a two-year project with a modest budget would be satisfying even if the work doesn't extend further. If you're testing whether a model system is viable, an R21 fits. If you're validating a clinical assay with the intent of running a larger study afterward, it probably doesn't. The R21 doesn't give you the runway to reach a meaningful clinical endpoint, and reviewers may question why you're not proposing the full work.

The R01 is appropriate when your preliminary data are strong enough that the main feasibility question is substantially answered and the main work is executing the full study. Writing an R01 when you're still testing a key assumption is risky. Reviewers will push back on the unproven elements, and if you have a strong R61/R33 option available, an R01 may not be the best fit for the current maturity of your project.

The R61/R33 sits between these two. It's right when you have genuine feasibility uncertainty that can be resolved with one to two years of focused work, when the answer to that feasibility question would meaningfully change your R33 scope or approach, and when you can articulate both phases clearly at the time of submission. If your project can't pass that three-part test, consider whether a different mechanism would serve you better before you invest several weeks in the application.

Frequently Asked Questions