What international schools should verify about exams, gradebooks, and report cards

Map the school’s structure

Record campuses, countries, time zones, academic calendars, programmes, subjects, cohorts, grading scales, assessment authorities, reporting periods, languages, users, and family audiences.

Ask which rules are global, programme-specific, campus-specific, or required by a local authority. Name who approves differences and how reports explain them.

Verify time and language

Test assessment date, submission time, marking time, moderation time, report time, notification time, daylight-saving changes, overnight imports, device clocks, and integration retries.

Check labels, status meaning, dates, names, scales, family communication, accessibility, translation quality, and support language. Do not infer equivalent assessment or legal meaning from a translated label alone.

Test cross-campus assessment

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

Check whether permissions follow a person, campus, role, subject, cohort, or temporary assignment. Inspect reports and exports for accidental cross-campus exposure.

Verify governance locally

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

GOV.UK guidance is a public reference, not a universal international rule. Obtain qualified local assessment, privacy, safeguarding, security, records, accessibility, and legal review before making cross-border claims.

Make the next improvement testable

Use this guidance to improve one bounded part of what international schools should verify 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.