From Pilot to Campus-Wide: A Rollout Plan

The pilot worked for fee FAQs on one faculty's students. Someone said the next logical step was turn it on for the whole university before the next syndicate. That sentence is how you inherit hostel medical notes, unpublished exam circulars, and a second identity store the agent was never mapped to.

A campus is not a tenant toggle. It is faculties, centres, hostels, a finance office, an exam pipeline, sometimes a distance arm, sometimes an affiliated-college problem. Each ring has a different records officer and a different way to be wrong in public.

This playbook is the expansion sequence we walk with registrars. It is written on 17 August 2026. It is not legal advice. It assumes you already have a 90-day pilot with a DPA, a training ban, and no production PII until a checklist was green. If you do not, stop and do that first.

Rings, not phases named after marketing seasons

Ring 0 is the pilot: one workflow, one signed corpus, one identity source, named officers, exportable logs. Exit clause live. Ring 1 is the same workflow for more students on the same identity and corpus — another faculty, another campus of the same legal person. You are testing load and FAQ drift, not new data classes.

Ring 2 is a second workflow in the same office (registrar), still no exam or health. You are testing whether the AI register and the DPA still describe reality. Ring 3 is a new office (finance, hostel administration, placements) with its own corpus pin and its own officer. New purpose. New retrieval allow-list. Ring 4 is write tools, if ever: tickets, exception requests, never the academic register, never marks, never mutation of fee paid. Officer-gated.

Affiliated colleges, if you have them, are not a ring. They are other legal persons or a messy hybrid. Do not share the vector store until counsel draws the map.

Expansion gates. If a gate is red, the next ring does not open.

Gate	Green	Red
Quality sample	Material error below the stop rule for four weeks	Any uncorrected wrong rule in the last sample
Export	Department-owned packet without vendor engineer	Logs only in a vendor console
Identity	One SSO, no shared passwords, no parent logins	WhatsApp groups as the identity layer
Corpus pin	Owner signed this term's pack	CMS crawl and we will tidy later
DPA / purpose	New ring named as a purpose or a new DPA annex	Same annex covering all campus data
Load	Replay of last peak survived	We will scale when students complain

Who has to be in the room each ring

Every ring: registrar or records officer, CIO, DPO-equivalent, the metric owner, the vendor technical lead (not only the CSM). Ring 1: the faculty manager who will field the first wrong answer. Ring 3: the new office's head, who must be allowed to say no. Hostel and health should usually stay no. Ring 4: finance and, if writes touch students' rights, counsel. A write tool is a delegation of authority, not a feature flag. Syndicate or board sees a one-page ring report, not a transformation roadmap with fourteen workstreams.

What campus-wide must never mean

One index over every filestore the CIO can mount. One agent identity that can open exam, hostel and finance. One prompt change pushed in registration week. Affiliated colleges silently included because they share an email domain. A student-facing bot that staff then use as a back office, mixing purposes.

Freeze windows

Do not open a ring in the first ten days of registration, in the hall-ticket-to-result window, or in the week of a fee-deadline. Those are production events. Expansion is a change. Treat it like an ERP change advisory. If a ring goes badly, you roll back the ring, not the entire campus. That is why you did not share one index.

Two rooms you can walk into

Expansion is where pilots go to become incidents.

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.

The licence is already enterprise. We should use it.

A licence is not a purpose. Unused capacity is cheaper than a leak. Turn on rings, not SKUs.

Other campuses went university-wide in a term.

Name them and ask what they indexed. Many university-wide bots are a FAQ on a marketing site. That is Ring 0 with a press note.

Faculties will revolt if they are not included.

Offer Ring 1 on the same workflow when their officer signs the pack. Inclusion is a signature, not a courtesy login.

We will govern it with a steering committee.

Committees do not close a corpus hole. A named pack owner does. The committee can hear the ring report.

A twelve-week expansion that can still be killed

If Ring 0 is not dull by week 0, do not start this clock.

1. Weeks 1–2: write the ring map and the freeze calendar. Counsel flags affiliated colleges and the distance arm as out.
2. Weeks 3–6: Ring 1 only. Same workflow, more students. Weekly quality sample. Load replay if you will cross a peak.
3. Weeks 7–8: decision gate. Green opens a second registrar workflow (Ring 2) or you stop and harvest the saving.
4. Weeks 9–11: if a new office (Ring 3) is even discussed, start a new purpose annex and a new corpus pin — do not just add folders.
5. Week 12: syndicate one-pager. No write tools unless finance and counsel opened Ring 4 on paper.

How this shows up in the file

Subject: Campus agent expansion — ring map. Ring 0 remains the named workflow. Proposed Ring 1 is the same workflow for a named population, same corpus and SSO. Gates must be green for four weeks. Exam, health, hostel medical, unpublished assessments and affiliated colleges are out of scope. Freeze windows are dated. Rollback is by ring, not by campus.

If the map has an arrow labelled everything else, redraw it.

What we will and will not claim

Prcept AI will not sell you a campus-wide toggle. We will run the next ring on your rack when the last ring's export and quality sample are boring. If you need a foundation-day announcement, announce a ring and a gate, not a transformation.

This article is informational field guidance for Indian universities and public institutions, not legal, procurement, audit or engineering advice. Confirm against the live Gazette, GFR, state financial rules, GeM terms, UGC text, GIGW, DPDP commencement, departmental manual and your counsel before you file it.

How this works on an Indian campus

A P3 University should be able to run “From Pilot to Campus-Wide: A Rollout Plan” without importing a US playbook. “university AI rollout plan” hits UGC/AICTE/NAAC clocks, exam secrecy, reservation rules, and students who may be minors.

Campus-wide is not a bigger licence. It is a sequence: one workflow, one corpus, one identity ring, then the next. Expand only when the last ring is reconstructable and dull. 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 “From Pilot to Campus-Wide: A Rollout Plan” 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. “university AI rollout plan” 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 “From Pilot to Campus-Wide: A Rollout Plan” is only a heading, it will not survive a file inspection. A P3 University should be able to attach one artefact that proves “university AI rollout plan”: 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 “university AI rollout plan” 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.