RFA-CA-27-021: Sustained Support for Informatics Technologies for Cancer Research and Management (U24 Clinical Trial Optional)

RFA-CA-27-021: Sustained Support for Informatics Technologies for Cancer Research and Management (U24 Clinical Trial Optional)

The U24 NOFO RFA-CA-27-021 is a sustained-support route in the NCI Informatics Technology for Cancer Research (ITCR) line. It is one of the clearest NIH opportunities for teams that already have an established informatics resource and now need to maintain, evolve, and scale that resource for the broader cancer community. The NOFO is explicitly positioned as continuation support for mature technologies and data resources, not for early-stage method invention.

Key details

What this opportunity is trying to fund (and what it is not)

This opportunity is not a generic new-idea program. The central promise is sustained support for informatics resources that already exist and are already used. The announcement language says the program supports sustainment and continued relevance of high-value informatics tools with demonstrated impact, rather than projects centered mainly on fresh exploratory research.

The distinction matters because teams coming from traditional early-stage grant pipelines often submit the same proposal as if they were applying for a classic R01-style exploration grant. In this NOFO, that is a mismatch. The NOFO says successful proposals should provide:

• evidence that the technology has already had significant impact;
• a clear sustainment plan that advances that impact;
• community support and outreach (training, documentation, help desk, adoption support);
• active engagement plans so the resource evolves with user need.

Applications that are primarily about creating something new from scratch can still be accepted in other companion NOFO tracks, but this specific call is for the later-stage stewardship stage of the ITCR lifecycle. You can think of it as “keep and strengthen what works” funding.

The practical implication is:

• your budget should justify support and maintenance complexity, not expensive proof-of-concept science;
• your narrative should show continuity and community dependency,
• and your requested activities should balance innovation with reliability.

Where projects should fit this call

The NOFO explicitly welcomes informatics technologies across the cancer research continuum. Real-world examples that are a strong match include:

• clinical or translational research tools used across active networks;
• platforms for data acquisition, integration, annotation, curation, and reproducibility;
• interoperability layers and APIs that improve how data and algorithms move between systems;
• community-facing training and support infrastructure where researchers depend on sustained uptime and support.

What the NOFO is less interested in:

• exploratory one-off analytic method papers;
• projects where the primary activity is applying existing methods without building an established resource;
• projects whose core activity is large-scale new primary data generation.

That last point is directly reflected in the non-responsiveness criteria where projects with excessive data generation are screened out.

Eligibility and organizational constraints you must respect

This NOFO is unusually permissive at the institution level. The listed eligible organizations include higher education entities, nonprofits (including small and non-501(c)(3) entities), for-profits, local government, federal organizations, and other specific U.S.-based structures. Non-U.S. entities are explicitly eligible too.

The important caveat is strict: foreign subawards/subcontracts are not acceptable in this specific call, despite broad organizational eligibility. If your team is internationalized, you can still collaborate, but the awarded funds should be awarded to compliant recipient structures as required by this NOFO.

At investigator level, a practical non-negotiable item is that each PD/PI must have an eRA Commons account and ORCID, with the ORCID profile linked to the eRA account. The call also sets PI effort expectations:

• minimum 1.8 person-months/year (15% effort) for single-PI applications;
• minimum 1.2 person-months/year (10% effort) for each PI in multi-PI applications.

Applicants should confirm registrations early because SAM, UEI, eRA Commons, and (if needed) ORCID linking are not optional administration details; they are gating requirements. The NOFO repeatedly emphasizes late registrations are not grounds for delayed submission acceptance.

Full proposal architecture for this U24

Your proposal should read like an operations and impact stewardship plan with explicit technical depth.

1) Start with evidence of current value

The first reviewer question is usually: has this resource already proven itself? You should include:

• adoption metrics (user base, publications, citations, pipelines, dataset reuse);
• concrete outputs generated with the current resource;
• evidence that users depend on it for reproducible workflows.

Even before reviewing future plans, reviewers will likely look for why this is a mature resource worth retaining.

2) Build a sustainment budget, not a discovery budget

The budget cap is explicit ($600,000 DC/year). Given this, your budget narrative should prioritize:

• core engineering maintenance;
• performance/stability/security improvements;
• user support (documentation, help desk, training);
• interoperability work;
• selective feature expansion aligned to community needs.

The NOFO explicitly pushes applicants to reserve 10% of annual direct costs in budget period 2 onward for collaborative activities with qualified ITCR groups or wider research communities. Include this line item explicitly in the right budget category and show alignment with your collaboration plan.

3) Demonstrate community-facing rigor

The page repeatedly highlights support, training, and engagement components. A technically excellent tool with little support architecture is still weak here.

You should include:

• onboarding resources;
• user documentation and training plan;
• bug triage process;
• release and change-management communication;
• mechanism for external contributions or open-source governance (if relevant).

4) Propose collaboration and interoperability as a core deliverable

The NOFO allows expansion through collaborative and post-award activities and says these are expected to be assessed. Good proposals typically:

• map planned collaborations;
• identify partner institutions and integration points;
• specify APIs or interoperability pathways;
• show how shared resources (within and beyond current ITCR components) increase impact.

Timeline and planning strategy for the 2026/2027 cycle

The key dates from the posting are:

• Posted: 21 May 2026
• Open date: 1 June 2026
• First due date: 1 July 2026
• Second due date: 19 October 2026
• Review and start follow with November 2026 / March 2027 review windows and April/July 2027 earliest start dates.

Use this as a two-step race:

• Round 1 target: early submissions in first half of June with internal review complete by 20 June.
• Round 2 reserve: if substantial redesign is needed, keep a clean alternate submission for July/October window, but do not rely on carryover from a weak first draft.

In both cycles, 5:00 PM local time is the hard due time, and late applications are not accepted.

Practical milestone map

1. Weeks 1–2 after open (June 2026): lock scope and confirm registration readiness.
2. Weeks 3–4: draft key narrative sections (sustainment, impact evidence, implementation plan).
3. Week 5: finalize budget with explicit collaborative-activity set-aside and effort declarations.
4. Week 6: internal compliance pass for NIH-specific registrations and policy language.
5. Final two days: pre-submit validation using ASSIST/Grants.gov/Grants submission path.

This timeline is aggressive but realistic for a U24 that is more systems-operations centered than discovery science centered.

Review signals and common mistakes

This section matters because teams sometimes fail even with technically excellent proposals.

Common mistake: treating this as a pure innovation grant

If your budget is mostly exploratory research without documented baseline utility, the proposal may be considered non-responsive. This NOFO is explicitly for sustainment and evolution, not first-generation invention.

Common mistake: missing demonstrated utility

If you cannot prove the existing value of your tool, reviewers cannot verify continuity. Include concrete usage numbers, maintenance history, and adoption evidence in your preliminary sections.

Common mistake: underestimating support operations

U24 reviewers read beyond novelty. They want sustained operations and community engagement capacity. Teams that submit “build-only” plans often score lower than teams that explain support strategy, training, and community responsiveness.

Common mistake: international collaboration setup errors

Foreign subaward/subcontract provisions disqualify proposals that ignore them. Be explicit in your consortium model and finance plan so there is no compliance ambiguity.

Common mistake: violating PI readiness

Missing eRA Commons or ORCID linkage creates avoidable administrative failure risk, especially for teams with multi-PI submissions. Confirm all PI accounts and links before final validation.

Required materials and submission channels

The NOFO allows submission through NIH systems:

• NIH ASSIST;
• an institutional system-to-system route (with Grants.gov + eRA Commons);
• Grants.gov Workspace + eRA Commons tracking.

The NOFO explicitly references NIH’s Research (R) instructions and standard application instructions. The safest approach is to use one submission system consistently for your institution and run a pre-submission compliance pass against the NOFO-specific instructions.

In practice, include at minimum:

• project abstract and significance narrative focused on sustainment;
• technical workplan for maintenance, expansion, and interoperability;
• clear budget with category controls and 10% collaborative funds in budget period two onward;
• PI profile and administrative compliance evidence;
• organizational registration confirmation.

Why this is a 2026/2027 candidate worth tracking

This is genuinely relevant to your target window because it opened in 2026 and includes a new funding cycle landing into FY 2027 timing. The award date window and project start dates align with planning for 2026/2027 strategy documents and can be slotted into 2027 planning meetings.

It is especially suitable if you are:

• an established consortium with an adopted resource;
• a center that has support commitments but no dedicated maintenance pipeline;
• a team needing to maintain software, security, documentation, and user support under a federal funding rubric;
• a group that already has publications and usage signals and needs to move from pilot success to reliable long-term usage.

If your team is pre-launch and mostly working on concept generation, this is likely not the best first NIH fit.

FAQ for fast decision-making

Is this open to individuals or only institutions?

The NOFO is institution/application-based. The organization must be eligible and complete NIH registration. PI credentials are required, but the mechanism is not a personal scholarship-type route.

Can I apply with a new software concept?

Only if you can frame it as a sustainment project with demonstrated prior impact and clear community dependence. Early-stage concepts are a poor fit and should go through other NOFO tracks.

Can foreign teams apply?

Yes, in principle as applicants, but subawards/subcontracts to foreign entities are disallowed under this NOFO. Keep that in scope.

Is there more than one application deadline?

Yes. The posted key dates include both July and October 2026 submission windows. The call is structured as multiple intake points into FY 2027 timeline planning.

Is the budget guaranteed per project?

No. The NOFO states NCI intent and award caps, not a fixed award amount per application. The cap is what you must respect.

Is this a clinical trial mechanism?

Clinical trials are accepted but optional.

Final checklist before submission

A submission-ready checklist for this NOFO:

• Confirm open/eligibility window and selected cycle (July or October 2026) with your institution’s grant office.
• Show sustained impact from current or historical use of the resource.
• Allocate collaboration funds as required in budget period 2 and beyond.
• Include user-facing support plan (documentation/training/help desk).
• Keep planned primary data generation modest and aligned to support goals.
• Avoid any ambiguity about foreign subawards/subcontracts.
• Complete NIH registrations and PI profile requirements early.
• Use one official submission route and align all package sections to NIH Research (R) instructions.

That checklist is less about paperwork and more about reducing preventable non-compliance risk.

Official references

• Official NOFO page: https://files.simpler.grants.gov/opportunities/0dbbed9f-dfa7-421b-b6f6-941de5a77342/attachments/00e91bf7-108f-45d0-8ed1-79a6ed6e1f08/RFA-CA-27-021-Full-Announcement.html
• Submission channels overview: NIH ASSIST, Grants.gov Workspace, and institutional S2S
• NIH policy references: Research (R) Instructions and Grants Policy Statement (as referenced in the NOFO)