NSF Future CoRe (NSF 25-543): Next Dates, $1M Cap, Rules
Updated 4 official sources
Quick Answer: NSF Future CoRe (opens in a new tab) is the CISE Future Computing Research competition under NSF 25-543.
Full answer and how we checked it
It covers 11 research programs, allows up to $1 million for up to four years, and limits each PI, co-PI, or Senior/Key Person to two Future CoRe proposals in any consecutive 12-month period. The next target date is February 4, 2027, then September 9, 2027. Proposals are accepted anytime, but NSF encourages target-date submission for the corresponding panel cycle.
This guide is for computing researchers, research administrators, and sponsored-research teams deciding whether a project belongs in Future CoRe and which program should review it.
Data note: Grantsights checked the current NSF Future CoRe program page (opens in a new tab), NSF 25-543 (opens in a new tab), and the NSF PAPPG (opens in a new tab) on July 27, 2026. On October 8, 2026, the official program page listed February 4, 2027 and September 9, 2027 as the next target dates.
In this guide
- NSF Future CoRe At A Glance
- Choose The Right Future CoRe Program
- Eligibility And The Two-Proposal Rule
- Budget And Duration Check
- Apply, Redirect, Or Ask NSF
- Proposal Setup Details That Cause Avoidable Errors
- What NSF Doesn't Tell You About Future CoRe
- Four Worked Route Examples
- Five Evidence Files To Build Before Proposal Setup
- A Seven-Day Future CoRe Readiness Check
- Public Guide And The Solicitation
- Sources
- Related Grantsights Pages
The first decision is not whether your work involves computing. It is whether the central research contribution fits one of the 11 Future CoRe programs. A project that merely uses computing to study another field may belong in that field's NSF program instead.
From Manusights, our sister product
Writing an NSF proposal? Manusights offers an AI critique of your proposal against the review criteria in your solicitation: $149 for a research proposal, $49 for a GRFP or other fellowship application. Back within 3 business days of your upload.
Order a grant reviewNSF Future CoRe At A Glance
According to NSF, Future CoRe includes 11 CISE programs and anticipates 400 to 600 awards, subject to available funds. NSF also documents a $1 million project maximum, a four-year maximum period, and a two-proposal personnel limit. Those numbers describe the competition, not an applicant's likelihood of selection.
| Rule | Current NSF answer | What to do |
|---|---|---|
| Solicitation | NSF 25-543 | Use this number in the proposal setup |
| Submission timing | Accepted anytime | Use a target date when you want the related panel cycle |
| Next target dates | September 10, 2026 has passed; the next upcoming target date is February 4, 2027 | Set the internal deadline several business days earlier |
| Project maximum | Up to $1 million and up to four years | Match the budget and period to the work |
| Typical project | About $150,000 to $250,000 per year for three to four years | Treat this as context, not an entitlement |
| Annual spending signal | NSF discourages projects above $300,000 in one year | Explain any uneven annual budget |
| Personnel limit | Two proposals per person in any consecutive 12 months | Check every PI, co-PI, and Senior/Key Person |
| Expected portfolio | 400 to 600 awards, subject to funds | Do not convert this into personal odds |
| Cost sharing | Voluntary committed cost sharing is prohibited | Do not add match as a competitiveness signal |
The September and February dates are target dates, not hard closing dates. NSF says proposals are accepted anytime, but a later submission may be considered in a later review cycle.
Get research funding calls by email
About once a week, we email open research funding calls with a real deadline, from federal agencies such as NIH and NSF, picked for research institutions. One click to unsubscribe.
No spam. Unsubscribe anytime.
Choose The Right Future CoRe Program
NSF requires the proposal title to begin with the acronym for the most relevant program. If more than one program fits, the lead acronym comes first and additional acronyms follow.
| Program | Start here when the research contribution centers on | Common wrong-route signal |
|---|---|---|
| AF | Algorithms, computational complexity, and rigorous analysis | The algorithm is only an implementation detail |
| CIF | Information acquisition, transmission, and processing theory | The work is mainly network deployment |
| CSR | Integrated software and hardware computing systems | The request is primarily equipment |
| CER | How computing is taught and learned | The project only delivers an existing curriculum |
| CPS | Cyber-physical foundations or community-inspired connected systems | The work is a local deployment without a research question |
| FET | Foundations for emerging computing approaches | The proposal is near-market product development |
| HCC | People, interfaces, interaction, and computing systems | User testing supports a product but not a research contribution |
| III | Information, data, knowledge, and intelligent systems | The project only applies an existing model |
| NeTS | Network architecture, protocols, and networked systems | The request is for routine network operations |
| RI | Artificial intelligence and intelligent systems research | The proposal only applies an available AI service |
| SHF | Software and hardware design, analysis, verification, and foundations | The work is ordinary software development |
Read the individual program description inside NSF 25-543 (opens in a new tab) before choosing an acronym. A cross-program proposal is allowed, but NSF still asks for one most-relevant program first.
Based on our review of the 11 program descriptions, the decision-changing pattern is simple: topic overlap does not prove review fit. The primary acronym should identify the research community that can judge the claimed contribution, not the community that uses the finished technology. If that distinction changes the primary acronym, it should also change the framing, related work, validation plan, and program contact.
A Fast Program-Area Test
Write one sentence in this form:
This project advances [computing research contribution] for [research problem], and [program acronym] is the primary home because [scope language from that program].
If the sentence describes only an application, deployment, dataset, user group, or social benefit, the program-area choice is not ready.
Eligibility And The Two-Proposal Rule
NSF 25-543 permits proposals from qualifying U.S. institutions of higher education, qualifying U.S. nonprofit nonacademic organizations directly associated with research or education, and federally recognized Tribal Nations. The solicitation contains conditions for international branch campuses and other organizational circumstances, so the sponsored-research office should check the source before proposal setup.
According to NSF, the two-proposal rule covers every PI, co-PI, and Senior/Key Person across all 11 Future CoRe programs during any consecutive 12-month window. This is stricter than checking only the lead PI or only proposals in the same program.
There is no organization-wide proposal limit and no separate PI credential restriction in the solicitation. The binding limit is participation:
- One person may appear as PI, co-PI, or Senior/Key Personnel on no more than two Future CoRe proposals submitted within any consecutive 12-month period.
- The count runs across all 11 Future CoRe programs.
- Proposals under the replaced CISE core, CPS, and Smart and Connected Communities solicitations do not count.
- A Future CoRe proposal withdrawn before review starts, or returned without review, does not count.
- NSF says a proposal that exceeds the limit at submission will be returned without review.
Build a personnel table before adding collaborators:
| Person | Role | Future CoRe submission date | Program | Counts in current 12-month window? |
|---|---|---|---|---|
| PI or senior person | PI, co-PI, or Senior/Key | Exact date | Acronym | Yes or no |
Do not rely on a department-level recollection. Check the dates for every listed senior person.
Budget And Duration Check
The $1 million maximum is not the normal request. According to NSF, typical Future CoRe projects are about $150,000 to $250,000 per year for three to four years, and projects are discouraged from exceeding $300,000 in any single year. NSF also says the portfolio includes projects of smaller scope.
Use three tests:
- Can each research aim be tied to a year, person, method, and deliverable?
- Does the annual budget fit NSF's stated typical range, or can the team explain why it does not?
- Does the project require four years, or is the duration carrying work that belongs outside the research plan?
For example, one university in California proposing a three-year systems project at $720,000 could fit the stated pattern if its personnel, systems work, evaluation, and collaboration plan support that scope. This is a hypothetical planning example, not a funded award. A request for the full $1 million is not stronger simply because the solicitation allows it.
Apply, Redirect, Or Ask NSF
Use these seven route decisions before drafting. The common mistake is treating every computing-heavy project as a Future CoRe project, even when the central contribution is infrastructure, training delivery, commercial development, or disciplinary science.
| Decision | Signal | Next action |
|---|---|---|
| Apply to Future CoRe | The computing contribution and one primary program are clear | Confirm personnel count, budget, title acronym, and target cycle |
| Ask for program fit | Two program areas remain equally plausible | Send a short scope question to the relevant NSF program contacts |
| Compare CICI | The work centers on security or integrity of scientific cyberinfrastructure | Read the NSF CICI guide |
| Compare Mid-scale RI-1 | The request centers on research infrastructure | Read the NSF Mid-scale RI-1 guide |
| Compare an education route | The project delivers training rather than studying computing education | Read the NSF IGE guide and current NSF education programs |
| Redirect outside CISE | Computing is mainly a tool for another discipline | Start with that NSF directorate or disciplinary program |
| Stop | The work is routine operations, procurement, or commercial product development | Do not force it into Future CoRe |
The live Future CoRe grant record is the quickest route to source status and current program details.
If scientific cyberinfrastructure security is the contribution, compare the NSF CICI guide before choosing Future CoRe. If the budget is mainly for a shared research facility, use the NSF Mid-scale RI-1 guide to test the infrastructure route instead.
Proposal Setup Details That Cause Avoidable Errors
Six setup checks protect the proposal after the program-fit decision. These are separate from the intellectual merit and broader impacts arguments.
Future CoRe adds program-specific setup rules to the PAPPG:
- Begin the title with the primary program acronym, such as
CSR: Project Title. - For a separately submitted collaborative proposal, use the collaborative title format required by NSF.
- For a multi-program proposal, put the primary acronym first, followed by the other relevant acronyms.
- Submit separately submitted collaborative proposals through Research.gov.
- Use the PAPPG version in effect for the relevant target date or submission date.
- Check current research-security requirements before submission.
The program acronym is more than a label. It tells NSF which research community should receive the proposal first.
For the wider submission sequence, pair these rules with the NSF grants complete guide. A team still needs the current PAPPG, institutional approvals, senior-person documents, budget review, and Research.gov validation.
What NSF Doesn't Tell You About Future CoRe
Six applicant decisions remain after the official rules are clear. The NSF source cannot decide them without the project's abstract, team, and budget.
The official source defines the competition. It does not choose the best program for an abstract, reconcile a senior person's proposal history, or decide whether a budget matches the research plan.
Grantsights adds a public decision sequence:
- Is the computing contribution central?
- Which of the 11 programs is the primary review home?
- Does every senior person pass the two-proposal rule?
- Does the scope fit the budget and duration?
- Is the next target cycle realistic?
- Would a more specific NSF route review the work better?
If the first two answers are not clear, do not start the project description. Write the program-fit sentence or contact the relevant NSF team first.
Honest Friction: One Topic Can Point To Three Review Homes
Consider a hypothetical university team studying wildfire response with sensors, edge computing, and community partners:
- A new theory for distributed sensing may point to NeTS, CSR, or CPS.
- A community-inspired cyber-physical research question may point to the CPS community track.
- Installation of an existing sensor platform for local operations is not enough for Future CoRe by itself.
The topic is identical in all three versions. The research contribution changes the route. A polished narrative cannot repair a route whose reviewers are being asked to judge the wrong contribution.
A second hypothetical team may propose an AI tutor for introductory programming. If the research question concerns how students learn computing, CER may be the first read. If the contribution is a new learning or reasoning method in the AI system, RI or HCC may be stronger. If the work only deploys an existing tutor, the project needs a different research question or a different program.
This is what Grantsights adds to the official sources: the 11 names are not a menu of application domains. They are 11 candidate review communities. The next action changes when the team selects the community first and rewrites the contribution, evidence, and evaluation around that choice.
Four Worked Route Examples
These four examples are hypothetical. They show how the same surface topic can lead to a different Future CoRe decision.
Example 1: Hospital Scheduling Software
A university team wants to improve hospital scheduling with a new optimization method. If the contribution is a provable algorithm with new complexity or approximation results, AF may fit. If the team is primarily configuring existing optimization software for one hospital, Future CoRe is a weak fit. Health impact alone does not create a CISE research contribution.
Example 2: Secure Research Computing
A research center wants to protect a shared computing environment. New security research may fit an NSF security program, while protection of scientific cyberinfrastructure may point to CICI. Routine security upgrades are operational work. The NSF CICI guide provides a more specific comparison than a generic Future CoRe label.
Example 3: Rural Connected Transportation
One university in Montana studies connected transportation with rural communities. A new cyber-physical research contribution and ongoing community participation may point to CPS. Purchasing roadside devices and deploying an existing platform does not establish that contribution. The community role should shape the research questions, not appear only in an outreach plan.
Example 4: Computing Curriculum
A college studies how students form mental models while learning parallel programming. That may fit CER if the work generates knowledge about computing education. Offering a summer course with an existing curriculum is delivery, not automatically research. Teams seeking broader training routes should also compare the NSF IGE guide.
Five Evidence Files To Build Before Proposal Setup
Five short files expose route problems before a team invests in a full narrative.
| File | Minimum contents | Stop signal |
|---|---|---|
| Contribution memo | One claim, prior-work gap, and new knowledge | Describes only a product or use case |
| Program comparison | Primary program, second choice, and scope phrases | Choice is based only on a familiar acronym |
| Personnel ledger | Future CoRe dates and roles for every senior person | Any person already counts on two proposals |
| Aim-budget map | Cost and duration tied to each aim | Budget starts at the maximum and works backward |
| Route memo | Future CoRe versus the nearest specific NSF route | A narrower program owns the central contribution |
Based on our review, the personnel ledger and program comparison should come before the project description. They can produce a no-go or redirect decision without rewriting a 15-page proposal. The NSF grants guide can then support the broader submission and compliance sequence.
A Seven-Day Future CoRe Readiness Check
This seven-day check produces one route decision, five evidence files, and either a program-contact question or an internal go/no-go memo.
| Day | Output |
|---|---|
| 1 | One-sentence computing contribution |
| 2 | Primary and secondary program-area comparison |
| 3 | Personnel submission-history table |
| 4 | Aim-to-budget and aim-to-year map |
| 5 | Alternative-route check |
| 6 | PAPPG and solicitation compliance list |
| 7 | Program-contact question or internal go/no-go memo |
At the end of the week, the team should be able to state the contribution, primary program, personnel-limit status, budget, duration, and target cycle without qualifiers.
Public Guide And The Solicitation
The public and project-specific layers serve two different decisions. This guide gives the current rules, 11-program map, personnel-limit screen, budget context, and route choices. The NSF grant search lists the alternative programs, and the Future CoRe solicitation itself controls what a specific abstract, team roster, and budget must satisfy.
Use the public guide to decide whether Future CoRe belongs on the shortlist. Check the solicitation's requirements against the team's real abstract and personnel list before committing to the program.
Sources
- NSF Future CoRe program page (opens in a new tab)
- NSF 25-543 solicitation (opens in a new tab)
- NSF Proposal and Award Policies and Procedures Guide (opens in a new tab)
- Research.gov (opens in a new tab)
Related Grantsights Pages
Next steps
Future CoRe and related NSF computing programs
These next pages help you move from research into a specific grant choice.
Open Future CoRe record
Check NSF 25-543, September and February target dates, $1 million cap, and the two-proposal rule.
Compare CICI
Use when scientific cyberinfrastructure security may be a better review home.
Compare SaTC
Use when security or privacy research is the main route choice.
Find grants that fit you
Free eligibility check: answer 9 questions and see ranked matches with deadlines and fit reasons.
Frequently Asked Questions
What is NSF Future CoRe?
NSF Future CoRe is the CISE Future Computing Research solicitation, NSF 25-543. It covers 11 computing research programs.
What is the next NSF Future CoRe target date?
The next listed target date is February 4, 2027, followed by September 9, 2027. Proposals are accepted anytime, but NSF encourages target-date submission for the related panel cycle.
How much can an NSF Future CoRe project request?
The solicitation allows up to $1 million for up to four years. NSF says typical projects are about $150,000 to $250,000 per year for three to four years.
What is the Future CoRe proposal limit?
A person may serve as PI, co-PI, or Senior/Key Personnel on no more than two Future CoRe proposals submitted in any consecutive 12-month period.
Which organizations may apply?
Eligible lead applicants include qualifying U.S. institutions of higher education, qualifying U.S. nonprofit nonacademic research or education organizations, and federally recognized Tribal Nations. Check NSF 25-543 for the full conditions.
Last updated October 10, 2026. Corrected October 10, 2026: what changed. Published by Grantsights from public sources. See our editorial policy, how we build and check guides, corrections and how we make money.
Related Guides
Complete Guide
NSF Grants 2026: Programs, Deadlines, and PAPPG
NSF grants 2026 include 12 new research opportunities worth over $1.5 billion. Compare the October GRFP route, PAPPG rules, and proposal fit.
NSF Analysis Guide
NSF Analysis under NSF 26-520: proposals accepted anytime, a $200,000 median research award in FY2026, and the 2026 NSF rule changes PIs need to know.
NSF Archaeology Senior Research Awards Eligibility
NSF Archaeology Senior Research Awards eligibility guide for NSF 23-566, source status, anthropological value, access proof, and route choice.
NSF AAPF Guide
NSF AAPF guide: $110,000 a year for 3 years, 5-year PhD window, citizenship rule, the Aug. 15-Oct. 15, 2027 window, 10 fellows in 2026, and host rules.
NSF CEDAR Upper Atmosphere Eligibility Guide
NSF CEDAR guide: NSF 25-510 is archived. Upper-atmosphere proposals now go to GEO Core (NSF 26-516), open anytime, with 200-350 awards expected.
NSF CICI Eligibility: Cyberinfrastructure Security
NSF CICI guide: Cybersecurity Innovation for Cyberinfrastructure eligibility, four program areas, Jan. 20 deadline, budget caps, and route checks.