Twelve modules, one record
Each one is a part of the school day rather than a product tier. They share a single set of students, staff and dates, so a fee concession, an attendance shortfall and a report card are all reading the same row.
What gets taught, and how it is marked
The academic spine: the structure a session is taught against, the papers and report cards that come out of it, and the books that support it.
Academics
Build the session once — departments, streams, classes, sections, houses and the subject directory — then map curriculum and competencies onto it. Promotion between sessions runs off rules you set rather than a manual re-entry.
Examinations
Blueprint a paper, schedule the exam, enter grades on a keyboard-driven grid, and generate report cards from the marks already in the system. Papers can be edited in a Word-style editor and kept in a reusable library.
Library
A catalogue with issue and return against real student records, so an outstanding book is attached to a person the rest of the platform already knows about, and lending rules live in settings rather than in a librarian’s memory.
The things that happen every morning
Who is present, who is teaching which period, and what the school needs to tell people. These are the ones staff reach for before nine.
Attendance
Fast per-class entry, a monthly register that finalises, and an eligibility engine that turns a shortage into a letter you can send. Leave is recorded against the same record, so a shortfall reflects approved absence.
Timetable
A grid built against real periods and teacher loads, with conflict detection while you edit rather than after you publish, and a substitution board for the morning a teacher calls in sick.
Notices
Publish a notice against an audience built out of the register — the whole school, named classes, named sections, named students — instead of a distribution list somebody maintains by hand. Students read it on their dashboard notice board and their messages page, which are the surfaces that exist.
The register, the payroll, and the premises
Students and staff as records rather than spreadsheets, plus the buildings and vehicles that have to be allocated to them.
Students
Admission through to alumni on one record: the admission form, documents, bulk operations for the work that is genuinely bulk, and a student portal students sign into themselves.
Payroll
Salary structures assembled from rules you write, a run you can review before it commits, and slips generated from the result. Attendance and leave feed the calculation instead of being re-keyed into it.
Transport
Routes and stops planned on a real map with driving distances from a routing service, passengers allocated to vehicles from the student register, and a live trip view whose position comes from the device travelling with the vehicle — not from fitted tracker hardware.
Hostel & events
Buildings, rooms and beds allocated to named students, with roll call and outpasses for the evening. Events and the school calendar sit alongside it, because both are about who is expected to be where.
What was billed, what was collected, what you can prove
Fee demands and receipts on one side, and exportable reporting on the other, both reading the same rows the rest of the platform writes.
Fees
Fee heads, concessions and automated demand generation, then a cashier session that reconciles at the end of the day. A receipt is tied to the demand it settles, so what is outstanding is derived rather than tracked separately.
Reports
Reporting over the same collections the modules write, exportable to Excel and PDF. It reads live data rather than a nightly copy, so a report run at noon reflects the fee collected at eleven.
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.