How should governments design digital identity enrolment for people without formal documents?

Why enrolment must work without formal documents

For people without passports, birth certificates, or parental records, the enrolment problem is not just verification, it is access. A design that only accepts conventional documents excludes the very groups the system is meant to serve, including displaced people, rural populations, children, and those affected by weak civil registration. Good enrolment therefore separates identity entry from the later strengthening of assurance.

That usually means allowing more than one route into the system: community attestation, field capture, assisted enrolment, mobile teams, or temporary records that can be upgraded later. The practical objective is to create a trustworthy starting point without pretending every applicant can meet the same evidence threshold on day one.

For broader context on modern identity systems, see Digital Identity, eID and Identity Wallets Guide, which explains how reusable credentials and verified claims can reduce repeated document burden once a person is enrolled.

What a document-light enrolment pathway should actually collect

A usable pathway collects evidence in layers. At the first layer, officials may capture biographic details, biometrics where lawful and appropriate, location, contact points, witness statements, and any available supporting records. At the second layer, the system should link that provisional record to additional evidence over time, such as school records, clinic records, utility evidence, or trusted referrals, depending on the national context.

The key design point is that the record should be created even when confidence is initially incomplete. That means the workflow needs a clear distinction between identity entry, identity assurance, and entitlement to services. If those are collapsed into a single yes or no gate, exclusion becomes the default outcome.

Governments that need a reference model for assurance-based identity proofing can compare their process with Identity Proofing and KYC Guide, which covers alternative evidence, document checks, and how to strengthen confidence over time.

For public-sector deployment patterns, Public Sector Identity Security Guide is useful because it frames citizen identity as a service-design problem, not just an authentication problem.

How governments keep low-document enrolment fair and defensible

Fairness depends on predictable rules, not discretionary exceptions. Applicants should know what evidence is acceptable, what happens when evidence is missing, and how they can later strengthen their record. The process should also be accessible for low-literacy users, people with disabilities, minors, and people whose naming conventions do not fit rigid forms.

Defensibility comes from keeping auditability at the centre. Officials need to record why a provisional identity was accepted, who vouched for it if attestation is used, which checks were completed, and what later review or upgrade path exists. Without that trail, a flexible enrolment model can drift into arbitrary decisions or weak fraud controls.

For governments building the operating model around this work, Identity Security Programme Guide helps connect enrolment rules to governance, ownership, and lifecycle management.

Where governments use multiple credentials or wallet-based journeys, the design should align with standards rather than inventing one-off local exceptions. The European model is useful here because it shows how identity entry, trust services, and cross-border verification can be separated while still remaining interoperable.

Risk and Threat Considerations

Flexible enrolment lowers exclusion risk, but it also raises fraud and record-quality risk if provisional identities are not controlled carefully. The main danger is that a system built to include people without documents can also become easier to game through synthetic identities, duplicate enrolment, or weak attestations.

Failure mechanism: If alternative evidence is accepted without clear provenance, the programme can create records that are hard to disprove later, while weak deduplication or poor review processes allow multiple identities for the same person or a false identity for a real person.

Impact: The state may issue benefits, credentials, or voting access to the wrong person, while legitimate applicants lose trust in the system because re-enrolment, correction, or appeal becomes slow and opaque.

Practitioner Guidance

What to prioritise: Design the enrolment journey so exclusion is treated as a system failure, not an acceptable default. The first implementation decision should be which minimum evidence set creates a provisional record, and which additional checks are required before higher-risk entitlements are unlocked.

What to verify: Make sure the workflow supports assisted enrolment, alternative evidence, and later record strengthening without forcing every case through the same document gate. Verify that operators can explain decisions to applicants and that every exception leaves an audit trail.

Common mistake: Treating document absence as a fraud indicator. In practice, lack of formal records is often a coverage problem, so the control objective is not to deny entry, but to manage assurance in stages.

Practitioner takeaway: The best digital identity programmes do not ask vulnerable people to prove a history the state never helped them formalise; they create a provisional path in, then harden assurance as better evidence becomes available.

Related resources from NHI Mgmt Group

• How should identity programmes handle people without formal identity documents?
• How should governments and service providers design mobile digital identity systems without creating unnecessary privacy risk?
• How should governments and private sector organisations design digital identity frameworks that support financial inclusion without excluding vulnerable groups?
• How should governments design digital passport renewal for citizens living abroad without weakening identity assurance?