RFA-DA-26-055: Accelerating the Pace of Substance Use Research Using Existing Data (R01)

RFA-DA-26-055: Accelerating the Pace of Substance Use Research Using Existing Data (R01)

Key details at a glance

What this NOFO is about

This NOFO is unusual in two ways. First, its scientific scope is very broad: it explicitly covers basic, translational, clinical, and implementation research around substance use disorders, overdose prevention, and HIV-related outcomes. Second, its execution model is narrow: the funding is for teams that can do high-quality analysis on data that already exists. The program is designed to move the field faster by rewarding teams that can mine existing evidence efficiently and responsibly.

The NOFO text says the opportunity is open to applicants proposing innovative analysis of existing social science, behavioral, administrative, and neuroimaging data to study the causes and patterns of substance use and related disorders, as well as prevention, treatment, and service use. It explicitly says primary data collection is not allowed. That is the most important rule to internalize early: you should not propose data collection as the core strategy. If your study design relies on acquiring new cohorts, recruiting participants for original surveys, or field data collection, it likely does not fit this mechanism.

The framing is practical rather than aspirational. The NOFO emphasizes that large quantities of already-collected data still have untapped research potential. In a funding environment where reviewers are skeptical of “description only” papers, proposals that transform old data into new causal, comparative, or implementation-level inferences are exactly where this NOFO gets traction.

The funding is anchored by NIDA through RFA-DA-26-055 and linked to companion RFA-DA-26-056. The companion note is useful operationally: if reviewers or your institution want a lower-risk entry point or a smaller pilot path, you may want to compare both calls and decide whether your work is better as an R01 or R21.

Who should apply (and who should not)

This is one of the more open NIH opportunity designs in terms of organizational eligibility. The NOFO lists eligible organizations broadly:

• public and private higher-ed institutions,
• nonprofit entities (with and without 501(c)(3) status),
• small and non-small for-profit organizations,
• local government and some federal entities,
• Native and tribal entities,
• non-domestic foreign entities.

In practical terms, that means this NOFO is not a narrow “academic-only” call. Nonprofits, public entities, and private organizations can apply, including foreign components of eligible U.S. organizations. The PI/PD eligibility language is explicit that any qualified individual with the relevant skills, resources, and team can apply, with the usual NIH PI-level compliance steps.

Who should apply:

• Teams that already have rights and access to well-curated datasets and can justify analytical leverage,
• Groups with strong methods capacity in causal inference, longitudinal modelling, implementation science, or linked administrative records,
• Institutions with a clear compliance profile for human subjects, data security, and cyber/protocol controls,
• Applicants comfortable with NIH’s electronic submission and post-submission compliance ecosystem.

Who should reconsider applying:

• Projects that depend on new data collection,
• Teams proposing clinical trials,
• Applicants who cannot complete core registrations before submission,
• Proposals with a weak statistical plan for secondary analysis risk (e.g., unclear missing-data handling, sample framing, temporal alignment).

Core requirements: what the NOFO explicitly allows and disallows

The strongest practical advantage of this NOFO is clarity:

• Clinical trials are not allowed.
• Primary data collection is disallowed for response to this call.
• Application budgets are not mechanically capped, but must be justified.
• Maximum project period is 5 years.
• No cost sharing is required.

This is not a “small, short pilot by default” mechanism, and your budget can scale with the analytic complexity — but only when justified. NIH reviewers and grants staff will reject hand-wavy cost asks quickly, especially if they see a high administrative burden without commensurate analytic output.

Application schedule: what matters before 2027

The public key dates section gives recurring opportunities and review cycles. As of now, the active timeline remains relevant for planning through 2027: key due dates include cycles in 2025 and 2026 and continue into late 2026 and 2027. The NOFO states an expiration date of December 04, 2027. That means this is still a valid, recurring source while we are in 2026.

For planning this year, the safest near-term target is the July 17, 2026 due date (5:00 PM local time). NIH explicitly encourages early submission to allow correction cycles before the deadline because electronic submission systems can flag critical issues that need a replacement/changed submission.

In a 2026 planning context, treat this as:

• A live, currently actionable cycle,
• A recurring NIH mechanism (so if your package is not ready by one cycle, you can iterate for the next),
• A call where timing around submission systems matters as much as scientific content.

Why recurring dates matter

The table includes July and December cycles in multiple years. That indicates this is not a one-off. For applicants with a strong proposal not yet polished for the next cycle, this flexibility can be useful. But there is a practical limit: if you submit a “not ready” application and do another full rework, the resubmission rule and overlap rules apply. NIH explicitly blocks duplicate or highly overlapping applications being reviewed simultaneously.

Submission and registration: build this early

All NIH pathways require clean administrative readiness. For this NOFO, the most common blockers are procedural:

1. SAM registration (including UEI/CAGE/NCAGE context as applicable)
2. eRA Commons registration
3. Grants.gov registration and workspace access
4. Organizational profile completeness in all systems

NIH flags this process as potentially six weeks or longer. If your team misses this setup window, submission delays are unlikely to be accepted as a valid excuse for late filing.

Registration checklist

• Confirm organization has active SAM registration.
• Confirm applicant organization and PI are fully set up in eRA Commons.
• Confirm PD/PI account is attached correctly and not conflated with signing roles.
• Confirm the organization has a valid eRA Commons credential for the PD/PI and all required key personnel.
• Confirm your institution’s system-to-system submission route is functioning if you do not submit through ASSIST or Grants.gov Workspace.

Submission mechanics

NIH offers ASSIST, system-to-system submissions, and Grants.gov Workspace for this NOFO. The NOFO and current portal instructions matter. For this opportunity, paper applications are rejected.

The practical filing strategy:

• Build a full pre-check version in your chosen submission system,
• Verify the application before the due date,
• Correct and re-submit if needed before the hard deadline,
• Watch eRA Commons and submission logs carefully to ensure an on-time status.

For corrected submissions, NIH is explicit: a changed/corrected application after the due date is treated as late. So timing is critical.

What a strong application should demonstrate

Because this is a data-analytics-focused R01, reviewers weigh both scientific vision and analytic execution. A winning bid usually demonstrates:

1) Data strategy is the actual strategy

Your central claim should be that existing data are not a second-best option but the best method to answer your exact question. The NOFO’s framing is to move from untapped archival resources to actionable science. Good teams explain:

• Why the selected dataset(s) are uniquely fit for the problem,
• What causal, comparative, or temporal structure can be extracted,
• What analytic uncertainty and missingness are anticipated,
• Why the expected findings are scientifically and policy/clinical-relevant.

2) Strong implementation pathway

Reviewers expect feasible execution within the proposed timeline and budget. If your plan is too large for two or three years of data preparation plus dissemination, score quality drops quickly. Use explicit phase mapping:

• Data harmonization and governance,
• Primary analyses,
• Secondary validation and robustness checks,
• Translation into prevention/treatment/service design implications.

3) Clear prevention and treatment relevance

The NOFO language explicitly connects research to prevention, diagnosis, treatment quality, service use, and HIV intersections. Proposals that only describe technical methods without direct pathway to outcomes in these domains can look disconnected.

4) Compliance with human subjects and data policy

Even when using secondary data, human subjects governance and data protection still applies. NIH expects proper treatment of human subjects forms, data sharing plans, and cybersecurity/data security controls where relevant. If the analysis includes identifiable data, include explicit governance and safeguards.

Review criteria and what reviewers are actually reading

The review section emphasizes three core factors plus additional criteria. In plain terms:

• Significance of the question and expected field impact,
• Approach with methodological rigor,
• Investigator(s), environment, and resources.

Additional criteria then test human subjects readiness, resource authentication, animal/hazard considerations, and budget justification where relevant.

NIH often applies a “top-half discussed” selection approach, so even technically solid proposals may fail if they are not clearly competitive relative to peers. Your job is to make your relative advantage explicit:

• Explain why your dataset and design outperform generic alternatives,
• Show novelty against existing literature,
• Tie statistical power and subgroup analyses to explicit claims,
• Show reviewer-facing feasibility with milestones.

Post-review and award expectations

This opportunity follows standard NIH behavior:

• Scientific Review Group evaluation and written critique,
• Advisory-level second-level review,
• Funding decisions based on merit, budget availability, and relevance.

Given the stated committed pools, this is not high-capacity funding. Even qualified projects can miss due to budget pressure, so framing relative fit matters as much as excellence.

Applicant mistakes that most often cause rejection or avoidable delay

1. Ignoring the no-primary-data rule. Any proposal that drifts toward new recruitment, data generation, or substantial original collection is likely non-responsive.

2. Submitting as a clinical trial by implication. “Clinical Trial Not Allowed” is strict. Confirm intervention/testing language does not accidentally imply trial design unless specifically excluded and compliant with the NOFO’s constraints.

3. Late registration completion. SAM/eRA Commons and required institutional permissions must be in place before submission; this is repeatedly enforced.

4. Incorrect electronic profile fields. If PD/PI credentials are missing or mismatched, NIH systems can block successful submission.

5. Weak non-compliance controls around human subjects and DMS plans. Even secondary data projects must address all applicable data governance requirements.

6. Multiple overlapping submissions. The NOFO disallows substantial overlap across applications under review. If you plan more than one application, make each one clearly distinct.

7. Underestimating the need for early dry runs. Plan for a pre-submission rehearsal to verify on-time status. The NOFO explicitly cautions about corrected submissions and system failure windows.

Practical preparation roadmap (12-week view)

Assuming a July 17, 2026 due date:

1. Weeks 1–2: finalize dataset permissions, governance letters, and data dictionary notes.
2. Weeks 3–4: draft Specific Aims and statistical framework (focus on innovation in reuse, not merely feasibility).
3. Weeks 5–6: build a complete outline of Research Strategy with clear methods and subgroup plans.
4. Weeks 7–8: finalize registration tasks (if incomplete), create budget logic and justification narrative.
5. Weeks 9–10: prepare human subjects, data management, and compliance materials.
6. Weeks 11–12: run internal peer review, fix warnings, perform pre-submission check, and upload.

If using a large team, make the PI-led narrative explicit: who owns data wrangling, who owns causal model selection, who owns interpretation, and who owns implementation translation.

FAQ

Is this opportunity good for a team starting from scratch with only public datasets?

Yes if the team can articulate a clearly scoped, feasible analytic strategy and has clear governance for data access/use.

Can a for-profit apply?

Yes, for-profit organizations are listed among eligible applicants when they meet all other NIH and NOFO requirements.

Can non-U.S. teams apply?

Yes, non-domestic entities are eligible, including foreign components where allowed by NIH policy.

Can this be used for clinical trial analysis?

No, the NOFO is explicit that only applications not proposing clinical trials are accepted.

Is budget capped?

The NOFO does not set a fixed budget cap, but budgets must match project needs and pass scrutiny under review.

Do I need a data sharing plan?

Yes. This is expected across NIH applications and especially relevant when using existing data.

Can I submit a resubmission after a rejection?

Resubmissions are allowed where applicable; submit a corrected application if needed, with clear improvements.

Official links and monitoring points

• Official NOFO: https://grants.nih.gov/grants/guide/rfa-files/RFA-DA-26-055.html
• Companion opportunity: https://grants.nih.gov/grants/guide/rfa-files/RFA-DA-26-056.html
• NIH application and system guidance: https://grants.nih.gov/grants/how-to-apply-2/
• NIH Guide for Grants and Contracts and grants policy references linked on the NOFO.

Because this opportunity is active over a multi-cycle window through late 2027, the highest-value action is to align your proposal with a specific release cycle and submit early. Treat secondary dataset leverage as your competitive edge: if your project can clearly outperform a “standard re-analysis” and show translational relevance to prevention, treatment, or service planning, this R01 mechanism is one of the better federal options for this year’s data-driven substance use research plans.