Seven modules that share one student record
Most school software is a set of separate products that happen to be sold together, so the same child exists three times and none of the three agree. ClassNet is one system. Admit a student and they are in fees, attendance and the parent app the same instant.
Every student's record, one source of truth
The file that everything else reads from, and the one place you update when a phone number changes.
- Demographic, guardian, medical and academic detail on one record, with sensitive fields encrypted and kept out of logs.
- Bulk CSV import with per-row validation, so a bad spreadsheet tells you which line is wrong instead of failing silently.
- The full lifecycle is recorded rather than overwritten: admission, promotion, transfer, withdrawal.
- Search that matches a full name whether it is stored in one field or two, and whatever the capitalisation. Typing it the way it appears on the register is enough.
Collect fees faster, reconcile in minutes
The module that pays for the rest of the system, and the one your accountant will judge it on.
- Fee structures per class and category, with concessions and scholarships applied as rules rather than manual edits.
- Receipts, part payments and pending-payment lists that stay accurate because they are computed, not maintained by hand.
- Every approval, waiver and reversal written to an immutable audit log, with the person and the time attached.
- Collection analytics by class, term and fee head, so you can see where the gap is before the term ends.
Daily attendance in under two minutes per class
If marking attendance is slower than a paper register, teachers will keep using the paper register. This is built for a phone held in one hand.
- Mark a whole class present by default and tap only the exceptions. The common case takes seconds.
- Absentee alerts reach parents automatically, without anyone remembering to send them.
- Corrections keep the original value. Old and new are both in the record, so a changed register is visible.
- Cumulative percentages computed against your school's calendar and timezone, not the server's.
Reach every parent on WhatsApp and push
One hub for everything the school sends, so a message is never stuck inside the module that generated it.
- Notices, fee reminders, absentee alerts and result announcements all go out through the same engine.
- Every alert lands in the in-app inbox as well as being pushed, so a swiped notification is not a lost notification.
- Parent-teacher messaging that stays inside the school's system instead of a personal phone number.
- Delivery is tracked per recipient per channel, so "we sent it" is something you can actually check.
Marks in, print-ready report cards out
Mark entry, grade computation and PDF generation as one flow, with publishing under your control.
- Subject-wise mark entry with your grading scheme applied automatically, so there is no parallel spreadsheet.
- Batch PDF generation for a whole class, produced in the background so nobody waits on a progress bar.
- Nothing reaches a parent until you publish, and a mark changed after publishing is logged.
- Published cards appear in the parent app, so the office stops fielding calls asking for a copy.
No enquiry falls through the cracks
The enquiries a school loses are usually the ones nobody wrote down. This is the register that does not get lost.
- Enquiries captured from the front desk, the phone or a public form, each with an owner and a next action.
- Applications tracked through their stages, converting to a student record without anything being retyped.
- Visitor logging and gate passes with a photo, so the front desk has a record rather than a memory.
- Public enquiry forms are rate-limited and CAPTCHA-protected, so the pipeline stays signal rather than spam.
One platform, many schools, hard isolation
The foundation the other six sit on, and the part that matters most if you run more than one campus.
- Each school is an isolated tenant, enforced by the database rather than by application code.
- One account per person, holding as many roles as they actually have, with per-user grants and revokes on top.
- Academic years, classes, sections and subjects configured once and inherited everywhere else.
- Every sensitive action is audited: permission changes, financial transactions, publishing results.
Before you ask for a demo
How long does it take to get a school running on ClassNet?
Most of the work is data, not software. Once your student list, class structure and fee heads are ready, a school can be configured and importing in days rather than months.
Can we use only some of the modules?
Yes. The modules share one student record, so you can start with student records and fees and switch on attendance, communication or results later without re-entering anything.
Do parents need to install an app?
Parents get the app on Android and iOS for fees, attendance, report cards and messages. Schools that are not ready for that can reach parents on WhatsApp instead, using the same communication hub.
Can we collect fees online through ClassNet?
Not yet. The fee module records and reconciles collections made at the school, and online payment collection is planned for a later release. We would rather say so than imply otherwise.
See the modules working together
A walkthrough with real data beats any feature list. Thirty minutes, and honest answers about what is ready today.