Skip to main content

Features

Every module, and the problem it solves.

SchoolerHub is organised around the work your school already does. Each module below starts with the problem, then explains how the system handles it and what changes for your team.

Student Management

The problem: a student's details live in an admission register, their fees in a ledger, their bus route on a list, and their certificates in a file cabinet.

SchoolerHub keeps one record per student, and every other module reads from it. Admission number, photograph, date of birth, blood group, address, class, section, roll number and enrolment status sit alongside guardian details, uploaded documents, fee history, transport assignment, attendance and marks.

Guardians

Primary and secondary guardian with relationship, occupation and contact number

Lifecycle

Admission, year-end promotion, exit with clearance checks, and alumni records

Bulk import

Bring existing students in from a spreadsheet instead of retyping them

Documents

Birth and transfer certificates, community, Aadhaar, vaccination and medical records

Outcome: one search answers the question, instead of three people checking three places.

Fee Management

The problem: knowing who has paid, who hasn't, and how much is outstanding takes a day of reconciliation.

Define fee structures with individual line items and categories, set them term-wise or one-time, and assign them to classes or students. The system generates each student's charges and invoices, records payments against them, and keeps a running picture of what remains due.

Payments & receipts

Multiple payment methods, allocation across charges, printable and PDF receipts

Concessions

Percentage or fixed reductions recorded as approved records with a status trail

Refunds

Refunds allocated back against the original charges, not adjusted by hand

Dues & reminders

A live list of pending and overdue students, with reminders sent from the same screen

Outcome: your accounts team starts the day with the pending list already built.

Transport

The problem: transport fees vary by stop, students change routes mid-year, and vehicle paperwork expires without warning.

Define routes and their stops, set a fee against each stop, and assign students to a route and pickup point. The correct transport fee links automatically to that student's fee account — so a route change updates the dues rather than requiring a manual recalculation.

Routes & stops

Ordered stops, pickup and drop direction, and per-stop fee amounts

Vehicles & drivers

Vehicle records, driver records and vehicle-to-driver assignment

Vehicle documents

Registration, insurance, fitness, permit and pollution certificates with expiry dates

Transport dues

Outstanding transport fees reported separately as well as within total dues

Outcome: route, student and fee stay in step, and no certificate quietly expires.

Parent Communication

The problem: the same notice gets retyped into a dozen class groups, and fee reminders are sent one number at a time.

Publish announcements to a chosen audience, and send fee reminders and absence alerts to the parents of selected students over WhatsApp and SMS. Messaging is delivered through MSG91, using pre-approved WhatsApp Business Platform templates.

Fee reminders

Sent from the dues screen to the parents who actually have a balance

Absence alerts

Triggered from attendance so parents know the same day

Announcements

Published by audience and type, with a record of what was sent

Delivery record

Messaging activity recorded in the system for staff reference

Messaging is configured per school during implementation and depends on your own WhatsApp Business Platform and SMS sender approvals. Charges are usage-based; the service does not include unlimited messaging.

Outcome: the right parents get the right message, from the record that already knows who they are.

Attendance & Leave

The problem: attendance registers are hard to summarise, and nobody notices a pattern until it's a problem.

Mark daily attendance by class and section, record staff attendance separately, and manage leave requests for both students and staff with an approval status.

Outcome: attendance becomes data you can report on, not a stack of registers.

Academics, Timetable & Homework

The problem: academic structure is rebuilt from scratch every year, and homework tracking lives in a notebook.

Set up academic years, classes, sections and streams, define subjects and curriculum, and build a period-based timetable. Teachers record homework assignments per class and subject and track submissions against them.

Academic years

Records are scoped by year, so history stays intact when a new year starts

Timetable

Periods and slots per class, with a teacher view of their own schedule

Calendar & events

School calendar, events and activities with participation tracking and reports

Teacher workspace

One screen for a teacher's classes, timetable, attendance and homework

Outcome: teachers spend less time on administration and more on their classes.

Examinations, Grading & Certificates

The problem: report cards are assembled in a spreadsheet each term and formatted by hand.

Create exam types and schedules, enter marks per subject, and apply configurable grading scales with grade bands. Report cards are generated from a template and printed in batch, as are transfer, conduct and other certificates.

Grading scales

Define your own bands and boundaries rather than accepting a fixed scheme

Report cards

Template-driven, generated per student, printable individually or in batch

Certificates

Certificate templates with batch printing and an issued-certificate record

Promotions

Year-end promotion with recorded outcome per student

Outcome: results day stops being a formatting exercise.

Library

The problem: nobody is quite sure which books exist, which are out, or who has had one since last term.

Catalogue books with authors, publishers and categories, and track each physical copy individually with its own condition and status. Issue and return through a circulation screen, with overdue detection and fines.

Outcome: the library is a managed collection rather than an honour system.

Inventory & Assets

The problem: stock runs out unnoticed, and nobody can say where a projector went.

Track stock items across locations with recorded movements and running balances, manage suppliers and purchase orders through to receipt, and maintain a register of school assets with assignments, condition and maintenance history.

Outcome: purchases are planned rather than urgent, and assets are accounted for.

Staff & HR

The problem: staff records, qualifications and verification documents sit in personal folders.

Maintain staff profiles and departments, record employment history, store staff documents such as photo ID, degree and experience certificates, appointment letters and police verification, and manage leave requests and staff attendance.

Outcome: an inspection request takes minutes, not an afternoon.

Documents & Compliance

The problem: an insurance certificate expires and the first anyone knows is when it's needed.

Store student, staff and vehicle documents with optional expiry dates. The system surfaces what is missing and what is about to lapse, and a compliance report shows which students still owe a document.

Files are stored on private storage and served only through authenticated, authorisation-checked routes — never from a publicly guessable URL.

Outcome: renewals happen on schedule instead of in a rush.

Dashboard & Analytics

The problem: management asks a question and three staff members go looking for the answer.

A dashboard summarises the figures management is usually asking for, with dedicated reports behind it for finance, admissions, students, operations, compliance, library, transport and inventory — plus data exports when the numbers are needed elsewhere.

Outcome: the answer is on screen before the question gets asked.

Roles, Access & Audit

The problem: everyone shares one login, so everyone can see everything.

Each person gets their own account with a role — school administrator, staff, teacher or parent — and sees only the modules that role needs. Every record is scoped to your school, so one school's staff can never reach another's data. Significant actions are recorded with the acting user and timestamp.

Outcome: access matches responsibility, and there is a trail when it matters. See our security page.

Which of these matters most to your school?

Tell us, and we'll shape the demonstration around it.