RFA-DE-27-002: Accelerating Product Excellence in Innovation and for Clinical Adoption (APEx) (U24 Clinical Trial Not Allowed)

RFA-DE-27-002: Accelerating Product Excellence in Innovation and for Clinical Adoption (APEx) (U24 Clinical Trial Not Allowed)

If your team works in tissue engineering or regenerative medicine and you are asking how to move from promising pre-clinical proof to a stronger translational pathway, this opportunity is directly in that gap. APEx is a U24 mechanism designed around a Resource Center model plus a cohort of Interdisciplinary Translational Projects. The official opportunity is structured for organizations and teams that can create a system around multiple projects, not a single fragmented portfolio.

This page is a practical planning guide for the FY2026 and FY2027 windows. It is not a legal opinion. All key facts below come from the official NIH solicitation text and associated submission instructions.

Quick key details

What this opportunity is really offering

APEx is often misunderstood as a standard RFA for a single lab project. The solicitation makes clear it is not. The call is explicitly structured as a translational infrastructure and acceleration mechanism. A successful application is expected to show that the center can support multiple projects and that these projects are ready for coordinated progression.

The solicitation’s expected architecture has these core components:

• a Resource Center lead organization with governance and coordination capacity,
• an initial set of ITPs, initially around 4 to 6,
• a roadmap to expand the portfolio toward a higher number of projects as milestones are met,
• robust integration with preclinical validation, commercialization planning, and FDA-facing readiness.

The critical interpretation is this: APEx money is used to make a process reliable and scalable, not simply to fund a single scientific idea. If your team cannot justify shared infrastructure and coordinated portfolio management, this might be a poor match.

The mechanism is a U24 cooperative agreement, which changes the relationship with NIH from pure pass/fail funding toward active scientific and programmatic interaction. That generally benefits teams with transparent, executable plans and strong organizational capacity. It can hurt teams that treat the mechanism as a simple grant where reviewer communication and milestone revision are afterthoughts.

Why this is different from common translational grants

Many applicants come in expecting a typical research grant logic: propose an idea, list milestones, get funded, execute. APEx changes that chain by requiring a center-like operating model.

Most common mistakes in comparable NIH calls include:

• treating the Resource Center budget as a collection of independent project allowances,
• underestimating required governance and reporting,
• proposing too early-stage science without near-term translational structure,
• assuming the mechanism can support clinical trials.

The explicit exclusion of clinical trials is key. You can include preclinical and preclinical-preparation work, but not interventional trial activity. That distinction should be visible in your work packages, timeline, and language. Any application language implying trial-ready claims without non-trial transition logic should be revised before submission.

Eligibility and policy constraints

Who can apply

The NOFO allows a broad set of U.S.-based entities, including research universities, nonprofits, businesses, and public-sector entities. This breadth is useful because APEx can require multiple disciplines and operational skill sets. However, that breadth does not remove the U.S.-based eligibility requirement.

Foreign institutions are not eligible as direct awardees. Foreign components in U.S. applications are also constrained and should be treated carefully. If your collaborative model includes international partners, ensure the core applicant structure and compliance language remains compliant with U.S. eligibility.

Leadership and effort expectations

The solicitation highlights leadership at the applicant level, with expected PI-level commitment. If PI effort is weak or only nominal, the application becomes vulnerable to impact scoring penalties. APEx is not a side effort for teams that already cannot support structured oversight. Leadership commitment also matters across project management, quality systems, and coordination.

For large portfolio activities, you should include explicit role-level accountability:

• PI or Project Director, with sustained commitment,
• science leads for ITP tracks,
• operations and regulatory strategy leads,
• partnership and commercialization interface leads.

What is clearly excluded

• clinical trials (not allowed),
• foreign applicants as lead organizations,
• minimal or duplicate portfolio logic,
• late submissions with unresolved portal or registration compliance.

Given this is a U24 call, the exclusion list should be treated as part of scope control, not as minor correction notes. Programs rejected for protocol mismatch are difficult to recover from even if the underlying science is strong.

Funding mechanics and 2026/2027 calendar

The official solicitation includes projected annual and annualized parameters for the mechanism and a clear direct-cost cap per year. The practical impact is straightforward:

• budget discipline is critical,
• no need to promise unrealistic inflationary or non-compliant spending,
• milestone planning must match available duration and funding.

A standard planning interpretation is to build a 12-month phased budget per ITP with clear RC-level shared costs and project-level spending separated.

For 2026/2027 planning, applicants should treat the published key dates as hard. The key posted and open dates indicate the call is active with multiple due dates. The 2026 cycle includes July 10, 2026 as a major deadline. Additional cycle dates in 2027 include January 5 and April 5.

A robust internal calendar typically has three gates before each due date:

1. internal science and governance draft readiness,
2. budget and compliance check,
3. submission rehearsal and final package validation.

For NIH applications, missing any registration prerequisite can become a submission blocker. Teams should complete registration updates at least 3 to 4 weeks before the target deadline, not hours before finalization.

What to include and how to structure your proposal

At a practical level, the proposal should read like a functioning operating manual.

Section architecture

A winning APEx application usually places these themes in the front of the technical narrative:

• clear statement of translational problem statement,
• RC governance model,
• project portfolio rationale,
• shared methods for validation and reproducibility,
• preclinical milestones linked to objective data,
• commercialization and regulatory planning.

Application bundle planning

Because this is a U24 mechanism, your strategy should explicitly separate:

• hub costs and shared service costs,
• ITP-specific costs,
• translational service infrastructure,
• milestone-triggered expansion readiness.

Budget logic should not mix these categories. Reviewers and grants management staff check internal consistency.

Scientific and operational scope

The solicitation expects technical depth and system-level execution. Build your narrative around what each ITP contributes to the program and why these projects are stronger together than separately.

A common reviewer friction point is a fragmented section where each ITP is described independently with no shared logic. Instead, emphasize:

• common assay or model platforms,
• shared quality systems,
• common commercialization or accessibility pathway,
• shared de-risking and prioritization framework.

Practical language choices that improve clarity

Avoid generic future-tense ambition language. Use evidence-first prose:

• what evidence exists,
• what evidence is missing,
• what evidence the RC enables,
• what triggers each next milestone.

This is especially important for multidisciplinary teams. The reviewers are looking for a system, not a collection of isolated hopes.

Review lens and common scoring drivers

NIH review still follows standard criteria in this mechanism, but APEx adds portfolio-level scrutiny.

The practical review lens often reduces to this:

• Is the RC real and sustainable?
• Are the projects truly connected by shared scientific and translational needs?
• Are milestones measurable, sequenced, and tied to outputs?
• Is the non-trial preclinical strategy rigorous and realistic?
• Is leadership capacity sufficient for five years of coordinated execution?

When reviewers see a proposal with vague governance, weak risk management, and ambiguous go/no-go logic, they usually assign lower feasibility scores regardless of novelty. Novelty matters, but feasibility in this mechanism is disproportionately important.

How to improve review signal before submission

• include explicit portfolio rationale with selection criteria,
• use one-page governance map for decision rights,
• map each ITP to a measurable short-term deliverable,
• add a short section on preclinical risk controls,
• describe what happens if an ITP fails a major milestone.

These changes reduce ambiguity and increase reviewer confidence that your team can execute at scale.

Preparation checklist: from discovery to submission

4 to 6 weeks before deadline

Set a dry-run submission and confirm that every required registration account is active:

• SAM,
• UEI,
• eRA Commons,
• Grants.gov/ASSIST path,
• institutional signature and authority workflows.

3 to 4 weeks before deadline

Use a full draft of the key narrative sections and route it through internal peer review, focusing on two points: portfolio coherence and objective milestones. At this stage remove optional complexity.

2 weeks before deadline

Freeze budget tables and compliance fields. Validate all administrative pages, attachments, and file formats. Run a “late change freeze” process; late corrections in this stage often introduce formatting errors.

5 days before deadline

Run a final technical check against the NOFO rules. Keep all major decisions unchanged for the final 48 hours unless a compliance issue is discovered.

Day of submission

Submit with enough buffer for NIH validation feedback windows. Do not rely on final-hour fixes for either content or registration errors.

Common mistakes and how to avoid them

1. Confusing APEx with a simple lab grant.

The mechanism is systems and portfolio-based. Write and budget accordingly.

2. Overpromising clinical work.

Clinical trials are explicitly excluded. Keep trial claims out of the work package language.

3. Submitting weak ITP selection logic.

Selecting 4 to 6 projects is not enough; there must be a logic for why these specific projects form a coherent first cohort.

4. Underestimating administrative workload.

A cooperative agreement requires sustained documentation and communication. Build that into planning.

5. Treating budget as a list, not a strategy.

Budget lines must map to translational operations and measurable milestones.

6. Delayed registrations.

Portal, Commons, and SAM issues usually cannot be fixed at 11:59 p.m. on due date.

Frequently asked questions

Is APEx only for institutions, or can companies apply directly?

Eligible applicants include multiple U.S. organization types, including business entities, but proposals must match the RC and translational structure expected in the NOFO.

Can an ITP include human subjects work?

Human-subject science can be included where it remains non-trial and consistent with preclinical translational objectives. Clinical trials themselves are not allowed.

Can existing collaborations be moved into the portfolio?

Yes, if the collaboration architecture is coherent and if projects can be integrated into the Resource Center model with measurable milestones.

Is there a minimum age or PI degree requirement?

The NOFO does not reduce eligibility to simple one-line thresholds in the way fellowships sometimes do. It focuses more on organizational and leadership capacity and translational readiness.

Can I apply in both 2026 and 2027?

In principle, recurring windows support multiple cycles. The strategic question is whether your team materially improves the package between cycles without weakening feasibility.

Official links and next actions

Use the official opportunity and NIH submission channels as your primary sources:

• APEx NOFO (full text): RFA-DE-27-002 full announcement
• Grants and application instructions: NIH grant system pages referenced in the NOFO
• Program administration: NIH institute pages and assigned program contacts listed in the solicitation

Before you finalize, do a final alignment check:

• Does your draft avoid trial language?
• Does your budget match the stated RC and ITP structure?
• Are leadership commitments specific and measurable?
• Can the portfolio function if one or two ITPs fail?
• Are your dates and deadlines accurate for the 2026/2027 cycle you are targeting?

If most answers are yes, your application is now in a review-ready state.