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

UK National Insurance Recording System (NIRS2) failure

A major upgrade to the UK's National Insurance records system, run by a private contractor, ran years late and caused widespread delays and errors in state pension and benefit payments.

1997-2001
When it happened
Government
Sector
#253 of 300
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

A major upgrade to the UK's National Insurance records system, run by a private contractor, ran years late and caused widespread delays and errors in state pension and benefit payments.

Government
Sector affected
1997-2001
Date of the event
#253
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 new software was not properly tested against the full complexity and volume of the UK's national insurance records before going live, leading to processing backlogs and incorrect records that took years to fully resolve.

01Root Cause

The National Audit Office found the new software was...

What Happened

The National Audit Office found the new software was not properly tested against the full complexity and volume of the UK's national insurance records before going live, leading to processing backlogs and incorrect records that took years to fully resolve.

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.