What to measure after launching exams, gradebooks, and report cards

Return to the original promise

Write the outcome the launch was meant to support: more complete marking, clearer moderation, faster reporting, fewer corrections, better feedback, less duplicate work, or more dependable learner and family communication.

Keep activity measures such as logins, assessments created, or reports sent separate from quality measures such as valid results, reconciled calculations, timely corrections, and understandable reports.

Measure the records

Check assessment completeness, submission status quality, valid learner and subject links, grading-period alignment, calculation exceptions, moderation changes, duplicate results, correction rate, and report reconciliation.

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

Measure work and controls

Review teacher, department, administrator, records, leader, learner, family, IT, and support effort; training competence; accessibility; support questions; manual copies; access exceptions; exports; incidents; backup; restoration; and retention.

The U.S. Department of Education data-quality guidance links reliable information with definitions, rules, validation, infrastructure, and professional learning.

Review at useful intervals

At 30, 60, and 90 days, compare the baseline with observed results and decide whether to expand, repair, consolidate, narrow, or hold. Do not infer long-term assessment benefit from launch-week activity.

GOV.UK guidance emphasises accountable and secure handling of school data. Keep local privacy, safeguarding, records, security, accessibility, and legal review in the measurement loop.

Make the next improvement testable

Use this guidance to improve one bounded part of what to measure after launching 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.