RFA-HL-26-017: NIH Catalyze Product Definition for Small Molecules and Biologics (R61/R33)

RFA-HL-26-017: NIH Catalyze Product Definition for Small Molecules, Biologics, and Combination Products (R61/R33)

At a glance

What this opportunity is really for

This NOFO is aimed at teams in the translational pipeline for heart, lung, blood, and sleep (HLBS) diseases and disorders that need structured support to move a concept beyond early discovery uncertainty. The project goal is not generic basic science output; it is candidate progression through a defined developmental path. NIH positions this as a mechanism to build evidence and readiness for later preclinical advancement.

In practical terms, RFA-HL-26-017 covers projects focused on target identification and validation, preliminary screening and characterization, and early decision-ready progress to a lead series. The NOFO explicitly links this effort to the broader NHLBI Catalyze framework, including program administration through a coordinating center that supports milestone-driven planning and development guidance.

The mechanism name can look intimidating, but this matters because of the intended sequence:

• R61 phase supports focused early-stage activities that shape a credible candidate direction.
• R33 phase supports continuation toward lead-series development suitable for preclinical testing and development planning.

For applicants, this two-step architecture is important for proposal design. A weak R61 concept can fail before reaching R33 because this NOFO expects clear milestones and staged logic, while a strong, realistic R61 plan can survive review even if it does not promise certainty.

Why this is still active for 2026 and 2027

The NOFO includes a full schedule of recurring cycles. The page lists multiple open/closed windows with NIH review and award timelines and shows that submissions can continue through cycles that run into 2027, with an expiration reference in late 2027.

For planning on 2026-05-20, the immediately relevant dates in the public table include:

• Open date listed as November 22, 2024 (historical entry that shows the NOFO remains in force)
• Due-date tracks with multiple cycles, including new/renewal submissions due on February 11, 2026, June 18, 2026, and October 21, 2026
• Continued cycles through 2027 (for example, October 21, 2026 and February 11, 2027 entries for additional opportunity windows)
• Expiration reference date shown as December 24, 2027

This matters because NIH often reopens rounds with fixed windows while maintaining a single NOFO, so teams need to time their readiness and internal approvals for a target cycle rather than a one-off final deadline. As of the current check date, this is best treated as a recurring solicitation path, not a one-date deadline.

Who this opportunity is for

If your team is trying to build a clinical product line immediately and you only have a broad idea, this may be too early to be competitive unless you have defensible technical rationale and early data direction. If your program has a clear disease-relevant target, assay strategy, and translational plan, this route is a better fit.

A practical applicant profile:

• PI leadership with NIH account readiness (eRA Commons involvement is specifically required during submission workflow)
• Strong science/biomed team that can define biological rationale and deliver reproducible execution plans
• Institutions that can handle NIH modular application mechanics and respond within the review-ready schedule
• Collaborations that can support IP and regulatory planning in later translational phases

The NOFO states that any individual with appropriate skills, knowledge, and resources can be invited to lead (PI-level), but this is bounded by institutional and submission process requirements from Section III and submission instructions. Because many teams underestimate process obligations, it helps to treat NIH administration readiness as part of the scientific plan.

This is particularly suitable for:

1. Projects aimed at early therapeutic definition work where no single product candidate is yet proven.
2. Teams that can defend both innovation and feasibility, not just novelty.
3. Programs with clear translational checkpoints that can be articulated in milestone terms.

Not suitable if:

1. You are submitting a clinical-trial-ready protocol (this NOFO is explicitly non-clinical-trials in focus and described for product definition/lead-stage development).
2. You cannot identify a concrete, practical, and measurable output for the R61 phase.
3. You lack an internal process for NIH registrations, page limits, and compliance requirements.

Eligibility and fit: beyond simple yes/no

The NOFO indicates recurring criteria that are practical to convert into a pre-submission checklist:

• Applicant submissions are electronic only. Paper applications are not accepted.
• eRA/Grants system readiness is mandatory by submission date.
• Applicants should understand cost-sharing expectations as defined by NIH policy, even where exact percentages are not the first thing to check.
• Required registrations and IDs must be in place before due date.

This NOFO is a translational grant path, but it still behaves like a serious NIH award cycle where procedural noncompliance disqualifies proposals quickly. In review language, a technically excellent idea can fail on form errors.

A useful way to think about eligibility:

• Before writing, map your team against process obligations.
• Confirm the PI, institutional officials, and administrative contacts are aligned.
• Verify the institution can support SF424(R&R) mechanics, page limits, and attachment naming requirements.

If this administrative side is not in place, your best strategic move is to pause concept development and fix the application channel first.

What applicants need to submit or prepare

The NOFO’s application sections call out several key parts that are non-negotiable:

• Project planning in a staged, milestone-driven format tied to R61→R33 progression.
• IP and regulatory strategy attachment explicitly required with a defined filename (IP and Regulatory Strategies.pdf). Missing this attachment can render the application incomplete.
• Compliance with NIH How to Apply - Application Guide, plus any NOFO-specific additions.
• Use of ASSIST, Grants.gov Workspace, or institutional S2S submission routes.
• Alignment with page limits and other SF424(R&R) rules.

In practical terms, you should build three artifact buckets before writing:

1. Science packet: problem statement, rationale, proposed mechanism, milestone sequence, and feasibility pathway.
2. Compliance packet: registrations, signatures, account roles, profile requirements, and budget rules.
3. Program-specific packet: IP/regulatory attachment and translational justification for project phase progression.

How review works and what reviewers are likely to reward

The review section is highly informative for proposal strategy. Reviewers are expected to assess

• Significance and innovation
• Rigor and feasibility
• Investigator and environment quality
• Project-specific criteria, especially milestone clarity and phase realism

This means a winning narrative cannot hide weak execution details under broad ambition. The strongest applications tend to do three things well:

1. Define the scientific gap clearly: what is missing in current HLBS understanding and how your project addresses that gap.
2. Keep the translational logic explicit: how activities convert to candidate definition and then to lead-series options.
3. Ground claims with realistic project management: staffing, decision points, and fallback plans.

Common evaluation failure points seen across this NOFO family include over-claiming timeline certainty, under-describing risks, and treating milestones as marketing statements rather than operational goals.

Common mistakes in this NOFO path

1) Treating milestones as slogans

A common error is to list ambitious outputs without specifying the exact evidence required to prove progress at each stage. NIH review teams need measurable milestones; vague milestones reduce credibility fast.

2) Ignoring the R61/R33 logic

If R61 and R33 are described as a single lumped ask, the application can look strategically weak. You should treat R61 as a defined exploratory block and R33 as a next-stage path with conditional logic.

3) Submitting incomplete administrative prep as if it can be fixed late

The NOFO repeatedly emphasizes eRA/Grants readiness and explicit required elements. Missing account readiness, incorrect due-date submission routes, or incomplete mandatory attachments usually produces immediate penalties and delays.

4) Underestimating IP/regulatory complexity

Projects at this stage can still require careful IP framing. The NOFO explicitly requires the IP/regulatory attachment, and NIH looks for applicants who can discuss constraints and mitigation.

5) Weakly linking business and science stakeholders

Even if your project is not a business collaboration program, translational projects often involve external service, assay, or regulatory-facing stakeholders. Reviewers look for coherent execution structures, not isolated technical work.

A practical application strategy for 2026 and 2027 windows

Because this NOFO has recurring cycles, teams should avoid the common trap of rushing just before a single due date. Use a cycle-based cadence.

90 days before target deadline (or earlier):

• Lock core biological hypothesis and decision criteria.
• Define measurable phase transitions for R61 completion.
• Validate that the project can produce interpretable outputs at each stage.

60 days before:

• Build a compliant skeleton package in SF424(R&R) sections.
• Draft the IP/regulatory strategy with clear contingencies.
• Confirm every required registration and profile requirement with your administrative office.

30 days before:

• Run an internal compliance dry run with a reader familiar with NIH formatting and page limits.
• Verify due-date channel (ASSIST vs Grants.gov Workspace vs S2S) and final submission testing.
• Prepare a revision plan with dates and owners.

Submission week:

• Finalize attachments, including the named IP/regulatory PDF.
• Submit early enough to resolve technical errors.
• Avoid assuming late adjustments are harmless; late corrections are frequently the risk point.

For teams targeting 2026, the practical next internal milestone is usually the June 18, 2026 cycle unless your team is already in advanced draft state and can target another window. But because recurring cycles continue, the best strategy is to submit in the window that best matches your readiness while preserving data quality.

Review the most important official links and where to verify details

Before you submit, open all three layers:

1. The NOFO itself at the official NIH page.
2. The referenced How to Apply - Application Guide for technical compliance.
3. The Catalyze program site for program coordination context and cross-call strategy.

Direct official links

• Official opportunity page: https://grants.nih.gov/grants/guide/rfa-files/RFA-HL-26-017.html
• NIH How to Apply guidance referenced by this NOFO
• Catalyze program information: https://www.nhlbicatalyze.org

If any instruction between the NOFO and application guide appears inconsistent, follow the NOFO and note the date/version of your interpretation.

Frequently asked questions

Is this opportunity still useful for teams aiming at 2027?

Yes. The NOFO clearly shows recurring review/pool windows and remains active with expiration into late 2027. Teams should treat each cycle as a separate submission deadline.

Is there a single fixed budget ceiling?

The NOFO does not present a single fixed top-line award amount in a simple headline format in the short listing extract. Budgets are proposal-level and tied to project scope and NIH review expectations.

Is this eligible for clinical trials?

The title and sections identify this as a clinical trials not allowed pathway, with emphasis on early product-definition and preclinical preparatory development.

Can one team submit multiple proposals?

Section III suggests applicant organizations may submit more than one application if each is scientifically distinct, subject to overlap and duplicate constraints.

What happens if a required attachment is missing?

At least one required item in this NOFO is explicit: the IP and regulatory strategy attachment is required and missing submissions can be treated as incomplete and not peer-reviewed.

Is this only for large organizations?

No single-size shortcut is stated in the public excerpt. The practical deciding factor is whether the organization can run NIH-compliant application mechanics and deliver rigorous milestone governance.

Should you apply?

Apply if your project can answer three questions with confidence:

1. What biological target/problem will we solve, and why is this the right stage for this mechanism?
2. What is the exact milestone sequence from target validation to lead-series readiness?
3. Can we submit cleanly, on time, and with all required administrative and attachment requirements in place?

If you can answer all three clearly, this opportunity is a strong fit for teams converting early translational ideas into NIH review-ready development programs. If you cannot answer those confidently before drafting, fix the internal structure first and return before the next cycle.

Bottom-line summary

RFA-HL-26-017 is a serious, recurring NIH development opportunity in the 2026/2027 cycle for teams ready to operationalize early-stage therapeutic candidate work. Its value is in structure: recurring windows, strong reviewer focus on milestones and feasibility, and a mandatory quality bar on IP/regulatory preparation. For applicants willing to do the discipline work, this is one of the clearest federal routes for targeted product-definition science in HLBS through the NIH Catalyze ecosystem.