RFA-HL-27-004: Limited Competition: Small Grant Program for NHLBI K01/K08/K23/K25 Recipients (R03 Clinical Trial Optional)

RFA-HL-27-004: Limited Competition: Small Grant Program for NHLBI K01/K08/K23/K25 Recipients (R03 Clinical Trial Optional)

Key details

What this opportunity is and who it is designed for

This is a transition-focused NIH/NHLBI opportunity for investigators in the middle of the mentored-to-independent path. The mechanism is a limited competition, not a broad open R03 call, which means it is intentionally narrow: the applicant pool is restricted to people who currently hold, or have recently completed, specific NHLBI career-development awards.

The opportunity is explicitly intended to support “the transition to research independence” of current and recently completed NHLBI K01, K08, K23, and K25 recipients. That target audience is unusual compared with standard R03 solicitations because it ties the application directly to a preceding K award trajectory. The design is strategic: use a short, flexible award to generate missing preliminary data, strengthen feasibility, and prepare for later, larger competitive bids (often R01-equivalent mechanisms).

If your project idea is already fully mature and your group is beyond career-development dependence, this NOFO may not be the best fit. It is strongest for people whose proposed work is close enough to be realistic in two years but still needs a bridge award to make a meaningful independence leap.

The NOFO also clarifies what this grant is not. It is not a full-size translational trial mechanism, and it is not the right route for candidates who have already received a substantial NIH independent research award. If your applicant already has that status, they fall outside the program by design because the purpose is transitional rather than post-independent expansion.

The activity includes projects that can be done in a limited budget and short period. The NOFO examples point to pilot/feasibility studies, proof-of-concept work, secondary analyses, and small method-development activities. Those are not secondary priorities; they are the central program logic.

Eligibility design and critical constraints

Eligibility is the first major gating layer. Unlike many investigator programs where people can guess and then narrow later, this NOFO enforces a strict applicant shape:

• You must be an NHLBI K01, K08, K23, or K25 awardee.
• You must be either:
  • a current NHLBI awardee applying in year 3 or later of your K Project Period, or
  • a recently completed awardee whose earliest R03 start date is within two years of K award completion.
• The award mechanism is R03, and you must remain within scope of NIH R03 standards.
• You can submit New (A0) or Resubmission (A1) applications.
• You must not have already secured a substantial NIH independent research award.

These constraints matter because “currently applying as a K recipient” is interpreted narrowly. An application that does not meet this profile will be rejected for eligibility reasons, and rejection at this stage happens before review quality is considered.

For organizations, the NOFO allows multiple types (higher education, nonprofit, small business, government entities, tribal and local entities) but retains a clear non-domestic restriction: foreign organizations and foreign components are not eligible. This is a U.S.-based federal opportunity.

Another subtle but important rule is the 40% protected effort requirement across the R03 period, achieved across the candidate’s portfolio, not exclusively on R03 hours. The requirement is interpreted as 4.8 person months minimum. The NOFO further expects the institutional commitment letter to explicitly document this protected effort and the supporting institution’s role in transition-to-independence.

The page also states there is no cost sharing requirement, which removes one common budget barrier. You should still still document a realistic budget and timeline because review checks are strict and award-level resources are bounded.

Why timing matters: open date, recurring due dates, and practical planning windows

This NOFO is structured as a recurring mechanism with multiple due dates per year. The key dates listed include:

• Open date: June 09, 2026
• Current first cycle due date in this posting: July 09, 2026
• Recurring due dates: October 06, 2026, February 10, 2027, June 09, 2027, and additional later cycles through 2028

As the user date (2026-05-31) is before the first full cycle deadline in this posting, the practical takeaway is that applicants can target the nearest cycle first, with future cycles available if the research package is not finalized.

Review and award cadence for a typical cycle follows the NIH route: application due, panel review, advisory council review, and earliest start date windows. In the posted table, the RFA links due dates to review and start points (for example, a July cycle aligns with review in November, council in November? the NOFO shows explicit columns and these should be followed from the official table). That sequencing matters for planning your internal compliance timeline:

• Submit early enough to fix portal errors and warnings before the hard deadline.
• Keep required registrations complete well in advance (eRA Commons, SAM, Grants.gov if using institutional workflows).
• Prepare required letters and attachments before the final submission window.

NIH explicitly discourages last-minute submission behavior because system-level errors can make late correction impossible. The NOFO is clear: corrected/changed applications must still be submitted by the same due date.

For this reason, treating one cycle as “open” is not the only planning cue. The recurring nature means you can target the next window, but the same compliance and content standards recur unchanged unless future notices modify them.

Funding amount, budget framing, and why project scope must match spend

The direct budget cap is straightforward: $85,000 per year in direct costs, and a maximum two-year project period.

The opportunity also includes top-line program commitment language:

• $3.9M in FY2027,
• $7.8M in FY2028,
• $7.8M in FY2029,
• $3.9M in FY2030,

with a stated intent to fund up to 29 awards in FY2027-29.

For planning, this means your application should behave like a genuine pilot or bridge package:

• Avoid trying to smuggle in multi-year infrastructure plans.
• Show a narrow scientific core that can produce interpretable evidence in 24 months.
• If preclinical, pilot-based, or methods-development centered, keep milestones measurable and tightly bounded.
• If human-subjects work is proposed, align scope with timeline and feasibility requirements.

The budget should be proportional to what you propose. NIH reviewers can score budget as part of criterion context (“Budget and Period of Support”), and the NOFO also says a poorly justified budget can reduce competitiveness even if science is strong.

Submission architecture and required components

This is not a paper-application NOFO. Submissions must be electronic, through NIH channels.

Core allowed submission paths:

• NIH ASSIST
• Grants.gov Workspace
• Institutional S2S solution that passes into Grants.gov and eRA Commons

All applicants need compliant registrations before submission, including eRA Commons credentials for PD/PIs and required registrational infrastructure.

Beyond standard application instructions, the NOFO imposes explicit required materials:

• Summary of K Award Research Progress attachment (up to 3 pages):
  • Current K award recipients: summarize how R03 work follows, extends, or strategically diverges from current K project.
  • Recently completed K award recipients: include prior K trajectory and current research status.
  • Missing this attachment or exceeding page limit is noncompliant.
• Letters of support (required package as a single attachment):
  • Mentor letter for current K recipients
  • Institutional commitment letter (required in any case)
• Institutional letter must include protected effort and explicit support language.

At minimum, your application should also include:

• NIH-compliant DMS plan using the NIH DMS format page
• Human-subjects and clinical trials disclosures as applicable
• Complete page limits from the NIH application guide
• Correct project/organizational information forms, including project locations and other project info

The NOFO also enforces a tightly limited appendix policy; this is one of the easy-to-miss traps. If your team plans to attach publication bundles or extra narrative material outside allowed sections, that can raise compliance issues.

Review criteria you should write to, not just list

NIH review is not only “is this a good idea,” it is “is this a feasible, high-impact follow-on for your trajectory and appropriate for this NOFO.” The reviewed criteria are standard NIH factors plus NOFO-specific lenses:

• Significance and innovation
• Approach and rigor
• Investigator and environment
• R03 readiness and 2-year completion viability
• Evidence that the R03 moves the applicant toward independence
• Clear timeline toward follow-on R01-equivalent submission

A strong NOFO-specific review strategy is to explicitly answer three questions in your narrative:

1. Why this proposal cannot be done as part of the current K award but is enabled by this R03 timing.
2. What unique preliminary evidence will this R03 generate to make the next independent stage credible.
3. How the applicant and institution will preserve protected effort and sustain progression after the R03.

For K recipients, this makes the narrative less about proving “why your science matters” in general and more about proving “why now and why this transition award specifically.” The reviewer set includes NHLBI program context, so mission alignment and independence-planning language should be explicit, not implicit.

Who should apply now vs. defer, and fit examples

This NOFO is a fit for:

• K awardees in year 3+ whose current projects have generated enough momentum for a focused next-step study.
• Recipients nearing the end of a K period and seeking a bridge that maintains continuity of effort.
• Candidates proposing evidence-building studies, including methods development and secondary analyses, that can realistically complete in two years.
• Teams with institutional willingness to provide explicit effort protections.

This NOFO is a weaker fit for:

• Applicants applying very early in a K award (before the allowed eligibility window).
• Teams with broad, long-form clinical trials that do not match R03 scale.
• Investigators already holding a substantial NIH independent research award.
• Applicants outside U.S. or with unresolved registrations.

In terms of project type, the strongest examples are narrow, high-yield follow-on projects directly tied to your K findings. Less aligned examples are sprawling, underpowered programs that need multiple subprojects, large sample expansions, or broad clinical infrastructures.

Step-by-step preparation strategy for teams

A reliable execution plan helps avoid common NIH administrative bottlenecks:

1) Eligibility confirmation sprint (T-minus 12 to 14 weeks)

• Confirm exact current K award status and K number(s).
• Validate start year (year 3+ for current awardees) or the two-year post-completion eligibility condition.
• Confirm no substantial NIH independent award.
• Lock ORCID and eRA links for all PIs before content drafting.

2) Registration and infrastructure sprint (T-minus 10 to 12 weeks)

• Confirm SAM active status, eRA Commons affiliation, and institutional official/signer setup.
• Confirm whether your institution uses ASSIST or institutional S2S and where review artifacts appear.
• Pre-flight a test submission path.

3) Proposal architecture sprint (T-minus 8 to 10 weeks)

• Draft Specific Aims to match independent trajectory logic.
• Build a concise milestones chart covering month-by-month outputs through 24 months.
• Draft the Summary of K Award Research Progress early and enforce 3-page limit.
• Draft mentor letter and institutional commitment letter in parallel.

4) Compliance and submission sprint (T-minus 2 to 4 weeks)

• Validate page limits and section placement.
• Check required tables, fields, and DMS plan requirements.
• Submit no later than several business days before due date to allow warning resolution and resubmission.
• Track status in eRA Commons before deadline.

5) Final hardening sprint (last 48 hours)

• Do a full “link check” of registration status and all required roles.
• Ensure all names, emails, and contacts are consistent across forms and letters.
• Ensure no disallowed materials in appendix.

The NOFO explicitly encourages early submission not as a suggestion but as a practical risk-control measure.

Common mistakes that reduce competitiveness

1. Using non-K trajectories or incomplete eligibility documentation.
2. Missing the 3-page progress summary requirement or violating page limits.
3. Failing to include mentor/institution letters in a single required attachment.
4. Not stating protected effort clearly in institutional letter.
5. Submitting a clinically large, non-specified plan that does not fit R03 scale.
6. Assuming that a recent completion automatically qualifies without checking the two-year window.
7. Submitting late corrected files after the due time.
8. Treating appendix as a dumping ground for materials outside NIH limits.

Nearly every rejection at this stage is preventable with a short compliance checklist. Unlike some general solicitations, this NOFO has many explicit gates and each of them is binary.

Frequently asked questions for quick decisions

Is this only for U.S.-based institutions?

Yes. Foreign organizations are explicitly ineligible; foreign components of U.S. organizations are also excluded.

Are new investigators who never held a K award eligible?

No. This is specifically for current/recent NHLBI K01, K08, K23, K25 awardees.

Is clinical trial research allowed?

Clinical trials are optional. The NOFO allows clinical-trial and non-trial proposals and includes extra requirements for human-subjects and trial-ready applications.

Is this one award only per lab?

An organization may submit more than one application if scientifically distinct, but duplicates/overlapping submissions can be disallowed.

Is there cost-sharing?

No cost-sharing requirement is listed for this NOFO.

What happens after review?

Applications undergo NIH peer review (study section), and top applications go to NIH Council review. Funding decisions incorporate merit, available funds, and alignment with NHLBI priorities.

Official links and where to verify current status

Use official channels directly (not only third-party listings):

• Official NOFO (primary source): https://files.simpler.grants.gov/opportunities/61b3fa3d-491d-4a13-b580-2000a9d17564/attachments/0d63af42-7ec2-42ab-bddb-1d52991b4055/RFA-HL-27-004-Revised-Full-Announcement.html
• NIH Guide for Grants and Contracts (policy notices and updates): https://grants.nih.gov/grants/guide/
• NIH How to Apply - Application Guide: https://grants.nih.gov/grants/how-to-apply-application-guide
• NIH Grants Policy Statement: https://grants.nih.gov/grants/policy/nihgps/
• eRA Commons: https://public.era.nih.gov/
• Grants.gov: https://www.grants.gov/
• NHSLI technical support (submission systems): eRA Service Desk via NHLBI RFA page contact section

For this program in particular, contact references in the NOFO are:

• NHLBI scientific contact: [email protected]
• Peer review contact: [email protected]
• NHLBI grants management: [email protected]
• Subject line for all three: RFA-HL-27-004

Practical fit assessment checklist

Before spending internal hours on this NOFO, confirm all boxes below in one meeting:

• Is the applicant a current or recently completed NHLBI K01/K08/K23/K25 with correct timeline?
• Can you make a 24-month project with defined outputs?
• Can the institution sign an effective commitment letter with 40% protected effort language?
• Can all registrational and system accounts be validated before submission?
• Are all required attachments complete and within limits?

If the answer to any one is uncertain, set a hard stop and either switch to a different cycle or use this cycle as a preparation run. This NOFO is intentionally narrow and administratively strict. The strongest teams treat it as a transition engineering project: disciplined scope, clean compliance, and explicit post-R03 plan.