The Glitch

Universal Credit is now the digital ‘catch-all’ benefit for millions. While the transition to a digital-only system was sold as a way to streamline support, we frequently see how it creates new, invisible walls.

Recently, we have been supporting a client facing a barrier that is as frustrating as it is mysterious: The Perpetual Glitch.

The Innocent Request

One of the eligibility criteria for Universal Credit is proving immigration status. This is a standard part of the initial application. Imagine being a UK Citizen, holding a UK Passport, and having successfully proven your status on day one only to be asked to do it again.

And again. Every single month. For over a year.

We know of at least one person who receives a notification in their online journal demanding they prove their right to live in the UK. Every month, they are required to provide their UK passport information. While this may appear to be an isolated incident, in our experience, one ‘glitch’ is often the tip of a larger iceberg.

The Wall of “Technical Error”

When we challenged the reason for this repeated request and mentioned the anxiety it causes, the response was: “It’s a known glitch. We are working on it. We don’t have a timeline of when it will be fixed”

But in a digital-only system, a “glitch” isn’t just a line of broken code; for some it is a recurring source of trauma. For over a year, this client has lived with the monthly fear that their financial lifeline might be cut off because the “computer says no.”

When a glitch persists for twelve months, it stops feeling like an accident. It raises uncomfortable questions:

• Why does the system “forget” this specific person’s status?

• Is the algorithm behind the “glitch” truly random?

• Would this “glitch” persist for so long if the claimant had a different surname or a different skin colour?

The Burden of Proof

Whether the cause is a genuine technical error or a deeper bias in the system’s design, the result is the same: The burden of proof always falls on the individual. In a human-centred system, a caseworker would see the note, see the UK Passport on file, and “click” a button to stop the cycle. Instead, the current system is set up that the user is trapped in a loop with a ghost. The advisor on the other end might want to help, but they too are stuck by software architecture they cannot override.

Why This Matters

Digital barriers aren’t always about a lack of Wi-Fi or a broken laptop. Sometimes, the barrier is a system that refuses to “see” you correctly.

When we automate public services, we must ensure that “glitches” are treated with the same urgency as a physical office being locked. If a system causes a citizen to feel targeted or harassed every month for a year, the system isn’t just “glitchy”, it’s broken.

We have formally requested data from the DWP to find out how many others are trapped in this loop. We will share those results when we have them.