NAAC §5.2 / NBA §3.4 / AISHE Block-16 — auto-generated, in one click

A college's IQAC coordinator told us recently: "The peer team asked me to prove that 60% of our students do non-academic activities. I had no way to prove it. The data exists in 12 spreadsheets owned by 12 people. I gave up and submitted what we had."

That's the everyday reality of accreditation in Indian higher education. The data exists. It's just nowhere near the report-builder when the report is due.

The fix isn't a better report-builder. It's capturing the data at the moment it happens.

The three reports

NAAC §5.2 — Career progression

What it asks: per academic year, how many of your graduating students went to (a) employment via campus drives, (b) employment via off-campus, (c) higher studies, (d) entrepreneurship.

Why it's hard: students who joined a job via the placement cell get recorded by the placement office. Students who joined a job through a family contact tell nobody. Students who went to higher studies tell the alumni office months later. Three different data sources, three different teams, no shared format.

The fix:

• One placement / offer table. Every offer — campus or off-campus — gets recorded against the student.
• Mandatory exit form. Before graduation, every student submits a one-page "what next" form. Drop-down: campus / off-campus / higher studies / entrepreneurship / other. 30-second form, 100% capture rate when made part of degree-issuance.
• Alumni one-line updates. Quarterly LinkedIn-style "are you still at the same place" check via the alumni app.

Once those three streams flow into one table, the §5.2 report is GROUP BY academic_year, exit_category, COUNT(*). Live-computed, snapshot-able. We've seen colleges go from 6-month assembly to 90-second generation.

NBA §3.4 — Course outcome attainment

What it asks: did your students attain the course outcomes you defined for each programme?

Why it's hard: most colleges define COs (course outcomes) in their NBA-prep year, then never refer to them again. By accreditation, the COs are 4 years old and nobody can map them to actual assessment data.

The fix:

• CO-to-assessment mapping at the moment of assessment creation. Teacher creates a midterm → assigns each question to one or more COs. Five seconds of work per question.
• Per-student CO score computed automatically. If a student scored 70% on questions mapped to CO-1 and 60% on questions mapped to CO-2, the system computes their CO-1 attainment as 70%.
• Programme-outcome rollup at the end of the term. Live.

Once COs live in the same table as marks, §3.4 is just averaging. We've seen colleges produce per-programme attainment PDFs in one click that used to take a faculty committee three weekends.

AISHE Block-16 — Annual submission

What it asks: a 50-column CSV of student/faculty enrolment, programme structure, financial data, infrastructure. Annual submission to the AISHE portal.

Why it's hard: the AISHE column order is fixed, and 50 fields means 50 places a typo can creep in. Most colleges hand-collate from spreadsheets each January.

The fix: AISHE is the easiest of the three. The data is all in a normal college ERP. We ship a one-click CSV export in the exact AISHE column order — including the awkward fields like "students from outside the state" and "permanent faculty by gender by qualification".

The pattern

All three problems are the same problem: capture data when it happens, in the format the report needs, in the same database every other workflow runs on.

Most accreditation tools sell a "report-builder" — a wizard that pulls from your existing spreadsheets and produces formatted PDFs. The wizard works on the data it has. But the data it has is the rolled-up, lossy, post-hoc data — not the original event.

The other approach: capture the event in canonical form, generate the report as a SELECT.

We picked the second.

What we don't claim

• The report doesn't write itself. Your IQAC coordinator still reviews the numbers, writes the narrative, attaches evidence files, signs off.
• It doesn't fix bad data. If your placement office records every offer as "Company X", you'll get a report showing one employer. Garbage in, garbage out.
• It doesn't replace peer team interpretation. They'll still grill you on why CO-3 attainment dropped 8% last year. The report just hands them the numbers; you explain them.

What we do claim

A college that runs day-to-day operations through School Console — admissions, exams, placement, finance, HR — can produce all three reports live, on demand, in under a minute each.

We've shipped this. Request a demo — we'll generate one of the three reports on placeholder data while you watch.