NIH Opportunities for Collaborative Research at the NIH Clinical Center (U01 Clinical Trial Optional)

NIH Opportunities for Collaborative Research at the NIH Clinical Center (U01 Clinical Trial Optional)

If you need a grant mechanism that is explicitly designed around a real-world translational workflow—moving from lab insight to patient study through NIH infrastructure—PAR-26-116 remains one of the most important NIH opportunities to understand deeply in 2026–2027. This is a U01 Research Project–Cooperative Agreement that pairs NIH Clinical Center access with a structured extramural–intramural partnership. The NOFO frames collaboration as the core, not an add-on: applications are expected to be built around co-execution with at least one NIH Clinical Center investigator and to use Clinical Center resources in more than a token way.

The NOFO is a reissue of PAR-21-343, with a posted key dates block showing annual cycles. The key due windows are February 5, 2026 and February 5, 2027, with corresponding March review windows and an expiration on March 6, 2027. Because your snapshot date is 2026-05-31, this means the next viable annual cycle (if still current in your local monitoring context) is the 2027 window.

Key details at a glance

What this opportunity is actually for

The NOFO repeatedly states that the purpose is to support collaborative, patient-centric translational research aligned with NIH priorities. The structure is very specific: external investigators bring a question, a hypothesis, and an experimental approach; NIH intramural investigators contribute scientific integration, resource access, and Clinical Center execution context. The program is not just about being near NIH; it is about using the patient access and infrastructure at the NIH Clinical Center to move a project to human-centered proof and mechanistic clarity.

This opportunity is especially relevant if your project needs one or more of the following:

• access to large patient cohorts and structured clinical workflows,
• Clinical Center protocols and procedures not available at your home institution,
• direct in-human feasibility work that bridges a promising preclinical signal with first-in-human clinical logic,
• formal collaboration with intramural experts in a niche area where NIH has rare disease depth.

The NOFO and associated program page are explicit that projects taking only minimal advantage of Clinical Center resources are likely to fail. A project limited to banked samples or data transfer, without meaningful Clinical Center clinical execution, is repeatedly described as nonresponsive.

Because this is a cooperative agreement, NIH is not a passive funder. It expects a working partnership role, while the recipient retains primary responsibility. In practical terms, you need to plan for a structured back-and-forth, clear work segmentation, and robust joint management from day one.

Who this opportunity is for—and who it is not for

This mechanism is strongest for teams in the translational valley: investigators with a real hypothesis and enough preclinical or observational depth to justify direct clinical translation. It is not designed as a low-commitment collaboration or a data-mining convenience grant.

It can work well for:

• translational science teams that can specify what each side (extramural/intramural) contributes at protocol, execution, and interpretation stages,
• programs that need NIH clinical trial support but remain adaptable to non-trial designs,
• disease areas with enough clinical complexity to justify NIH Clinical Center engagement,
• institutions that can sustain the administrative requirements of NIH peer-review pipelines.

It is likely a poor fit for:

• applications that cannot define Clinical Center involvement beyond sample processing or passive data use,
• teams without a committed intramural collaborator or with only vague letters,
• applicants unable to support required registrations (SAM, eRA Commons, Grants.gov),
• teams submitting late-compliant-only applications with incomplete attachments, because NIH treats incompleteness as a no-review event.

The funding is open to a broad set of applicant types, but the practical burden varies. Higher education institutions and large nonprofits often have stronger administrative support for multi-system submissions. For-profit organizations are explicitly eligible, but this is still not an SBIR program.

Eligibility, institutional conditions, and hard constraints

The NOFO lists an unusually broad eligible organization set: public and private higher education institutions, nonprofits (with and without 501(c)(3) status), for-profit organizations including small business, local and federal governments, and foreign entities. The breadth is real, but there is a strict boundary: no new awards with foreign subawards/subcontracts are allowed after the stated policy cutoff, and foreign subawards/subcontracts in submitted applications can make your submission noncompliant.

Critical participation constraints are non-negotiable:

1. At least one NIH intramural scientist must be named as a co-Program Director/PI role (in terminology consistent with current NIH policy).
2. At least some clinical research must occur at the NIH Clinical Center.
3. The collaboration must show substantial, structured Clinical Center use, not just peripheral involvement.
4. For projects with an NIH-defined clinical trial component, specific planning and monitoring instructions in the PHS Human Subjects form apply.
5. All PD/PI and organizational registrations must be completed before submission.

The NOFO also clarifies that applications may be clinical trial or non-clinical trial. If the work includes human intervention components, plan to satisfy human subjects and IRB requirements appropriately, including one or more IRB records where required.

For teams involving multiple PDs/PIs, NIH multiple-PI policy applies. The FAQ page from the program reiterates that multi-PI is allowed, and that the application should come from one applicant organization. That aligns with standard NIH policy and has real operational consequences for budget routing and leadership accountability.

Funding mechanics and budget strategy you can actually use

The budget cap is clear and important: $500,000 direct costs per year total, and this total must include extramural costs, intramural investigator costs, and Clinical Center costs associated with the proposed project. A frequent misunderstanding is reading this as a maximum only for the applicant institution. It is not; it is a total annual cap across all components.

Two additional practical budgeting points matter a lot:

• The final award to the applicant organization excludes Clinical Center-associated funds requested for the Center’s participation.
• For budget preparation, requests for Clinical Center and intramural investigator costs are still needed in the application to establish feasibility and alignment, even though payment structures differ.

The NOFO explicitly states the maximum period can be up to 4 years, with an optional 5-year plan if year 1 is a planning year at reduced budget. This option is useful for projects that require regulatory setup, protocol build, credentialing, or method development before full patient accrual.

Clinical drug costs are treated as a special handling area. Program instruction notes that drug cost coverage is determined by Clinical Center coordination and that expensive drug regimens may need explicit budget coverage in the grant, the participating Institute, or sponsorship. Because this can materially affect feasibility, teams should model this early and not assume automatic absorption.

From an evaluation standpoint, budget reasonableness is part of review. Your period-of-support narrative should connect timeline to feasible milestones and to the Clinical Center work actually planned. Thin budgets with ambitious enrollment plans are often reviewed as unrealistic, especially for studies requiring complex patient coordination.

Step-by-step application workflow (practical implementation)

A strong submission is more process than prose. Use this sequence:

1) Confirm scientific scope against clinical center suitability

Use the NOFO language and program FAQ as a filter before drafting. If your question can be fully executed without NIH Clinical Center physical participation, it likely does not fit. The NOFO is explicit that Clinical Center interaction must be meaningful. Keep this in your internal scorecard: what unique Clinical Center assets are essential, and why cannot the same question be run solely at your institution?

2) Identify and onboard the intramural counterpart early

The extramural PI must submit with a robust NIH intramural collaborator. This is not a letter-of-intent phase; it is a collaborative design phase. The pre-application process on the OCReCo program site is described as required and includes a required collaboration plan structure. If you cannot get a committed intramural investigator early, stop and reconsider before investing in drafts.

3) Request Letters of Support (LOS)

The NOFO states applications without both required letters—the Clinical Center LOS and one NIH Institute/Center LOS—are incomplete and not reviewed. This is one of the highest-risk failure points. The NOFO notes requests should be submitted by October 31 through the program channel, with point contacts listed. Track this date as hard-blocking.

4) Build the application architecture around required attachments

Beyond standard SF424(R&R) forms, mandatory collaborative content includes a Collaboration Plan with explicit organization structure and management details. The pre-application guidance emphasizes:

• clear communication rhythm between teams,
• detailed resource-use plan, including what is expected from the Clinical Center,
• effort splits and responsibilities,
• patient and site-specific plans.

When clinical protocols are not final at submission, include explicit justification and milestone logic. The NOFO explicitly warns that incomplete justification can harm scores. For human studies, include required protocol and human subjects records as appropriate.

5) Use the allowed submission channel and avoid compliance traps

You can submit via NIH ASSIST, Grants.gov Workspace, or an institutional S2S workflow. Regardless of channel, NIH systems will validate structure and compliance. Applications that are noncompliant can be delayed or not reviewed.

Make sure all PD(s)/PI eRA Commons IDs are in credentials, SAM and UEI are active, and registrations are complete before the due date. The NOFO states late registrations are not valid reasons for delayed submission.

6) Prepare for review and post-submission integrity

Review is through NIH peer review with factors tied to significance, innovation, feasibility, and investigator/resources quality. Commonly, projects fail when the collaboration mechanism is vague: e.g., “will work with intramural team” without operationally defined governance and milestones. The NOFO emphasizes communication cadence, recruitment feasibility, and milestone credibility.

How applications are reviewed and what reviewers prioritize

Section V criteria are clear about the core score drivers:

• Significance: does the project address a meaningful gap?
• Innovation: does the approach open genuine new paths?
• Approach/Feasibility: is the project design practical with defensible methods and achievable recruitment?
• Investigator(s) and Environment: is leadership strong and is the collaborative environment realistic?

For human-subject studies, reviewers also look closely at risk/benefit balance, protections, and monitoring, as well as the inclusion of populations and recruitment plans. For trials, milestone feasibility and protocol quality are heavily weighted.

Additional non-scoreable but impactful criteria include budget and period reasonableness, resource authenticity, and for biomedical projects, whether the resource and data plans are realistic. In practice, many applications look scientifically strong but lose credibility because milestones are disconnected from Clinical Center capacity or operational sequencing.

Because the mechanism is cooperative, NIH staff are involved as a substantive programmatic partner after award. This means your proposal is not evaluated only on science; implementation clarity matters.

Common mistakes that reduce review quality

1. Treating the Program as a simple co-author opportunity A generic letter from an intramural investigator is usually not enough. Reviewers and program staff evaluate whether the collaboration is operational, not ceremonial.

2. Minimal Clinical Center use narrative The NOFO calls out that projects relying mainly on existing samples or banked data can be nonresponsive. If Clinical Center patient-facing work is thin, re-scope the project or exit.

3. Missing LOS workflow or incomplete support letters This is a hard fail. Missing LOS leads to automatic non-review in explicit instructions.

4. Weak cost segmentation Budget narratives that do not separate extramural recipient costs, intramural costs, and Clinical Center costs make review and administration harder. NIH explicitly asks for this separation and clear justifications.

5. Assuming foreign subawards are automatically acceptable The NOFO allows foreign collaborators and certain foreign components, but explicitly limits monetary foreign subawards/subcontracts. Flag this early in your budget and subaward design.

6. Underestimating registration and submission time SAM, eRA Commons, and Grants.gov set up can take weeks. Incomplete registrational status is a frequent reason for missed deadlines.

2026/2027 preparation notes and FAQ

Q1. Is a clinical trial required?

No. Clinical trial status is optional. You can propose non-trial translational research, but if trial status is Yes, follow the NIH-specific clinical trial requirements in your PHS form and submission package.

Q2. Is IND required at submission?

For this program, FAQ guidance indicates a formal IND is not necessarily required at submission; the requirement depends on planned intervention status and regulatory path. In practice, if the project needs an IND/IDE, include a concrete plan and status update.

Q3. Is an FDA approval required before submission?

No general precondition for submission; your protocol and compliance documents should be staged with timeline realism. IRB approval is typically needed before award, and the NOFO indicates protocol maturity expectations should be described in your milestones.

Q4. Can for-profit entities apply?

Yes. The NOFO states for-profit groups are eligible, but this is not an SBIR solicitation. It remains a U01-style collaborative research instrument with NIH oversight and NIH-specific policy framework.

Q5. Can I submit multiple applications from the same team?

More than one is possible only if they are scientifically distinct. Overlapping applications can be blocked or deprioritized depending on review overlap rules.

Q6. What does “cooperative agreement” change for me?

The applicant retains prime responsibility but NIH staff have substantial involvement post-award. Operationally, you should budget in collaboration capacity and internal management capacity for this level of coordination.

A strong strategy for teams targeting March 2027 in this cycle

Use a reverse timeline.

• T-16 to T-12 weeks: finalize clinical hypothesis, intramural counterpart, and feasibility mapping; request pre-application/LOS instructions and verify scope with IC contacts.
• T-12 to T-8 weeks: draft collaboration and milestone plan, define resource split, secure internal registration readiness.
• T-8 to T-6 weeks: finalize draft protocol assumptions, human subjects/clinical-trial sections (if applicable), and budget split.
• T-6 to T-3 weeks: collect LOS packages from both NIH Clinical Center and IC; if any required piece is late, re-scope.
• T-3 weeks to due date: run internal compliance check for all NIH-specific form requirements, eRA credentials, and attachment naming.
• T-2 days: submit early and validate final status in eRA Commons.

This timing is not overkill for NIH applications; it is often too late if done afterward. The NOFO includes explicit language that non-compliance can prevent review.

Official links and primary sources

• Official full announcement: https://files.simpler.grants.gov/opportunities/b6a413a2-36d3-43b6-a38a-c3dfaebc20c9/attachments/322acd11-1445-44ab-8634-5f000d673c70/PAR-26-116-Full-Announcement.html
• Program site and workflow context: https://ocreco.od.nih.gov/new_u01/new_u01.html
• Pre-application and LOS instructions: https://ocreco.od.nih.gov/new_u01/pre-app_and_los.html
• LOS submission page: https://ocreco.od.nih.gov/new_u01/letters_of_support.html
• Program FAQ: https://ocreco.od.nih.gov/new_u01/faqs.html
• NIH NIMH listing (for status context): https://www.nimh.nih.gov/funding/opportunities-announcements/listings/pas

This opportunity is highly practical for teams that need a true clinical partnership model, and it rewards teams who treat collaboration as an executable design requirement, not a compliance appendix.