Why does digital identity exclusion persist even after large enrolment programmes?

Why enrolment does not equal inclusion

Large enrolment programmes often measure coverage, not usable access. The gap appears when the system assumes the person will always have the same device, phone number, card, or credential available. That assumption fails in real life, especially for low-income users, migrant populations, older adults, people with unstable housing, and anyone whose access path changes after enrolment.

Identity systems also tend to optimise the first login journey more than the recovery journey. If the design cannot handle lost devices, expired credentials, SIM changes, or failed biometrics, the programme can still create a verified population that remains effectively locked out of services.

Enrolment volume is therefore a weak success metric on its own. A programme can be technically impressive and still exclude people when the operating model does not provide a durable, human-safe path back into the account.

Where exclusion is created after enrolment

The most common failure point is recovery. If reset and fallback paths are too weak, too manual, or too heavily dependent on one channel, the user is stranded when that channel breaks. Recovery needs to be as intentional as enrolment, because it is the mechanism that turns an identity record into repeatable access.

Consent and alternate verification also matter. Some systems require a smartphone, a persistent email address, a live biometric match, or a trusted third party even when those options are not available. The result is a brittle access model that privileges the most connected users and quietly excludes everyone else.

There is also a governance problem. When service owners treat digital identity as a front-end issue rather than an access assurance issue, they underinvest in exception handling, assisted journeys, and offline paths. That is where Identity Security Programme Guide and Identity Proofing and KYC Guide are useful complements, because they separate proofing strength from the broader ability to keep access usable.

What a resilient digital identity model has to support

A resilient model accepts that identity is not a one-time event. It has to support re-access after device loss, fallback when a factor is unavailable, and alternative routes when a primary verifier fails. That usually means designing for recovery assurance, not just initial assurance.

Practically, that means offering more than one recovery path, bounding which changes can be self-served, and ensuring the fallback is strong enough to prevent abuse but simple enough for the intended population to complete. If the only recovery path is as hard as full re-enrolment, exclusion will persist even if enrolment numbers look healthy.

This is also where wallet and credential models can help, but only if the ecosystem supports portability and revocation without forcing a complete restart. For that reason, Digital Identity, eID and Identity Wallets Guide and the legal structure in eIDAS 2.0, EU Digital Identity Framework are relevant reference points, because they show why interoperability and reusable identity matter more than a single enrolment event.

Risk and Threat Considerations

Exclusion is not only an inclusion failure, it can become a security and resilience problem. When legitimate users cannot recover access, they may reuse shared devices, borrow credentials, rely on intermediaries, or abandon official channels entirely, which increases fraud exposure and weakens accountability.

Failure mechanism: the identity system binds access too tightly to one device, one credential, or one verification path, then provides no durable recovery route when that dependency fails.

Impact: people remain formally enrolled but operationally excluded, while the organisation absorbs higher support load, weaker trust, and more workarounds that can expand fraud and privacy risk.

Practitioner Guidance

What to verify: Test the full journey, not just registration success. A programme is not inclusive until a user can lose a phone, replace a number, change contact details, or fail one factor and still regain access through a controlled alternative path.

What to prioritise: Measure successful service use after enrolment, recovery completion rates, and exception handling time. If those figures are poor, fix recovery and assisted access before adding more enrolment channels or tighter proofing.

Practitioner takeaway: Treat enrolment as the start of identity assurance, not the end of access design. The real test is whether ordinary disruptions still leave people able to reach the service without unsafe workarounds.

Related resources from NHI Mgmt Group

• Why do large IAM programmes often struggle even after the technical design is completed?
• When do digital identity programmes create exclusion risk for users?
• Why do non-human identities create compliance risk even when policies exist?
• Why do collaboration tools create such a large secrets risk?