Twelve modules that share one record of each child
Nothing here is a bolt-on. A student admitted in module one is the same student the register marks, the mark sheet grades, the invoice bills and the leaving certificate names — which is why the numbers agree.
From the first enquiry to an admission number
An enquiry from the school website arrives with its own reference and sits in a queue the office works through, so nothing is lost between a phone call and a form. When a place is offered, the enquiry becomes an admission without retyping anything.
- Enquiries captured from the public site, each with a reference the family can quote.
- Triage by the office: assigned, answered, converted or closed with a reason.
- Admission numbers issued in an unbroken sequence and never reused.
- Guardians recorded and verified by the office — there is no self-service linking.
One profile, and the history behind it
A student's record is not a row that gets overwritten each June. Enrolments are added, so last year's class, section and roll number stay readable, and a transfer mid-year is a fact in the record rather than a correction to it.
- Class, section and roll number per year, kept as history.
- Transfers between sections, promotion, withdrawal and graduation.
- Guardian links created and revoked by the office, taking effect immediately.
- Sign-ins for students and parents, with accounts that can be suspended or restored.
- Who may see which fields depends on the relation — class teacher, subject teacher, parent, the student.
One register, one calculation, no arguments
The class teacher marks the day. The school calendar — weekends, holidays and the working Saturdays a class has but the school does not — decides which days count. A day nobody marked is counted against the figure and reported as unmarked, because the alternative is a percentage that quietly flatters everyone.
- Present, absent, late and excused, with late counting as attended.
- School calendar with holidays, working days and class-specific exceptions.
- An editing window, after which a change needs a reason and a permission.
- Corrections kept alongside the original, with who made them.
- Summaries per student, section and month, on the same calculation everywhere.
Set once, delivered to the class as it stood that day
Publishing homework takes a snapshot of who was in the class, so a child who joins next week does not silently inherit last week's work, and one who leaves stops seeing it. Attachments are validated by what the file actually is, re-encoded where they are images, and encrypted before they are stored.
- Per subject and section, with due dates and attachments.
- Files served only after the reader's right to them is checked again.
- Late joiners added deliberately; leavers removed automatically.
- Visible to parents and students on a phone.
Nothing reaches a family before it is approved
A mark sheet is one subject in one section. The teacher fills it and submits it; the office approves it, or returns it with a reason. A blank mark blocks submission — an empty cell is never read as a zero. Results are published only when every sheet is approved.
- Terms with weights that must add up to exactly one hundred.
- Grading scales, absent and exempt handled by an explicit policy.
- Report cards as fixed snapshots — reissuing a changed card needs a reason and makes a new version.
- Family screens that cannot show an unpublished result, by construction.
A receipt book that ties up
Fee schedules generate invoices; concessions reduce them; payments allocate across them in one transaction that either completes or does nothing at all. Receipt numbers run without gaps for the financial year, which is the first thing an auditor looks for.
- Money held in whole paise from end to end — never a decimal that drifts.
- Part payments, concessions, and balances that are derived rather than stored.
- Reversals as a counter-entry; the person who collected a payment cannot reverse it.
- Statements per family, and collection reports per class, day or instalment.
- Overdue worked out when asked, so it is never a stale flag on a row.
It refuses to make an impossible timetable
Bell periods are set for the year; the weekly grid is filled per section. A teacher who is already teaching in that period, or a room already in use, is rejected as the entry is made rather than found on the first day of term.
- Bell schedule per academic year, with breaks.
- One entry per section, weekday and period; edits archive what was there before.
- Teacher and room clashes refused with the reason.
- Each teacher's own day, used by meeting booking to find genuinely free time.
Reaching exactly the people it concerns
A notice is addressed to the school, to a group, to classes or to sections; when it is published the audience is resolved into a list of real people, each with their own notification and read state. Teachers can write to their own sections, and where the school wants a second pair of eyes, "send" means submit for approval.
- Scheduled notices published on time without anyone being logged in.
- Approval step for staff without publishing rights.
- Important and urgent notices also sent by email.
- Read state per recipient, so you can see what landed.
Booked against time that is actually free
A booking checks the staff member's other meetings, their teaching timetable, the school calendar and the meeting hours before it is accepted. A clash comes back with the next few free slots rather than a refusal.
- One student and one responsible member of staff per meeting.
- Reminders that only go out if the meeting is still on.
- Shared outcomes and actions that reach the family once published.
- Internal notes kept separately and encrypted — the family's copy has no such field.
Requested, approved, numbered, verifiable
Bonafide, transfer, character, merit — each moves through request, approval, generation and issue. Generation freezes the facts as they stood, gives the document a number in a gapless run and a verification code, and prints to a layout the office controls.
- The office can ask for more information before approving.
- A transfer certificate needs a clear fee balance, or an explicit override.
- Issuing a transfer certificate withdraws the student, in the same step.
- Families see a certificate only once it has been issued.
The public site, edited by the office
The website parents see is part of the system, not a separate project. Pages are built from blocks, news is written in the admin screens, and the colours are set by the school. The contact form on it lands in the enquiry queue.
- Home, about, academics, admissions, news and contact, all editable.
- Blocks: hero, statistics, cards, text, gallery, news and calls to action.
- Theme colours and buttons applied everywhere from one screen.
- Images uploaded and reused from a media library.
The parts nobody demonstrates, and everybody needs
Staff invitations, permissions, sign-in security, audit, backups, a queue for email and a health check that tells you what is wrong before a parent does.
- Staff invited by email; roles and permissions per person.
- Two-factor sign-in codes for office accounts; sign out everywhere in one action.
- An audit trail on every table: who made it, who changed it, when.
- Maintenance mode, backups and a full health report from one command or one screen.
Reading about it only goes so far
Open the demo school and mark a register, approve a mark sheet or take a fee payment. Everything resets, so nothing you do there matters.