Multilingual Student Support Across States

A central university with students from the Northeast, Kerala and Rajasthan bought a helpdesk agent that advertised '22 official languages'. The demo was Hindi and English. The first production week, a Khasi-speaking first-year asked in English when the scholarship form closed. The agent answered with a paragraph about a state scheme from another year. The language failure was not Khasi. The language failure was that the English was fluent and the circular was wrong.

This guide is for student-welfare deans, registrars of multi-campus universities, and computer centres who are being sold coverage of the Constitution's Eighth Schedule as if it were a product certification. The Eighth Schedule lists languages for specified constitutional purposes. It is not an evaluation harness. If you will not mark a language, do not claim it.

Prcept will not claim twenty-two. We will ask you which three you will score this semester, including the code-mix. That is the only honest SKU.

Coverage is a test set, not a schedule of the Constitution

Write language, script, register and code-mix. Hindi in Devanagari, Hindi in Latin letters, English, and a sentence that switches, are four rows if you will mark four. A campus in Tamil Nadu that does not mark Tamil in Tamil script has not bought multilingual support. It has bought a Delhi demo.

Register matters. Secretariat English, student SMS, and a parent's voice note are different. A model that can discuss cricket in Telugu and fail on a fee-refund sentence is not a student-support model.

Political pressure to list every home state is real. Split mandatory go-live languages from a dated roadmap. Put the roadmap in the file so nobody can pretend the roadmap was go-live.

Paste rows you will mark. Delete the rest. A short table is a serious campus.

Language / mix	Script	Domain	Pass
English	Latin	Exam form dates, fee status	Exact date and amount from the pinned circular
Hindi	Devanagari	Hostel SLA, scholarship name	Correct desk and document list
Hinglish / Tanglish / other named mix	Latin or mixed	The same domains	Same facts as the formal row
State language you actually staff	Native script	Admissions and hostel	No silent fallback to English that changes the fact

Facts travel worse than fluency

The failure mode is a correct-sounding sentence attached to the wrong circular. Multilingual generation multiplies that failure because reviewers cannot read every output. So do not generate the rule. Retrieve the standing order and quote it. If you must generate, generate the navigation — 'this is the scholarship desk, here is the PDF' — not the eligibility clause.

Pin language-specific PDFs when they exist. Many campuses have an English circular and an unofficial Hindi WhatsApp paraphrase. The agent retrieves the circular. The paraphrase is not a source.

Names, roll numbers and village names will be transliterated badly. Do not let the agent 'correct' a student's name into a more common spelling. Identity is not a language-model preference.

People behind the language

A multilingual agent is not a substitute for a Malayalam-speaking clerk at the scholarship desk if that is what the student needed. Publish the human escalation in that language. First-generation students will not type 'escalate'. They will type 'I don't understand'. That string is a route, not a failure.

Do not detect 'education level' from grammar and then offer a simpler, less accurate rule. Simplification that drops a condition is a different rule. The accurate rule, in shorter sentences, is the job.

Parents calling from another state are not students. Their identity, their right to hear a result, and DPDP are a consent-and-notice design. Fluency in the parent's language does not create a right to the mark sheet.

Who writes the eval set

Not the vendor. Student welfare, the exam cell and hostel office each write twenty real questions in the languages you marked, including the angry ones and the code-mix. Hold them out. A vendor Indic benchmark of news headlines is entertainment.

Re-run the set when the circular changes. Language quality and fact quality are different scores. A pretty Hindi sentence with last year's fee is a zero.

Voice notes and the parent phone

Many first-year messages arrive as voice notes in a state language the desk does not staff at midnight. A speech-to-text step is processing. It needs the same basis and the same isolation as the ticket. Do not send the audio to a public transcription API. If you cannot transcribe on-prem, offer a human callback window instead of a broken transcript that invents an amount.

Code-mix eval sets should include the ugly strings: Latin-script Tamil with English verbs, Hindi with roll numbers in the middle, Odia names spelled three ways. If your set is only newspaper Hindi, you will pass a test and fail the hostel.

When you add a language, add a human who can read the abandoned chats in that language. An eval no one can mark is a decoration. That human is also the door you promised in the first-generation piece.

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.

The ministry note said all Eighth Schedule languages.

Then write a dated roadmap and an eval budget, or write back that the note is a destination. Shipping twenty-two unchecked ticks is a false statement in a government file.

English is enough; our medium is English.

Your medium is English. Midnight messages are not. If you refuse other languages, say so, and staff the human desks that will absorb the rest. Do not claim coverage you marked as out of scope.

We will use machine translation on the way out.

Then evaluate the translation against the circular, not against fluency. And do not translate a mark or an amount. Numbers pass through untouched.

A larger model will just handle it.

Larger models are more fluent. Fluency is the risk. Retrieval and eval sets are the control.

Pick three languages and survive the semester

If you cannot name three, you are not buying multilingual support. You are buying a slogan.

1. Week 1: name languages, scripts, code-mix, and the two domains (usually fees and hostels).
2. Week 2: pin live circulars. Commission human translations if a language has no official PDF.
3. Week 3: write the hold-out eval, including 'I don't understand' as a route.
4. Week 4: go live with retrieval-first answers. Generation only for navigation sentences that cannot change a right.

How this shows up in the file

Syndicate sentence: we claim these languages, we evaluate them, we do not claim the Eighth Schedule, we do not correct names, we retrieve circulars rather than paraphrase rights.

Attach the eval scores when you renew the vendor. No scores, no renewal story.

This article is informational field guidance for Indian public universities and colleges, not legal, regulatory, academic, labour or procurement advice. Confirm against the live AICTE / UGC / NAAC notice, the DPDP Act and Rules as commenced, your Act and statutes, reservation orders, labour counsel and the syndicate before you file it.

How this works on an Indian campus

A P3 University should be able to run “Multilingual Student Support Across States” without importing a US playbook. “multilingual student support AI” hits UGC/AICTE/NAAC clocks, exam secrecy, reservation rules, and students who may be minors.

A central university is not a language-pack SKU. Name three languages you will actually evaluate, including the code-mix students type at midnight. 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 “Multilingual Student Support Across States” 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. “multilingual student support AI” 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 “Multilingual Student Support Across States” is only a heading, it will not survive a file inspection. A P3 University should be able to attach one artefact that proves “multilingual student support AI”: 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 “multilingual student support AI” 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.