What teachers need from exams, gradebooks, and report cards

A clear starting point

Teachers need to know which assessment they are marking, which learners and components are included, which scale applies, what deadline matters, and where the current instructions live.

The system should make assessment, submission, mark, grade, missing, absent, late, pending, moderated, approved, published, and corrected meanings understandable without requiring administrative expertise.

A workable marking path

Provide a short route for reviewing evidence, entering a mark, adding feedback, saving progress, spotting an out-of-range value, and requesting help. Do not make a teacher hunt through unrelated configuration.

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

Safe judgement and correction

Teachers need to know what they may change, what requires moderation or approval, how to correct a mark, how history is preserved, and how a learner or family receives the right explanation.

The U.S. Department of Education data-quality guidance links reliable information with definitions, rules, validation, infrastructure, and professional learning. Controls should support judgement rather than hide it.

Support in the real cycle

Review device access, connectivity, accessibility, deadlines, shared work, support coverage, training, permissions, privacy, safeguarding, records, security, backup, restoration, retention, and report confidence.

At 30, 60, and 90 days, measure marking completeness, correction time, moderation, staff effort, support demand, access exceptions, and outcome. GOV.UK guidance emphasises accountable handling of school data.

Make the next improvement testable

Use this guidance to improve one bounded part of what teachers need from 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.