QRCertificates
UniversitiesVerificationIndia

DigiLocker for universities: what it solves, and what it leaves on your desk

A person scanning a certificate QR code with a phone to verify it
Key takeaway

DigiLocker is where students see their records. It is not where employers check the certificate you issued last week.

DigiLocker is the citizen-facing wallet. For academic records it is the surface on which depository records appear: an institution publishes to the National Academic Depository, and the student sees the result in DigiLocker.

For a university this is genuinely useful. It is also frequently over-read, and the over-reading causes real operational surprises.

What it does well

It removes the duplicate-copy request. Students who can access their own records stop asking the office for another printed copy.

It gives the student a durable home. Records survive a lost file or a house move, which for a graduate a decade out is not a small thing.

It puts the record at source. What the student shares came from the institution, rather than being a scan of uncertain provenance.

Where the over-reading starts

"We're on DigiLocker, so our certificates are verifiable." Only the records you actually published are, and only formal awards are eligible. The workshop certificate you issued last week is not there.

"Employers can just check it." Access is student-mediated. A recruiter with a PDF and no contact with the candidate has nothing to check against.

"It covers our old cohorts." Only if you published them, which for pre-digital records is a real project rather than a switch.

The arithmetic worth doing

Take a month of verification emails your office answered. Sort them into two piles: those about degrees, diplomas and marksheets, and everything else.

The first pile is what publishing to the depository reduces over time. The second pile: internships, workshops, FDPs, bonafide letters, event awards, anything from a centre or cell: is unaffected, and at most institutions it is the larger pile.

That second number is the honest measure of what remains to be solved after a successful DigiLocker rollout.

Handling the rest

The properties that make a depository record trustworthy can be applied to any document you issue: a unique reference distinct from the student's roll number, a page that opens without an account, a signature over the record so an altered copy fails, and a revocation path for documents issued in error.

Put the verification address on the document itself. A verifier who has to work out where to check will email you instead, which is the outcome you are trying to remove.

The two approaches are complementary rather than competing. Publish formal awards where they belong; make everything else answer for itself.

For current DigiLocker and NAD procedure, use the official portals, process details change more often than guides are updated.

FAQ

Frequently asked

Does DigiLocker make all our certificates verifiable?

Only the records you have actually published to the depository, and only formal academic awards are eligible. Workshop, internship, bonafide and event certificates are not covered.

Can an employer check a record in DigiLocker directly?

Access is student-mediated by design. A recruiter holding only a PDF, with no contact with the candidate, generally cannot resolve it independently.

Does DigiLocker cover our older graduates?

Only if those records were published. Pre-digital cohorts usually require a deliberate data project rather than being covered automatically.

What should we do about documents outside the depository?

Give each one a unique reference, a public verification page that opens without an account, a signature over the record so tampering fails, and a revocation path, with the verification address printed on the document.

Issue your first credential in minutes

Start free, no credit card. Design a certificate, issue a verifiable copy, and watch it verify on a public page. Scale to thousands when you are ready.