Mathematical Sciences Infrastructure Program (NSF, 2026 and 2027 target dates)

Mathematical Sciences Infrastructure Program (NSF, 2026 and 2027 target dates)

The NSF Division of Mathematical Sciences (DMS) page for the Mathematical Sciences Infrastructure Program is a broad, continuing infrastructure pathway for the U.S. mathematical sciences ecosystem. It is not a one-off challenge with a single fixed pool and one-off close, but a recurring opportunity with explicit full-proposal target dates that include 2026 and 2027. That distinction is important: this is useful both for teams planning immediate submissions and for teams planning an upcoming cycle in a few months.

The official page states that the program supports efforts that strengthen research infrastructure, enable training projects linked to the Workforce Program, and support conference/workshop/travel activities with broader impact. In practice, this is where NSF asks a simple but demanding question: are you proposing something that improves the field’s collective capacity, not just one lab’s short-term need?

Key details at a glance

What this opportunity actually funds

This program is not a narrowly bounded grant focused on one instrument type; it is best understood as a program family with three practical lanes.

1) Novel infrastructure projects

The page describes projects that strengthen research infrastructure across the mathematical sciences community, often through cross-disciplinary scope or shared resources that affect more than one institution. Reviewers are looking for something with community-level value:

• a new infrastructure model, or
• a meaningful improvement of existing infrastructure,
• with evidence that impact goes beyond the host institution.

For teams coming from a math department, data science center, or multi-institution network, this lane is relevant when the proposal can clearly explain what shared capability will remain beyond the end of the award window.

2) Training projects

The training lane is explicitly scoped as a complement to the DMS Workforce Program and focuses on trainees in mathematical sciences. The proposal must be broader than a single institution workshop and must show regional or national impact.

From a planning perspective, strong training proposals include:

• clear trainee outcomes,
• a staffing/mentoring model,
• inclusion and broadening participation pathways,
• a measurable success framework,
• sustainability of activity after grant end.

If your team is writing around workforce development, this is where they expect to see explicit alignment with participant support and evidence that participants can move from training to sustained research contribution.

3) Conference, workshop, and travel-related requests

NSF notes that conferences/workshops can qualify when they are disciplinary-span in nature or otherwise outside narrow single-discipline solicitations. On this page, the key nuance is routing:

• proposals with narrow disciplinary scope often belong in specific program solicitations,
• infrastructure program eligibility depends on fit.

The page also lists lead-time expectations when conference activity is requested:

• about 6 months for domestic events under a lower budget threshold,
• 9 months for larger domestic meeting requests,
• 12 months for international travel support.

In other words, this lane does not behave like an “anything goes” event grant—you must prove scope, timing, and routing fit.

Who this is for and who likely should not apply

The source page does not provide an all-in-one list of accepted legal-entity types in one block, so the safest interpretation is the standard NSF full-proposal logic: this is a regular NSF grant route with institutionally submitted proposals, where eligibility and PI authority are governed by NSF rules and the applicable solicitation terms.

From the public summary, the best-fit profiles are:

• institutions and teams proposing broad math-community development,
• collaborations that can show sustained regional/national benefit,
• training consortia with measurable impact design,
• event teams with demonstrable national relevance and proper lead-time planning.

Common mismatch cases are teams that propose:

• local internal workshops only,
• project scale that clearly belongs in disciplinary programs,
• ad hoc activity with no clear sustainability,
• conference-only requests where disciplinary fit is stronger elsewhere.

If the project’s real outcome is one institution’s internal convenience, this call is probably not the right lane.

Timing and submission strategy for the 2026/2027 cycle

NSF lists upcoming target dates as part of this program’s recurring cycle:

• 4 August 2026
• 2 February 2027

It is easy to treat these as “nice-to-know” dates. They are not. They are your anchor dates.

Practical cycle planning (recommended)

For a target in February 2027, practical planning should be set backward from that date:

• 10–12 weeks before target: complete a full draft with compliance language aligned to PAPPG,
• 8 weeks: secure internal approvals from research office, accounting office, and data/compliance if needed,
• 6 weeks: complete required external partner letters and any collaborator confirmations,
• 4 weeks: run section-by-section internal review focused on scope/fit/impact,
• 2 weeks: final technical and budget validation; convert all references to official NSF terminology,
• 5 business days before target: final readiness review and system upload checks.

Most applications fail at the last minute not because the idea is weak but because of portal sequencing, missing signatures, or routing errors.

NSF explicitly lists both Research.gov and Grants.gov routes. Use the route that matches your internal grant workflow and the solicitation’s routing assumptions. The page references PAPPG and NSF Grants.gov Application Guide, so your proposal integrity depends on platform compliance, not just scientific quality.

How proposals are reviewed in this lane

NSF does not publish a single rigid scoring formula on this page. What is visible is the review architecture:

• full proposals submitted close to the target date,
• section 121 style quality expectations managed under PAPPG,
• strong emphasis on breadth, impact, and evidence.

That means your proposal should be written for reviewability:

• define the program need in national/regional terms,
• show why the project is not just one institution’s internal improvement,
• tie resources to outcomes and outputs,
• quantify expected change.

A recurring scoring failure is “good science, weak structure.” Reviewers can see great technical content but still fail a proposal that does not explain how participants are selected, how the project scales, and how outcomes are measured.

What to include in your application package

Because this is a recurrent infrastructure call, strongest proposals do not rely on “nice ideas” alone. They present operational confidence.

Core proposal structure that helps reviewers

1. Problem framing in ecosystem terms

   Show that the proposal addresses a structural gap in the mathematical sciences community.

2. Impact chain

   Explicitly connect activity → output → evidence of broader impact.

3. Scale and replication model

   NSF repeatedly expects outcomes beyond the host institution. Include a clear model for transfer or community adoption.

4. Trainee design (training lane)

   Include recruitment logic, access and retention provisions, and inclusion planning.

5. Governance and staffing plan

   Explain roles and lead responsibility, especially for multi-site consortia.

6. Budget logic by activity type

   There is no one-size fixed award value in the program page; budget should be tied tightly to described activities.

7. Sustainability section

   Reviewers want signs that the capability will persist once funding ends.

Common mistakes and how to avoid them

Mistake 1: Submitting a narrow topic under this broad program

If your proposal is clearly disciplinary and not cross-cutting enough, route it to the best fit disciplinary solicitation first.

Mistake 2: Confusing conference request amounts and timing

The page gives explicit lead-time rules. If your meeting calendar is wrong or too close to target, eligibility can be rejected on timing.

Mistake 3: Treating this as an unlimited amount program

The page intentionally does not publish a universal award ceiling here. Oversized or unfocused budgets read as weak project discipline unless linked to evidence and scope.

Mistake 4: Weak fit statement

Claims of “national impact” need proof. If you say it will affect multiple institutions, you need evidence and mechanism.

Mistake 5: Late institutional dependencies

Because NSF applications are systems-heavy, internal office bottlenecks can break submission. Build internal ownership around submission dependencies 2–3 weeks ahead.

Practical fit questions before you start

Use this short pre-check before you begin a full proposal:

• Are we proposing something that improves the mathematics ecosystem, not only one campus?
• Is the impact regional or national enough to justify Infrastructure Program routing?
• Is the target submission tied to the announced target date (August 2026 or February 2027)?
• Do we have a measurable outcomes framework and sustainability path?
• Are we respecting conference lead-time rules if event support is included?
• Have we confirmed whether our activity is best in this lane versus DMS disciplinary routes?

If at least four answers are uncertain, go back to framing rather than spending proposal bandwidth.

Frequently asked questions

Is this an always-open opportunity?

It is a recurring opportunity with recurring target dates. The page is effectively a standing call with explicit upcoming dates. It is therefore useful for cycle planning rather than a one-week, single-window event.

Is there a single fixed amount?

Not on the public page. Amounts vary based on project type, scale, and proposal specifics.

Can universities submit this type of application?

Yes, this route is for full proposals submitted under NSF’s normal pathways and is commonly used by institutional teams and collaborative projects that meet the DMS routing logic.

Is this for students or scholars directly?

The page is structured around project proposals submitted through DMS with institutional leadership. Student outcomes are relevant in the training lane, but the route itself is not primarily an individual scholarship call.

What should be our deciding factor between lanes?

Use this rule:

• choose infrastructure if the project builds shared capability,
• choose training if the core deliverable is workforce development,
• choose conference/workshop only if your event scope and lead-time fit the specified cross-disciplinary/infrastructure criteria.

What happens after submission?

The page does not publish final award timelines in detail. As with most NSF programs, internal NSF review and decision cycles follow standard section-level processes after submission.

Recommended preparation for this specific 2026/27 call

For teams targeting the February 2027 lane:

1. Set target date as a policy deadline, not just an internal target.
2. Map routing early: check whether event-heavy pieces are better placed in disciplinary calls.
3. Draft impact logic for two audiences: reviewers and practitioners who may implement outcomes.
4. Add a continuity section: what remains running after the grant and who owns follow-through.
5. Do not rely on one-shot submissions: run at least one mock review with a senior colleague before uploading.

For teams targeting August 2026, the same steps apply, but with tighter preparation and an earlier proofing cycle because summer institutional closures can compress approvals.

Official links

• Official program page: https://www.nsf.gov/funding/opportunities/mathematical-sciences-infrastructure-program
• NSF PAPPG (current): https://www.nsf.gov/policies/pappg.jsp
• Research.gov: https://www.research.gov
• NSF Grants.gov application guidance: https://www.grants.gov
• Grants.gov proposal processing in Research.gov: https://www.research.gov/research-info