How teams document exams, gradebooks, and report cards

Document the decision

Every material assessment decision should state purpose, subject, cohort, campus, grading period, assessment, owner, audience, deadline, evidence, approval, effective date, and review date.

Include what was considered, what was rejected, what remains uncertain, what action follows, and what would cause the decision to change.

Document the record and formula

Define assessment, component, attempt, submission, mark, grade, percentage, weighting, rounding, boundary, missing, absent, late, exempt, pending, moderated, approved, published, and corrected.

Keep formula, version, input, output, approver, exception, report effect, and correction history. A screenshot of a result is not a complete record of how it was produced.

Document the workflow

Map setup, submission, marking, feedback, moderation, approval, publication, report, correction, resit, special consideration, withdrawal, transfer, archive, support, and incident handling.

Record view, create, mark, review, moderate, approve, publish, export, correct, archive, and delete permissions by role, subject, cohort, campus, learner, family, supplier, and support user.

Document evidence and change

The U.S. Department of Education data-quality guidance connects dependable data with definitions, rules, validation, infrastructure, and professional learning. The governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring.

At 30, 60, and 90 days, review corrections, moderation, report confidence, access exceptions, staff effort, support demand, 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 how teams document 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.