Why US Campus AI Playbooks Fail in India

The PDF arrived from a well-meaning alumnus in California. It was a campus AI playbook: traffic-light guidance for faculty, a blessed list of cloud tools, an honour-code paragraph, a FERPA appendix, and a sentence about equity that never named a category certificate. The vice-chancellor asked that it be 'adapted'. Adaptation, in the first draft, meant replacing FERPA with DPDP in the headers and adding a tricolour on the cover. The hostel still ran on WhatsApp. The exam cell still had EXAM_MASTER. The admissions desk still had to apply reservation law. The playbook still assumed a student named Alex who owned a laptop and spoke one language.

This is an opinion about why those playbooks fail on Indian campuses, including well-funded private ones that think they are global. The opinion is not that American colleagues are foolish. It is that their constraints are not yours. If you copy their blessed-cloud list you will import their processors. If you copy their honour code you will miss unofficial paste. If you copy their equity paragraph you will skip the files that actually cause writs.

It is not legal advice and not a comparative-law treatise. FERPA, COPPA and US state laws do not apply because a PDF said so. DPDP, UGC, AICTE, professional councils, reservation statutes and your ordinance do. Read those.

Different privacy statute, different job

US campus memos orbit FERPA — an education-privacy statute with its own consent, directory-information and school-official patterns. DPDP is a general personal-data statute. Students are Principals. The university is usually the fiduciary. Vendors are usually processors. Children's data has its own treatment. That is a different design. Search-and-replace is not a design.

US memos often assume a cloud tool can be blessed if the vendor signs a FERPA-shaped addendum. Your question is also where the traces live, whether they train, whether unofficial staff phones are the real path, and what 13 May 2027 does to duties you are forming now.

IRB habits from US research culture get imported as if they were the only ethics door. Indian campuses may have IECs for human research. A production fee-helpdesk is still not a clinical trial. The companion piece on ethics committees is the rest of this point.

Cloud-first is a posture, not a virtue

US playbooks bless a short list of SaaS because the campus already lives in a suite and the lawyers have a rhythm. Many Indian public campuses do not have that rhythm. They have a state data centre, an ERP that only one SI understands, and a political expectation of sovereignty language that may be confused but is not meaningless.

A blessed public model is how mark sheets leave the estate. On-prem or otherwise estate-held official agents are not nationalism. They are how you hold traces. Private campuses that can buy the US suite still have Indian students, Indian category files, and Indian regulators. The suite does not delete those.

Air-gap thinking for question banks is not a US undergraduate default. It is an Indian exam-cell default if you have been paying attention.

When a playbook is imported, mark the assumption, not the logo.

US playbook assumption	Indian campus fact	What to write instead
FERPA addendum blesses the SaaS	DPDP roles, child rules, unofficial phones	Fiduciary map + training ban + AUP
English LMS, laptop-first	Code-mix, shared phones, assistance bureaus	Language evals; authenticated sessions; no 'paste your form'
Honour code for student AI use	Staff paste and setter leaks	Staff AUP and exam isolation first
Equity as a paragraph	Reservation, vertical and horizontal categories	Completeness yes; interpretation no
CIO shop with 40 people	Two officers and an SI	Buy less surface; name one owner
Cloud is inevitable	Estate, state DC, or a small room	Posture by data class, not by fashion

The files they do not have

Caste, tribe, OBC-NCL, EWS, domicile, PwD, minority-institution certificates, income for scholarships, and the politics of management seats. A US equity clause about names in a language model will not tell you whether an agent may interpret a certificate. Your ordinance and the Constitution-shaped law of reservation will.

Admissions is a public function even in many private campuses that take a statutory category. A playbook written for a private US admissions 'experience' will happily coach. You cannot.

Exams are still, in much of India, a high-stakes paper-or-OMS event with a leak radius that can cancel a session. A playbook about take-home essays and honour codes is a different planet.

WhatsApp is the SIS

Until you admit that, you will deploy a portal agent nobody uses and a phone habit everybody uses. US playbooks mention 'shadow IT' as a footnote. On many Indian campuses it is the production system for hostels, some teaching, and a shocking amount of official dak.

The Indian playbook therefore starts with amnesty, an AUP, and an official path that is faster than the group. It does not start with a traffic-light PDF for faculty who already have a US vendor login.

Indic languages and code-mix are not an accessibility add-on. They are the ticket. A playbook that scores English prompts will pass a demo and fail the first week.

What to steal anyway

The habit of writing something down. Many Indian campuses have no staff AUP at all. Steal the idea of a short, readable note. Rewrite every clause.

The habit of a blessed-and-forbidden list. Fill it with your estate tools and your unofficial bans, not with their SKUs.

The habit of telling students what is allowed in assessed work. Write it for your ordinance and your exam cell, not for a US honour board.

Leave behind their cloud list, their FERPA appendix, their assumption that the CIO can just SSO another SaaS, and their silence on reservation files.

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.

Our campus is global. We should follow global practice.

Global practice is a magazine. Your students, regulators and files are Indian. A global private campus still answers UGC or a professional council and still holds category data. Write for that.

We do not have time to write our own.

A two-page AUP and a no-decision list for admissions take less time than adapting a 40-page US memo badly. Time is the excuse that produces the header swap.

Donors expect to see a modern AI policy like theirs.

Give them your public card: existence, purpose, human gate, no unofficial paste of files. That is more modern than a FERPA appendix in Bengaluru.

DPDP is basically FERPA.

It is not. Different scope, different roles, different child rules, different regulator. Read the Act. Stop translating in your head.

A 10-day de-Americanisation of the draft

If a US PDF is already in circulation, do not edit it. Write the Indian two-pager beside it and withdraw theirs.

1. Days 1–2: list the assumptions in the imported memo. Strike FERPA, blessed US SKUs, and honour-code-only enforcement.
2. Days 3–5: write staff AUP, student assessed-work rule, admissions no-decision list, exam isolation sentence, DPDP role sentence.
3. Days 6–8: add languages you will actually serve and the WhatsApp residual-risk note.
4. Days 9–10: registrar signs the Indian note. The US PDF becomes a library item, not a policy.

How this shows up in the file

Keep the imported PDF with a cover slip that says not adopted, assumptions fail on X. Keep the signed Indian note as the policy. If someone later asks why you ignored 'global best practice', the slip is the answer.

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 “Why US Campus AI Playbooks Fail in India” without importing a US playbook. “AI higher education India” hits UGC/AICTE/NAAC clocks, exam secrecy, reservation rules, and students who may be minors.

A US campus AI memo assumes FERPA, cloud, English, and a well-funded CIO. An Indian campus assumes reservation files, DPDP, UGC folklore, Indic code-mix and WhatsApp. Copying the memo is how you buy the wrong risk. 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 “Why US Campus AI Playbooks Fail in India” 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. “AI higher education India” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.