RFA-DE-27-001: Community Engagement Evaluation and Data Coordination (CEED) Hub to Advance Data and Practice Transformation for Optimizing Oral Health for All (U01, Clinical Trial Not Allowed)

RFA-DE-27-001: Community Engagement Evaluation and Data Coordination (CEED) Hub to Advance Data and Practice Transformation for Optimizing Oral Health for All (U01, Clinical Trial Not Allowed)

This funding opportunity is a new NIH announcement for a Community Engagement Evaluation and Data Coordination (CEED) hub within the larger ADAPT consortium (Advancing Data and Practice Transformation) for oral health. It is a U01 cooperative agreement (research project cooperative agreement) focused on building infrastructure, technical capacity, and evaluation capability to support community-based participatory research (CBPR) around oral health outcomes.

The NOFO explicitly frames this as a coordination mechanism rather than a standalone laboratory protocol grant. The core mission is to make local- and community-level oral health interventions stronger through better data planning, stronger community engagement methods, and a shared consortium operating model.

Key details

The page itself is the official source and includes a full text notice with all compliance details, application instructions, review criteria, and contact points.

Why this opportunity is a good fit for 2026–2027 planning

This call is a strong example of an NIH opportunity with a 2026 submission timeline and likely 2027 funding execution window. The posted date is April 2026, and the application cycle opens in late September 2026, with a deadline in October 2026. The earliest start date is listed in March 2027 with availability tied to peer review and council review timing. In practice, that means organizations can still act in 2026 but should expect award execution and implementation to roll into 2027.

For teams working in oral health, prevention, behavioral risk factors, epidemiology, or translational public-health systems, this is especially relevant because the grant is built around community-level transformation and data harmonization across CBPR projects. It is not a clinical intervention grant and not for individual laboratory pilots. If your project concept already depends on clinical trial outcomes, this opportunity is not the right mechanism.

This also matters because the NOFO is positioned as a hub for an existing consortium design:

• The ADAPT consortium itself includes separately funded CBPR projects under a related UG3/UH3 pathway.
• CEACR (NIH Community Engagement Alliance Consultative Resource) consultation is available to support partnership approaches.
• SCHARE is used as a data collaboration and analytics platform.

Because the hub is meant to connect workstreams instead of replacing them, institutions that can contribute coordination architecture, community engagement strategy, and analytical support have an advantage over teams with only one scientific project idea.

What this opportunity is actually funding

The CEED award is explicitly scoped to three coordination domains. Applicants must propose a viable plan covering all three:

1. Data planning, consultation, and technical assistance for research methodology and analytics.
2. Community engagement evaluation for partnerships and project implementation quality.
3. ADAPT consortium infrastructure and operations support to keep projects, data flow, and governance functioning.

In plain language, NIH is funding the layer that allows multiple CBPR projects to remain coherent, measurable, and reusable over time. The NOFO repeatedly notes that projects should not only run independently but also contribute to cross-project learning and better practice transformation.

The intended beneficiaries are not only communities and public health systems but the full consortium workflow:

• Projects in the network need planning support for standardizing measures.
• Community-based interventions need quality assessment and evaluation, especially around engagement quality.
• Data from projects needs harmonization and safe sharing structures.
• Consortium governance needs stable operations and recurring coordination.

This makes the grant closer to infrastructure and coordination leadership than to direct treatment innovation, despite the public-health impact goals.

Eligibility and applicant profile (important)

The NOFO opens eligibility to a broad set of domestic entities, including:

• Public and private higher education institutions
• Nonprofits (including and excluding 501(c)(3) status categories)
• Small businesses and other for-profits
• State, county, city, and other local or regional U.S. governments
• U.S. territories and certain federal entities, where appropriate

Critical exclusion: foreign organizations are not eligible. Foreign subawards are explicitly disallowed in this NOFO, and NIH confirms in its policy language that this mechanism is limited to domestic awardees.

If your team includes international collaborators for scientific advice, that may be possible informally, but you should not include foreign entities as funded subawards or subcontracts. In practice, the clean way to manage this is:

• Keep the administrative host organization in the U.S.
• Exclude foreign subaward budget lines under this NOFO.
• If needed, use non-funded technical collaboration paths that do not create award-linked subrecipient obligations.

Who should consider this now?

• Institutions with established community-research programs in oral health,
• Organizations already prepared for data governance and cross-site coordination,
• Teams with documented experience in coalition-style work and community partnerships,
• Applicants that can show U.S.-based legal and registration readiness before the deadline.

Who should avoid?

• Teams whose proposal is clinical-trial centered,
• Groups without current grants administration infrastructure,
• Applicants who expect to submit a simple one-lab application and call it a consortium,
• Organizations that still need to close SAM/Grants.gov/eRA registrations by late September/October 2026.

Registration and compliance requirements that can block a submission

This NOFO is specific that registration is a hard precondition for submission eligibility:

• SAM registration must be complete and active.
• eRA Commons account with valid organizational and PI/SO roles must be set.
• Grants.gov Workspace or ASSIST route should be ready before submission.
• PI(s) should have linked ORCID in their eRA Commons profile.

Reviewers and systems teams often fail on timing here. Even when the science is strong, late registration can lead to non-submission or administrative rejection. The notice states registrations can take up to six weeks or more, which means teams should start weeks before the September 19 opening date.

The NOFO also flags the standard NIH application framework obligations:

• Follow the NIH Research (R) instructions in full,
• Comply with all page limits,
• Use the required forms and sections,
• Include required plans, especially around data management and cloud/storage costs for SCHARE workspace.

Because this is a U01 cooperative agreement, it is expected that NIH has substantial post-award involvement. That is not equivalent to a directed project takeover, but it changes how you should present governance: this is partnership-oriented execution with oversight and coordination built into expectations.

Application content: what to include and why

The application should be structured around the three domains and demonstrate operational readiness. In writing terms, treat each part as a subsystem:

1) Data planning and technical assistance pathway

You need to show how your team will support data harmonization across projects, and the NOFO expects realistic implementation detail, not conceptual intent. Good sections include:

• Standard outcome definitions and recommended common measures,
• A cross-project plan for data collection quality,
• Clear workflows for missing data, inconsistent coding, and data dictionaries,
• Technical support for statistical methods for community-level and systems-level effects,
• A plan for data sharing within SCHARE.

Avoid the common mistake of describing a central warehouse without staffing, governance, and quality oversight. NIH reviewers treat this as a feasibility issue and will score accordingly.

2) Community engagement evaluation design

The NOFO repeatedly ties value to partnership quality and community-researcher relationship continuity. This means you should include:

• Evaluation frameworks and specific engagement metrics,
• A method to measure partnership quality and trust indicators,
• A process for periodic feedback from project teams and community partners,
• Explicit plans to adapt strategy based on evaluation findings,
• Capacity building approach for CEACR consultations and workforce readiness.

The grant is not only about intervention outcomes, but about how partnerships function over multiple years.

3) ADAPT consortium operations

This section should explain your governance model with precision:

• ADAPT Steering Committee structure and operating rhythm,
• Quarterly review and meeting cadence,
• Coordination mechanisms between project teams and the hub,
• Resource allocation logic (who does what, when, and with which costs),
• Dissemination plan to convert lessons into usable products/resources.

Because this is an award with one intended awardee, the hub can define the consortium logic for multiple ongoing projects. Reviewers will check whether your structure is administratively feasible and whether your team can actually run it from year one.

Budgeting expectations

The NOFO states application budgets are not pre-capped, but this does not reduce scrutiny. Applicants should align budget with actual needs in each domain:

• Operational support and coordination,
• Staffing for data planning and technical support,
• Meetings, webinars, workshops, and community interaction,
• SCHARE cloud and analytics support,
• Consultant and expert committee costs as appropriate.

Given the stated $1M intent for one award, the budget should be defensible and tightly linked to measurable deliverables.

Review process and what reviewers prioritize

The review framework is NIH-standard peer review with an added lens for this opportunity:

• Scientific significance and public-health relevance,
• Adequacy of consortium architecture,
• Methodological rigor in community-level evaluation,
• Investigator and environment readiness,
• Feasibility of operations and timeline,
• Compliance with the three-domain scope.

A critical failure mode is being too vague on operations. The review section includes specific attention to:

• Whether proposed consultation and technical assistance capacity is real,
• Whether investigator expertise covers data methods, community evaluation, and systems-level coordination,
• Whether institutional environment supports the promised operations,
• Whether collaboration governance is practical.

Because this is not a simple one-project grant, your narrative should constantly connect each claim to the consortium function. A common successful strategy is a one-page “hub operations map” showing:

• Inputs (subprojects, staff, data sources),
• Processes (harmonization, review, engagement metrics, decision pathways),
• Outputs (resources, reports, training materials, policy-relevant learning),
• Decision gates (quarterly steering checkpoints, escalation paths).

Timeline and preparation plan for teams targeting this cycle

You should back-plan from the due date:

1. Now to early August 2026: final mechanism decision, team assembly, role mapping.
2. August 2026: complete registration status checks; start SAM/eRA/Grants.gov prevalidation.
3. Late August–mid September: draft full technical sections for all three domains; design data governance and evaluation framework.
4. September 19, 2026 (open date): submission-ready draft lock.
5. By October 19, 2026, 5:00 PM local time: submit final package.
6. Post-submission: keep materials ready for corrections and NIH system validation checks.

Applicants can strengthen competitiveness by aligning internal tasks with the review phases in the NOFO:

• Before submission: strengthen governance + domain completeness,
• During peer-review prep: ensure all required forms complete and consistent,
• During decision period: prepare for compliance questions and potential additional documentation.

This timeline appears strict and it is worth planning for an internal dry-run 1–2 weeks before the due date if any piece is delegated.

Common mistakes and how to avoid them

1) Proposing only two domains

The NOFO explicitly requires activities across all three CEED domains. If your proposal neglects one, it can be non-responsive.

2) Treating this like a standard clinical grants package

This is a coordination hub for CBPR consortia, not a single hypothesis-driven biomedical intervention grant. Applications that center on one project team without a consortium infrastructure narrative are likely misaligned.

3) Underestimating registration and system setup

Missing registration readiness is the most common submission blocker. This includes SAM/Commons/Grants.gov dependencies and ORCID linkage.

4) Ignoring clinical-trial restrictions

Any proposal with a clinical trial logic is out. Non-trial human subjects work is allowed, but clinical trial design is not.

5) Weak consortium governance model

This award values operations and coordination. Reviewers penalize vague committee plans, vague communication cadences, or underdescribed decision-making pathways.

6) Underestimating data management expectations

A required DMS Plan is expected. Plan should specifically address SCHARE usage and realistic cloud costs, including storage and analytics planning.

Practical preparation checklist

Before drafting, run this internal checklist:

• Confirm domestic status and NOFO-aligned applicant eligibility,
• Verify whether your institution is already in SAM and eRA Commons,
• Confirm PI(s) ORCID linkage is in place,
• Draft three explicit subsections matching the three CEED domains,
• Document consortium-level metrics and reporting cadence,
• Build a realistic cloud/data costs section,
• Prepare evidence of prior community engagement and data planning capacity,
• Prepare an explicit one-page operational timeline for 5-year feasibility,
• Build an internal QA pass against NIH R instructions and page limits,
• Prepare contact and support paths for technical/application issues.

For institutional teams, this is not the “quickest” submission. The strongest teams treat it as a governance exercise first, then a science exercise.

FAQ

Is this suitable if my institution is outside the United States?

No. The NOFO is explicit that foreign organizations are not eligible as applicants, and foreign subawards are barred from compliant submissions.

Is this a one-time award or recurring?

The published notice is specific with current cycle dates for submission and review. Even if a broader ADAPT ecosystem has multiple related opportunities, this is one distinct NOFO tied to RFA-DE-27-001.

Can small businesses apply?

Yes. The eligible organization categories explicitly include for-profits and small businesses, but applications must still satisfy all infrastructure and consortium responsibilities.

Can this support direct treatment studies?

No. Clinical trials are not allowed under this NOFO. If your project depends on a clinical trial model, this mechanism is not appropriate.

Can I submit from an institution currently running ADAPT-related pilot work?

Potentially yes, but only if the proposal clearly fits the CEED hub responsibilities and does not replace the separate CBPR project mechanisms with an ineligible structure.

Official links and source pages

• Primary official NOFO text (direct): https://files.simpler.grants.gov/opportunities/07b5ef08-35da-4934-94a6-389b5dd4e221/attachments/1ba1e177-e590-4312-bfae-cf835a2e1550/RFA-DE-27-001-Full-Announcement.html
• NIH grants application guidance (How to Apply): https://grants.nih.gov/grants/how-to-apply
• Companion ADAPT project NOFO: https://www.grants.gov/search-results-detail/ (PAR-27-015 listing)
• eRA Commons support channel: https://era.nih.gov/
• Grants.gov support: https://www.grants.gov

Final reading

If your organization can only do one thing well with this opportunity, it is not writing a scientifically impressive narrative alone. It is demonstrating that you can run a durable, cross-project hub where data and community engagement are both designed, managed, and improved over time. The application should make NIH’s own review standards visible in every section:

• clear scope coverage,
• measurable operations,
• real capacity,
• and a practical five-year operating model for community-centered oral-health outcomes.

That is the difference between a technically decent proposal and a competitive one for this U01 call.