Multi-campus guide to school management, ERP, and SIS

Define the central and local decisions

A multi-campus organization needs a deliberate boundary between standards that should be shared and rules that should remain local. List the central decisions—identity, reporting, access principles, support, data governance—and the local decisions—calendar, curriculum, payment, language, family communication, or regulatory requirements.

Give every decision an owner and evidence requirement. “One system for all campuses” is a direction, not a testable requirement.

Define the unit of comparison before the pilot begins. A campus may use a different calendar or payment rule and still meet a shared identity or reporting standard. The review should distinguish a legitimate local rule from an uncontrolled divergence that creates duplicate work or weakens access.

Build a cross-campus data model

Map students, guardians, staff, classes, subjects, academic periods, campuses, fees, payments, attendance, assessment, documents, and communications as relevant. For each entity, state which campus owns it, which central team may view it, how changes move, and what happens when a record is archived or transferred.

Include data quality rules. The U.S. Department of Education’s data-quality guidance emphasizes business rules, validation processes, infrastructure, and professional learning. Those controls become more important when multiple campuses use different local practices.

Test the transfer and exception journeys

Run a student transfer, staff move, guardian correction, campus closure or archive, calendar mismatch, local fee rule, and family communication case. Record the source, destination, approval, permissions, outputs, and reconciliation result.

Test a local exception without allowing it to become invisible. Each variation should have a reason, owner, evidence, scope, and review date. An undocumented exception becomes a future migration and support problem.

Use the same cases in each pilot campus, then add local cases that the central team cannot predict. Compare results without treating local variation as failure by default. The question is whether the variation is intentional, controlled, supportable, and visible to the people who rely on it.

Evaluate vendor architecture and support

Ask vendors to distinguish native behavior, configuration, integration, manual work, roadmap, and unknown. Request support coverage by campus and time zone, update communication, escalation, data return or deletion, and responsibility for subprocessors.

GOV.UK guidance on procuring educational technology recommends involving the data protection officer early and checking security measures, staff access control, subprocessors, incident handling, and end-of-contract data management. Obtain local advice for each operating jurisdiction.

Plan governance and rollout

Name central and local owners for data, workflow, access, implementation, training, support, and go-live. Tie rollout dates to each campus’s academic calendar. Define the evidence that lets a campus join the shared model and the failure that holds or narrows the release.

Pilot one campus or bounded workflow before scaling. Carry its test set, lessons, exceptions, and decision record into the next campus rather than copying configuration without context.

Create a short operating agreement for changes after launch. It should say who proposes a shared change, who checks its local effect, how campuses are notified, how the change is tested, and how a rollback or hold is requested. This protects both central consistency and local accountability.

Measure shared value without hiding local cost

Review duplicate entry, correction loops, transfer time, support questions, access exceptions, workflow completion, and the original outcome by campus. A central improvement may still create local support work; measure both.

Use the 30, 60, and 90-day review to decide whether to expand, hold, consolidate, or change a rule. Multi-campus scale should follow evidence, not merely the success of a central demonstration.