Document Verification and Exceptions

Document Match

The document must match the resident and the demographic field being captured or updated.

Legibility

A document that cannot be read clearly should not be treated as a clean proof.

Fraud Indicator

Mismatch, tampering, suspicious photo, inconsistent age, or altered address can indicate fraud risk.

Accepted List

Use the current accepted document list instead of personal judgment or local habit.

Exception Handling

Exception handling must follow UIDAI process and should be documented, reviewed, or escalated as required.

Introducer Route

Introducer-based enrolment applies only where the official process permits it and role conditions are met.

Head of Family

HoF-based processes require correct relationship and supporting information under the UIDAI workflow.

Escalation

When document authenticity or applicability is uncertain, escalate instead of inventing a workaround.

Document Verification and Exceptions: first read

Candidates need accepted document categories, document-resident match, legibility, fraud indicators, exception handling, Introducer or HoF concepts where applicable, and escalation discipline. First read the official source, role boundary, and stated facts together.

Document Verification and Exceptions: shortcut trap

In Quality, Fraud Prevention and Compliance, eliminate the fastest-looking answer if it skips a document, disclosure, consent, calculation, quality check, or audit trail.

Document Verification and Exceptions: exam-safe action

The exam-safe answer keeps user protection, the current India rule, a traceable record, and role-appropriate escalation together.

Document Verification and Exceptions: review cue

For UIDAI Operator/Supervisor review, ask whether the answer follows the official workflow and can be defended later in an audit.