Publishing academic records to NAD: what an institution needs in place
The hard part is rarely the portal. It is having records clean enough to publish in the first place.
Most guides to publishing on the National Academic Depository describe the portal. In practice, institutions rarely get stuck on the portal. They get stuck on their own data: and that part is worth preparing before anyone logs in.
The real prerequisite: clean records
A depository is only as good as what you put in it, and publishing exposes every inconsistency an examinations office has been quietly tolerating.
- Name variants. The same student appears as "Rajesh Kumar", "Rajesh Kumar S" and "R. Kumar" across three systems.
- Identifier drift. Roll numbers reused across years, or changed after a re-registration.
- Programme naming. The degree is written one way on the marksheet, another in the student information system, and a third in the affiliating university's records.
- Historical gaps. Older cohorts sitting in spreadsheets or scanned registers rather than a database.
- Post-result changes. Revaluations and corrections that were applied to a printed document but never back to the source record.
Every one of these becomes a rejected record or, worse, a published record that does not match what the student is holding.
Identifiers are the load-bearing part
A student's APAAR ID is what ties them to their credits and records across institutions. Collecting it accurately, and associating it with the right internal record, is the step that determines whether everything downstream works. Collect it at admission where you can; retrofitting identifiers for a graduating batch is materially harder.
Sequence that tends to work
- Pick one recent cohort in one programme. Do not start with the archive.
- Reconcile names and identifiers for that cohort against a single source of truth.
- Agree the canonical programme name and stick to it everywhere.
- Publish that cohort, then check a handful of student-side results yourself.
- Only then widen: by programme, then by year, working backwards.
Work backwards from the present rather than forwards from the archive. Recent cohorts have the cleanest data and the highest verification demand, so you get the benefit soonest.
Decide the revaluation rule first
Results change. Before you publish anything, decide what happens when a grade is corrected: the record is superseded, the earlier version remains resolvable, and the student's held document points somewhere sensible. Retrofitting that policy after the first correction cycle is painful and confusing for the student caught in it.
What still will not be covered
When formal awards are published, the remainder of your issuance is unchanged: workshop and FDP certificates, internships, bonafide letters, event awards. Those never enter the depository, and the verification emails about them keep arriving.
Plan for them in the same project rather than a year later. The requirements are modest: a unique reference per document, a page anyone can open without an account, and a signature over the record so tampering is detectable.
For current procedure and technical specifications, work from the official NAD and DigiLocker documentation, which changes more often than third-party guides do.
