RFA-OD-27-005: INCLUDE Project: Clinical Trials Phased Awards for Down syndrome Research (R61/R33 Clinical Trial Required)

RFA-OD-27-005: INCLUDE Project: Clinical Trials Phased Awards for Down syndrome Research (R61/R33 Clinical Trial Required)

The INCLUDE Project NOFO RFA-OD-27-005 is a trans-NIH, milestone-driven grant opportunity to build clinical trial capacity for health conditions affecting people with Down syndrome. It is a reissue of RFA-OD-22-010 and uses the NIH R61/R33 exploratory/developmental phased structure. This design requires applicants to think in two linked stages: an early feasibility phase (R61) and an implementation/clinical trial phase (R33) that can follow if pre-specified milestones are met.

The opportunity is directly relevant to the 2026–2027 planning horizon because the page provides a key date sequence starting with opening on 15 September 2026, a 2026-10-15 full submission, and a second major cycle in 2027-06-15. It is especially useful if your team is prepared for translational clinical work and can show a defensible milestone architecture for a concrete health need in the Down syndrome population.

Key details

What this NOFO is for in practical terms

This NOFO is about one of the strongest gaps in current Down syndrome care: translation from preclinical and observational insights into interventions that are actionable in real clinical settings. Unlike discovery-only opportunities, this mechanism is explicitly tied to clinical trial development for co-occurring conditions. The NOFO states the project intent as improving health and quality-of-life by supporting phased development of clinically relevant research questions that can produce durable practice-relevant outcomes.

In practice, this means the right projects tend to share several characteristics:

• They target one or more high-impact co-occurring conditions in Down syndrome (for example sleep apnea, epilepsy, cognitive decline, immunological/neuroinflammatory pathways, or other health challenges).
• They need a clearly staged experimental logic, where preparatory steps in R61 reduce risk before trial implementation in R33.
• They can show how findings can scale into routine settings, not stay as a pure lab-only experiment.
• They can generate useful clinical data and infrastructure outputs (e.g., partnerships, registries, shared datasets, trial-readiness tools).

The mechanism is not best for fully mature clinical trials requiring a one-step submission with no development sequence. If your proposal is already in late-stage trial execution mode, this may not be the most aligned instrument unless you can justify a true R61-to-R33 transition pathway.

Why this is relevant for 2026/2027 planning

There are two separate reasons this is strategically timely:

1. Application timing is concrete and still actionable with 2026 preparation The posted schedule gives early-cycle visibility: posted in May 2026, open in September, due in October for the first listed cycle. If your institution can finalize registrations and align IRB/legal compliance now, this opportunity supports mid-year planning for teams with strong research leads.

2. Phased architecture supports better portfolio management NIH-style programs with strict review criteria heavily penalize unfocused plans. R61/R33 allows teams to present an explicit sequence: what the pilot phase proves, what success gates must be cleared, and what the trial phase looks like. This is more realistic for difficult patient-population studies than forcing one overpacked narrative.

Teams that are not ready for the first 2026 cycle can often use the 2027 cycle as a second major chance, but they should treat review cycles as an evidence-building ladder rather than a reset button.

Eligibility and who can apply

The NOFO has unusually broad institutional eligibility and does not present a narrow applicant-type lock-in. Eligible organizations include:

• Higher education institutions (public and private)
• Nonprofits (both 501(c)(3) and non-501(c)(3))
• For-profits, including small businesses
• Local and federal government entities
• Certain non-domestic organizations and foreign components of U.S. entities

That breadth means many teams can qualify institutionally, but several practical constraints remain high-impact:

• Foreign entities are eligible in general, but the NOFO does not allow awarded projects to include foreign subawards/subcontracts unless the program path is specifically designed for those collaborative forms.
• The rules explicitly discourage duplicate or overlapping submissions under active review; teams cannot move too quickly with parallel near-identical A0/A1 applications.
• Applicant registrational compliance is mandatory: SAM (via Grants.gov), eRA Commons, and PD/PI account preparation are expected by submission time, with ORCID linkage required.

Interpretation for applicants: This is broad on paper but strict on process architecture. Your biggest risk is usually timing/compliance, not concept eligibility.

Funding structure and review logic you should design for

The NOFO does not publish a single flat award amount. It says budgets are not limited by a fixed mechanism-specific ceiling in the announcement text, so you must cost realistically and justify every budget line against milestones and deliverables.

The mechanism is five years max overall:

• up to 2 years in R61 (preparatory/feasibility)
• up to 3 years in R33 (later trial implementation)

Reviewers evaluate whether the two-stage logic is actually integrated. A common failure mode is treating R61 and R33 as two unrelated mini-proposals. The page requires explicit milestones, and transition depends on documented achievement of these milestones.

What tends to satisfy reviewers

The likely review emphasis is on impact and feasibility, but this NOFO is clearly structured to reward:

• a tight clinical rationale rooted in Down syndrome-specific unmet needs,
• feasibility data or methods that reduce trial failure risk,
• a credible recruitment and implementation pathway,
• measurable milestones that justify resource asks,
• and strong planning for data quality, safety, governance, and reporting.

Application process: what to submit, and when

The full path is standard NIH, with NIH-specific details layered on top:

1. Obtain system and role setup:
   • SAM registration (via Grants.gov requirements)
   • eRA Commons with valid Signing Official and PI accounts
   • ORCID linkage for all PDs/PIs
2. Confirm submission route:
   • NIH ASSIST, Grants.gov Workspace, or approved institutional S2S.
3. Prepare SF424(R&R) elements with NOFO-specific structure:
   • separate R61 and R33 components in Research Strategy,
   • milestone plan for the transition.
4. Ensure all pages and instructions align with the NIH Application Guide and NOFO section requirements.
5. Submit before 5:00 PM local time of applicant institution on due date.

Deadlines to track

• Open date: 2026-09-15
• First hard due date: 2026-10-15 (full cycle submission details in same NOFO)
• Second full-cycle date: 2027-06-15
• Expiration for current NOFO content: 2028-06-16

The NOFO says applicants should submit early where possible, because NIH systems can produce pre-submit errors and late corrections are constrained by final due dates.

Required proposal content and quality bar

You should structure your package as a sequence map, not a generic application.

Minimum content architecture

• Clinical strategy split by phase
  • R61: trial preparatory/feasibility activities, proof-of-concept data generation, cohort preparation, and readiness planning.
  • R33: trial execution plan, full methods and safety governance, recruitment pathway, and implementation architecture.
• Explicit milestone table
  • Include timeline, measurable outputs, and go/no-go criteria.
  • Tie each milestone to scientific risk reduction.
• Data and governance plan
  • The NOFO references NIH-wide data requirements and expects robust sharing and management planning.
  • Explain how data are structured, stored, shared, and reused.
• Safety, monitoring, and oversight
  • Include a realistic monitoring model, including Data Safety Monitoring Board processes in budget and planning.
• Reviewer-aligned risk framing
  • Avoid broad claims like “we can scale quickly.” Show how you will de-risk recruitment, protocol complexity, and retention.

Critical operational constraints

The opportunity allows and expects milestone transition logic. This can become a trap if under-specified. Put each milestone into the workflow language used by your team:

• Objective, metric, threshold for success
• What counts as go vs. stop vs. revise
• What resources are required to complete each checkpoint

Also, if your work includes human subjects, standard NIH forms remain required and should be handled as first-class workstream items, not an afterthought after science sections.

Common mistakes that reduce competitiveness

1. Ignoring the two-stage logic Writing a single continuous plan without a hard distinction between R61 and R33 suggests weak project planning and can weaken significance in review.

2. Underestimating administrative readiness Most high-quality grants are first delayed by missing registrations or account roles, especially when PI roles, signing officials, and eRA account types are incomplete.

3. Overestimating budget without milestone grounding Even without a stated direct cap, NIH reviewers and staff will inspect budget reasonableness relative to milestones. Unjustified spend profiles are viewed as a control problem, not a strength.

4. Treating international collaboration as simple addition The NOFO is strict on foreign subawards/subcontracts. Partnerships can still work, but only if they satisfy the NOFO’s collaboration and compliance boundaries.

5. Treating the NOFO as disease-general This is not a generic clinical innovation mechanism. Proposals must be specifically tied to Down syndrome comorbidity burden and how your intervention changes outcomes for this population.

6. Not planning for review-response discipline If the first cycle is not successful or is delayed, teams that preserve a clean audit trail of feedback and fixes are in better position for the next cycle.

Practical preparation workflow for teams

If you are targeting the 2026-10-15 window

• 90 days out: lock the clinical question and confirm trial feasibility.
• 60 days out: complete all registrations and PI account validations.
• 45 days out: finalize R61 scientific plan and milestone gate set.
• 30 days out: align R33 buildout and budget narrative with transition logic.
• 10 days out: run a pre-submission systems checklist for ASSIST/Grants.gov/eRA.
• Week of submission: submit early and resolve correction requests before final timestamp.

If you are targeting 2027-06-15

Use this as a development cycle, not an idle delay:

• Run a mini pilot during 2026/early 2027 to strengthen feasibility claims.
• Use NIH comments from prior cycles (if applicable) to harden milestone logic.
• Add stronger data infrastructure and recruitment reliability language.

Frequently asked questions

Is there a fixed award amount?

No fixed amount is stated in the pages retrieved for the NOFO. Budget requests are allowed to be set by project needs, with justification.

Can a foreign organization apply directly?

Yes, some foreign entities and components can be eligible. But this NOFO explicitly disallows awards involving foreign subawards/subcontracts unless the solicitation pathway permits it. Confirm your collaboration structure early.

Can I ask for renewal, resubmission, and multiple applications?

The NOFO permits more than one submission from the same applicant if scientifically distinct, but it restricts duplicate/overlapping applications under review and overlapping A0/A1 pathways.

Is this still relevant after 2026?

Yes, the same NOFO provides multiple cycles, with an explicit 2027-06-15 due date and publication window through 2028. But for strategy clarity, teams usually optimize around the latest upcoming cycle matching readiness.

Reviewer expectation framework for this NOFO

A winning application usually demonstrates:

• conceptual precision: one main translational hypothesis with clear clinical implications;
• evidence planning: what must be observed in R61 to justify R33;
• implementation realism: where participants will be recruited, retained, and measured;
• governance maturity: governance of human-subjects and data requirements;
• reproducible rigor: explicit data-sharing and safety/compliance alignment.

Avoid proposing a list of disconnected projects. The NOFO is much more persuasive when it reads like a coherent pathway from biological/clinical observation to improved trial execution and patient-relevant outcomes.

Official links and direct contacts

• Official NOFO page: https://files.simpler.grants.gov/opportunities/ce88b262-95b3-4f53-942d-41dc3ff2fa7f/attachments/628129bc-33ce-4cef-93c9-a3a5769e4efb/RFA-OD-27-005-Full-Announcement.html
• Application systems: NIH ASSIST, Grants.gov Workspace, institutional S2S
• Administrative support:
  • eRA Service Desk (submission and system operations): https://public.era.nih.gov
  • Grants.gov Support Center
• Scientific/program contact: [email protected]
• Peer review contact: [email protected]

This is a strong 2026/2027-cycle opportunity when your team can demonstrate practical readiness, milestone discipline, and a realistic pathway from preparation to clinical trial execution. The quality bar is high, but predictable: if your project has a credible R61-to-R33 progression, strong Down syndrome relevance, and clean compliance execution, it is aligned with the NOFO’s intended model.