How it works
A day at school, step by step.
These flows illustrate how the platform's enforced states guide everyday work. They describe platform behavior for illustration — the staff, parent, and admin applications that carry them are under active development.
Admissions, reviewed properly
Every application moves through explicit states — nothing slips from enquiry to classroom by accident.
Apply
Application recorded as applied with the school's required details.
Review
Administrators approve, reject, or record a withdrawal — each a deliberate action.
Enroll
Approved applicants become student records with enrollment history.
Attendance in minutes
Sessions belong to one class and section, so registers always match the room in front of the teacher.
Open session
Pick the class, section, and date; the right student list loads.
Mark
Present, absent, late, half-day, or holiday — each state visually distinct.
Confirm
Review before submitting; the server confirms what was recorded.
Exams you can defend
Marks travel a one-way street toward publication. Parents see results only after the school publishes them.
Schedule
Create the exam and attach its subjects with maximum marks.
Enter
Teachers enter marks for their permitted subjects.
Publish
Completed exams publish; published results are frozen and undeletable.
Fees without double-charging
Totals are computed on the server, and payments reference the invoice — so the books always reconcile.
Draft
Build the invoice; totals are calculated server-side, never trusted from the screen.
Issue
Issue to move from draft to payable, with overdue tracking.
Record
Record each manual payment once — repeat submissions reuse the same reference.
Bring your school's records into one system.
Walk through the proposed onboarding above, then request a demo — every step from there is confirmed with you.