← Back to the 300 Software Failures Timeline
Case Study #259 — 300 Software Failure Case Studies

UK GOV.UK Verify digital identity system failure

The UK government's flagship digital identity-verification service, meant to let citizens securely prove their identity online for government services, was shut down in 2020 after years of underperformance, having cost hundreds of millions of pounds.

2016-2020
When it happened
Government
Sector
#259 of 300
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

The UK government's flagship digital identity-verification service, meant to let citizens securely prove their identity online for government services, was shut down in 2020 after years of underperformance, having cost hundreds of millions of pounds.

Government
Sector affected
2016-2020
Date of the event
#259
Rank in the 300 Software Failure Case Studies
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

The National Audit Office found the system never achieved anywhere near its target verification success rate, as its identity-matching software struggled to reliably verify a large share of real users against commercial data sources, undermining the whole premise of the service.

01Root Cause

The National Audit Office found the system never achieved...

What Happened

The National Audit Office found the system never achieved anywhere near its target verification success rate, as its identity-matching software struggled to reliably verify a large share of real users against commercial data sources, undermining the whole premise of the service.

How Requs AI Catches This

Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.

03 — How This Gets Caught Before It Happens

Beyond code coverage and "shall" testing

Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.

Requs AI Edge Case

Surfaces this before code exists

Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.

Requs AI Software FMEA

Connects the failure mode to the hazard

Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.

Find the overlooked root causes before they ship.

Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.