One-time setup
Configure once and reuse every term: exam types (Unit Test, Mid-Term, Pre-Board, Final, Practical), grading scales, component templates, the marks-entry policy, and hall-ticket setup.
The most detailed module in the product, because exams involve money-grade trust: once a result reaches a parent, it's an official academic record. So every exam follows a careful, step-by-step lifecycle that prevents half-finished or unchecked marks from ever being published.
A school sets up an exam, teachers enter marks, a coordinator checks them, and the admin locks and publishes results. Everything flows from one design choice — two layers of control: the exam's overall stage (DRAFT → OPEN → ENTRY LOCKED → PUBLISHED) and each individual mark's state (Draft → Submitted → Verified → Locked) inside the OPEN stage.
Moving forward is only allowed when the current stage's work is genuinely complete; moving backward to fix something requires a written reason and is recorded in history. That's what guarantees a parent never sees a result built on missing or unchecked marks.
Configure once and reuse every term: exam types (Unit Test, Mid-Term, Pre-Board, Final, Practical), grading scales, component templates, the marks-entry policy, and hall-ticket setup.
Every exam moves through four stages in order — DRAFT, OPEN, ENTRY LOCKED, PUBLISHED — with guards that refuse to advance until the current stage's work is truly complete.
Split a subject into parts — Theory + Practical, or Written + Oral — each with its own maximum, pass mark and weight (weights must add up to 100%). A subject can also be one simple mark out of 100.
Each set of marks travels Draft → Submitted → Verified → Locked. A coordinator's second pair of eyes catches typos before they become official. Any step backward needs a written reason of at least 20 characters.
Published results are frozen as snapshots. To fix a mistake, the admin rolls the exam back with a reason, re-locks the marks, and re-publishes — creating a fresh, version-bumped record. Results never silently change.
Issue admit cards to a whole class, block ineligible students (e.g. outstanding fees) with an override option, allocate seats and rooms, and print cards as a PDF in the school's chosen layout.
Two views: a class-wide tabulation sheet for the office, and a per-student report card for the parent — subject-wise marks and grades, percentage, result, and rank, all frozen at publish time.
Permissions follow the lifecycle: teachers enter marks, a coordinator verifies and locks, the admin publishes. Each stage controls exactly which actions are allowed and who may take them.
The admin creates the exam, schedules each paper with a date, room and invigilator, and defines how each subject is marked — including any Theory + Practical split.
Teachers type marks on a grid — one row per student, one column per part — saving drafts as they go, then submit for verification. A coordinator verifies them or sends them back with a reason.
Marks entry is closed — no new marks can be typed. The verified marks are locked, and the exam is ready to publish only when every mark is locked.
In one action the system totals every subject, applies the grading scale, decides Pass / Fail / Compartment, computes rank, freezes the result, and makes it visible to parents.
A published result is an official document a parent may have already screenshotted or downloaded. Because each one is frozen as a snapshot, any correction is deliberate, audited, and produces a new official version — a result never silently changes under a parent. It's a small detail that signals real seriousness about academic records.
Honest note: our own team (the Application Admin) has no access to a school's exam configuration — it belongs to the school.
A 30-minute walkthrough tailored to your institution. Bring your current admissions process; leave with a clear migration plan.