Academics
Questions leaders ask about exams, gradebooks, and report cards
Questions leaders should ask about exams, gradebooks, and report cards before approving a system, covering assessment integrity, workload, governance, reporting, and outcomes.
Ask what decision improves
Which assessment, marking, moderation, reporting, or correction decision is currently slow, inconsistent, difficult to explain, or dependent on one person?
Ask for baseline, affected subjects or campuses, outcome, acceptance test, accountable owner, review date, and what the school will not attempt in the first phase.
Ask what each value means
How are assessment, component, attempt, submission, mark, grade, scale, percentage, weighting, rubric, comment, absence, late, missing, exempt, pending, moderated, approved, published, and corrected defined?
Who approves calculation, rounding, weighting, resit, special consideration, withdrawal, transfer, duplicate, missing-value, and report-finalisation rules? How are changes recorded and communicated?
Ask about real exceptions
How does the system handle missing submission, late work, absent learner, amended mark, moderation adjustment, duplicate entry, changed grading period, withdrawn learner, report correction, access failure, and outage?
Ask what the teacher, administrator, leader, learner, family, records team, IT, and support team see. Record manual steps, permissions, evidence, escalation, and owner.
Ask how leadership will know
The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. Ask who reviews access, corrections, exports, retention, and incidents.
GOV.UK guidance emphasises accountable and secure handling of school data. At 30, 60, and 90 days, review completeness, timeliness, moderation, report confidence, staff effort, support demand, and the agreed outcome.
Make the next improvement testable
Use this guidance to improve one bounded part of questions leaders ask about 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.
