RFA-HL-26-016: Catalyze Enabling Technologies and Transformative Platforms for HLBS Research (R33)

RFA-HL-26-016: Catalyze Enabling Technologies and Transformative Platforms for HLBS Research (R33)

If your lab has a promising HLBS-oriented technology that is beyond the pilot stage but still needs a major validation push, this NIH opportunity is unusually structured around execution discipline. It is not a generic discovery grant and it is not an implementation grant for a whole clinical product. The call is explicitly designed for enabling technologies and transformative platforms that can be moved from “interesting proof of concept” to a stage where real-world translation is plausible and measurable.

This opportunity lives under NHLBI’s Catalyze framework and is intended to fill a real gap between exploratory innovation and downstream translational programs. It is a competitive R33 mechanism and therefore has practical constraints that are easier to satisfy if your team already has hard data, a clear performance model, and project management capacity.

The official page lists this as an NIH opportunity with no clinical trials allowed and a two-year maximum project period. The NOFO indicates repeated application due dates, which means timing is important if you are missing this spring cycle but can target a later open window.

Key details at a glance

What this funding is specifically for

The grant supports projects developing and validating enabling technologies or platforms that can create meaningful changes in HLBS research capabilities. That includes tools, models, and systems with potential to improve prediction, detection, diagnosis, treatment, prevention, or translational workflows.

The NOFO language is clear: the fit is strongest when your proposal is beyond “concept only” but still has unresolved performance and scale questions. It is best suited for projects where feasibility is partly established through preliminary data, yet still needs focused validation with explicit milestones.

You are expected to show why your technology is not merely incremental and why it has a plausible, broader impact path. This matters because Catalyze avoids routine technical upgrades unless they are shown to be truly enabling. A generic incremental upgrade of existing methods is usually a weak fit.

A useful way to decide fit is to check each point:

• Does your target solve an HLBS-relevant technical bottleneck?
• Can you define objective performance thresholds and not just narrative goals?
• Can reviewers see where milestones indicate success vs failure?
• Is the innovation likely to generate stronger downstream research, diagnostics, or translational outputs if validated?

If you cannot answer these with concrete outputs and numbers, you need to de-risk your concept before applying.

Who this opportunity fits best

This call is best for teams that can operate like an engineering project rather than a broad biological hypothesis project. Strong candidates include:

1. Teams with a working prototype or platform that has preliminary proof but still needs structured validation.
2. Multi-disciplinary groups that combine technology development with project management and measurable execution controls.
3. Applicants with leadership that can align scientific uncertainty, risk and schedule with predefined milestones.
4. Organizations already comfortable with NIH compliance and submission systems (ASSIST/Grants.gov/eRA Commons).

Because this is an NHLBI program tied to heart, lung, blood, and sleep mission areas, proposals should have clear relevance to those systems, disease contexts, or enabling needs.

In practical terms, teams from universities, hospitals, translational institutes, and SMEs can be eligible, but they must comply with a broad NIH systems framework and complete registrations correctly. The NOFO’s eligible organization list is unusually broad, which helps consortiums and multi-entity teams, but it still excludes non-U.S. independent organizations.

Eligibility details and who can apply

The opportunity is available to a wide set of U.S. entities, including higher education institutions (public and private), nonprofits, for-profits (including small businesses), local and federal governments, and several other eligible public-serving bodies. Foreign primary organizations are not eligible, but non-domestic components of U.S. organizations can participate.

For individuals, the NOFO centers on the PD/PI and applicant organization rather than imposing narrow career-stage or field-only restrictions in the way some fellowships do. If the team is PI-ready and the organization has the right registrations and capacity, the pathway is open.

Key eligibility and readiness requirements:

• No clinical trials: this is an R33 without clinical trials.
• Electronic registration is mandatory: SAM, eRA Commons, and Grants.gov setup must be complete before submission.
• New submissions and resubmissions allowed: there are accepted cycles for renewed, revised, and resubmitted applications according to cycle rules.
• Project-level fit required: applications outside technology development and transformation are at high nonresponsive risk.

The registration burden is not cosmetic; unresolved registrations are a common delay risk. The NOFO explicitly warns that registration issues are not valid reasons for late submission.

Application timeline and deadlines

This is a recurring-cycle opportunity. As of the last published schedule, the notable cycle points around current planning include:

• 2026-02-11 (earlier window in spring)
• 2026-06-18 (important for this cycle)
• 2026-10-21
• 2027-03-?? and 2027 onward repeated windows depending on cycle shape in later years

The NOFO also lists expiration at the end of 2027 for this solicitation series. That means this is a genuine 2026-27 and later cycle opportunity, not a one-day-only announcement.

Use this as a practical planning rule:

• If you are ready to submit by the earliest cycle, target the first due date available in your planning window.
• If you are not ready, avoid trying to “patch up” at the end. Build to the next window with revised milestones and clearer performance measures.

All applications are submitted at 5:00 PM local time of applicant organization. Missing that deadline invalidates submission under the standard NIH late-submission framework.

Funding size and budget constraints (practical interpretation)

The NOFO publishes two financially useful anchors:

• NHLBI intends up to $2,156,000 in total costs each year.
• Individual applications are capped at $350,000 direct costs per year.
• Targeted new awards of up to 4 per fiscal year are expected in each target year.

Because funding is year-based and project-based, teams should write budgets that directly support milestones and project management rather than large generic contingencies. A clean way to align your budget narrative is:

1. Allocate explicit budget lines for the experimental validation pathway that drives each milestone.
2. Include project management support, as this mechanism emphasizes timeline tracking and progress governance.
3. Avoid inflating budget with activities that are not directly linked to measurable outputs.

Most competitive applications avoid overbuilding the budget plan and get stronger marks for coherence between budget, timeline, and deliverables.

Application materials and required submission mechanics

NIH submission has a standard route, but this NOFO adds specific expectations. You can apply via ASSIST, Grants.gov Workspace, or an institutional S2S solution. Paper submission is not accepted.

Core submission package expectations include:

• Standard NIH SF424(R&R) forms (cover, performance site, project info, budget, and research plan).
• Dedicated attention to page limits in the NIH guide.
• A one-page Statement of Potential Impact attachment.

The Statement of Potential Impact is important enough to treat as a mini-proposal inside the proposal. It should explain:

1. The transformative capability your technology adds,
2. Why this goes beyond existing approaches,
3. What successful transfer from capability to broader use looks like,
4. Partnerships or support pathways already in place for next-stage adoption.

The call also requires a research strategy built around:

• performance measures,
• milestones,
• feasibility plan,
• project management and timeline.

This is why teams that cannot clearly define milestones in advance are often penalized regardless of scientific quality. The NOFO language explicitly indicates unquantified milestones and weak performance metrics are major weaknesses.

How reviewers will evaluate your application

The review framework is aligned with normal NIH merit review structures, but this NOFO applies specific emphasis:

• Technical responsiveness: Is it truly an enabling platform/technology, not just a routine study?
• Performance measures: Are they quantifiable and pre-specified?
• Milestones: Are they specific, measurable, realistic and tied to expected progress?
• Project management: Is there a real system for tracking and responding to timeline drift?

The reviewer lens is strict on rigor and feasibility. Projects with clear logic but weak evidence of feasibility control often fall behind even if innovative. Good teams proactively show:

• baseline evidence that early feasibility is established,
• risk points and fallback decisions,
• an explicit plan to manage delays and rerouting,
• clear rationale for why milestones are achievable under the proposed budget.

Common mistakes that usually sink applications

1. Turning in a broad biology proposal with weak technology framing.

The NOFO is not just “a grant for science.” It is explicitly targeted at platform validation and transformative capability.

2. No quantifiable performance metrics.

If reviewers cannot measure success against explicit numbers, the application is vulnerable.

3. Vague milestones.

The NOFO distinguishes milestones from specific aims. General milestones like “complete validation” without criteria are frequently inadequate.

4. Underestimating project management needs.

The program expects schedule governance, and the coordinating center may monitor progress. A strong team structure should include a named management process and ownership.

5. Registration or submission friction.

Missing any SAM/eRA Commons/Grants.gov prerequisite can quietly derail on the submission side.

6. Treating budget as a generic estimate.

Budget needs to reflect milestone logic, not just a generic spending estimate. This includes support for meetings and oversight required by the NOFO if they are justified.

Practical preparation plan (from announcement-ready to submission-ready)

A realistic pathway for a first-time team is:

Week 1–2: Scope check and portfolio audit

• Confirm HLBS relevance and non-clinical-trial status.
• Map your proposal against the NOFO emphasis points.
• Choose a small set of 3–5 performance measures with numeric targets.

Week 3–4: Team and registration readiness

• Confirm PI, key personnel, and organization roles.
• Validate SAM/eRA Commons/Grants.gov setup and status.
• Decide whether to use ASSIST or institution S2S workflow.

Week 5–6: Technical narrative build

• Build a single-page performance-measure table.
• Convert specific aims into a milestone chart with dates.
• Draft Statement of Potential Impact in plain, measurable language.

Final stretch (submission window minus 14 days):

• Check page limits and all attachments.
• Verify no clinical trial language or design claim inappropriately appears.
• Verify on-time submission status in eRA Commons.

This process is not glamorous but it directly maps to likely failure points.

FAQ for applicants

Is this a discovery grant?

Not exactly. It is best for projects that already clear early feasibility and need development plus rigorous validation.

Can startups apply?

Eligible small businesses can apply if all administrative requirements are satisfied.

Do clinical trials count as disqualifying?

Yes. The NOFO explicitly says clinical trials are not allowed.

Can a non-U.S. company collaborate?

A non-U.S. primary entity cannot apply, but non-domestic components associated with U.S. organizations can be part of the project.

Can I submit a resubmission?

Yes, resubmissions are allowed, along with new applications.

What is the main differentiator from other NIH technology calls?

Milestones, performance measures, and management discipline are central. The review logic is operational, not just conceptual.

Official links and follow-up resources

• Official NOFO page: https://grants.nih.gov/grants/guide/rfa-files/RFA-HL-26-016.html
• NIH How to Apply Application Guide: https://grants.nih.gov/funding
• NIH application systems (ASSIST, Grants.gov, eRA Commons): official NIH/NIH-supported resources listed in the NOFO and NIH pages

The opportunity is still active for 2026–2027 planning and beyond into later cycles, but windows are finite and submission systems are strict. If you are reading this near the end of a cycle, do not assume a late correction will be treated favorably; NIH submission policy is explicit about on-time requirements.

Bottom line

This is one of the better-defined translational-enabling opportunities for technical groups that can convert a strong prototype into measurable, validated outputs. It rewards teams that can prove they understand both science and execution. The winning applications are generally the ones that can be summarized through three elements:

1. A clear HLBS-relevant transformative capability,
2. Concrete performance metrics and milestones,
3. A budget and management plan that makes the project look executable rather than aspirational.

If your team has preliminary data and can define success in terms of measurable performance, this is a real pathway for catalytic support in the 2026/27 cycle.