AICTE Compliance Reporting: Automate What?

Every June, someone in a technical campus discovers that the AICTE portal does not care about the beautiful dashboard the vendor sold in March. It cares about faculty uniquely identified, student intake against approved intake, land and built-up figures that match last year's affidavit, and a set of declarations a principal will later have to defend. The dean of academics asks whether 'the AI' can just fill it. The computer centre nods because saying no feels like a career event. That is how a campus ends up with an agent that invents a professor.

This is a field guide for registrars, principals of AICTE-approved institutions, IQAC coordinators and computer-centre heads who want agents on the reporting grind without committing a false statement to a statutory council. As of 17 August 2026, AICTE's public face for the current cycle is the Approval Process 2026-27 pages, sitting on top of the Approval Process Handbook 2024-25 to 2026-27 and the corrigenda that keep arriving. We are not going to invent a circular number. We are going to tell you what an agent may assemble, what a human must still sign, and what you must re-read on aicte.gov.in the week the portal opens.

Prcept AI is a B2G, on-prem and air-gapped agent platform. We are DPIIT-recognised and we do not train on customer data. That is a procurement fact, not an AICTE exemption. The Council has not, that we can see, published a product certification for campus agents. Treat every vendor who says otherwise as a brochure.

What AICTE actually asks — and what it does not

AICTE approval is not a chatbot conversation. Existing institutions typically live or die on Extension of Approval, variation of intake, new programmes, and the documentary trail the Approval Process Handbook and the year's public notices describe. New institutions and certain programme groups have their own windows. The Council publishes user manuals for generating reports and affidavits. Institutions upload supporting documents through the Council's document channel. Helpline numbers and temporary login freezes appear on the portal itself. If your agent cannot point at the current notice, it is guessing.

The Handbook for 2024-25 to 2026-27 is a multi-year instrument. The portal cycle is annual. That split is the first place automation lies. A row that was true for 2025-26 can be wrong for 2026-27 because a corrigendum moved a definition, a programme group, or a late-fee date. We have seen public notices that extend submission dates and separate guidelines for Extension of Approval of BBA, BMS and BCA programmes. Those are examples of the class of document you must pin. They are not a substitute for opening the live page.

AICTE is also not UGC and not NAAC. A central university with an AICTE-approved school has three reporting grammars. An affiliated engineering college has the university, the state technical directorate, AICTE and often NAAC. An agent that 'does compliance' as one skill will mash those grammars into a single spreadsheet and then be shocked when the Council's faculty-student definition is not the university's workload definition.

Separate the council from the campus file. One agent, four owners, is how numbers drift.

Instrument	Who owns the number	What an agent may do	What it may not do
AICTE EoA / variation / new programme	Principal / registrar with the dean of the school	Assemble last year's pack, flag missing unique faculty IDs, calendar the portal window	Submit, pay TER charges, or invent a faculty member to fix a ratio
UGC returns, 12B / 2(f) correspondence, regulation filings	Registrar	Index letters and extract named fields into a working sheet	Treat a UGC letter as an AICTE fact, or the reverse
NAAC SSR / AQAR evidence	IQAC director	Map evidence files to the current NAAC template the campus has downloaded	Rewrite peer-team language or back-fill a metric the file does not support
University affiliation / state directorate	The college principal and the university affiliation section	List discrepancies between the three intakes	Pick the most flattering intake and hide the other two

Automate the pack, not the oath

The honest work is dull. Last year's approved intake versus this year's proposed intake. Faculty uniquely identified against the Council's current definition, not against the WhatsApp group of 'visiting experts'. Built-up area that matches the architect's drawing that was already filed, not a new measurement the civil contractor invented this morning. Student enrolment that matches the university exam-form count, not the marketing brochure. Occupancy certificates, land documents, and the affidavits the current user manual tells you how to generate.

An on-prem agent that can retrieve those artefacts from the registrar's file store, the HRMS, the exam cell and the estates office, and then produce a discrepancy list, is worth buying. An agent that writes the affidavit prose and invites the principal to click submit is a disciplinary case waiting for a login.

Build three outputs only. A calendar of the live window, with the URL of the notice you pinned that morning. A pack: PDFs hashed, named, and mapped to the portal's current field list. A gap list: fields the source systems cannot support, written in the principal's language. If the gap list is empty every year, someone is lying or the systems are unusually good. Assume the former until the internal auditor samples.

• Pin the Handbook PDF, the year's public notice, and every corrigendum as versioned objects. The agent retrieves those, not a vendor blog.
• Key faculty on a stable unique identifier the Council already understands. Do not let the agent merge 'Dr S. Sharma' across two departments because the names look similar.
• Refuse to compute a ratio the Council has not asked for this cycle. Decorative KPIs become affidavit numbers under deadline pressure.
• Keep the TER payment, digital signature and final submit on a human desk with a named officer.
• Log who asked the agent to 'fix the faculty shortfall'. That log is the file when a show-cause arrives.

Data classes hiding inside an EoA row

Faculty records are personal data. Student enrolment lists are personal data. Caste and category fields, disability certificates, and minority-institution facts are not 'just compliance'. Under the Digital Personal Data Protection Act, 2023 the university or the society that runs the college is the Data Fiduciary for those records. The agent vendor is a processor if the contract says so and the architecture behaves that way.

Do not send the EoA working sheet to a public chatbot to 'make the language nicer'. Do not fine-tune a vendor model on last year's faculty list. Prcept's rule on our side of the table is that we do not train on customer data. Your rule should be the same for every processor, including the SI who 'just wants a copy for the demo tenant'.

Minors appear in diploma and some first-year lists. Section 9 of the Act is about children, defined as under eighteen, and verifiable parental consent except where the government has prescribed otherwise. An EoA pack is a poor place to discover you have been publishing a seventeen-year-old's mobile number in a spreadsheet that sat on a contractor laptop. Check the live Rules for any educational exemption that actually applies to your processing. Do not assume one.

What we checked on 17 August 2026 — and what we refused to invent

AICTE's site advertised Approval Process 2026-27 with effect from 28 November 2025, published an Academic Calendar 2026-27 pointer, and carried guidelines for Extension of Approval for BBA, BMS and BCA programmes for 2026-27. The older Approval Process 2025-26 page still pointed at the Handbook for 2024-25 to 2026-27 and its 2025-26 addendum. Document upload still sat at the Council's documents host. We are describing a public page as we found it. Pages move. Corrigenda land on Fridays. Your file must cite the PDF you downloaded, with a date and a hash, not this paragraph.

We did not find, and therefore will not cite, an AICTE circular that authorises generative agents to complete statutory filings. We did not find a product whitelist. If a bidder shows you one, ask for the URL on aicte.gov.in. If the URL is a LinkedIn carousel, mark the bid down.

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.

Other campuses already use ChatGPT to write the annexures.

Other campuses also receive show-cause letters. A public model is a processor you do not control, trained on terms you did not negotiate, often outside your perimeter. Pasting faculty and student lists into it is not clever. It is a transfer and a security incident that happens to look like typing.

If we cannot automate submit, the purchase is pointless.

The purchase is the three weeks you currently lose to hunting PDFs and reconciling three spreadsheets. Submit is a five-minute act that carries a principal's name. Keep the name human.

AICTE will soon require AI reporting anyway.

When the Council publishes that, we will read it. Until then, do not write a future notice into this year's affidavit. Speculation is not a lawful basis and it is not a project plan.

Our SI says the cloud region is in India so the pack can live there.

Residency is not control, and AICTE evidence is still personal data plus declarations. Prefer on-prem or the campus data centre. If you must use a hosted store, name the processor, the training ban, and the exit. Do not let the SI's region name do the work of a contract.

A four-week EoA pack you can defend

Run this before the portal login is enabled, not the night TER charges are due.

1. Week 1: download the live Approval Process notice, the Handbook PDF you will actually use, and every corrigendum. Hash them. Name the principal, the school dean, the HRMS owner and the estates owner.
2. Week 2: point the agent only at last year's filed pack, payroll, exam enrolment and estates drawings. Produce the gap list. Do not draft affidavits yet.
3. Week 3: close gaps in the source systems. Appoint, reclassify or withdraw a programme in the real world. The agent only refreshes the list.
4. Week 4: human review of every changed row. Internal audit samples ten faculty and ten student rows. Then, and only then, a named officer enters the portal.

How this shows up in the file

The note to the principal can be five sentences. One: we are automating assembly and discrepancy, not submission. Two: the source of each number is named. Three: the live AICTE notice we pinned is attached. Four: no public model will see the pack. Five: the officer who will click submit is named, and the agent log will show who asked for a 'fix'.

If those sentences cannot be written, you do not have a compliance agent. You have a risk with a login.

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.