NSF 25-522: EPSCoR Research Infrastructure Improvement Program: E-RISE

NSF 25-522: EPSCoR Research Infrastructure Improvement Program: E-RISE

Key details at a glance

E-RISE is a strong fit if you need a structured federal pathway to build durable science and technology capacity at a jurisdiction level rather than a single lab project. The NSF solicitation is an active version, explicitly marked as the current one, and it is a recurring opportunity with an annually moving full proposal cycle in August. That makes it useful for teams planning for both the 2026 and 2027 windows.

What this opportunity is (and is not)

NSF 25-522 is part of the NSF EPSCoR portfolio and targets research ecosystem development, not routine project seed funding. The official text frames E-RISE as a program to improve the research capacity and competitiveness of eligible EPSCoR states, territories, and commonwealths by creating and strengthening a jurisdiction-wide network around one STEM research area. It explicitly asks for projects that can grow skills, infrastructure, and collaboration capacity and sustain activity beyond the grant period.

What the solicitation confirms:

• The program is for hypothesis-driven or problem-driven research approaches embedded in an ecosystem strategy.
• It expects clear integration with workforce development, inter-institutional collaboration, and societal impact.
• It emphasizes long-term sustainability, not a one-off pilot with no follow-through.

What it is not:

• It is not an individual fellowship, stipend-only award, or purely consumer-facing public benefit program.
• It is not a single-institution program with no partner network.
• It is not an open-ended micro-grant; it is an institutional submission with portfolio scale and reporting.

For applicants, this distinction matters because many excellent ideas are rejected early for being too narrowly framed around one department, one institution, or one artifact. The strongest proposals are usually those that show how a networked effort improves local competitiveness by combining universities, local government, and private actors where relevant.

Why this is a 2026/2027-cycle opportunity worth tracking

As of the provided date and confirmed by the solicitation, this opportunity lists a full proposal deadline pattern of August 12, 2025 and then the second Tuesday in August annually thereafter. For your planning cycle, that means the next likely submission point is in August 2026, with another in 2027. The page is marked as an active funding opportunity with a direct NSF funding-opportunity URL and a current version notice.

For a user or institution focused on practical planning, this gives a reliable cadence:

• Build consortium and internal approvals in spring.
• Use summer to finalize budgets and letters from participating partners.
• Submit in August with enough buffer for system checks.

Because NSF explicitly states recurring timing, this can be treated as both a live current cycle and a reusable planning asset for next-year opportunities.

Eligibility in detail (read this carefully)

This is a frequent area of confusion, so the eligibility section should be treated as a hard gate.

Eligible proposal leaders

The solicitation allows three broad categories:

• Institutions of higher education (PhD and non-PhD granting) with accreditation and a U.S., territory, or possession campus.
• Qualified non-profit, non-degree-granting domestic U.S. entities tied to research and education, with stable administrative capacity and 501(c)(3) status.
• Tribal governments and qualifying Indigenous communities as defined in the rules cited in the solicitation.

Regardless of the lead type, all submitters must work within an EPSCoR-eligible jurisdiction. The opportunity is not a generic national competition.

EPSCoR jurisdiction rules are central

The project must be tied to a jurisdiction that currently meets EPSCoR criteria. NSF references the eligibility criteria through official EPSCoR documentation and states that suspension of new additions/graduations is in force through FY2027 under the CHIPS and Science Act context. That means you should verify jurisdiction status before writing the full technical content.

PI and team restrictions

• Each PI must hold at least 50% appointment in an eligible organization within an EPSCoR jurisdiction.
• Each collaborating organization should have PI, co-PI, or another senior/key participant represented.
• An individual may only lead one E-RISE submission as PI/co-PI at a time unless specific exceptions apply.
• Only one lead submission per organization is allowed.

Collaboration model and partner roles

E-RISE explicitly asks for multi-institutional submissions. Collaborators outside EPSCoR jurisdictions can be included only with strong justification, and participation may be unfunded in many external contexts. This is one of the easiest places teams fail: they over-rely on non-EPSCoR institutions without proper role definition. The safer interpretation is to design partnerships where the core funded action stays in the eligible jurisdiction while leveraging outside expertise strategically.

Award size, funding shape, and award duration

From the official funding page:

• The solicitation is a continuing grant.
• NSF anticipates up to 15 awards.
• Program-level annual available funding is up to about $31.5M for new E-RISE awards.
• Each project is usually built as a four-year project with a possible renewal of three additional years.
• The requested budget per project can total up to $8,000,000 over four years.
• Renewal can be up to $4,500,000 total for three more years if performance supports it.
• Cost sharing is not expected/prohibited; voluntary committed cost sharing is prohibited.
• NSF flags that no-cost extensions are rare and exceptional.

In practical grant-planning terms, this means the solicitation is most useful when your team can show:

• A multi-year capacity plan with milestones per year.
• Clear rationale for why NSF support is needed now.
• Institutional commitment to sustain staff, shared facilities, and collaborative governance after funding cycles.

Applicants frequently lose competitiveness by treating E-RISE as one-time equipment funding. The NSF language repeatedly asks for ecosystem-level outcomes, sustainability, and workforce effects.

Proposal preparation and submission mechanics

This solicitation is straightforward in one useful way: there is no letter of intent requirement and no preliminary proposal requirement. You focus directly on the full proposal.

Practical submission details

• Full proposals may be submitted through Research.gov or Grants.gov.
• Applicants should follow the standard NSF PAPPG rules and the NSF Grants.gov Application Guide depending on submission channel.
• The solicitation is explicit that proposals submitted earlier still must meet current due-date rules and requirements.

Suggested planning sequence

For teams building an E-RISE application, the safest sequence is:

1. Confirm EPSCoR eligibility and gather formal jurisdiction evidence.
2. Confirm PI eligibility (50% appointment rule and workload fit).
3. Write a concise project concept that aligns with a single STEM topical area in your jurisdiction’s S&T plan.
4. Build a multi-institution work plan with governance, budget rationale, and workforce development outcomes.
5. Pre-draft reporting and sustainability plans before proposal budget finalization.
6. Run compliance pass with systems teams (Research.gov/Grants.gov) well before the second Tuesday in August.

The official contact line for program-specific technical questions includes NSF email and phone support; using it early can prevent late-cycle surprises when institutions have unique organizational structures.

Application strategy for institutions aiming at high-quality review outcomes

This opportunity is reviewed with NSF merit-review principles plus additional program criteria. The strongest proposals usually prove that the project can improve a jurisdiction’s research infrastructure capacity at scale.

When writing, focus on these points:

• Start with the problem the jurisdiction faces (capacity gap, workforce shortage, collaboration bottleneck, infrastructure fragility).
• Tie the proposed approach to a clearly articulated “incubator” logic: how one initiative builds a durable network and not only one deliverable.
• Show a governance design that includes campus-level coordination and mechanisms for cross-partner coordination.
• Show why your approach is not duplicative of existing NSF/EPSCoR or similar federal investments.
• Make the S&T plan alignment explicit: identify the relevant jurisdictional science and technology plan and link each objective to it.
• Provide explicit hiring/training and outcomes metrics.
• Build a conservative but believable four-year budget map with sustainability and transition steps.

Reviewers at NSF generally value clarity on who owns each component, not only innovation claims. A technically brilliant idea can underperform if governance is vague.

Common mistakes to avoid

1. Treating the effort like a normal single institution grant and underplaying the required jurisdiction-scale collaboration.
2. Forgetting the 50% PI appointment rule in eligible jurisdictions.
3. Submitting teams with weak steering roles across partner organizations.
4. Ignoring evidence of active jurisdiction governance (Steering Committee, S&T plan validity).
5. Writing around a static “project output” without a sustainability chapter.
6. Misaligning budget with the ecosystem logic and overloading personnel categories without role justification.
7. Assuming unlimited no-cost extensions or renewal certainty.
8. Using non-EPSCoR collaborators as if they were funded core operators without clear justification and role definition.

Each one of these usually appears as a recoverable issue in reviews if surfaced early. Given the complexity of multi-party governance, teams should perform at least one internal red-team pass specifically on eligibility and compliance.

Frequently asked questions

Is this open for a specific geography?

Yes, but only for eligible EPSCoR jurisdictions. You need to confirm current status before writing. The solicitation itself states that current criteria and links are maintained by NSF EPSCoR.

Can a non-university organization lead?

Yes, in certain cases. Non-degree-granting domestic U.S. organizations and some Tribal governments can be eligible under the listed conditions, but eligibility details and lead constraints apply.

Are there application rounds with a fixed annual date?

The solicitation shows a recurring cadence: second Tuesday in August annually after the first listed 2025 date. Treat each August as a new expected cycle.

Is preliminary submission needed?

No. There is no required letter of intent and no preliminary proposal step listed.

Are renewals automatic?

No. Renewal proposals are possible at year three if performance and reporting support it. They are not automatic and depend on approved progress and NSF review.

Can I submit while already holding another E-RISE or RII award?

The lead restrictions can prevent conflicts. Reviewers and officials treat PI and institutional limits strictly, so confirm role definitions before submission.

Official links and best-check checklist

Primary source:

• NSF 25-522 official solicitation

Supporting reference points for planning:

• EPSCoR criteria and eligibility references linked from the NSF page.
• NSF Proposal and Award Policies and Procedures Guide.
• NSF grants administration and system support pages through Research.gov and Grants.gov.

Before submission, validate this checklist:

1. Confirm that your jurisdiction qualifies under current EPSCoR rules.
2. Verify PI appointment percentages and active role definitions.
3. Map your budget to the four-year cap and include realistic annual spending.
4. Confirm jurisdictional governance assets (Steering Committee, S&T plan) exist and are current.
5. Use one consolidated full proposal path and avoid duplicate lead submissions.
6. Check for recurring due-date assumptions in 2026 and 2027 planning timelines.

E-RISE works best for teams that can show that this is not a one-off project but a foundation for long-term research competitiveness. That focus—capacity, collaboration, workforce development, and durable infrastructure—is exactly what the solicitation emphasizes.