Build the session once, teach against it
Every other module reads its shape from here — which classes exist, which sections sit under them, which subjects are taught, when the terms run and which days are not working days. Define it once in Academics and nothing downstream has to be told again.
The workbook that gets copied forward every April
The shape of a school year usually lives in three or four places at once, and they disagree by the second week of term. Academics keeps one parented structure with a change log against it, and a new session can be cloned from the previous one instead of retyped.
A class-and-section workbook duplicated each session
A wall calendar of terms, exam weeks and holidays
A subject allocation sheet held per department
Promotion decisions pencilled onto a class printout
Academics, screen by screen
Each of these is a screen or a service in the module rather than a heading on a roadmap.
One institution tree
Institution, campus, department, programme, grade, class, subject group, section and subject are nodes in a single parented tree, each one active, archived or draft. Archiving is a status rather than a delete, so records attached to a retired class stay readable.
A session with typed terms
Terms are marked as instruction, exam, break, result or holiday, holidays are listed against the session, and the working-day count is computed from the two rather than counted on a calendar.
Classes, sections and houses
A class carries a capacity and shows how much of it is used. Houses are a separate grouping from sections, so a house can cut across classes the way it does in practice.
Subjects, curriculum, competencies
A subject directory with subject groups and teacher mappings; a curriculum blueprint per grade recording the board or framework, its version and credit hours; and competency frameworks organised into domains and attached to subjects.
Promotion rules, per class
Minimum attendance, minimum pass mark, how many subject failures are tolerated, and whether promotion is automatic, manual or conditional — with a partial failure routed to a compartment instead of to somebody’s judgement.
A change log with both sides of the change
Creating, editing, deleting, archiving, publishing or cloning a session, class or subject records the field values before and after, and the person who made the change.
The same row, read from somewhere else
The point of an ERP is not that it has a lot of modules. It is that a fee concession, an attendance shortfall and a report card are all reading one record. These are the places Academics touches.
Attendance
The minimum-attendance figure in a promotion rule is the same percentage the attendance register computes. One number, not two policies that drift.
Timetable
The grid is built against these classes, sections and subjects, and against the periods defined on this session.
Examinations
Report cards are issued against this class, section and subject list, so a subject renamed here is renamed on the report card.
What Academics does not do
Stated here rather than discovered in week three. If something you need is on this list, ask before you buy — it is a better conversation than the one after.
The “simulate” button on the promotion-rules screen counts the active students in the class. It does not evaluate the rule against their marks — read it as a headcount, not a dry run. The promotion itself is run from the students module, where each decision is promote, retain or graduate and the batch is recorded.
Competency frameworks are structure. They record which domains a framework contains and which subjects it applies to; they do not score a student against a competency.
A curriculum blueprint holds the plan for a grade — board, version, credit hours, subject links. Lesson-level delivery and day-to-day teaching notes are not modelled here.
Set your institution up on Elevate
Start on the free plan for up to 250 students. Paid plans begin at ₹1499 per month, billed to the institution.