RFA-MH-26-140: BRAIN Initiative: Brain Behavior Quantification and Synchronization- Next Generation Sensor Technology Development (U01 Clinical Trial Optional)

RFA-MH-26-140: BRAIN Initiative: Brain Behavior Quantification and Synchronization- Next Generation Sensor Technology Development (U01 Clinical Trial Optional)

RFA-MH-26-140 is an NIH BRAIN Initiative NOFO that supports a technology-development cooperative agreement in neurobehavioral sensing. The NOFO is for teams building new sensor systems and bioelectronic devices that can collect behavioral and neural data together, especially in naturalistic or complex experimental environments. This is the key distinction: this NOFO is not a clinical trial pipeline, not a biology-only study, and not just an improvement of existing tools. It is centered on what the announcement calls novel sensor technologies and device development, tied to measurable synchronization with brain recordings.

The program is active through the 2026/2027 funding cycles with a clear new-rx due-date cadence. As of the timestamped check (2026-05-31T18:23:40Z), the next near-term due date is the 2026 receipt cycle.

Key details

What this funding opportunity is designed to fund

The NOFO is highly specific in what it wants: next-generation sensors and bioelectronics that improve the quality, realism, and synchronization of behavioral and neural data collection.

From the announcement text, the expected output is not just one device that exists in isolation. The work must support the broader Brain Behavior Quantification and Synchronization goals under the NIH BRAIN initiative. That means applicants should connect technology development to actual scientific questions about behavior in real environments, and to integration with neural recordings.

The page explicitly describes desired sensor features that go far beyond “another small tweak,” including:

• minimal-power operation (low or zero power, and energy harvesting when possible),
• long-term performance reliability (including operation on the order of 48 hours or longer),
• multimodal sensing approaches where feasible,
• compact, robust design that can support natural behavior and realistic environments,
• and demonstrably novel performance compared with existing methods.

The NOFO also emphasizes dissemination and use by the broader community. There is explicit expectation for cross-lab sharing, rigorous design and validation, and work that can become useful infrastructure for the BBQS ecosystem. In practical terms, this is better aligned with teams that can build something reusable, test it in realistic settings, and communicate reproducibly enough for cross-site adaptation.

Important: the announcement explicitly states this is a consortium-oriented opportunity. Successful applicants are not expected to operate as isolated projects. The BBQS consortium model is a key part of program expectations and can influence reviewer perception because collaboration, interoperability, and standards-aligned outputs are valued.

Eligibility and fit: what makes this a “good fit”

The NOFO has broad institutional eligibility. It allows universities, nonprofits, small businesses, for-profit organizations, government entities, and certain non-domestic entities/foreign components as eligible applicants under NIH rules. That makes it unusual compared to many NIH calls that are more restricted by organizational profile.

However, broad eligibility does not mean loose eligibility in practice. A good fit usually has:

1. A clearly multidisciplinary technical team. The NOFO gives examples and expectations around combining engineering, neuroscience, computational, and behavioral expertise.
2. A direct line from device/sensor concept to measurable behavior-neural synchronization outcomes.
3. Strong implementation realism, not only “cool idea” framing.
4. A concrete plan for real-world performance and validation, including sustained operation and integration with neural recording streams.
5. Real preparedness for NIH submission systems (SAM/eRA Commons/Grants.gov registrations and documentation).

Who should likely avoid this NOFO:

• Projects that only repurpose existing devices without substantial novel development.
• Concepts that do not address behavioral quantification linked to neural data.
• Ideas built only for proof-of-concept with no path to testing beyond the lab.
• Teams that cannot show they can operate inside a cooperative-research consortium model.

One explicit note from the page is crucial for planning: applications focused on existing tools are directed toward other NOFOs, and the NOFO lists alternate RFA references for teams to consider instead.

Funding and review expectations you can prepare for

This is a U01 cooperative agreement, not a standard grant contract. In NIH terms, that means NIH program staff may have substantial involvement in stewardship post-award. It does not replace scientific leadership by investigators, but it does mean planning and governance expectations are different from purely investigator-led grants.

For this opportunity:

• The NOFO reports an estimated $10M total at each receipt date.
• It expects 6–8 awards per cycle.
• Budgets are not set with a hard cap in the announcement text.
• Project period may be up to five years.
• Applications can be new, resubmitted, or revised.

The review logic is also standard NIH-style but tuned to this program’s technical goals:

• Significance, innovation, and approach quality
• Rigor and reproducibility framing
• Feasibility of timeline and methods
• Investigator readiness, including the team’s ability to execute a technical build-research-validation loop
• Environment quality and resources
• Additional NOFO-specific expectations around low-power operation, real-time and multi-hour-plus operation, sensor integration with brain recordings, and validation for dissemination.

In this NOFO, review criteria are practical and engineering-informed: reviewers are looking for how well the proposal maps technical ambition to robust staged deliverables. A common failure mode is a concept-only narrative without hard validation milestones and fallback pathways.

Application mechanics and process you must complete

NIH gives explicit routes for submission and no ambiguity: use NIH electronic routes (ASSIST, institutional S2S, or Grants.gov Workspace) and track in eRA Commons. This is standard for NIH but the NOFO reiterates strict conformance to instructions and warns that non-compliant submissions may be delayed or not accepted.

For teams moving forward in 2026:

1. Confirm eligibility registrations early.

   • SAM active registration (including associated identifiers)
   • eRA Commons account configuration (Signing Official + PI/PD details where required)
   • Grants.gov registration and workspace readiness
   • Do not leave this for the final week. The NOFO indicates registration can take 6 weeks or more.

2. Register collaborators and define consortium strategy.

   • This NOFO expects coordinated consortium participation.
   • Plan for how your team will share protocols, datasets, and technical lessons with the BBQS network.
   • Confirm internal responsibilities for data standardization and artifact handling.

3. Build application architecture around milestones.

   • The NOFO requires proposed milestones and timeline as an attachment via other project information.
   • Milestones should be realistic by year and include measurable outcomes (for example, sensor yield, real-time performance, reliability, synchronization quality, packaging for dissemination).
   • Reviewers explicitly evaluate milestone logic.

4. Prepare a strong technical section that speaks to NOFO goals.

   • Emphasize novel sensor modality, miniaturization, power constraints, and integration with brain recordings.
   • Show reproducibility controls and failure planning.
   • Include evidence of multidisciplinary execution capability.

5. Confirm compliance sections before submission:

   • human subjects / vertebrate animals / biohazard sections if applicable,
   • resource authentication as needed,
   • budget justification for requested timeline and scope,
   • and any required forms/instructions from the NIH how-to-apply materials referenced in the NOFO.

6. Submit early.

   • The NOFO says applications are due 5:00 PM local time of the applicant organization.
   • It explicitly encourages early submission for correction windows.

Why this is practical for a 2026–2027 application cycle

This is a useful opportunity for teams whose products are at the boundary between prototype and applied behavioral neuroscience. The NOFO is especially relevant for people targeting technology translation into neuroscience pipelines, including wearable sensor systems, novel biopotential platforms, and compact data-rich modalities that can work alongside neural signals.

The cycle pattern in the source is clear:

• June 2025 cycle (applications with review and start dates in 2025/2026),
• June 2026 cycle (next realistic near-term opportunity),
• June 2027 cycle.

With an expiration date in June 2027, this is not a one-week “flash” call but a rolling multi-cycle opportunity. For practical planning in 2026, that means there is room for two strategies:

• Attempt the first open 2026 cycle with an early, feasible design.
• Use feedback-like learnings (review, internal critiques, peer feedback) to reposition for the 2027 intake if needed.

Because budgets are not hard-limited, teams can propose meaningful development pathways, but that also means reviewers and NIH staff expect spending plans to be tightly tied to deliverables and not speculative.

Consortium behavior and reviewer expectations

The NOFO repeatedly describes expected behavior inside a shared research consortium. This is not a decorative detail. It affects the whole proposal logic.

What reviewers expect to see:

• explicit collaboration model (not only names, but a real work-sharing plan),
• standard-compatible data generation and sharing strategy,
• explicit intent to align protocols and validation language with other BBQS efforts,
• and practical dissemination plans (including how your developed technology can be adopted by other labs).

This matters because the program is less about one lab “delivering a single product” and more about a distributed innovation system. A technically excellent device without clear dissemination and integration potential is weaker than a slightly less novel design that is clearly interoperable and validated with partner groups.

NIH’s language also points to expected interaction channels: annual PI meetings and regular meetings/coordination among recipients. For teams that are used to isolated grant writing, that means your project management section should include communication governance, versioning of methods, and clear responsibility for consortium interfaces.

Proposal quality framework: a practical scoring checklist

The most robust applications in this NOFO tend to do three things at once:

1. Tie novelty to user-observable scientific impact.

   • What specific neural or behavioral measurement gap does your design fill?
   • Why does this gap currently block understanding of the behavior-neural link?
   • What is the measurable scientific upside if your sensor improves this gap?

2. Tie feasibility to realistic engineering milestones.

   • Break the build into stages with deliverables and gating criteria.
   • Define what counts as “success” at each stage and what data proves it.
   • Show failure contingencies and decision points.

3. Tie dissemination to community uptake.

   • How will other groups test or adopt your platform?
   • Can outputs be standardized for comparability across studies?
   • Can your design remain “portable” across species or settings where relevant?

The NOFO’s own review language also includes standard rigor criteria: design rigor, controls, inclusion/execution feasibility, analysis plans, and statistical/scientific defensibility. Even for device-focused projects, reviewer expectation is still scientific discipline, not engineering storytelling.

Common mistakes to avoid

• Submitting overly broad aims without a hard focus on BBQS requirements.
• Failing to explain why the sensor design is genuinely next-generation versus incremental.
• Weak milestone logic, especially around long-duration operation and synchronization quality.
• Ignoring consortium expectations by omitting sharing, coordination, or interoperability planning.
• Underestimating NIH submission compliance: missing registrations, wrong route, or incomplete compliance sections.

What to prepare in the 6–12 weeks before submission

If you are targeting the 2026 cycle, build a week-by-week plan that aligns with NIH system timelines:

• Weeks 1–2: confirm registrational readiness and institutional signatory details.
• Weeks 3–4: finalize research direction and objectives around NOFO-required goals.
• Weeks 5–6: draft technical core: sensor design, synchronization pathway, milestone plan.
• Weeks 7–8: write validation/testing plan and environment/collaboration sections.
• Weeks 9–10: complete budget narrative and data management/sharing plan.
• Weeks 11–12: internal NIH-compliance sweep, internal review, and early submit for correction window.

The exact duration depends on consortium size, but teams that submit in this window are usually those with a clear project structure and less uncertainty in integration architecture.

Frequently asked questions

Is this open to non-U.S. groups?

Yes, the NOFO explicitly includes non-domestic entities and non-domestic components of U.S. organizations as eligible. You still need to satisfy NIH systems and administrative requirements through the proper channels.

Is this call suitable for clinical trials?

Clinical trials are optional. The NOFO title says this is a U01 with clinical trial optional, so proposals may include them where directly relevant, but design has to remain aligned with the sensor development priorities and consortium goals.

Can small businesses apply?

Yes. For-profit organizations, including small businesses, are listed among eligible categories.

Is there a hard budget cap?

The NOFO states application budgets are not limited, but budgets must be justified and aligned with the work. The absence of a hard cap places greater pressure on budget logic.

Are there explicit project restrictions?

Yes. Proposals with non-innovative, heavy, short-battery, hardwired, or non-synchronized designs are at high risk of non-responsiveness if they do not meet goals that are central to the BBQS program.

How often are cycles?

The listed key dates show recurring receipt dates, including June 2025, June 2026, and June 2027.

What happens after award?

The NOFO indicates normal NIH post-award reporting, including annual progress reporting obligations for multi-year awards. Data sharing requirements are tied to NIH policy and must be implemented during execution, not deferred indefinitely.

Official links and next steps

Official application surface:

• NOFO page: https://grants.nih.gov/grants/guide/rfa-files/RFA-MH-26-140.html

Related official links inside NIH ecosystem (not reproduced as additional source URLs in this page):

• NIH application guides and policy notices linked directly from the NOFO,
• eRA/ASSIST/Grants.gov instructions,
• NIH peer review and reporting references for NIH awards.

If you are planning submission in 2026/2027:

1. confirm applicant organization registration status first,
2. align your scope to at least goals 1–6 from the NOFO research scope,
3. build a feasible milestone ladder with measurable outcomes,
4. and submit before the local 5:00 PM deadline with room for corrections.

That route is currently the strongest match between administrative feasibility and scientific quality for this NOFO.