NSF 24-586: National Quantum Virtual Laboratory - Quantum Testbeds (NQVL)

NSF 24-586: National Quantum Virtual Laboratory - Quantum Testbeds (NQVL)

The National Science Foundation has built the NQVL program as a multi-stage infrastructure path for quantum technologies that move from demonstration concepts toward practical systems. The 2024 opportunity for Quantum Science and Technology Demonstrations (QSTD) Design and Implementation asks teams to propose not just a single prototype, but an integrated development pathway that can survive through pilot, design, and operations stages.

The page currently shows a target full-proposal date in 2027 for both QSTD:Design and QSTD:Implementation pathways. That makes this one of the more strategically important NSF opportunities for groups that can show real project maturity and multi-organization execution capacity in quantum hardware, systems integration, software, sensing, or quantum applications.

Key details at a glance

This opportunity is not a standard short-duration research award. It is a staged, programmatic investment in infrastructure and implementation where progression from one phase to the next depends on prior technical milestones and reviews.

What this opportunity is really trying to fund

The official description frames the NQVL as the mechanism for translating quantum science and engineering from basic advances into use-inspired systems with economic and societal value. The funding intent is to lower barriers for end users, industry, and other sectors by creating shared, federally coordinated testbeds and demonstration pathways.

The 24-586 solicitation text highlights three important priorities:

• It is explicitly translational, not purely curiosity-driven.
• It is phased, with Design and Implementation proposals evaluated in context of prior Pilot outcomes.
• It values teams that can demonstrate coordinated systems-level planning: technical readiness, community integration, partnerships, and project governance.

A high-quality proposal under this opportunity is expected to answer not only “what is innovative?” but also “how do you move from demonstration concept to reliable operation at scale?” The strongest submissions usually do that through evidence: clear phase history, quantified technical plans, realistic cost structure, and an implementation model tied to U.S. quantum needs.

Why this matters for 2026 and 2027 applicants

For people tracking opportunity windows in 2026/2027, this call is unusually important because it has recurring due-date context and not a single fixed one-time grant cycle mindset. The page shows target dates in 2026 and 2027, indicating continuity across rounds. That is operationally meaningful for teams in the following way:

• Teams already in QSTD:Pilot can target Design if they have positive review outcomes.
• Teams building toward implementation need a credible Design pedigree, not just scientific novelty.
• Applicants who miss an early window can potentially compete in later rounds if they meet evolving technical readiness.

Unlike many grant calls where only one submission is possible, this program is designed as a pathway. That means your preparation can be phased too: secure evidence, strengthen weak dependencies, and then escalate funding requests as project maturity improves.

Eligibility: what is required before you even write section 1

NSF’s published solicitation makes three filters explicit for this program:

• Eligibility to submit is phase-dependent.
• The program is only open to organizations and teams that can manage the required Lead Organization and subaward structure.
• Stage constraints are enforced, including dependencies on prior phase recommendations.

For QSTD:Design, the proposal must tie to an existing or completed QSTD:Pilot project in the same topical area and come after a favorable recommendation from the Pilot review stage in that topic area. For QSTD:Implementation, the same rule applies one level up: approval and progress from Design must be demonstrated first.

The solicitation also sets practical limits that trip up many teams. Each Lead Organization can submit only one QSTD Design or Implementation proposal, and each PI/co-PI can appear on only one such proposal. So teams need strict internal coordination on portfolio strategy. If you have multiple strong ideas in different subtopics, you may need to delay or split efforts across cycles.

One important governance rule is not optional: a single lead organization submits the application and all collaborators or partner groups are included through subawards. Separately submitted collaborative proposals are not allowed in this structure.

No direct PI exclusion is stated in this solicitation. The posted lines indicate there are no restrictions on who may serve as PI, but submission/organizational limits still govern practical competitiveness.

Who this is best for

The opportunity rewards teams that can operate like small-scale national infrastructure programs, not one-off labs with weak integration plans.

Good fit:

• Teams with a defined quantum topic where a Pilot has delivered credible proof-of-concept progress.
• Groups that can explain how Design work will feed directly into Implementation and then operations.
• Institutions that can support multi-year management requirements, reporting cadence, and technical risk management.
• Proposals built around multi-organization collaboration with clearly allocated responsibility.

Weak fit:

• New teams with no Pilot trajectory in same topical area.
• Technical concepts lacking implementation schedule, risk posture, and transition strategy.
• Proposals that are excellent science narratives but weak on systems engineering and cost realism.
• Submissions built around endorsement letters and broad claims rather than deliverables.

This does not mean only huge universities can apply. The rule set says a Lead Organization can be any eligible entity that can carry overall management, while partners can be layered in via subawards. In practice, your risk is not who you are on paper but whether your program management and systems logic are credible at implementation scale.

Funding, award format, and review logic

The solicitation identifies the award as a cooperative agreement, which usually implies more active NSF engagement in implementation compared with some standard research grants. For NSF QSTD Design, support can be up to $2,000,000 per year for up to two years. For Implementation, support can be up to $10,000,000 per year for six years. NSF also signals a total Design budget target of up to $32,000,000 across the set of Design awards and up to six Implementation projects overall, with actual award counts depending on proposal quality and federal appropriations.

Review expectations include normal NSF merit principles and additional QSTD-specific criteria around:

• technical feasibility,
• community engagement,
• partnerships and leverage,
• management maturity,
• outcomes, and
• metrics of success.

At both Design and Implementation, the proposals are judged not only on novelty but on readiness and feasibility across the available timeline. Design proposals must include practical planning artifacts (for example, a scoped project execution plan and work breakdown structure content in the required detail) and explicit path logic for the full anticipated QSTD lifetime. Implementation proposals must show that prior design milestones, partner commitments, and acquisition readiness are sufficiently mature.

A recurring misunderstanding is treating QSTD as a single grant with two tracks. The solicitation is explicit that phase transitions are real gates. Missing a gate can end progression regardless of scientific quality.

How and where to apply (and where people most often fail)

The solicitation offers full-proposal submission through Research.gov or Grants.gov. That sounds flexible but is often a failure point because teams choose channels opportunistically and then get caught by instruction mismatches. The official instructions are:

• follow NSF Proposal & Award Policies (PAPPG) version in force for your target date,
• prepare proposals according to the specific solicitation requirements,
• ensure required sections are complete and formatted per NSF requirements, and
• do not rely on unsupported shortcuts in attachment content.

For both phases, the program sets specific content and documentation constraints:

• Letters of support or endorsement are not permitted.
• Collaboration statements are allowed only in a strict template and only for critical collaborator commitments.
• The proposal must clearly show the “what/why/how/who/readiness” structure for a concrete QSTD vision.
• Data management requirements include standard PAPPG obligations plus explicit security and proprietary information handling notes.
• You must contact the NQVL program office as early as possible, and at latest no later than two weeks before submission.

For 2027-focused planning, the current due-date landscape suggests the major full proposal target is 2027-04-06. Teams should not treat that as a single-line event. You should build milestones backward from that date: technical package finalized, budget assumptions validated, collaborator letters in approved format, internal compliance checks completed, institutional sign-off complete.

Documentation and evidence expectations for competitive proposals

In Design phase proposals, expected evidence is not just conceptual. You need material that convinces NSF of staged execution capability:

• detailed project execution plan,
• work breakdown structure and dictionary,
• project-wide budget estimate and basis,
• contingency and risk assessment methodology,
• lifecycle planning across QSTD implementation,
• resource-loaded schedule where appropriate.

For Implementation, the burden increases. NSF expects completion of enabling research and technology development for the first-generation integration route, vendor-level readiness, budget realism, and staffing readiness.

Commonly seen weak points include:

• Vague milestones that are not mapped to resource and schedule,
• missing evidence that partner commitments are substantive and documented,
• budget logic disconnected from system integration complexity,
• understating implementation risk and workforce demands.

A strong response should connect each technical claim to a testable deliverable and an accountable timeline. If you propose system-level activities, spell out where the work transitions from conceptual design to fabrication/integration and where decision gates happen.

Strategic prep checklist for the 2027 window

Treat this as a staged internal program. The following checklist reflects official constraints and avoids common disqualification triggers.

1. Confirm phase path
   • Choose whether your organization is targeting Design, Implementation, or both depending on existing Pilot/Design outcomes.
   • Verify you can cite the required favorable recommendation and phase continuity in the same topical area.
2. Lock governance
   • Decide Lead Organization and subaward partners.
   • Confirm only one proposal per Lead Organization and per PI/co-PI under this specific solicitation.
3. Build a proposal architecture that matches the required artifacts
   • PEP and WBS details for Design,
   • Implementation readiness and procurement maturity for Implementation.
4. Validate constraints before drafting final narrative
   • no voluntary cost sharing,
   • no prohibited endorsements,
   • strict letter-of-collaboration formatting.
5. Prepare evidence and compliance documents
   • COA form completion for senior/key personnel,
   • data security/proprietary management narrative,
   • broad-impact and intellectual-merit alignment.
6. Build review-ready package
   • include clear criteria mapping to technical feasibility, readiness, partnerships, management, and community impact,
   • include risks, dependencies, and alternatives if one technical path fails.
7. Final pre-submission controls
   • run institutional internal reviews,
   • test portal submission path and package completeness,
   • ensure deadline is met with enough buffer for technical corrections.

Common mistakes and how to avoid them

1) Treating this as a normal single-phase grant

The submission rules are phase-gated. If you cannot show proper continuity from Pilot/Design to Implementation, the proposal does not progress as expected.

2) Assuming more than one submission per lead organization is useful

The solicitation permits only one Design/Implementation proposal per lead organization. Multi-idea groups must prioritize early.

3) Over-relying on generic recommendation letters

Endorsements are not permitted. This is strict and can lead to return without review if you rely on unsupported narratives.

4) Weak lead/partner architecture

One lead organization must submit. If your collaboration model is unclear, NSF reviewers will read that as execution risk.

5) Ignoring PAPPG/version drift

Submission requirements can change over time. The solicitation stresses that the relevant PAPPG applies and is your responsibility.

6) Underestimating reporting and compliance intensity

This is a cooperative agreement and a systems-level program. Reviewers and program officers expect project management rigor through the project lifetime.

FAQ

Is this still relevant for 2027 even though solicitation is 2024?

Yes, the official funding page lists 2027 target dates, which indicates continuation into that window and that this is a multi-round opportunity path.

Do I need a Pilot project for Implementation?

Implementation submissions are expected to be tied to an approved Design project in the same topical area, with review outcomes supporting progression.

Are letters of support allowed?

No. The solicitation explicitly says letters of support/endorsement are not permitted. Letters of collaboration are allowed in a narrow, specific template.

What is the maximum award size?

For Design, up to $2,000,000 per year for up to two years. For Implementation, up to $10,000,000 per year for six years.

Can I submit through either Research.gov or Grants.gov?

Yes. The solicitation allows both channels, but all submission documents must match the solicitation’s instructions and NSF proposal standards.

Is there a location restriction?

The opportunity is in the United States federal system and includes NSF directorates aligned with US QISE and national science priorities.

Official links and next actions

Use the official page and solicitation links for full instructions before drafting:

• Opportunity page: https://www.nsf.gov/funding/opportunities/nqvl-nsf-national-quantum-virtual-laboratory-quantum-testbeds
• Solicitation (same program, full instructions): https://www.nsf.gov/funding/opportunities/nqvl-nsf-national-quantum-virtual-laboratory-quantum-testbeds/nsf24-586/solicitation
• Programmatic contact: [email protected]

Before submission, re-check the current version and the due-date block for your exact phase path. The 2027 opportunity window is validly present today, but deadlines in NSF systems are frequently revised in place; your own institutional grants office should confirm final date integrity before final upload.