NSF 25-543: Computer and Information Science and Engineering: Future Computing Research (Future CoRe)

NSF 25-543: Computer and Information Science and Engineering: Future Computing Research (Future CoRe)

If your team is building foundational work in computing, communication, or information systems and wants a federal pathway in 2026/2027, NSF 25-543 is one of the most practical NSF options. It is the current NSF CISE Future CoRe solicitation and replaces earlier versions (including NSF 24-589, NSF 24-581, and NSF 25-527). That matters because it consolidates and updates what used to be separate Core, Cyber-Physical, and connected communities tracks, while preserving a broad portfolio and opening explicit recurring annual submission windows.

The opportunity is listed as an active funding opportunity and is described as a current version, which indicates that the page is not an archive-only listing. The solicitation is not tied to one single hard deadline in the way fixed competitions are. Instead, it has target dates in September and February each year and states that proposals are accepted at any time, but encouraged to hit the target dates to align review cycles.

Key details at a glance

What this opportunity is really funding

Future CoRe is not a narrow program. It is a funding umbrella for a family of CISE programs that together cover theoretical foundations, systems, networking, AI-centered reasoning, human-computer interfaces, computing education research, cyber-physical systems, and more.

From the solicitation text, the listed Future CoRe programs include:

• Algorithmic Foundations (AF)
• Communications and Information Foundations (CIF)
• Computer Systems Research (CSR)
• Computing Education Research (CER)
• Cyber-Physical Systems Foundations and Connected Communities (CPS)
• Foundations of Emerging Technologies (FET)
• Human-Centered Computing (HCC)
• Information Integration and Informatics (III)
• Networking Technology and Systems (NeTS)
• Robust Intelligence (RI)
• Software and Hardware Foundations (SHF)

This means an applicant does not need to guess a single narrow discipline fit before writing. The program is explicitly designed for interdisciplinary ideas that span one or more of these tracks, and it allows proposals that intersect multiple areas. In practice this is useful for teams whose work includes both technical and people-facing dimensions, such as networking systems with policy-driven user behavior, AI and systems co-design, or security in socio-technical systems.

Another practical point: the program is positioned as a major NSF portfolio that expects both foundational and educational research and explicitly references broadening participation in STEM. So teams should not just propose a technical advance; they should describe the community impact path, the user groups served, and why the proposal is not just a useful prototype but a piece of future computing infrastructure and science.

Why this is relevant for 2026–2027 planning

The dates and structure are important if you are planning for the 2026/2027 cycle. The solicitation lists target dates, not one-time closure windows:

• September 11, 2025, with an annual recurrence in September
• February 5, 2026, with an annual recurrence in February

It also explicitly says proposals are accepted anytime, though only highly encouraged by target dates for panel alignment. For planning teams, this suggests two things:

1. You can spend more time on proposal quality and still be considered in the next cycle.
2. You should still treat those target dates as your internal hard stop if you want timely review.

For applicants targeting 2026–2027, this is especially useful because you can choose a target date and design your workplan backward. NSF’s cycle here rewards readiness over perfection-on-the-final-day because proposal volume and review windows are tightly integrated with these targets. Missing the target may not immediately disqualify you, but it usually makes scheduling and panel placement harder and can delay decisions.

Given the user prompt’s emphasis on upcoming cycles, this matches well: it is not a closed announcement-only call, but an annually recurring funding architecture with program-wide budget signaling.

Eligibility and strategic fit: who should apply

The solicitation is clear in eligibility categories and submission controls:

• U.S. Institutions of Higher Education (including 2- and 4-year institutions and community colleges) acting on behalf of faculty.
• U.S.-based non-profit, non-academic research organizations, including certain institutional research and educational organizations.
• Federally recognized Tribal Nations.
• There are no stated PI citizenship or discipline exclusion rules in the snippet captured, but regular NSF rules in the PAPPG and institutional eligibility must still apply.
• Importantly, each PI/co-PI has a submission cap: no more than two proposals across all Future CoRe programs in a 12-month window.

This submission limit is strictly enforced and can cause automatic return without review. Many teams are caught by this because they do not cross-check prior submissions before the call closes. If your PI is leading many proposals across departments, you need a central tracker before final sign-off.

Best-fit profiles

Strong candidates typically include:

• Faculty teams building high-ambiguity foundational systems that need 3–4 years to show sustained impact.
• Research labs where one part is deep theoretical innovation and another part is deployment in communication, hardware, or human-centered systems.
• Institutions from EPSCoR and similar contexts seeking to scale regional capacity into national relevance.
• teams that can make a clear case of broader U.S. educational and research benefit.

Good-but-not-ideal profiles

Potentially eligible but weaker fits include:

• very small exploratory ideas that resemble short pilot studies with no scalability plan,
• narrowly commercial projects that look like product development instead of research and education outcomes,
• applications that list many unrelated aims without a coherent Future CoRe program label,
• proposals that underexplain compliance with NSF standard award conditions.

Financial and program shape: what to assume in planning

The page states an estimated annual budget of $280,000,000 and an expected 400–600 awards. That is a high-level portfolio number, not a guaranteed award amount for your single proposal. What is confirmed for each proposal is the upper range and likely structure:

• maximum single-project budget: $1,000,000
• project duration max: up to 4 years
• typical annual size: around $150,000–$250,000
• no proposed single year budget should exceed $300,000
• projects discouraged above that threshold in a year

This matters for budgeting your budget narrative. Teams often over-extend in year one and then reduce the final year too late. Use year-wise phasing and keep a strong justification for each budget line. Since voluntary committed cost sharing is prohibited, avoid proposing your own mandatory match and instead strengthen cost realism via institutional commitments, existing platform reuse, and clear labor plans.

Because this is a federal solicitation, all standard NSF award administration and reporting applies. The solicitation does not expose non-standard terms on the summary page; you need to follow NSF-wide policies for compliance and award conditions.

How to apply and prepare a winning package

The application process follows standard NSF channels:

• Full proposals via Research.gov
• Full proposals via Grants.gov
• No letters of intent
• No preliminary proposal stage
• Standard NSF PAPPG compliance for the relevant due date

Since there is no preliminary step, the strongest submissions are those that are complete from the beginning. This means your package should already carry:

1. A strong intellectual merit argument mapped to one or more specific Future CoRe programs.
2. A broader impacts section with clear beneficiaries and measurable impact beyond your lab.
3. A staffing and execution plan that can support a multi-year duration.
4. A realistic budget narrative that avoids over-ambitious short-term procurement.
5. A compliance check against all required sections in the solicitation and PAPPG.

The solicitation says proposals can be submitted anytime, but NSF encourages target-date submission for review alignment. That phrase is operationally critical. If you submit early, you may still be considered in a later panel cycle, but internal scheduling can be less predictable.

Practical application timeline

Use a backward timeline:

• T - 10 weeks: finalize program track and gather all cross-track alignment evidence.
• T - 8 weeks: draft research and education plan; run budget audit.
• T - 6 weeks: secure institutional approvals and compliance attestations.
• T - 4 weeks: internal technical panel and writing review.
• T - 2 weeks: finalize all forms, data rights statements, bios, and upload package.
• T - 0: submit at least 48 hours before target date to avoid last-minute portal issues.

Even though this timeline is generic, it reflects why this call can be won: review panels reward teams that can defend technical depth, execution quality, and readiness.

What reviewers are likely to score highly

The solicitation references the National Science Board criteria, which means the classic review balance applies. In practical terms, NSF panels typically look for:

• Novelty and rigor in computing science and engineering.
• Evidence that the project advances foundational knowledge or educational outcomes.
• Technical feasibility with realistic scope and milestones.
• Team capacity and leadership.
• Broader impacts: who benefits and how the contribution scales.

For Future CoRe specifically, a frequent differentiator is how cleanly the proposal matches one of the internal program families. If your concept is interdisciplinary, explicitly state how each interdisciplinary link maps to AF, CIF, NeTS, HCC, etc. Do not rely on panel inference.

Some reviewers also respond positively when teams explicitly mention EPSCoR strategy where appropriate. NSF states that it welcomes proposals that broaden participation and notes EPSCoR engagement, including collaborative opportunities led by EPSCoR institutions.

Common mistakes that get proposals returned or weakened

This is an area where strong teams fail, often not because the research idea is weak, but because process details are missing.

Mistake 1: Treating this as a normal fixed-deadline grant

Because there are annual target dates and “proposals accepted anytime,” teams sometimes submit late into the cycle with incomplete review alignment. This is not a disqualifier by itself, but it can hurt timing and competitiveness.

Mistake 2: Ignoring the PI limit rule

Submitting more than two proposals per PI/co-PI in 12 months can lead to administrative return without review. That can waste months.

Mistake 3: Not mapping to a specific Future CoRe track

Broad interdisciplinary ideas are welcome, but they still need explicit track alignment. A proposal that says “computing” without a clear track is often scored as unfocused.

Mistake 4: Over-budgeting year one

The solicitation discourages budgets above $300,000 in a single year. Teams that overshoot can still win if justified, but this needs strong grounding in plan, milestones, and deliverables.

Mistake 5: Forgetting review-quality evidence

NSF does not reward broad claims with no validation path. Include datasets, prior artifacts, early pilot evidence, and metrics that make the proposal credible for years 1–4.

FAQ

Is this call still open as of May 2026?

The solicitation page is marked as the current version and active. It uses recurring annual target dates rather than a single one-time deadline, so the right framing is that it is ongoing by cycle.

Do I need to submit letters of intent?

No. No LOI and no preliminary proposal are required.

Can only one proposal be submitted per person?

Not exactly. The key cap is two proposals per PI/co-PI across all Future CoRe submissions in any 12-month period.

Can non-NSF researchers apply?

The solicitation defines institutional eligibility, not PI career-stage restrictions, but proposals must be submitted by eligible institutions or organizations.

Can institutions with limited budget request full NSF-scale projects immediately?

Possible, but submissions are judged by scope-quality alignment. Projects with a realistic scope and clear growth path generally perform better than oversized plans.

Where should I submit through?

Via Research.gov or Grants.gov, following the NSF PAPPG and the Grants.gov application guide depending on your routing.

What is the minimum budget if the opportunity is funded?

The solicitation does not state a hard minimum grant value. It does specify upper limits and typical size ranges, so your budget should be proportional and review-ready rather than artificially large.

Preparation checklist before submission

Use this final internal pre-submit checklist:

1. Confirm all proposal team members are within allowed proposal frequency.
2. Identify one primary Future CoRe track and optionally one supporting track for interdisciplinary work.
3. Draft a project-level narrative with measurable yearly milestones.
4. Validate that no year exceeds the discouragement threshold without strong justification.
5. Confirm no voluntary committed cost sharing is included.
6. Verify all required forms and bios are consistent with PI and institutional records.
7. Confirm submission route (Research.gov or Grants.gov) and package integrity before upload.
8. Prepare reviewer-facing summary points with evidence in first one-two paragraphs.

This checklist exists to reduce non-substantive rejection risks. In NSF-funded programs, these risks often consume more team energy than technical risk.

Why this opportunity may be stronger than it appears

Future CoRe sits in a useful middle ground. It is broad enough to include many research directions but structured enough to still require discipline. Because it consolidates multiple CISE tracks and has recurring target dates, it behaves more like a platform than a one-off competition. If your project is in serious need of multi-year continuity and review-cycle predictability, this is one of the most relevant NSF routes in the computing stack.

The opportunity also tends to attract high-quality proposals from teams that align technical novelty with implementation maturity. The annual budget and broad award count signal that NSF expects a portfolio, not only a handful of flagship stars. That creates a practical entry point for institutions that may not be mega-center sized but can still demonstrate excellence and scaling readiness.

The practical implication for 2026/2027 is simple: treat this as a recurring, strategic submission track. Use one strong target date, submit once with a complete package, and maintain continuity into the next cycle if needed.

Official resources

• Official solicitation (current): https://www.nsf.gov/funding/opportunities/future-core-computer-information-science-engineering-future-computing/nsf25-543/solicitation
• Program landing page: https://www.nsf.gov/funding/opportunities/future-core-computer-information-science-engineering-future-computing
• Proposal policies: https://www.nsf.gov/publications/pub_summ.jsp?ods_key=pappg
• NSF Grants.gov guide (NSF route): https://www.nsf.gov/publications/pub_summ.jsp?ods_key=grantsgovguide