01 — Entry
Enter once.
Lecturers enter or upload continuous assessment and examination scores for the courses allocated to them. Score ranges validate on entry, and incomplete entries are visible before anything is submitted.
Solution — Results
Script to Senate. Sorted.
Five stages, four sets of eyes, one audit trail. The Result Processing Engine moves a score from a lecturer’s desk to a student’s phone without a spreadsheet leaving anyone’s laptop.
Scroll
4 approval stages, 0 spreadsheets
Nobody can enter, approve and publish the same result. Every stage is a distinct role with distinct permissions, and every change is logged with who, when and what it was before.
How it works
From a score sheet to a student’s phone.
- 01 Lecturer Enters or uploads scores
- 02 HOD Reviews, queries or approves
- 03 Dean Approves at faculty level
- 04 Senate Approves at institutional level
- 05 Student Sees the result and new CGPA
02 — Departmental review
Query with context.
The HOD reviews, queries or approves at course level. A query returns to the lecturer with a comment thread attached to the record itself — not as a phone call that nobody can later evidence.
03 — Faculty approval
Four eyes. Always.
The Dean reviews at faculty level with visibility of distribution and anomalies. Nobody signs off their own work, because entry, approval and publication are held by distinct roles by design.
04 — Senate approval
Signed, and stamped.
Senate approves at institutional level. The approval is recorded with a timestamp and an identity, and post-approval amendments follow their own controlled workflow.
05 — Publication
Published in a click.
Approved results become visible to students immediately. GPA, CGPA, class of degree and academic standing compute automatically across every semester and session.
The product
Look closer.
Seven things the engine does that a spreadsheet cannot.
What this changes
Results published in days, not terms.
Separation of concerns
Nobody can enter, approve and publish the same result. Every stage is a distinct role with distinct permissions, enforced server-side rather than by convention.
Full auditability
Every score change is logged with who, when and what the previous value was. Post-approval amendments follow their own controlled workflow with its own approval trail.
Automatic academic standing
Probation, withdrawal and progression determinations are computed against your senate-approved regulations — consistently, for every student, every session.
Transcript-ready from day one
Because results are structured and complete at the point of approval, transcript generation is a query rather than a research project.
The other end
Senate approves. Your CGPA updates.
No noticeboard, no crowd, no photograph of a printout circulating on WhatsApp. The result appears where the student already is.
- Semester results and running CGPA the moment they are approved
- Only approved results are shown — pending results stay hidden
- Class of degree and units passed computed across every session
- The same record that produces the official transcript
Request a demo
See the result engine on your regulations.
Bring your grading scale, your carry-over rules and your approval hierarchy. We’ll show you the engine running against them.