ID.me facial-recognition verification failures for US unemployment claims
Facial-recognition identity verification required by several US states and the IRS to access unemployment benefits or tax accounts caused major access problems and long delays for many legitimate claimants.
The damage was public. The root cause was preventable.
Facial-recognition identity verification required by several US states and the IRS to access unemployment benefits or tax accounts caused major access problems and long delays for many legitimate claimants.
What the software actually got wrong
The facial-matching software had documented higher error rates for people with darker skin, older adults, and other groups, and the system's account-recovery process for people it failed to verify was itself slow and understaffed, leaving eligible claimants locked out of benefits for extended periods.
The facial-matching software had documented higher error rates for...
The facial-matching software had documented higher error rates for people with darker skin, older adults
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.
Other groups
other groups
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.
The system's account-recovery process for people it failed to...
the system's account-recovery process for people it failed to verify was itself slow and understaffed, leaving eligible claimants locked out of benefits for extended periods
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.