NSF 26-1517: Electronic, Photonic, Magnetic, and Quantum Devices (EPMQD)

NSF 26-1517: Electronic, Photonic, Magnetic, and Quantum Devices (EPMQD)

The Electronic, Photonic, Magnetic, and Quantum Devices (EPMQD) opportunity, indexed as PD 26-1517 by NSF, is a high-leverage research support channel for device-level innovation in the engineering stack. The opportunity page was published 16 April 2026 and explicitly says full proposals can currently be submitted at any time, so it functions as a rolling entry point for research teams rather than a narrow campaign deadline. That makes this one unusually useful if your proposal has reached a strong technical point but your discipline window is often tightly deadline-driven elsewhere.

Unlike many themed calls with one application season and strict one-shot windows, this program is organized by a broad solicitation umbrella: if your concept aligns with EPMQD priorities and you can submit through a full NSF proposal package on Research.gov, you can continue preparing as your technical and collaboration readiness improves. That said, “ongoing” should be interpreted as “always open” only in the narrow sense of submission mechanics; competitiveness still depends on proposal quality, relevance, and how well your work advances NSF priorities at the time of review.

Key details

Why this opportunity is distinctive

EPMQD is not a challenge grant with a narrow outcome like “build one specific prototype.” It is explicitly framed as fundamental research support for device capabilities, including electronic, photonic, magnetic, and quantum platforms. The page separates the mission into multiple scientific pillars and expects work that expands device frontiers in miniaturization, integration, and practical operating robustness.

In practice, it works as a bridge between early-stage science and future system-level technology. NSF’s own text highlights a direct chain: understanding materials and structure → new device functions → advances across AI, computing, communication, healthcare, energy, and manufacturing. For applicants, this matters because your proposal should never be purely characterization for its own sake. Even when the project is exploratory, it should include a plausible path from scientific insight to device behavior with measurable improvement in performance, manufacturability, reliability, or interoperability.

The listing’s scope is broad but coherent:

• Electronic devices: semiconductor and other device classes, including design/modeling/simulation, fabrication, and scaling. They call out candidates using reduced dimensionality, quantum effects, and operation under extreme conditions.
• Photonic devices: research across light–matter interaction, optical platforms, nanophotonics, and device system integration with targets like sensing, imaging, communications, and computing.
• Magnetic/highly correlated devices: spintronics and related topological/superconducting areas, including magnetic logic/memory concepts and correlated materials.
• Quantum devices: robust, scalable systems for quantum computing, networking, and sensing, with emphasis on co-design, control/readout, and real-world operating conditions.

The breadth is broad enough for teams from materials science, electrical engineering, physics, and systems engineering, but narrow enough to demand a real device thesis and rigorous demonstration plan.

What makes an EPMQD proposal stronger

The most reliable pattern in rolling NSF submissions is to treat EPMQD like a technical mission with three layers that each needs to be explicitly documented:

1. Core scientific novelty: what new mechanism, architecture, or material interaction is being explored, and why it cannot be achieved by incremental extension.
2. Device translation logic: how that scientific novelty becomes a device-level performance increase, new function, or new operating regime.
3. Evaluation credibility: why your team’s experiments, simulations, modeling, and characterization can resolve failure modes.

NSF’s wording suggests projects using machine learning for design/optimization are acceptable, but not required. In stronger applications, ML should support design-space reduction, failure prediction, or materials-device coupling—not replace rigorous physical understanding. If your proposal is purely data-driven without mechanism-based hypotheses, reviewers can score it lower on intellectual merit.

Because this is an ENG/ECCS opportunity, teams usually need a mix of depth and feasibility. Your narrative is strongest when it includes:

• A crisp problem statement tied to one to three quantified metrics (for example, energy efficiency, switching speed, noise floor, integration density, reliability metrics).
• A defined route from concept to prototype or demonstrator, even if early stage.
• An explicit risk register: fabrication uncertainty, scalability uncertainty, thermal or radiation resilience, control/readout noise, and mitigation experiments.

The strongest proposals do not claim broad industrial impact in vague terms; they show why your architecture gives measurable advantage over alternatives. In this area, a “better and larger” claim without architecture-level trade-off is a common weakness.

Who should apply (and who should not)

This opportunity is worth targeting if you are:

• working on novel device concepts in semiconductor, photonic, magnetic, or quantum systems with material-structure-driven function;
• able to articulate a strong link between scientific mechanism and measurable device output;
• comfortable navigating NSF full proposal submission logistics through Research.gov and PAPPG 24-1;
• positioned for multi-year engineering research timelines where iteration and verification are realistic.

It is likely a poorer fit if your project is:

• a commercialized product already beyond fundamental research and validation stage,
• only policy, training, or deployment planning without device-level novelty,
• mostly service-level engineering with no clearly described materials/device mechanism,
• or lacks a PI and institutional backbone ready to manage proposal administration.

Because the full NSF route applies, be explicit early on about institutional readiness: data management, subawards, compliance sign-offs, and responsible conduct in any sensitive technology area.

Eligibility and submission specifics

The page states a few direct procedural constraints:

• Portal: use Research.gov (not currently Grants.gov) for proposal submission.
• Framework: submit as NSF 24-1, with Directorate ENG, Division ECCS, and program name selected.
• Award governance: proposals follow NSF award terms and PAPPG guidance.

Those lines are operationally critical because many teams lose time switching between portals or using stale internal defaults. For this opportunity, your pre-submission checks should include:

• whether your team’s budget templates and facilities statement match NSF assumptions;
• whether subawards (if any) are fully scoped and justified;
• whether security and export-relevant governance discussions are complete if sensitive materials or defense-adjacent work are involved.

The program explicitly notes NSF’s updated research security policies. Even if your topic is not obviously dual-use, teams should review whether their planned collaborations or equipment purchases raise additional review notes.

Eligibility at the front end for this writing remains mostly “as defined by NSF solicitation and PAPPG.” If you need a non-US institution status check, foreign collaboration policy, or citizenship constraints for PI roles, those details should be confirmed through the official guidance stack and agency emails before finalizing your team list.

Preparation strategy for a rolling deadline opportunity

A rolling window can create urgency around readiness, not around calendar. The practical playbook:

1. Draft core narrative before budget finalization. Ensure your technical narrative can stand alone with clear aims and evaluation criteria.
2. Pre-register and test your Research.gov setup. Teams lose valuable review windows over profile and compliance mismatches.
3. Create a living review map: one reviewer section each for significance, integration, feasibility, broader impacts, and execution plan.
4. Attach a materials-to-performance map. Even a short appendix table linking each task to the specific device property it improves can turn a dense proposal into a readable technical argument.
5. Run an internal red-team review. Ask a colleague to challenge your architecture assumptions and your scalability claim without telling them your preferred outcome.
6. Submit when the packet is internally coherent. Since there is no posted fixed cycle, “waiting for a better day” is often worse than submitting when you have a complete package and can revise after feedback from NSF internal or institutional review.

Given the full-proposal accepted anytime format, timing strategy differs from typical NSF cycles. You can submit earlier to test institutional readiness and then refine with future iterations only if you prepare a strong revision plan for any resubmission requirements your program office requests.

Review expectations and what reviewers typically reward

The opportunity page itself does not publish criterion scoring language, so the best method is to align with NSF principles while keeping the review lens specific:

• Technical depth with clear mechanisms: reviewers need to understand not just what device you build, but why.
• Evidence quality: simulation and experimental pathways should map to each central hypothesis.
• Integration awareness: heterogenous system context and interface constraints matter in device programs.
• Feasibility realism: milestones should show that your team can execute inside a realistic timeline.
• Potential broad impact without overpromising: NSF programs with cross-domain relevance penalize generic “this will change everything” rhetoric without hard pathways.

A proposal with high conceptual ambition but vague performance metrics often reads as incomplete science. A proposal with less hype but tightly defined objectives usually fares better.

Common mistakes to avoid

1. Treating a rolling opportunity as informal. “Ongoing” is true for deadlines, not for standards. Keep the bar full-proposal level from day one.
2. Mis-routing the submission. The page says Research.gov only for this opportunity, so using Grants.gov templates can create avoidable friction.
3. Ignoring NSF security and compliance updates. The program page explicitly references updated research security policy.
4. Overbroad device scope. Attempting to cover all electronic + photonic + quantum pathways without focus usually weakens claims. Choose one high-coherence technical route.
5. Missing the institution-level execution plan. NSF proposal review often fails teams that under-define staffing, schedule, or subaward dependency risks.
6. Publishing vague impact statements. Strong proposals should connect each broader impact claim to a realistic outreach, education, or industry transfer route.

Frequently asked questions

Is there a published deadline?

No fixed recurring date is visible in the EPMQD listing. The page states “Full proposal accepted anytime.” That is interpreted as rolling acceptance.

Is funding amount published?

The publicly visible program page does not list a single amount ceiling or standard award size. Treat this field as unknown until you confirm through the solicitation details or official pre-award contacts.

Can proposals be submitted via Grants.gov?

Not currently, according to the program listing. Use Research.gov per the official instructions.

Which funding instrument does this support?

The listing describes the program as a standard NSF award route under ENG/ECCS and ties it to PAPPG 24-1 proposal rules.

Who can I contact for clarification?

The EPMQD page lists EPMQD Program Team at [email protected].

Official links and next steps

• Official opportunity page: https://www.nsf.gov/funding/opportunities/epmqd-electronic-photonic-magnetic-quantum-devices
• Division context: https://www.nsf.gov/eng/eccs
• NSF Research.gov portal: https://www.research.gov
• NSF announcement status page (for monitoring related NSF updates): https://www.nsf.gov/funding/opportunities

For teams preparing a 2026 or 2027 submission, this opportunity is typically a good match when your research can be cast around a device-defining mechanism and a credible pathway toward integration-ready performance. The highest-value applications are the ones that sound both ambitious and execution-grounded: they show deep physics or materials insight while speaking in terms of concrete engineering results and verifiable milestones. If your team has a concept ready to move from idea to implementation now, this is one of the few NSF channels where that state of readiness is already sufficient to submit.