UK Passport Agency 1999 computer system rollout crisis
A new UK Passport Agency computer system caused massive processing delays, leaving hundreds of thousands of applicants without passports for weeks during the summer travel season.
The damage was public. The root cause was preventable.
A new UK Passport Agency computer system caused massive processing delays, leaving hundreds of thousands of applicants without passports for weeks during the summer travel season.
What the software actually got wrong
The National Audit Office found the new system was rolled out to two large processing offices before it, and the staff using it, were fully ready, and productivity per clerk dropped sharply as workers struggled with the unfamiliar software, creating a backlog the agency could not clear for months.
The National Audit Office found the new system was...
The National Audit Office found the new system was rolled out to two large processing offices before it
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.
The staff using it, were fully ready
the staff using it, were fully ready
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Productivity per clerk dropped sharply as workers struggled with...
productivity per clerk dropped sharply as workers struggled with the unfamiliar software, creating a backlog the agency could not clear for months
Requs AI Edge Case and Software FMEA together treat this as a known, catalogued defect pattern — not a novel surprise — so it gets tested for deliberately rather than discovered after deployment.
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.
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.
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.