Scholiv
Custom school management software
Admissions, attendance, exams, fees and staff on one platform.
For schools and institutes where admissions, attendance, examinations, fees and staff records currently live in five unconnected places. Built around your academic structure, your grading scheme and your fee heads rather than a template that assumes someone else's.
Screens
What it looks like
4 screens from the working demo — the same data you will see if you open it.
The problem
Why this gets built
Fee follow-ups live in a diary, attendance is a paper register photocopied at term end, and marks are typed into a spreadsheet three times before a report card appears. None of it talks to each other, so the principal's simplest question takes a day to answer.
Who it is for
Fit
Schools from primary through senior secondary that have outgrown registers and spreadsheets.
Capabilities
What the system does.
Student records
One profile per student carrying admission details, guardians, contacts, documents and history.
Attendance
Class-wise daily marking with absence patterns surfaced rather than buried.
Timetable & classes
Sections, subjects and teacher allocation with clash detection.
Exams & grading
Term exams, marks entry, grade computation and printable report cards.
Fees & receipts
Term-wise fee heads, part payments, receipts and an outstanding list that is actually current.
Staff administration
Teaching and non-teaching records, attendance and payroll inputs.
See it running
Scholiv is a clickable demo — open the modules, browse the tables, see how the screens fit together.
Buying decision
Why off-the-shelf falls short here.
Every school is convinced its requirements are standard until it tries to buy software. Then the grading scheme does not fit, the fee heads do not map, the section and stream structure is wrong, and the term structure assumes two where there are three. These are not edge cases - they are the parts parents and boards actually see.
The usual response is to bend the school to the software: re-label a fee head, approximate a grade boundary, keep the real thing in a spreadsheet alongside. Within a year the spreadsheet is authoritative and the software is a data-entry chore that produces reports nobody trusts.
A custom build takes the academic structure as given. Your streams, your sections, your weightages, your concession rules and your fee heads go in as they are, so the report card and the fee receipt come out right the first time and nobody maintains a parallel copy.
Comparison
Packaged product vs a custom build.
The differences that decide it, for this sector specifically.
| Aspect | Packaged product | Custom build |
|---|---|---|
| Grading | A fixed scheme with configurable boundaries | Your scheme, including weighted internals, practical components and subject-wise rules that differ by stream |
| Fee structure | Flat heads with a discount percentage | Head-wise structure with concessions, siblings, staff wards, instalments and late fees as rules rather than manual edits |
| Academic structure | Class and section | Streams, electives, combinations and houses as your school defines them |
| Report cards | A fixed template | Your format, your remarks, your signatures, produced in bulk without a design round each term |
| Attendance | Daily present or absent | Period-wise where it matters, with the leave and medical categories your policy recognises |
| Parent access | A generic app | Only what your school wants visible, in the languages your parents actually read |
Integrations
What it connects to.
A system that cannot reach the tools already in use becomes another island. These are the connections this sector normally needs.
Accounting
Fee collection and staff payroll posted to Tally or Zoho Books, with head-wise revenue preserved.
Payments
Online fee collection with UPI, card and netbanking, reconciled against the receipt automatically.
Biometric attendance
Staff and student readers, with phone-based marking for classes where hardware is impractical.
Messaging
Attendance, fee and circular notifications over WhatsApp and SMS to the number on record.
Board portals
Export formats that match what the board's own upload expects, instead of retyping.
How it runs
From first conversation to cutover.
Indicative for a build of this shape. The parallel run is not optional — nothing is retired until the numbers agree.
- 1-2 weeks
Discovery
We take your fee structure, grading scheme, a real report card and one term's timetable.
- 4-7 weeks
Core build
Student records, fees and attendance first - the three things that touch every parent.
- 3-4 weeks
Term pilot
One section or one stream runs on it through a real fee cycle and a real assessment.
- 2-3 weeks
Rollout
All classes, parent access and staff records switched on, timed to a term boundary.
After rollout
What changes day to day.
- Report cards come out of the system in the school's own format instead of being assembled in a spreadsheet each term.
- Fee follow-up works from an accurate outstanding list rather than a diary, including concessions and instalments.
- Attendance, marks and fees describe the same student record, so a parent question has one answer.
- Staff spend term-end on teaching rather than on transcription.
Described qualitatively on purpose. We do not publish percentage improvements we cannot attribute to a named client with their agreement.
Questions
Common questions.
Can it handle multiple sections and streams?
Yes. Classes, sections, subjects and teacher allocation are configured per academic year, so a school can run different streams without needing separate systems.
Does it generate report cards?
Yes. Marks entry feeds grade computation and printable report cards in your own format, including term-wise and consolidated views.
How are fees and outstanding amounts tracked?
Fee heads are defined per class and term, with part payments, receipts and a live outstanding list rather than a reconciliation at term end.