RFA-OD-27-003: INCLUDE Project: Exploratory/Developmental Research Awards for Down syndrome (R21 Clinical Trial Not Allowed)

RFA-OD-27-003: INCLUDE Project: Exploratory/Developmental Research Awards for Down syndrome (R21 Clinical Trial Not Allowed)

Key details

What this opportunity is for

This NOFO is a focused NIH funding line inside the INCLUDE umbrella—INvestigation of Co-occurring conditions across the Lifespan to Understand Down syndrome. The title is explicit: this is not a standard long-form clinical R01 style opportunity, and it is not a pilot program for routine translational continuation work. It is for high-risk, high-reward projects where a novel idea, method, model, or tool might materially change how investigators study Down syndrome.

NIH’s stated scope is to support early-stage research that can address critical Down syndrome gaps in co-occurring conditions and lifecycle changes in health outcomes. The page presents this as a mechanism for projects that might not yet have mature preliminary datasets but can still justify why the idea is scientifically credible and worth an exploratory trial. The logic is straightforward: NIH wants to seed approaches that might otherwise fail to pass conservative grant screens because they are too novel, too early, or too risky for traditional funding routes.

Unlike larger programmatic consortia or infrastructure calls, this NOFO is tied to concrete project-level ideas from single teams. That makes it practical for principal investigators with one clean scientific pitch who can move quickly but still need NIH-level review and accountability.

What it funds and what it does not fund

The opportunity is intended to fund exploratory and developmental studies that align with three broad research components in the INCLUDE ecosystem:

1. targeted high-risk basic science around chromosome 21 biology,
2. approaches that help assemble or improve large Down syndrome cohorts,
3. clinical-trials research inclusive of individuals with Down syndrome (with the explicit caveat that projects proposing actual clinical trials are excluded from this specific NOFO).

The NOFO repeatedly highlights novelty and risk acceptance. It explicitly says projects should be exploratory and developmental, with room for uncertainty. If your plan requires a long, incremental pipeline with extensive existing infrastructure as its central rationale, this likely belongs in a different mechanism.

It also places clear limits: the mechanism is for R21-type work and does not function as the channel for low-innovation routine studies. It says such studies are better served through smaller grants with low novelty, which helps separate strategic intent from standard R01-style continuity work.

What this means in practice:

• You should avoid proposals that read like scaled-up replications of already published methods without a clear new angle.
• You should center the scientific gamble and how you will produce decisive proof within 1–2 years.
• You should still provide enough rigor to satisfy NIH peer review, especially around rigor and reproducibility.

Who should apply and who should skip

Because this call is under the trans-NIH INCLUDE program, organizations and teams can be broad. That said, “open” does not mean “easy fit.” You should apply only if your idea genuinely needs an exploratory R21 and if reviewers can see an explicit relevance to Down syndrome and its comorbidities.

A strong fit usually includes:

• a distinct conceptual gap in Down syndrome biology or care-related science,
• an approach that is not a routine extension of common protocols,
• measurable outputs deliverable in 2 years,
• a team and data strategy clear enough for NIH review.

Organizations should be prepared to meet compliance obligations. In practice, the NOFO is often won by teams that can pass administration cleanly rather than by teams that only have a strong idea. If your institution has chronic SAM/eRA timing issues, this is a high-friction program to submit on time.

Avoid applying if:

• your study has clinical trial endpoints in a way that NIH will classify as a trial,
• your project is mature, long-horizon, and primarily optimization rather than feasibility discovery,
• your applicant organization has not completed registrations in time.

Eligibility and administrative requirements

This NOFO has a broad list of eligible entities. It includes higher-education institutions, nonprofits (including and excluding 501(c)(3) categories), for-profits, small businesses, local and federal governments, certain housing and tribal entities, and additional public organization categories.

Important nuance: non-U.S. entities are present in the listing, and non-domestic components can participate. But the NOFO draws a hard line on foreign subawards/subcontracts. The page states that NIH will not issue awards to domestic or foreign entities involving monetary foreign subawards/subcontracts under this opportunity, and that violates responsiveness if present. In practical terms, collaborative science is not banned, but financed international subcontracts are heavily constrained.

For investigators, the practical checklist is:

• confirm PI(s)/PD(s) have active eRA Commons accounts,
• link each PI profile to a valid ORCID ID,
• complete organization registrations before submission,
• ensure all required signatures and roles in eRA Commons are set by an organizational SO and PI accounts,
• confirm SAM is active and UEI is current.

For applicants planning multiple PIs, the NOFO points to NIH’s multiple PI policy and form pathway. If roles are unclear, use internal governance first to avoid a late compliance failure.

NIH also explicitly warns that failed or delayed registrations are not accepted as a late-submission excuse. That is not just administrative advice; it affects eligibility directly. The required registrations can take several weeks; this is why teams that begin near the deadline typically lose.

Funding structure, review cycle, and timing implications

The posted timeline includes:

• posted: May 12, 2026,
• open: September 15, 2026,
• application due windows: October 15, 2026 and June 15, 2027,
• recurring later cycle behavior through FY2029.

For planning in 2026–2027, the first usable window is the 2026 cycle, but the NOFO’s table makes clear that this is not a one-off. If your package is not fully compliant in time for the first round, there is a published later annual window.

Funding intent is around five awards per year with a $1,000,000 total, subject to appropriations and merit. That size profile implies selectivity. It is not a broad “wide net” program and can be treated as portfolio-limited: strong ideas still compete within a capped number of grants.

Budget and award conditions

The NOFO provides a strict budget frame:

• maximum direct cost total: $275,000 over two years,
• maximum direct per year: $200,000,
• maximum project period: 2 years,
• direct funding instrument: NIH grant.

Most teams should treat this as a constrained engineering problem. The key is to design a protocol that can produce a decisive scientific output in 24 months under the R21 ceiling while preserving rigorous controls and reporting integrity.

No cost sharing is required. This helps proposal design because you do not need donor commitments or parallel institutional match to be competitive. However, that does not weaken the need for a strong budget narrative. Reviewers still evaluate budget reasonableness against scope.

A good budget logic for this NOFO should prioritize:

• personnel time for exploratory experiments,
• limited but credible assay or cohort data collection,
• essential data sharing and core resource compliance,
• a plan that explicitly avoids overexpansion into “full study” design.

Application process: from package access to submission

The NOFO names NIH’s normal submission pathways:

• NIH ASSIST,
• institutional system-to-system route via eRA Commons and Grants.gov,
• Grants.gov Workspace with eRA Commons tracking.

In all tracks, the NOFO and NIH Research (R) Instructions govern compliance. The message is not “optional.” If you miss format, field names, required pages, or attachments, application correction windows are short and missed deadlines are likely fatal.

Operationally, apply this sequence:

1. Build your compliance timeline backward from the due date.

• complete SAM and UEI,
• finalize institutional roles,
• register all PI accounts and link ORCID,
• verify that Grants.gov can ingest your package.

2. Build the submission workflow early.

• run a dry submission (or at least a full pre-submission test build),
• confirm all required forms are present,
• verify no missing required attachments for page limits and signatures.

3. Submit early and avoid “last-day correction traps.”

• NIH explicitly says all applicants should submit before the deadline,
• applications that require changes after due time are late by NIH systems standards,
• weekend deadlines slide to next business day only, not indefinitely.

Given that the due time is 5:00 PM local applicant-time, teams in cross-country review cycles must plan internal approval windows in local time.

The NOFO also states that paper submissions are not accepted. This is fully online and strict.

Review criteria that matter for this specific NOFO

The NOFO makes one important contrast: R21 review emphasizes concept and potential over extensive preliminary data. The criteria stack mirrors NIH peer-review practice but with practical emphasis on novelty and feasibility under uncertainty.

Reviewers focus on:

• significance and innovation (is it genuinely important and novel?),
• approach and rigor (can it realistically produce reliable results in two years?),
• investigator/team and environment (is the team capable, and is the setting realistic for the plan?),
• and additional resource considerations (human subjects, animal research, biosecurity where relevant, and budget/project period reasonableness).

Because preliminary data are not mandatory for R21s, teams should not overspend writing effort trying to defend huge pilot evidence. The stronger strategy is a clean conceptual framework plus concrete methods that can succeed even with limited starting data.

A common mistake is to over-index on broad Down syndrome language but fail to tie the specific aims directly to one of the program-relevant components. Applications should make explicit which component(s) they are advancing. If reviewers cannot map that quickly, the score drifts lower due to ambiguity.

Practical fit checklist (before you write)

Before drafting final prose, answer these seven checks in writing:

1. Is the proposal genuinely exploratory/developmental, or is it a scaled-up standard study?
2. Does your method carry novelty sufficient to justify risk acceptance under R21 logic?
3. Can all core tasks be completed in the two-year window and within budget caps?
4. Are human/animal compliance items pre-planned with no trial claim that violates this NOFO’s “no clinical trials” rule?
5. Have you mapped each specific aim to one clear reviewer criterion?
6. Is your team registration complete (SAM, eRA Commons, ORCID, roles) by the cutoff date?
7. Can this be submitted with all required forms completed before a correction window closes?

If you can answer yes to each, your concept has baseline fit. If you cannot, you should either narrow scope or move to a different mechanism.

Common errors seen in submissions

Error 1: Treating R21 like an R01 with a small budget

People often write a full-scale R01 with too many dependent milestones and still keep an R21 cap. That creates review skepticism.

Fix: trim to the smallest package that answers one high-clarity question.

Error 2: Underestimating submission systems

Applicants frequently assume registrations are “background work” and leave them for later.

Fix: set registrations as a prerequisite deliverable and assign owners for each system account and role.

Error 3: Ignoring foreign financial collaboration constraints

Teams may submit structures that include disallowed foreign awards.

Fix: keep foreign collaboration non-monetized where possible, and ensure no blocked subaward/subcontract pathways exist.

Error 4: Weak alignment to INCLUDE priorities

Some proposals mention Down syndrome but are not anchored to co-occurring conditions and the INCLUDE framework.

Fix: explicitly state why your method fills a clear Down syndrome evidence gap and how findings map to cohort or life-span relevance.

Error 5: Late fixes after due date

Many applications fail during compliance checks before review.

Fix: submit for internal QA at least one to two weeks before official deadline.

Frequently asked questions

Is this still relevant if I only start preparing in early 2027?

Yes, if your team is ready for the 2027 June window. This NOFO appears structured around recurring annual cycles through FY2029, so the second and later windows are meaningful for planning.

Can foreign institutions apply as a lead?

The listing allows some non-U.S. entities and foreign components, but monetary foreign subawards/subcontracts are disallowed for this NOFO. That means legal structure, not just scientific intent, matters.

Is preliminary data required?

No. The NOFO explicitly aligns with exploratory R21 logic, and preliminary data are not required. But lack of data does not replace rigor: your rationale, design, and risk controls still need to be robust.

What date should I treat as the “deadline”?

For planning, use the published due dates (e.g., 2026-10-15 and 2027-06-15 in current cycles) and set your internal cutoff at least one week earlier to catch technical errors. Always submit before 5:00 PM local-time and account for federal holiday shifts.

Can this support population-level recruitment work?

Potentially, yes, if your project design fits R21 developmental goals and aligns with data sharing and cohort-quality standards referenced in the NOFO and related NIH guidance.

Official links and next steps

• NIH NOFO (official source): RFA-OD-27-003 full announcement
• INCLUDE program context: NIH INCLUDE website
• NIH grants policy and submission guidance: NIH Grants Policy Statement
• Application submission and system-specific process: NIH How to Apply - Application Guide
• DS-Connect registry reference for subject recruitment: DS-Connect

Use these links to verify the most recent version before drafting final forms, especially if you are preparing for the 2027 cycle. The NOFO text is the legal source for requirements, and this guide is designed to convert that source into a submission strategy for teams already aligned with Down syndrome exploratory research.