Transcript and Degree Verification Agents

The email looked like every other employer query. A recruiter asked whether a named person had earned a B.Tech in 2019 with a particular class. A clerk, trying to be modern, pasted the query into the new campus assistant. The assistant, which had been indexed on an old result PDF and a department souvenir booklet, said yes, with a fluent confidence. The register, when someone finally opened it, said the person had been withheld. The souvenir booklet had listed the class photograph anyway. A chatbot had just created a degree.

This is a guide to transcript and degree verification helpers on Indian campuses. The National Academic Depository, DigiLocker NAD paths, ABC where it applies, and your own signed register are the sources of truth. An agent is a window or a clerk. It is not the register.

It is not legal advice. NAD/DigiLocker processes and UGC directions on depositories move — check live pages. This article will not freeze a 2019 circular as if it were today's screen. Fraud is real. Your answer to fraud is a signed record and a lawful verification path, not a clever model.

The register is the product

Before you buy an agent, know where the truth lives. Examination database. Signed tabulation. NAD upload. DigiLocker issued documents. A paper minute that corrected a mark. If those disagree, you have a data problem. An agent will pick a side at random and sound sure.

The first project is often not AI. It is depositing current and recent records, reconciling withheld and withheld-then-cleared cases, and naming the officer who may confirm a degree.

Only then do you add a helper that can take an employer request, authenticate the requester, and return what the register already knows — or a refusal.

What the agent may do

Intake. Structured fields: name, period, programme, identifier the university actually uses, requester identity and purpose.

Status of a request. Not a preview of the answer.

Citation. 'See the DigiLocker document the graduate can present' or 'see the NAD record' when that is the official path. Do not paraphrase a class into a new adjective.

Drafting a confirmation letter from a locked template whose facts are pulled by a non-generative query from the register. If you do not need a language model for that sentence, do not use one.

Generative fluency is the enemy of a yes/no register fact. Prefer boring queries.

Employer / graduate need	Safe automation	Unsafe automation
Is this degree genuine	Query the signed register / NAD; template letter	LLM 'looks legitimate' on a scanned certificate
Transcript dispatch	Status of the paid request; checklist of holds	Invent a mark or a subject name from a brochure
Name-change / correction	Intake and cite the ordinance	Quietly serve the old or new name without a minute
Withheld / malpractice	Refuse detail; route to the controller	Explain the UFM file to a recruiter
Old pre-digital records	Human search; then a template	Guess from a souvenir PDF or a news clipping

Fraud and the scan

Employers will send photographs of certificates. A model that says the seal looks fine is not a verification. It is a vibe. If you offer a scan path, it is only to extract fields for a register query, with a human on mismatches, and with a written limit: we do not authenticate a paper by its pixels alone.

Deepfakes and well-printed fakes exist. Your defence is that the university's yes comes from the register, not from the paper. Push graduates and employers toward NAD/DigiLocker or your signed digital transcript. That is unglamorous and correct.

Do not build a public box that accepts anyone's certificate scan without requester identity. You will become a free laundering desk.

Privacy of alumni

Alumni are Principals too. A recruiter is not entitled to a narrative. Publish what your ordinance and the law require to be public. For the rest, prefer graduate-mediated sharing — the graduate presents a DigiLocker document — over a campus agent chatting about a third person.

DPDP's operational calendar does not make this optional in spirit. Purpose limitation is older than the Gazette.

Traces of verification requests are personal data of the graduate and sometimes of the requester. Retain to the record schedule. Do not train on them.

ABC and NAD are not your chatbot

Do not impersonate them. Do not promise a credit or a document they do not hold. If your deposits are incomplete, say so on the public card rather than letting the agent fill gaps from a souvenir.

Check live NAD/DigiLocker and ABC pages for how third parties are expected to verify. Align your helper with that path instead of inventing a parallel chat.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note. A spoken answer without paper will be forgotten by the next officer.

Employers want a WhatsApp yes.

Give them a portal and a NAD path. A WhatsApp yes is how you mint degrees in a group. Publish that you will not confirm by informal message.

Old records are not in NAD, so we need a model to read ledgers.

You may need scanning and a human-in-the-loop capture into the register. That is digitisation. It is not a conversational authority. Do not skip the capture and hope the model saw the ink.

A visual authenticity model is standard now.

It may flag crude fakes. It must not be allowed to say genuine. Register or refuse.

We will charge per AI verification.

You may charge for official verification as your rules allow. Do not charge for a fluent maybe. Price the signed fact.

A 40-day verification hygiene path

If NAD deposits are a mess, that is week one. The agent waits.

1. Days 1–10: locate the source of truth. Reconcile withheld, name-change and souvenir conflicts. Pause any tool that indexes brochures as records.
2. Days 11–20: official employer/graduate path — NAD/DigiLocker or a non-generative register query with a template letter.
3. Days 21–30: optional intake agent for how-to and status only. Public card: we do not confirm on WhatsApp or by looking at a photo.
4. Days 31–40: table-top the souvenir graduate. Audit who can run a yes. Bind logs. DPO reviews alumni personal-data handling.

How this shows up in the file

Source-of-truth note, NAD deposit status, the sentence that brochures are not records, the template letter, and the refusal to confirm by informal channel. If the file leads with a model card, you have the wrong artefact on top.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation, academic-regulation or engineering advice. Confirm against the current Gazette, DPDP text and Rules, CERT-In direction, India AI Governance Guidelines, UGC/AICTE/NAAC notices, NEP documents, GFR, departmental manual and your counsel before you file it. Guidelines are not statute. Circulars move.

How this works on an Indian campus

A P3 University should be able to run “Transcript and Degree Verification Agents” without importing a US playbook. “degree verification automation” hits UGC/AICTE/NAAC clocks, exam secrecy, reservation rules, and students who may be minors.

A degree is a register fact, not a conversational opinion. Agents can take employer requests and cite NAD or your signed record. They must not invent a graduate. DPDP applies to student personal data. Chatbots are not a strategy. Exam and admissions writes stay with officers. Affiliated colleges need isolation, not one shared index.

• No production student data in a vendor SaaS sandbox.
• Write the academic integrity policy before the tool.
• Consent and purpose tags on student-facing agents.
• Budget for staff training, not only licences.

Close this loop before the next CAB

Put “Transcript and Degree Verification Agents” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P3 University, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “degree verification automation” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What must be true before you file this

If “Transcript and Degree Verification Agents” is only a heading, it will not survive a file inspection. A P3 University should be able to attach one artefact that proves “degree verification automation”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “degree verification automation” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.