Academics
How to review exams, gradebooks, and report cards
How to review exams, gradebooks, and report cards after launch by checking calculation, moderation, record quality, corrections, access, support, reporting, workload, and outcomes.
Review the intended work
Return to the original decision: set an assessment, mark work, moderate a judgement, approve a result, publish a report, answer a family question, or correct a record.
Observe the complete path and compare expected and actual steps, manual work, exceptions, handoffs, time, and evidence.
Review quality and control
Check learner, subject, cohort, assessment, component, attempt, submission, mark, grade, scale, calculation, report, moderation, permission, export, correction, and audit history.
The U.S. Department of Education data-quality guidance links quality with definitions, rules, validation, infrastructure, and professional learning. Test missing, late, absent, amended, moderated, duplicate, withdrawn, and changed-period cases.
Listen to the people doing the work
Ask teachers, department leads, administrators, records, leaders, learners, families, IT, support, privacy, safeguarding, accessibility, and security owners what is clear, slow, inaccessible, unsafe, duplicated, or missing.
Review support questions, training gaps, private copies, unowned corrections, reports that disagree, and calculations that cannot be explained.
Choose the next action
At 30, 60, and 90 days, decide whether to expand, repair, consolidate, narrow, or hold. Record evidence, owner, due date, limitation, support need, and next review.
GOV.UK guidance emphasises accountable handling of school data. Keep local privacy, safeguarding, records, security, accessibility, and legal review in the decision.
Make the next improvement testable
Use this guidance to improve one bounded part of how to review school exam and gradebook software. Name the owner, assessment or gradebook record, evidence, correction route, and review date so staff can apply it consistently.
Check an ordinary case and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, validation rule, permission, training note, or support route.
Record what changed, what remains manual, and who reviews the result before the next marking or reporting cycle.
Keep the decision beside its evidence so the next teacher or administrator can understand the rule without relying on informal memory.
Use the review to decide whether the change should be expanded, repaired, narrowed, or held.
Recheck the boundary when a subject, campus, grading scale, role, integration, calendar, or policy changes. A familiar workflow can carry a different access or reporting risk after a small change.

