RFA-AI-27-016: Tuberculosis Research Advancement Centers (TRACs) (P30, Clinical Trial Not Allowed)

RFA-AI-27-016: Tuberculosis Research Advancement Centers (TRACs) (P30, Clinical Trial Not Allowed)

Tuberculosis remains a major infectious disease burden globally, and NIH has continued to use the TRACs model to build durable, institution-level research capacity. Under RFA-AI-27-016, NIH is running a reissue of the TB center approach with a clear structural design: institutions build a core-and-core network that combines facilities, mentoring, collaboration, and pilot-scale project support so new TB researchers can enter the field with real infrastructure.

This NOFO is not a single-project lab grant. It is a multi-component program support mechanism with a center structure (P30) and an explicit expectation that you submit a coordinated institutional application with a defined core architecture, not just one isolated protocol. The call is for work relevant to Mycobacterium tuberculosis and/or nontuberculous mycobacteria and is explicitly clinical trial not allowed.

At-a-glance key details

What this opportunity is (and what it is not)

This is a research center support mechanism tied to TB capacity and workforce development, not a direct one-project discovery grant. The proposal must establish or expand a Tuberculosis Research Advancement Center around an Administrative Core, a Developmental Core, and at least two additional Cores such as:

• Basic Science Core(s)
• Clinical Science Core(s)
• Specialty Core(s) for bioinformatics, statistical support, omics, and related functions

The intent, per the NOFO narrative, is to sustain a local research ecosystem rather than a single hypothesis test. TRACs are meant to create shared tools, training channels, and mentoring for new investigators, while also enabling institutional members to pursue additional developmental pilot projects in TB-related themes.

This matters because many investigators overfit their TRAC idea into a standard R01 narrative and lose points. Reviewers and staff expect the center logic to be visible in your design:

• Why this center is needed at your institution
• Which researchers will use shared resources
• How trainees/new investigators are recruited and retained
• What measurable transition outcomes the center should produce after startup

If your institution is seeking a one-off seed project, this is likely a poor match. If your institution has existing TB research capacity and wants to scale shared functions and create a sustainable pipeline of TB investigators, this can be strategic.

Why this is currently relevant for the 2026/2027 cycle

The posting date is May 4, 2026, with open submission starting June 10, 2026 and a deadline of 2026-07-10 for new applications. The NOFO shows peer review and council review windows leading to an anticipated March 2027 start window for awards. The posted NOFO indicates key dates for the current cycle including peer review and council review timing and a July 11, 2026 expiration marker for the notice package.

Even if the first round is now in history relative to your current planning date, this specific call remains relevant because:

• It is explicitly a center model and may serve as a template for future NIAID infrastructure programs.
• The structure (Administrative + Developmental + Cores) can be reused for internal planning even when deadlines are missed.
• The exact reviewer questions and compliance requirements often carry forward into subsequent cycles in related TRAC and P30 programs.

If your priority is a live filing in 2026/2027, you should act only if you can reach 2026-07-10 and complete registrations and drafts before the final internal approval milestone. NIH-style NOFOs penalize late registration and incomplete administrative setup much as strongly as scientific weakness.

Eligibility and hard constraints

The NOFO has straightforward and rigid constraints that should be checked immediately before application work begins.

Eligible applicant types

The call includes a broad U.S. base set:

• Public and private institutions of higher education
• Nonprofits (including 501(c)(3) and non-501(c)(3) non-institutions)
• For-profit organizations, including small businesses and larger non-small-business entities
• Local and federal governments
• Tribal, school district, regional and housing authorities in specified categories

Not eligible

The page is explicit: non-U.S. organizations are not eligible, and foreign components tied to U.S. organizations are also not allowed. If your institutional team includes a foreign partner as a core collaborator, define clearly whether they are sub-award collaborators versus the applying entity. The strict non-domestic rule on U.S. eligibility is often a silent killer in multinational TB collaborations.

Application limit and duplication policy

Only one application per institution is allowed. NIH also applies overlap restrictions on new vs resubmission sequencing and will not accept duplicate or highly overlapping applications under review. If your institution has attempted multiple versions, you need to decide early whether to withdraw and consolidate.

Investigator-level constraints

• Every PD/PI must have an active eRA Commons account.
• If the PD/PI is also an institutional signing official, two separate Commons accounts are required (one per role).
• PD/PI profiles must be linked to ORCID IDs.
• For multi-PI applications, NIH-specific multiple PI submission logic applies.

Clinical trial scope

This NOFO is clearly marked clinical trial not allowed. Applicants whose core activities involve clinical trials must confirm that their planned work stays within non-clinical-trial-defined projects, or they risk rejection before scientific review.

Application process and required components

This is the part where most teams fail: TRACs are administratively complex and require careful construction of a multi-component SF424 package. The NOFO provides explicit component-level instructions. The practical minimum for planning is:

1. Prepare registrations early (SAM.gov, eRA Commons, Grants.gov workspace links as required).
2. Build an institutional application package via ASSIST or approved institutional S2S route.
3. Construct the Overall component plus mandatory Administrative Core, Developmental Core, and additional Cores.
4. Attach plans and narratives requested under each core.

Critical submission mechanics

NIH expects electronic submission only via Grants.gov and eRA Commons tracking. Paper submission is rejected. The NOFO is explicit that changing/ correcting submissions is possible only if corrected versions are accepted before the deadline.

What to prepare technically:

• Ensure applicant UEI aligns across SAM and eRA Commons.
• Confirm PD/PI Commons credentials and ORCID links early (obtain up to 2 weeks lead-time is common for account setup).
• Confirm that every PD/PI and project lead has a valid eRA Commons credential in the Senior/Key Person Profile.

Required or emphasized materials

The NOFO references NIH application guide instructions and then layers specific requirements:

• Developmental Core and Cores must describe how they train and support new investigators.
• Specificity on compliance systems (IRB, IACUC, FWA) is expected where applicable.
• Human subjects sections are not optional where applicable: include required records when Are Human Subjects Involved is marked yes.
• Include strong narrative in Research Strategy and Specific Aims for each core and the overall center.
• Resource sharing requirements apply where applicable.
• Data Management and Sharing Plan is required overall (if required by this NOFO) and included in the Overall component.
• Appendix content is intentionally limited.

What your core model should show reviewers can follow

A strong TRAC application usually reads like a coordinated operations plan, not just a scientific concept deck. Use this architecture:

• Administrative Core: governance, budgeting, progress tracking, reporting, and institutional alignment with NIAID priorities.
• Developmental Core: mentoring, pilot projects, NI/early investigator support, and career progression pathways.
• Technical cores: explicit service outputs, user demand process, turnaround expectations, and utilization metrics.

If this structure feels forced for your institution, pause. The NOFO is explicit that each core should avoid overlap and duplication.

Review process and what reviewers are actually scoring

The review chain is standard NIH peer review with additional P30-specific scrutiny around center coherence.

Stage 1: peer review criteria

Reviewers evaluate scientific and technical merit using:

• Significance
• Investigator(s)
• Innovation
• Approach

The narrative quality expected is not a list of TB facts. It is a demonstration that:

• The scientific problem is urgent and tractable within this center design
• Leadership has complementary expertise and governance for collaborative multi-core operations
• Approach includes risk management, rigor, and measurable milestones
• There are realistic plans for diversity variables where relevant (e.g., biological variables in applicable studies)

Additional review considerations

Reviewers also comment on:

• Select agent handling and biosafety if relevant
• Resource sharing and justification for non-sharing
• Validation of biological/chemical resources
• Human subjects protections and humane animal use where applicable
• Budget reasonableness relative to proposed scope

Common review-level failure modes

• Weak center rationale: submitting a disconnected set of pilot activities instead of a system.
• Underdeveloped Developmental Core: no clear NI/early-career pathway.
• Over-broad scope with no triage logic for core selection.
• Non-specific budget rationale across five-year horizon.
• Administrative/Core duplication (same services described twice, unclear governance).

Funding decisions and likely outcome path

NIH indicates that only a subset typically reaches full discussion (often top half in similar processes), then second-level review follows council consideration. Decisions are based on scientific merit, available funds, and relevance to NIH priorities.

Preparation roadmap for institutions

The TRAC route is not for speed. It is for institutions that can deliver an operational document before they deliver a pure scientific breakthrough. A practical sequence:

8–10 weeks before the deadline

• Decide institution and legal entity strategy (UEI, SAM.gov, eRA profile scope).
• Finalize institutional commitment letter and identify in-kind support (lab space, shared equipment, shared support personnel).
• Confirm each PD/PI role and leadership hierarchy.

6–8 weeks before the deadline

• Lock final center architecture and core definitions.
• Draft Administrative and Developmental core sections in parallel with science team.
• Identify first-wave pilot projects and expected applicant cohort (NI/trainee support pathways).

4–6 weeks before the deadline

• Finish scientific narrative and approach sections.
• Verify registration dependencies (eRA and ORCID).
• Conduct internal compliance pass for every mandated section and form.

Final 2 weeks

• Build and run an NIH-style error check via internal systems.
• Confirm submission and final validation in eRA Commons.
• Confirm no overlap with pending submissions.
• Submit a backup changed/corrected package only if required and by deadline.

Common mistakes and pre-submission checklist

Use this checklist to catch preventable rejection points:

• ✅ One application only per institution (and no overlap with other pending A0/A1 work)
• ✅ Clinical trial status confirmed as not allowed.
• ✅ All PD/PI credentials in place before submission
• ✅ Single coordinated UEI and applicant entity across systems
• ✅ Full core structure described in non-overlapping way
• ✅ Compliance paragraphs and approvals are planned (IRB/IACUC/FWA where required)
• ✅ DMS plan placement is in the Overall component if required
• ✅ Budget tables consistent with 5-year scope and annual direct-cost logic
• ✅ Limited appendix usage and no unsupported add-ons
• ✅ Error correction completed before deadline window closes

Teams often fail here because they overbuild science but underbuild operations. For TRAC, operations are review evidence.

FAQ

Is the program open to foreign institutions?

No. The NOFO explicitly excludes non-U.S. entities and non-domestic components.

Can an institution submit both a new application and a renewal?

In this NOFO, allowed application types are new and renewal. But NIH rules prevent duplicate or overlapping submissions across unresolved stages.

Can industry apply as a lead applicant?

Yes, provided it falls into NIH-eligible categories. The NOFO includes both nonprofit and for-profit entity categories among possible applicants.

Are clinical trials allowed?

No. This opportunity is marked clinical trial not allowed.

Does this fund salary-only projects?

No. It funds multi-core center operations and supports shared resources and trainee-facing activities with annual budget expectations capped by the NOFO guidance.

Where do post-award requirements start?

RPPR and final closeout requirements follow NIH standard policy, including annual progress reporting and post-award monitoring for data, fiscal, and compliance performance.

Official links

• Full NOFO: https://files.simpler.grants.gov/opportunities/e69c1e21-0138-46be-8b75-3d6967e80238/attachments/a6689148-46af-401d-bf4a-716afb9f9440/RFA-AI-27-016-Full-Announcement.html
• Grants submission support: NIH and eRA application guide links are referenced within the NOFO
• Program office contact: [email protected]
• Scientific review contact: [email protected]
• Financial/grants management contact: [email protected]

Final guidance

RFA-AI-27-016 is most suitable for institutions aiming to build TB capacity over several years rather than teams chasing a single milestone. Its design rewards evidence of organizational readiness. If your strongest asset is a compelling idea but you do not yet have a functional center structure, it is likely to underperform.

If your institution already has TB-relevant infrastructure and leadership bandwidth to run a multi-core model, this is one of the few opportunities that combines workforce development and infrastructure under a single review framework. The practical advantage is not just potential direct costs per year; it is the ability to embed new investigators in a sustained TB research pathway with coordinated resources.

A well-structured TRAC proposal should answer, before reviewers ask it: how this center changes the institution’s ability to produce TB science, not just one project’s ability to pass peer review.