What Is Q-Day? How Close Are We and What Should You Do Before It Arrives?

The answer, up front

Q-Day is the point when a quantum computer can break today's public-key encryption. No one knows the date. In the Global Risk Institute's 2025 survey of 26 experts, the averaged estimate put the chance of that machine arriving within 10 years between 28% and 49% 1. Because migration takes years, your data's shelf life matters more than the exact date.

What Q-Day means

"Q-Day" is an informal label. Government documents use "cryptographically relevant quantum computer," or CRQC. OMB defines the concept as a quantum computer powerful enough to decrypt data protected by many common forms of cryptography and to defeat existing authentication protocols 2. OMB also states that a CRQC is not yet known to exist 2.

What the experts estimate

The Global Risk Institute and evolutionQ have surveyed experts since 2019. The 2025 edition drew 26 experts. They judged a CRQC "quite possible" within 10 years, with an averaged probability of 28% to 49%, and "likely" within 15 years, at 51% to 70% 1. Respondents chose probability bins, not exact numbers. The low end of each range counts every answer at the bottom of its bin, and the high end counts every answer at the top 1. The survey authors report that experts believe the timeline has accelerated compared with earlier editions 1.

Three cautions apply to any survey figure:

• The sample is small (26 experts).
• The figures describe opinion, not a forecast model.
• The two ends of each range depend on how the authors weight uncertain responses.

What the technical estimates show

Resource estimates show how big a machine an attacker needs. In 2019, Gidney and Ekera estimated that factoring a 2048-bit RSA integer would take about 20 million noisy qubits and eight hours. In May 2025, Gidney estimated that the job could finish in under a week with fewer than one million noisy qubits 3. That paper states its assumptions and gives an estimate, not a demonstration. Germany's BSI reaches a similar horizon by a different route. Its 2025 study gives a conservative estimate that a CRQC is likely within 15 years, and about 10 years if current qLDPC-code demonstrators perform well 10.

What governments assume

OMB writes that steady advances in the field may yield a CRQC in the coming decade 2. The UK NCSC asks organizations to finish discovery by 2028 and migrate high-priority systems by 2031 4. The EU asks Member States to secure high-risk use cases by the end of 2030 5. These dates are planning targets, not predictions of when the machine appears. They reflect how long migration takes.

Some companies plan even earlier. Cloudflare moved its own target for full post-quantum security, including authentication, to 2029, citing new research and industry developments 6.

Why the date matters less than your data

You cannot pin down Q-Day, but you can measure two things you control:

1. How long your data must stay secret. Data that must last beyond the plausible window carries risk today, because an attacker can collect it now. Harvest Now, Decrypt Later explains harvest now, decrypt later.
2. How long your migration will take. The NCSC expects large organizations to need 2 to 3 years for discovery and planning and another 2 to 3 years for early migration 4.

If your shelf life plus your migration time exceeds the years left before a CRQC, you have a gap no matter which expert estimate proves right.

What to do before Q-Day

1. Inventory your cryptography. The federal migration memo calls a dynamic, automated inventory the foundation of every migration plan 2. See Cryptographic Inventory and CBOM Guide.
2. Prioritize by data lifespan and exposure. See Harvest Now, Decrypt Later.
3. Adopt the finished NIST standards. FIPS 203 7, 204 8, and 205 9 exist now. See NIST Post-Quantum Standards Guide.
4. Build crypto-agility. OMB directs agencies to make systems cryptographically agile so they can swap algorithms with minimal disruption 2. See Crypto-Agility.
5. Set dates. Use the timelines in Global Mandates and Deadlines to set your own milestones.

What this means for executives and the board

Q-Day is a planning problem, not a prediction problem. Nobody can give your board a date, and any adviser who does is guessing. The Global Risk Institute survey shows why. It reports an averaged 28% to 49% chance of a CRQC within 10 years, and its figures describe opinion from a small sample of 26 experts, not a forecast model 1. Treat that as a signal that the risk is real and unresolved, not as a countdown.

Your leadership team owns three things that no expert survey can settle:

• Data lifespan. Your CISO and your general counsel decide which records must stay confidential for years, such as contracts, health records, source code and merger files. Data that must last past the plausible window carries risk today, because an attacker can collect it now.
• Migration lead time. Your CIO and CISO estimate how long you need to find, replace and test cryptography across every system. The NCSC expects large organizations to need 2 to 3 years for discovery and planning and another 2 to 3 years for early migration 4.
• Accountability. Regulators and customers will ask who owns the plan. Governments already set dates. The UK NCSC asks for discovery by 2028 and high-priority migration by 2031 4. The EU asks Member States to secure high-risk use cases by the end of 2030 5. Those are planning targets, not forecasts, but they show what supervisors consider a reasonable pace.

Your CFO should read the risk as a timing gap. If your data shelf life plus your migration time exceeds the years left before a CRQC, you carry exposure whichever estimate proves right. That framing lets the board fund the work without arguing about physics.

Decisions leadership must make in the next 90 days

ArcQubit guidance: keep the first 90 days small and concrete. You do not need to migrate anything yet. You need to decide who leads, what you measure and how you report.

1. Name one accountable owner. Pick an executive who reports to the board on quantum risk. Give that person authority across security, infrastructure and procurement.
2. Approve a discovery scope. Decide which systems, vendors and data stores the first cryptographic inventory covers. The federal migration memo calls a dynamic, automated inventory the foundation of every migration plan 2.
3. Set a data-lifespan rule. Ask each business unit to classify data by how long it must stay secret. Use those answers to rank systems.
4. Add quantum readiness to vendor conversations. Ask key suppliers for their post-quantum plans before your next renewal.
5. Pick your reporting rhythm. Agree what the board sees each quarter, for example inventory coverage, top-ranked exposures and named owners.

Questions to ask your team this week

Put these to your CISO, CIO and head of procurement. Weak answers tell you where to start.

1. Which of our data must stay confidential for 10 years or longer, and where does it live?
2. Do we have a current inventory of the cryptography in our applications, devices and vendor products? Who updates it?
3. How long would it take us to replace a public-key algorithm across our estate? What is that estimate based on?
4. Which of our suppliers have published a post-quantum plan? Which have declined to share one?
5. Can our systems swap algorithms without a rebuild? OMB directs agencies to make systems cryptographically agile for this reason 2.
6. Do our contracts and procurement rules ask suppliers to support the finished NIST standards, FIPS 203 7, 204 8 and 205 9?
7. Who reports on this to the board, and when did they last do it?
8. Which dates from the NCSC or EU roadmap apply to us, directly or through our customers [4]5?

What it costs to wait

ArcQubit guidance: waiting has costs even if Q-Day never arrives on a near date. We describe them qualitatively because no source supports a number.

• Data you have already exposed. An attacker can collect encrypted traffic and stored data now and decrypt it later. Every month of delay adds more data to that pile, and you cannot recall it.
• Procurement lead time. Replacing cryptography touches vendors, hardware and contracts. Suppliers with long release cycles set your pace, not your own team.
• Supplier dependence. If a key vendor moves late, your migration moves late. You learn this only if you ask early.
• Audit and customer exposure. Government targets already exist [4]5. Customers in regulated sectors may ask you to show a plan before those dates arrive.
• Compressed schedules. Discovery and planning alone can take a large organization years 4. Starting late forces rushed decisions and raises the risk of error.

How to brief your board

Use these talking points. Adjust the wording to your organization.

1. Q-Day means a quantum computer able to break today's public-key encryption. OMB states that such a machine is not yet known to exist 2.
2. Experts disagree on timing. One survey of 26 experts gave an averaged 28% to 49% chance within 10 years. It reflects opinion, not a forecast 1.
3. Governments plan around migration time, not around a date. The UK and EU set targets between 2028 and 2031 [4]5.
4. Our exposure depends on how long our data must stay secret and how long our migration takes. We are measuring both.
5. We ask the board to approve an owner, a discovery scope and a quarterly report.

Common mistakes and how to avoid them

• Waiting for a firmer date. The date will not firm up in time to help. Plan from data lifespan.
• Treating one estimate as a forecast. A resource estimate describes what a machine would need, not when anyone will build it 3. A survey describes opinion 1.
• Starting with algorithms instead of inventory. You cannot replace what you cannot find. Inventory first.
• Leaving it to one team. Security cannot migrate vendor products or business data alone. Assign executive ownership.
• Ignoring suppliers. Many of your dependencies sit outside your control. Ask early.

Owner and timeline table

ArcQubit guidance, not a regulatory requirement. Adjust the dates to your own calendar.

A worked example

Consider a generic mid-sized organization that stores customer contracts for many years. Its CISO ranks data by lifespan and finds that contract archives and design files must stay secret for well over a decade. Its CIO estimates that inventory and planning will take 2 to 3 years, in line with NCSC expectations for large organizations 4. The board sees that the archives outlast the survey's 10-year window, and that migration time adds to the gap 1. It does not need a Q-Day date to see the problem. It funds discovery, assigns an owner and asks its three largest suppliers for post-quantum plans. The result is a ranked list of exposures with named owners that the board reviews each quarter.

How ArcQubit approaches it

QuCode runs read-only scans and ingests output from scanners you already use. It produces a ranked Quantum Exposure Report with an owner for each finding. We sell it directly as fixed-scope discovery. QuTrust then turns those findings into a living migration roadmap and keeps the evidence your board and auditors will ask for.