NEP 2020 + Academic Bank of CreditsImplementation Playbook
A practical, week-by-week implementation guide for university registrars, IQAC heads, and CTOs operationalising the NEP 2020 Academic Bank of Credits mandate. Covers Samarth ERP, NAD push, DigiLocker, NAAC alignment, and DPDP Act compliance.
Why this is no longer optional
The National Education Policy 2020 reorganised India's higher education around three interconnected systems: the Academic Bank of Credits (ABC) for credit-banking and transfer, the National Academic Depository (NAD) for recognised digital records, and the multi-entry/exit programme structure for flexible degree paths.
UGC has progressively made ABC participation mandatory across recognised universities. NAAC's revised assessment framework increasingly weights digital-credential maturity in criteria 1.4 (curriculum design), 2.6 (student performance and learning outcomes), and 7.1 (institutional best practices).
The institutions that get this right early reduce verification overhead, accelerate alumni mobility, and earn measurable NAAC criterion uplift. The institutions that defer it are accumulating compliance debt — and a manual catch-up at scale is far more expensive than implementing once, properly, with W3C-standard infrastructure.
The six-phase implementation plan
The phases below are sequential because each builds on the previous one's deliverables. Universities that try to parallelise typically end up redoing schema work after ABC ID coverage gaps emerge.
Stakeholder alignment & scope
Convene the registrar, IQAC head, controller of examinations, IT head, and a vice-chancellor sponsor. Decide which programmes go first — usually the latest UG batch — and document the credential schemas you currently issue. NEP 2020's multi-disciplinary, multi-entry/exit model needs your schemas to support partial completion (Certificate, Diploma, Bachelor, Bachelor with Research).
Deliverables
- Approved scope document signed by the VC
- Inventory of existing credential types
- ABC ID coverage audit (which cohorts have ABC IDs)
ABC ID coverage drive
Every student needs an ABC ID before the credit-bank flow works. Run an enrolment drive: ABC IDs are generated at abc.gov.in via DigiLocker. Most universities find 60–80% coverage at the start; you need >95% for production issuance.
Deliverables
- ABC ID generation campaign collateral
- Helpdesk for students who hit DigiLocker friction
- Daily coverage dashboard
Credential schema mapping
Map your existing credentials onto W3C Verifiable Credential JSON-LD schemas. ABC requires per-credit issuance, not just per-degree — so mark-sheets must decompose into individual course completions, each with its credit weight, NEP-classified discipline tag, and assessment type.
Deliverables
- JSON-LD schema definitions for each credential type
- Mapping document: existing fields → W3C VC fields
- ABC course-credit metadata standardisation
ERP integration (Samarth or custom)
Wire your examination workflow to issue credentials at the moment results are published. For Samarth ERP universities, this is a webhook from the result-publication module. For custom ERPs (universities running on legacy SQL or SAP), this is a CSV-based bulk-issuance pipeline with a daily cron. Either way, no parallel data-entry — issuance must happen automatically when results are declared.
Deliverables
- Webhook or batch pipeline live in staging
- Test issuance for one programme (≤500 credentials)
- Rollback procedure documented
NAD push + ABC credit posting
Each issued credential pushes (a) the official record to NAD via NSDL/CDSL APIs and (b) the credit transaction to ABC. Both happen in the same transaction so the on-chain anchor and the regulatory records stay synchronised. If NAD is down, the system queues — issuance never blocks on a downstream regulator.
Deliverables
- NAD API integration tested end-to-end
- ABC credit posting verified for sample students
- Reconciliation report (on-chain vs NAD vs ABC)
Verifier rollout & training
Equip your registrar's office, alumni cell, and student support to handle verification queries. Most universities receive 50–500 verification requests per week — Gradify's public verifier handles all of them automatically, but staff should know how to read the verifier output and where to escalate edge cases.
Deliverables
- Verifier walkthrough deck for registrar staff
- FAQ for the alumni cell
- Public announcement to students and alumni
ERP integration — pick your pattern
Whatever student information system you run, there is a deterministic, audited path from result publication to verifiable credential issuance.
| ERP / SIS | Pattern | Notes |
|---|---|---|
| Samarth eGov ERP | Webhook (where enabled) or scheduled API pull from the examination module | Most central universities and many state universities run Samarth, the MoE-backed open-source ERP. Where the examination module is configured with outbound webhooks, issuance can trigger automatically on result publication; where it is not, a scheduled API pull or CSV export from the same module covers the same flow with a small reconciliation lag. |
| TCS iON | Scheduled CSV export → bulk-issuance API | Common in private universities. Daily or per-batch CSV export from iON's results module is fed into the credential issuance pipeline. |
| SAP SLcM (Student Lifecycle Management) | RFC/OData feed → middleware | Used in some autonomous and private universities. Lightweight middleware layer translates SAP records into W3C VC JSON-LD. |
| Custom / legacy SQL ERPs | Read-replica → ETL → bulk issuance | For state universities on bespoke systems. Read-only replica avoids touching the source ERP; ETL handles schema mapping. |
Compliance posture — what an auditor will check
Print this. Walk it past your IQAC team. Every box should be ticked before institution-wide go-live.
UGC ABC compliance
- Every credit-bearing course issued as a separate credential
- ABC ID present in credentialSubject of every credential
- Credit transactions posted to ABC API within 7 days of result declaration
- Multi-entry/exit credentials issued (Certificate / Diploma / Bachelor / Bachelor-with-Research)
- Credit-transfer events recorded as VC presentations
NAD integration
- NAD certificate ID generated for every issued credential
- Original credential pushed to NAD within UGC's mandated window
- On-chain proof references the NAD ID for audit reconciliation
- Revocation events propagated to NAD within 48 hours
DigiLocker presence
- Issued credentials accessible via DigiLocker pull
- Wrapped in W3C VC for interoperability with international verifiers
- Backlink to public verifier from DigiLocker entry
NAAC accreditation alignment
- Credential-issuance metrics included in IIQA submission
- Verification-request analytics available for AQAR
- Audit-ready logs of every issuance and verification event
DPDP Act 2023
- No personally identifiable data on the public chain — only hashes/proofs
- Holder consent recorded before pushing to NAD/ABC/DigiLocker
- Retention policy documented and enforceable
- Selective-disclosure flow available for sensitive fields (CGPA, attendance)
The four failure modes we see most often
ABC ID coverage gap
If a programme rolls out without 100% ABC ID coverage, partial credit-bank posting creates reconciliation pain. Resolve coverage before issuance, not after.
Schema drift between batches
Every time examination policy changes (new grading scheme, new course codes), the credential schema must update. Version your schemas and tag every credential with its schema version — otherwise verification breaks for older cohorts.
Convocation crunch
Issuing 5,000 credentials in a single day around convocation is a load test. Test the full pipeline at 2× peak before convocation week — Solana throughput is fine, but ERP exports and ABC API rate limits often are not.
Revocation handling
Plan for the case where a credential must be revoked (degree withdrawn, plagiarism finding). Revocation should propagate on-chain, to NAD, to ABC, and to DigiLocker — all in one transaction.
Implementation FAQs
What happens if NAD or ABC is down during issuance?+
How does this support multi-entry/exit credentials under NEP 2020?+
Is this only for UGC-recognised universities?+
What does the convocation-day issuance flow look like?+
How does this integrate with our IIQA / AQAR submission for NAAC?+
Get NEP 2020 + ABC live this semester
Send us your enrolment numbers and ERP. We'll come back with a tailored rollout plan, a fixed quote, and the schema mapping document for your credential types.