APAAR, ABC ID and NAD: what they cover, and what universities still verify themselves
India now has a national academic identity stack. It covers less than most registrars assume, here is the honest boundary.
If you run examinations or records at an Indian institution, four acronyms now sit between you and a verified student record: APAAR, ABC, NAD and DigiLocker. They are related but not interchangeable, and the difference matters the moment somebody asks you to prove a document is real.
What each one actually is
DigiLocker is the citizen-facing wallet. A student logs in and sees documents issuers have pushed to them.
NAD, the National Academic Depository, is the depository behind it for academic awards. Institutions publish degrees, diplomas and marksheets into NAD and they surface to the student in DigiLocker.
ABC, the Academic Bank of Credits, is a credit ledger rather than a document store. It accumulates credits earned across recognised institutions so they can be transferred and redeemed toward an award.
APAAR is the student's permanent academic identifier, tying a learner to their ABC credits and NAD records across institutions.
The boundary registrars discover late
The stack is built for formal awards from recognised higher education institutions. That is a deliberate scope, and it is narrower than the set of documents your office actually signs.
Consider what a department issues in a year:
- Degree certificates and semester marksheets: in scope, once you publish to NAD
- Workshop, FDP and short-course certificates: not covered
- Internship and training completion letters: not covered
- Bonafide letters, conduct certificates, migration certificates: not covered
- Event, hackathon and competition certificates, not covered
- Anything issued by a centre, cell or society under your name, not covered
Every one of those carries your institution's name and seal. None lands in NAD. When an employer or a foreign university asks whether one is genuine, the request comes back to your office as an email and somebody answers it by hand.
Why "we are on DigiLocker" is not a complete answer
Three practical gaps come up repeatedly.
It is student-mediated. The verifier generally needs the student to share the document. A recruiter holding a PDF that somebody emailed them has no way to check it independently.
It covers the award, not the paperwork around it. Most verification requests an institution receives concern letters and short-course certificates, not the degree.
Backlog and non-degree records stay manual. Historical cohorts and anything outside the formal award set still land on a clerk's desk.
What to do about the rest
The pragmatic position is not "instead of NAD". It is: publish formal awards to NAD because you are required to, and make everything else independently checkable so it stops generating email.
For that second category the requirements are modest. Each document needs a unique identifier, a public page anyone can open without an account, a signature over the contents so tampering is detectable, and a way to revoke a document issued in error. A QR code is simply the fastest route from paper to that page.
The test to apply: if a recruiter in another city holds only the PDF, can they establish it is genuine without contacting your office? If not, that document class is still costing you staff time however complete your NAD publishing is.
A sensible sequence
- List every document type your institution issues in a year, not just the awards.
- Mark which are genuinely in NAD scope, usually degrees, diplomas and marksheets.
- Count the verification emails you answer for the remainder. That number is the cost of the gap.
- Make the highest-volume remaining class verifiable first, normally internship or workshop certificates.
- Put the verification URL on the document itself, so the next request answers itself.
None of this competes with the national stack. It covers the documents the national stack was never designed to hold.
