Multi-campus guide to exams, gradebooks, and report cards

1. Decide what is shared

List common standards for learner identity, subject, cohort, assessment, component, attempt, mark, grade, scale, weighting, rounding, moderation, report, correction, role, retention, and support.

Then document legitimate local differences in programme, calendar, language, grading scale, reporting authority, policy, staffing, and family communication. Shared does not mean identical.

2. Map the records

Identify authoritative systems for learners, teachers, subjects, cohorts, campuses, assessments, components, attempts, submissions, marks, grades, reports, moderation, and archive.

Test duplicate identity, transfer, withdrawal, shared subject, resit, special consideration, changed grading period, amended mark, report correction, integration delay, and outage.

3. Set decision rights

Name central and campus owners for scales, calculations, marking, moderation, approval, publication, corrections, reports, access, integrations, support, backup, restoration, retention, privacy, safeguarding, records, and security.

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

4. Validate cross-campus reporting

Reconcile reports across scales, programmes, grading periods, time zones, languages, and campus filters. Show source, calculation, refresh, version, missing values, correction state, and finalisation.

The U.S. Department of Education data-quality guidance connects dependable information with definitions, rules, validation, infrastructure, and professional learning. Keep the data dictionary beside the cross-campus report.

5. Protect lifecycle and users

The U.S. Department of Education data governance checklist covers quality, access, security, lifecycle, sharing, disposal, and monitoring. GOV.UK guidance is a public reference, not a universal international or cross-campus compliance rule.

Apply qualified local privacy, safeguarding, records, security, accessibility, assessment, and legal review. Check family access, supplier access, exports, backup, restoration, retention, disposal, incidents, training, and support.

6. Manage the network

Use a shared change record for new campus, subject, programme, grading scale, assessment, role, report, integration, or policy. Record reason, risk, test, approver, communication, effective date, rollback, and review.

At 30, 60, and 90 days, review completeness, calculation differences, moderation, corrections, report confidence, staff effort, support demand, access exceptions, continuity, and outcome. Expand, repair, consolidate, narrow, or hold.

Turn the guidance into an accountable decision

Apply this guidance to one bounded part of multi-campus guide to school exam and gradebook software. Define the assessment or reporting decision, authoritative record, accountable owner, permitted users, correction route, evidence, and review date.

Test an ordinary assessment and meaningful exceptions such as a missing submission, late work, absent learner, moderation change, amended result, withdrawn learner, duplicate mark, grading-period change, report correction, access failure, or outage.

Keep supplier capability, school responsibility, professional judgement, local policy, legal advice, and measured outcome separate. If evidence is incomplete, narrow the claim and pilot the smallest safe change.

Review at 30, 60, and 90 days. Check completeness, timeliness, consistency, moderation, corrections, access exceptions, staff effort, support demand, reporting confidence, and the original outcome. Decide whether to expand, repair, consolidate, narrow, or hold.

Before approval, ask a reviewer who was not involved in the design to challenge the strongest assumption. Replace broad language with the exact evidence, population, date, and limitation the school can verify.

Document what was tested and what was not. A successful demonstration with a simple gradebook does not establish readiness for moderation, resits, special consideration, changed grading periods, multiple campuses, or a changed assessment policy.

Keep evidence beside the decision record so a later reviewer can distinguish observed behaviour from an assumption, estimate, or supplier statement. Name the next test where evidence remains incomplete.

Revisit the boundary when the school adds a subject, year group, campus, grading scale, role, integration, reporting period, or policy. A small change can alter permissions, definitions, calculation, timing, retention, or support demand.

Set the next review date and owner. A dependable exams and gradebook operation is maintained through clear definitions, controlled change, professional judgement, and visible accountability rather than a one-time setup.

Make the handoff readable to a teacher, administrator, leader, learner, and reviewer. State what passed, what remains manual, which records are authoritative, who owns unresolved conflicts, and how a correction is communicated without creating an uncontrolled copy.

Keep approved definitions beside calculation rules, moderation notes, training, support routes, and change history. New subjects, scales, integrations, or reporting windows can change the risk even when field names stay the same.