ARPA-E Grants and SBIR/STTR 2025: Your Practical Guide to MAGNITO, ROCKS, QC3, GLASING, SCALEUP, SPARKS and More (SPARKS Awards up to $500K)

ARPA-E Grants and SBIR/STTR 2025: Your Practical Guide to MAGNITO, ROCKS, QC3, GLASING, SCALEUP, SPARKS and More (SPARKS Awards up to $500K)

If you are trying to figure out whether ARPA-E is worth your time, this guide is written for that moment.

ARPA-E’s catalog in 2025 is not one program with one set of expectations. It is a cluster of programs with different goals, different deliverables, and different ways of judging success.

This page is a practical decision map for six named opportunities connected to that period:

• MAGNITO (DE-FOA-0003590)
• ROCKS (DE-FOA-0003592)
• QC3 (DE-FOA-0003482)
• GLASING (DE-FOA-0003488)
• SCALEUP Ready (DE-FOA-0003467)
• SPARKS (DE-FOA-0003164)

The best way to use ARPA-E is to treat each NOFO as a separate grant conversation with your team, not as one big pile of programs. The team’s best outcome is often choosing one path early and refusing to split effort across all of them.

At a glance

Use these dates as a signal of what ARPA-E published, not as legal certainty for your submission window. Every NOFO can post changes in updates, and some deadlines can move.

What this page solves

Most teams that fail at ARPA-E submissions do so for the same reasons:

• They apply broadly and spread themselves thin across several NOFOs.
• They overpromise technical maturity.
• They treat application formatting like paperwork rather than a technical test of readiness.
• They assume one ARPA-E track can be “just repurposed” for the next.

If you want a practical answer to whether to apply, ask this first:

• Do we understand the problem statement in this NOFO as clearly as we understand our own lab or company’s constraints?
• Can we show a path from current capability to a measurable deliverable inside the funded window?
• Do we have all required administrative setup in place (portal registration, organizational signatures, budget signoff, collaboration letters) before writing final copy?

If the answer is weak on any two of these, you should pause and strengthen before drafting.

What each program actually expects, in normal language

The titles alone are not enough. Below is the practical interpretation from the official NOFO summaries.

MAGNITO: hard science with clear performance uplift

MAGNITO is not a “materials exploration” program with fuzzy goals. The NOFO describes a very specific bar:

• discover and characterize magnets with stronger properties than known materials in either saturation magnetization or energy product;
• combine computational prediction, synthesis, and characterization;
• show that your team can move beyond just screening toward proof that a class of candidates is physically better.

Practical implication for teams:

• You need both materials-science depth and computational capability.
• If you only have one of those and no partnership pipeline for the other, expect delays and weak review comments.
• You need to propose an experiment design that reduces uncertainty quickly (not just lists a long research list).

ROCKS: mining and critical minerals with measurable characterization gains

ROCKS is about faster, more informative resource characterization in critical-mineral contexts.

The NOFO language emphasizes:

• penetration and recovery in drilling,
• better sensing/analysis chains,
• and disruptive methods that materially improve how ore characteristics are inferred for hard-rock and other resource settings.

Practical implication for teams:

• field credibility matters even if work starts in the lab;
• your signal-processing and sampling assumptions need to match how reviewers expect real deposits to behave;
• partnership and teaming readiness (industry or geology domain support) matter early.

The ROCKS listing also includes a teaming partner list setup, which indicates practical team-formation value for this area.

QC3: quantum advantage or proven path to scalable advantage

QC3 is explicit about a hard performance goal: scalable quantum methods that beat classical capability by substantial margins on energy-relevant chemistry or materials problems.

The NOFO text calls for:

• clear target problem where classical methods are insufficient;
• algorithm-to-hardware integration across the stack;
• validation against classical and experimental baselines;
• explicit scalability and hardware resource planning.

Practical implication for teams:

• you must pick a real problem where quantum methods can plausibly dominate, not just “quantum for quantum’s sake”;
• claims of 100x improvement require a validation plan that is technically credible at your stage.

A team that treats the NOFO as a “future-proofing science grant” instead of a strict algorithm-to-impact program usually gets a weak fit reading from reviewers.

GLASING: high-performance windows with manufacturing realism

GLASING is a concrete product-outcome challenge:

• improve thermal performance in Insulated Glass Units (IGUs), with target thermal benchmark above legacy standards;
• move beyond material novelty to manufacturing scalability and durability.

The official summary includes these practical targets:

• 0.6 m × 0.6 m IGU prototypes,
• whole-window thermal targets above the conventional low-e/argon baseline,
• third-party thermal/optical/durability testing.

Practical implication for teams:

• prototypes must be framed as manufacturable units, not lab curiosities;
• you need testing and reliability strategy, not just materials science narrative;
• optics, optics-haze, edge sealing, vacuum stability, and process consistency are likely as important as material novelty.

SCALEUP Ready: the “what to do after early-stage success” program

SCALEUP Ready is the correctional lane for projects that were previously funded and then need scale-up support to show reliability and commercial potential.

From the NOFO summary:

• it targets technologies that already had prior ARPA-E progress,
• it emphasizes pre-pilot scale-up,
• it seeks evidence on manufacturability, integration, performance retention, and cost/quality trajectory.

Practical implication for teams:

• this is typically not the right landing spot for first-time discovery-only teams;
• strong evidence of prior progress is expected,
• the submission should show path-dependent scale barriers and a clear plan to reduce them.

SPARKS: small, fast, exploratory, and bounded

SPARKS is broad on topic but narrow on size and speed:

• single-phase projects,
• durations around 18 months or less,
• total project cost of $500,000 or less,
• concepts not covered by an open focused FOA and not incremental.

Practical implication for teams:

• this can be a good entry point only if your idea is genuinely new and outside an existing focused call;
• because the 2026 record shows this FOA closed on 4/28/2026, this current cycle is not a live submission route there.

Who this page is for

This page is for:

• principal investigators and founders who can already show evidence of technical capability;
• teams with at least one collaborator who understands commercialization constraints (or is committed to adding one);
• teams deciding whether to invest in full proposal preparation.

It is probably not useful for teams still at problem-framing stage with no domain or execution commitment.

Who is the best candidate for each route

Strong grant NOFO route candidates

• University, lab, or mixed teams with rigorous technical depth and access to required facilities.
• teams with a clearly bounded research question and measurable milestones.
• teams that can tolerate a potentially high-risk technical path with a well-defined risk management plan.

Strong SBIR/STTR candidates

• small businesses with a plausible commercialization pathway and market need.
• teams with early customer understanding, partnering strategy, and post-award commercialization plan.
• teams that can propose near-term commercialization and technical milestones together.

Good candidates for all NOFO types (with different writeups)

• teams with strong cross-functional collaboration where one team owns the science and one owns integration/commercialization.
• teams that already have access to test infrastructure or secure it before proposal submission.

Teams that should probably skip now

• teams without access to critical resources (compute, fabrication, mineral field access, glass-matrix testing, or quantum hardware access as relevant);
• teams with only a broad idea and no problem-specific benchmark target;
• teams waiting on missing registrations, approvals, and signatures to do late-stage assembly.

Eligibility and compliance checks before writing

Before drafting anything, complete this checklist:

• Organization type and route: grant NOFO vs SBIR/STTR distinction must be real, not just a naming preference.
• Date windows: confirm current CP/FA dates and any “open until replaced” language directly on each NOFO.
• U.S. presence expectations and eligible entity constraints from each NOFO’s application materials.
• Registration and legal prerequisites (institutional signoff, portal access, any required profiles and registrations).
• Required attachments: technical volume, budget worksheets, forms, public summary, assurance/disclosure pages.
• Contact channels: keep [email protected] for portal, [email protected] for FOA questions.

Do this once, upfront. It prevents 90% of unforced rejection risk.

Route decision: which program should be your first target?

Do not write six proposals and submit none.

Use this triage:

1. Pick one technical anchor from your team’s strongest domain.
2. Map that anchor to program objectives.
3. Verify that objective is still open and currently relevant.
4. Confirm internal capacity to deliver evidence by full proposal date.
5. Draft only for the top fit.
6. Expand to secondary routes only after draft quality and proof points are stable.

Route decision pattern

Practical application process

1) Start with the official NOFO and latest documents

Open the official NOFO pages and read:

• Program objective and exclusions
• Definitions of concept paper and full application stages
• Required forms and submission process
• Evaluation criteria and selection format

Do not rely on third-party summaries for your core checklist.

2) Pick CP-first vs full-application-first strategy

For programs with concept paper stages, use CP as a technical pre-check:

• validate terminology,
• test your main claim,
• collect early critique points,
• prepare for expansion in full application with tighter milestones.

Programs without CP (or where full application is the operative first submission) need earlier internal synchronization of budget and compliance.

3) Build your proposal from outcomes backward

Start with this structure:

• problem statement in one paragraph,
• measurable target and test method,
• why existing methods fail,
• what your team contributes differently,
• where failure is expected and what you will do when it happens.

Every paragraph should point to one measurable proof point.

4) Prepare materials in this order

1. Technical scope and milestones (not abstract background)
2. Validation plan and evidence architecture
3. Budget and work breakdown
4. Compliance attachment package
5. Public summary and commercialization narrative if needed
6. final formatting and portal dry run

5) Build and test your non-specialist summary

ARPA-E review has technical depth, but your summary should still be readable by an evaluator who scans quickly. Ask two people not in your lab domain to explain your summary back to you. If they can repeat the objective and success condition in one minute, you are closer to passable clarity.

6) Build an internal pre-submission QA pass

Run a full review at T-2 weeks:

• deadline and time-zone check,
• all forms and attachments present,
• signatures and permissions,
• budget and role clarity,
• final page limits respected.

Submit before your final internal buffer in case of portal or compliance surprises.

Required package checklist

Technical plan (most important)

• Problem statement and specific objective.
• Exact metric and target threshold.
• Milestone chart by quarter or month.
• Clear failure criteria and alternate approaches.

Budget and administration

• Labor and subcontracting assumptions,
• equipment/testing costs,
• travel only when justified by technical need,
• budget justification tied to milestones.

Evidence and collaboration documents

• collaborator commitments with scope and time windows,
• facility access letters (instrument time, field windows, fabrication/compute bookings),
• commercialization support letters only where needed.

Public-facing summary

ARPA-E often asks for accessible summaries. Make sure it can stand without jargon.

For SPARKS-style/SMALLER routes

• keep the concept compact,
• avoid oversized scope,
• show why your concept is outside existing active focused FOAs.

10-step readiness checklist (use before submission)

1. Can we name the NOFO objective in one sentence?
2. Is the target metric measurable with clear units?
3. Can we show why this path is likely better than alternatives?
4. Are all roles, facilities, and dependencies assigned?
5. Is the budget defensible and aligned to milestones?
6. Are concept paper and full application requirements both satisfied?
7. Does our team have evidence-generation access before kickoff?
8. Are we not claiming outcomes that depend on infrastructure beyond our control?
9. Are all administrative and compliance steps complete?
10. Do we have a backup scope if a key collaborator drops?

If more than two items are “not yet,” pause writing and fill gaps before adding pages.

Common mistakes (and how to avoid them)

• Mistake: treating all programs as one broad “ARPA-E track.”

  • Fix: pick one NOFO and force every sentence to support that objective.

• Mistake: overpromising technology impact without clear measurement.

  • Fix: replace every claim with a number, a test, and a date.

• Mistake: forgetting that SPARKS-like and other small routes still need full rigor.

  • Fix: keep scope small, but keep evidence plan strict.

• Mistake: last-minute compliance catch-up.

  • Fix: complete portal account and attachment structure before writing final pages.

• Mistake: missing the “not covered by active focused FOA” constraint.

  • Fix: explicitly mention why your idea sits outside active topic-specific calls.

• Mistake: assuming prior ARPA-E success automatically grants fit for SCALEUP Ready.

  • Fix: show specific scale, cost, reliability, and integration risks you will reduce.

Program-specific caveats you should track before submission

• MAGNITO and ROCKS are technically demanding and reward teams with real team diversity across simulation, experiments, and analysis.
• QC3 requires a credible hardware-aware plan, even if full quantum scale is not yet possible.
• GLASING rewards manufacturability realism; prototype demonstration pathways matter as much as peak material performance.
• SCALEUP Ready works only if you are demonstrably in the “pre-commercial scaling” lane.
• SPARKS (as shown in current listing) has moved from active to closed in the retrieved record; verify if a reissued version exists before planning.

FAQ

Are these programs only for universities?

No. Several are open to small businesses via SBIR/STTR companion routes, while others have grant routes for broader organizations. Route by eligibility, not by sector.

Is SPARKS currently open?

The record I checked shows DE-FOA-0003164 as closed effective 4/28/2026 and “single-phase, up to $500,000” in the archived line item. Check current catalog or any replacement FOA for an updated status.

Do I need a non-incremental idea?

For SPARKS, yes: it is intended for concepts not covered by active focused FOAs and not incremental improvements. For the focused NOFOs (MAGNITO, ROCKS, QC3, GLASING), incrementality is assessed against their specific stated goals and expected novelty.

Can MAGNITO and ROCKS both fit my team?

Possibly, but not as two parallel full submissions from one team without distinct technical framing. It is usually better to pick one as primary and leave secondary concepts for future cycles.

Can one proposal support both grant and SBIR/STTR?

You should avoid duplicative cross-route submissions of the same concept unless each has genuine, separated objectives and compliance routes. Mixing routes confuses review narrative.

Where should I check the most current details?

Directly on ARPA-E eXCHANGE and the specific NOFO pages linked below. The “official page” is the source for current dates, attachment updates, and status.

How do I reduce rejection risk quickly?

Do three things: one metric per objective, one schedule per milestone, one partner commitment per external dependency.

Official links and current references

• Main verified index used for this page: DE-FOA-0003590 (MAGNITO)
• ROCKS listing: DE-FOA-0003592
• QC3 listing: DE-FOA-0003482
• GLASING listing: DE-FOA-0003488
• SCALEUP Ready listing: DE-FOA-0003467
• SPARKS listing: DE-FOA-0003164
• ARPA-E main exchange hub: ARPA-E Funding Opportunities

If these links change after you read this page, follow the “official links” and then reopen the latest NOFO PDFs and attachments before writing the final draft.

Next steps

1. Open the NOFO page for your top-fit program.
2. Confirm the current NOFO/FOA status and dates.
3. Build a 1-page “fit + milestones + evidence” brief.
4. Use that brief as the first chapter of your concept paper or full application.
5. Prepare the compliance package in parallel with technical writing, not afterward.