NAAC evidence is a filing problem, not a writing problem

Accreditation is announced. A committee forms. For the next several months, senior faculty stop teaching properly and start hunting: attendance registers from a year they cannot find, minutes of a meeting somebody remembers happening, participation lists for an event whose organiser has since left.

What gets submitted is then partly reconstruction. Not invention — the events happened — but the evidence is assembled after the fact from memory and scattered files, which is why it is thin, inconsistently formatted, and occasionally contradicts another section of the same report.

The cost is not only the marks. It is two terms of your best people doing clerical archaeology.

Not because nobody kept records. Because the records were kept in the shape the daily work needed, not the shape the criteria ask for.

Attendance is kept so a shortage notice can go out this month, then the register is closed. Committee minutes live in the convenor's email. Event participation is a signed sheet in a drawer. Grievances are a WhatsApp thread and a resolution nobody timestamped. Each of these is fine for its own purpose and useless eighteen months later.

The criteria, meanwhile, ask for things with dates, counts and continuity — participation over three years, average resolution time, percentage of courses with stated outcomes. Those are aggregate questions, and you cannot aggregate a drawer.

The alternative is not a better filing habit. It is arranging things so the evidence already exists because the work was done in a system rather than beside one.

If attendance is marked in software, the three-year attendance picture is a query, not a search. If a grievance is logged with a category and a deadline, average resolution time is a number you already have. If an event records who attended rather than collecting a signature sheet, participation counts are immediate.

The test for any module is not "can it store this" but "does the person doing the daily work have a reason to use it". A committee-minutes feature nobody touches produces exactly as much evidence as the drawer did.

In rough order of how much evidence they generate per unit of effort:

It will not write your report, and it will not turn a weak programme into a strong one. If courses genuinely have no stated outcomes, no system invents them. If a committee did not meet, there are no minutes to produce.

It also will not fix the years already behind you. A system installed today starts generating evidence today. The cycle you are in now still needs the hunt, and anyone who tells you otherwise is selling.

What it changes is the next cycle. The difference between a college doing this for the second time with records and the first time without one is measured in months of senior faculty time.

Our college product covers admissions through convocation — academics, attendance with shortage escalation, continuous assessment, examinations, fees, HR and payroll, hostel, library, placement, research projects and publications, grievances, and events. Accreditation reporting reads from those modules rather than asking anyone to maintain a second set of books for it.

One precision, since the section above made a point of resolution time: grievances carry a category, an escalation action and a resolved-at timestamp, so average resolution time is a real figure you can produce. What they do not carry is a per-category deadline the system enforces — the clock is measurable after the fact rather than a target the software holds you to. If your criteria response needs the latter, say so early.

The honest framing: it is a reporting layer over operational records, not an accreditation consultancy. It answers the questions the criteria ask about things the system already knows, and it will tell you plainly where a record does not exist. Filling those gaps is still your academic work, not a software purchase.