College ERP software, shaped round the academic year.

Yes, and it is usually the thing we design backwards from. An affiliated college spends the year producing the same documents — nominal rolls at registration, subject-wise enrolment for each of the eight semesters of a four-year programme, internal marks uploaded before the university's cut-off, condonation lists, transfer and migration certificates — and in most colleges each one is assembled by hand from a different register. The format the university publishes keeps changing; the data underneath it does not. So we model the data properly, with one student record carrying programme, batch, section, elective choices and every mark and period recorded against it, and treat each return as an export written over that. When the format is reissued in a new shape, changing the export is an afternoon rather than a season. Where the university accepts a portal upload, we generate the file in the shape the portal wants instead of someone retyping four hundred rows.

Partly, and it is worth being precise about which part. The system holds the data; the IQAC still writes the institution's account of itself. An AQAR or an NIRF submission is largely a request for counts a college already has somewhere — strength by programme and category, faculty with qualifications and years of experience, student-to-teacher ratio, pass percentages by batch, scholarships disbursed, placements. What makes those painful is not the questions, it is that the answers sit in six offices and get collected by circulating a spreadsheet in the final fortnight. If admissions, examinations, fees and staff records share one system, most of those cells become a query. The real work is earlier: making sure the fields exist at all — category, entry qualification, year of joining, sanctioned intake against admitted strength — because a count nobody recorded in July cannot be reported in March.

Fees are the module we build first in most institutions, because it has the most exceptions and the fastest payback. A fee is rarely one number: it varies by programme, by year of joining, by management or government quota, by hosteller and day scholar, and it arrives in two or three instalments against dates that shift. Over that sit concessions — staff wards, siblings, merit waivers, first-generation graduates — and government scholarships that land months after the due date and have to adjust against a balance the student was already being chased for. We build the structure as rules the office can set for a new batch without calling us, and every receipt, adjustment, fine and refund posts to one running balance per student. The dues list a correspondent asks for on a Monday morning is then read off the system rather than prepared for it.

Hourly and subject-wise is the only version that is actually useful in a college, so that is the default. Day-level attendance answers whether a student reached the campus, which is not the question the regulations ask — eligibility and condonation are decided on attendance per subject, and a student can be on campus all day while missing the two theory hours that matter. So attendance is captured against the timetable: period, subject, faculty, section, for each of the five to eight hours in the day, marked by the person taking the class on a phone in the room rather than copied into a register and typed up the following week. The percentage per subject is then live instead of computed at term end, the shortage list exists while something can still be done about it, and a tutor can see the pattern in one student's absences rather than the total.

They are two different things and the system should keep them apart. Internal assessment belongs to you — cycle tests, assignments, seminars, practical records, an attendance component — with weightings the department sets and your own approval before anything locks. The university examination does not belong to you: you register candidates, submit internals in the university's format by its date, and receive results back to post against the same student. Between those two sits the part colleges do by hand. Arrears and re-registration. Students carrying subjects from an earlier regulation after a syllabus revision. Revaluation that changes a figure already published. Supplementary attempts that have to reconcile with the original. We treat a mark as belonging to a student, a subject, a regulation and an attempt, which is what makes an arrear student's transcript come out right instead of being reassembled by whichever clerk remembers the case.

Yes, and they belong in the same system rather than beside it, because both are money and both are safety. Hostel covers room and block allotment, vacancy at a glance, in and out movement, leave and late entry with the warden's record of it, and mess charged per day rather than as a flat figure — a student who went home for three weeks should not be billed as though they ate. Transport covers routes, stops, fee slabs by distance, and which student is on which bus, which is what matters on the afternoon a parent rings to ask where their child is. Both post to the same ledger as tuition, so a cleared tuition balance and an outstanding hostel balance read as one position instead of two. Both use the same contact record, so the warden and the tutor are not keeping parallel lists of the same students.

A deliberately narrow view, because a full parent portal is mostly a login nobody remembers. What a parent wants is three things: attendance as it stands, fees due with the date, and marks once published. Those go out when they happen — a message the day a shortage crosses the line, not a summary in the last week of term when nothing can be done — and are readable without installing anything, because a password set once in June will not be recalled in October. Everything sent is logged against the student, so when a parent says they were never informed, the office answers from a record rather than from memory. What we would talk you out of is a channel that lets several hundred parents message faculty directly; it becomes a thing the institution manages instead of a thing that helps, and the messages that matter get lost among the ones that do not.

Rarely all of it, and never on an opinion formed before we have looked. Most institutions are running something — a package bought years ago, a set of workbooks, occasionally a system a former staff member wrote — and the honest position is that parts of it work. The usual route is to move one module across into real daily use while everything else stays where it is, and fees or attendance is normally that module because either is verifiable within a month by anyone in the office. Data comes across in the same step: student masters, outstanding balances, marks history for students still on the rolls, reconciled against your own figures before anybody is asked to trust it. Opening balances that do not agree get found during migration rather than after go-live. If your existing licence turns out to cover most of what you need and the gap is two modules and an export, we will say so.

It is the week the system is designed for rather than the week it gets tested. Load in a college is not spread evenly across the year: counselling and admission run over a few weeks, and in those weeks the office creates records, collects fees, prints receipts and answers enquiries with a queue at the counter and every terminal on the same screens at the same hour. Systems that were comfortable in February are the ones that give way in July, and it is almost never the whole system — it is one report or one search that nobody noticed was merely slow against a thousand records and is unusable against fifty thousand. So we size against that week: load tested before the season, heavy reports served off something other than the live counter path, and the counter kept fast even while a management report is running. Results day is the same problem in a shorter window.