Separation of concerns
Nobody can enter, approve and publish the same result. Every stage is a distinct role with distinct permissions.
Lecturers enter or upload continuous assessment and examination scores for courses allocated to them. Score ranges validate on entry. Incomplete entries are visible before submission.
The HOD reviews, queries or approves at course level. Queries return to the lecturer with a comment thread attached to the record.
The Dean reviews at faculty level, with visibility of distribution and anomalies.
Senate approves at institutional level. Approval is recorded with timestamp and identity.
Approved results become visible to students immediately. GPA, CGPA and class of degree compute automatically across semesters and sessions.
Nobody can enter, approve and publish the same result. Every stage is a distinct role with distinct permissions.
Every score change logged with who, when and the previous value. Post-approval amendments follow their own controlled workflow.
Probation, withdrawal and progression computed against your senate-approved regulations, consistently, for every student.
Because results are structured and complete at approval, transcript generation is a query, not a research project.
| Role | Can do | Cannot do |
|---|---|---|
| Lecturer | Enter and submit scores for allocated courses | Approve, publish, or amend after approval |
| HOD | Review, query and approve at department level | Enter scores, approve at faculty level |
| Dean | Review and approve at faculty level | Enter or alter individual scores |
| Senate | Approve at institutional level, release results | Enter scores |
| ICT | Configure grading scales and course allocation | Approve results at any level |
Roles and permissions are configured to your institution during implementation. The separation above is the default.
We'll walk through a full approval cycle with data that looks like yours.
Request a demo →