Build the result process so published marks stop changing casually.
The important part of a result workflow is not only calculating totals. It is knowing which marks were valid, when the result became final, and who is allowed to reopen it.
Prepare subjects and maximum marks first
Before entering marks, verify the subject list, exam setup and maximum marks for the class. Validation can reject a mark that is above the maximum only if the maximum itself is correct.
Restrict entry by class/division
Use class/division scope so a teacher enters marks only for assigned students. This reduces accidental edits and keeps academic authority consistent with attendance permissions.
Validate before calculating
Marks imports and manual entry should be checked for missing students, invalid maximums, unexpected subjects and values outside the permitted range. A clean validation stage is more useful than fixing a report after publishing.
Calculate from the same verified dataset
Totals, percentage, grade and rank foundations should use the same accepted marks records. Avoid maintaining a second spreadsheet solely to calculate the “final” result after data is entered in the ERP.
Finalize when the school is ready to publish
Finalization is the operational boundary between draft and published results. Once finalized, routine editing should stop. If a correction is genuinely required, an authorized reopen should make that action deliberate and traceable.
Parent Portal should show finalized results
Parents should not see marks that are still being entered or corrected. Showing finalized results only helps the school avoid confusing families with draft values.
Practical review before finalization
- confirm student count for the class/division;
- review missing subject entries;
- spot-check maximum marks and totals;
- verify grade rules;
- check a few report-card outputs;
- confirm who is authorized to reopen after publication.