What a weekly review of exams, gradebooks, and report cards

Review the coming deadline

Start with assessments, subjects, cohorts, grading periods, submission windows, moderation dates, report deadlines, responsible staff, and dependencies. Use the approved academic calendar and current assessment plan.

Identify what is complete, late, missing, blocked, awaiting moderation, awaiting approval, or ready for publication. Record owner, next action, evidence, and deadline rather than relying on colour alone.

Check data quality

Look for missing submissions, duplicate learners, wrong subject or cohort, stale assessment, invalid mark or grade, hidden formula, inconsistent status, unapproved change, duplicate result, and report mismatch.

Test absent learner, late work, amended mark, moderation adjustment, resit, special consideration, withdrawal, transfer, changed grading period, and correction.

Review workload and control

Ask teachers, department leads, administrators, records, leaders, learners, families, IT, and support where work waits, duplicates, depends on memory, or uses a private copy.

Check view, mark, moderate, approve, publish, export, correct, archive, and delete access; staff leavers; supplier access; backup; restoration; retention; privacy; safeguarding; accessibility; and security.

Close with action

The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. Use it to assign one owner and one evidence request for each material risk.

At 30, 60, and 90 days, review completeness, timeliness, moderation, corrections, report confidence, staff effort, support demand, access exceptions, and outcome. GOV.UK guidance emphasises accountable school-data handling.

Make the next improvement testable

Use this guidance to improve one bounded part of what a weekly review of 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.