How multi-campus teams coordinate exams, gradebooks, and report cards

Choose what should be shared

List definitions and controls that should be common across campuses: learner identity, subject, cohort, assessment, component, attempt, mark, grade, scale, weighting, rounding, moderation, report, correction, role, retention, and support.

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

Set decision rights

Name central and campus owners for assessment setup, scales, calculations, marking, moderation, approval, publication, corrections, permissions, integrations, training, support, incidents, backup, restoration, privacy, safeguarding, records, and security.

Define when a local change needs central review. Record effective date, affected campus, impacted reports, communication, rollback, and evidence for every material change.

Test movement and exceptions

Rehearse teacher or learner movement, shared subjects, missing submission, late work, absent learner, amended mark, moderation adjustment, resit, transfer, duplicate identity, changed grading period, report correction, and outage.

Check whether access follows campus, role, subject, cohort, learner, temporary assignment, or support function. Inspect exports and notifications for accidental cross-campus exposure.

Operate the network

The U.S. Department of Education data-quality guidance connects quality with definitions, rules, validation, infrastructure, and professional learning. Use a cross-campus dictionary, sample validation, reconciliation, calculation tests, and role training.

GOV.UK guidance emphasises accountable and secure handling. At 30, 60, and 90 days, compare completeness, moderation, corrections, staff effort, support demand, access exceptions, report confidence, and local differences.

Make the next improvement testable

Use this guidance to improve one bounded part of how multi-campus teams coordinate 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.