Skip to content

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

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 review

NSF 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.

RuleCurrent NSF answerWhat to do
SolicitationNSF 25-543Use this number in the proposal setup
Submission timingAccepted anytimeUse a target date when you want the related panel cycle
Next target datesSeptember 10, 2026 has passed; the next upcoming target date is February 4, 2027Set the internal deadline several business days earlier
Project maximumUp to $1 million and up to four yearsMatch the budget and period to the work
Typical projectAbout $150,000 to $250,000 per year for three to four yearsTreat this as context, not an entitlement
Annual spending signalNSF discourages projects above $300,000 in one yearExplain any uneven annual budget
Personnel limitTwo proposals per person in any consecutive 12 monthsCheck every PI, co-PI, and Senior/Key Person
Expected portfolio400 to 600 awards, subject to fundsDo not convert this into personal odds
Cost sharingVoluntary committed cost sharing is prohibitedDo 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.

ProgramStart here when the research contribution centers onCommon wrong-route signal
AFAlgorithms, computational complexity, and rigorous analysisThe algorithm is only an implementation detail
CIFInformation acquisition, transmission, and processing theoryThe work is mainly network deployment
CSRIntegrated software and hardware computing systemsThe request is primarily equipment
CERHow computing is taught and learnedThe project only delivers an existing curriculum
CPSCyber-physical foundations or community-inspired connected systemsThe work is a local deployment without a research question
FETFoundations for emerging computing approachesThe proposal is near-market product development
HCCPeople, interfaces, interaction, and computing systemsUser testing supports a product but not a research contribution
IIIInformation, data, knowledge, and intelligent systemsThe project only applies an existing model
NeTSNetwork architecture, protocols, and networked systemsThe request is for routine network operations
RIArtificial intelligence and intelligent systems researchThe proposal only applies an available AI service
SHFSoftware and hardware design, analysis, verification, and foundationsThe 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:

PersonRoleFuture CoRe submission dateProgramCounts in current 12-month window?
PI or senior personPI, co-PI, or Senior/KeyExact dateAcronymYes 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:

  1. Can each research aim be tied to a year, person, method, and deliverable?
  2. Does the annual budget fit NSF's stated typical range, or can the team explain why it does not?
  3. 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.

DecisionSignalNext action
Apply to Future CoReThe computing contribution and one primary program are clearConfirm personnel count, budget, title acronym, and target cycle
Ask for program fitTwo program areas remain equally plausibleSend a short scope question to the relevant NSF program contacts
Compare CICIThe work centers on security or integrity of scientific cyberinfrastructureRead the NSF CICI guide
Compare Mid-scale RI-1The request centers on research infrastructureRead the NSF Mid-scale RI-1 guide
Compare an education routeThe project delivers training rather than studying computing educationRead the NSF IGE guide and current NSF education programs
Redirect outside CISEComputing is mainly a tool for another disciplineStart with that NSF directorate or disciplinary program
StopThe work is routine operations, procurement, or commercial product developmentDo 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:

  1. Is the computing contribution central?
  2. Which of the 11 programs is the primary review home?
  3. Does every senior person pass the two-proposal rule?
  4. Does the scope fit the budget and duration?
  5. Is the next target cycle realistic?
  6. 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.

FileMinimum contentsStop signal
Contribution memoOne claim, prior-work gap, and new knowledgeDescribes only a product or use case
Program comparisonPrimary program, second choice, and scope phrasesChoice is based only on a familiar acronym
Personnel ledgerFuture CoRe dates and roles for every senior personAny person already counts on two proposals
Aim-budget mapCost and duration tied to each aimBudget starts at the maximum and works backward
Route memoFuture CoRe versus the nearest specific NSF routeA 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.

DayOutput
1One-sentence computing contribution
2Primary and secondary program-area comparison
3Personnel submission-history table
4Aim-to-budget and aim-to-year map
5Alternative-route check
6PAPPG and solicitation compliance list
7Program-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

Next steps

Future CoRe and related NSF computing programs

These next pages help you move from research into a specific grant choice.

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.