Operating model for implementation, security, and multi-campus operations

1. Define the shared operating model

An operating model should state how the school governs implementation, security, data, campuses, users, integrations, support, reporting, privacy, records, safeguarding, accessibility, backup, recovery, vendors, change, renewal, and exit.

Set shared baseline, local variation, decision rights, authoritative records, role boundaries, service targets, evidence, approval, risk tolerance, fallback, and review cadence.

2. Assign accountability

Name executive sponsor, product owner, campus leads, data owners, security, privacy, records, safeguarding, accessibility, finance, IT, support, communications, supplier, and independent reviewer responsibilities.

Define who can approve scope, data, access, integrations, migration, security exceptions, local configuration, incidents, recovery, go-live, rollback, renewal, data return, deletion, and exit.

3. Design service and controls together

Usable workflows, least privilege, authentication, logging, patching, backups, recovery, support, accessibility, training, records, and incident response must fit the ordinary work of every campus and role.

Test new user, offboarding, transferred student, changed role, duplicate record, failed sync, lost device, phishing report, outage, restore, export, and urgent safeguarding or privacy escalation.

4. Govern local variation

For each campus variation record purpose, scope, affected records, users, permissions, calendar, language, connectivity, local requirement, risk, owner, evidence, approval, support, rollback, and review date.

Do not allow local copies, shared accounts, unapproved integrations, or inconsistent retention to become invisible operating-model decisions.

5. Measure the model

At 30, 60, and 90 days review adoption, data quality, access exceptions, failed integrations, incidents, recovery, support demand, training, campus variation, manual work, cost, and outcome.

Decide expand, repair, narrow, consolidate, or hold. Keep supplier capability, school responsibility, local advice, professional judgement, and observed evidence separate.

Turn the guidance into an accountable implementation decision

Apply this guidance to one bounded part of operating model for school software implementation. Define the authoritative student, staff, household, academic, attendance, finance, HR, communication, identity, integration, security, backup, or report record; accountable owner; permitted users; support route; evidence; and review date.

Test ordinary work and meaningful exceptions such as a new user, offboarding, transferred student, changed role, duplicate record, failed sync, lost device, phishing report, outage, restore, export, or urgent safeguarding or privacy escalation.

Keep supplier capability, school responsibility, local privacy or security requirements, safeguarding judgement, professional judgement, 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 adoption, data quality, access exceptions, failed integrations, security events, incident recovery, backup and restore, support demand, training, campus variation, manual effort, and the original outcome.

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

Document what was tested and what was not. A successful demonstration or pilot on one campus does not establish readiness for different campuses, roles, devices, calendars, records, integrations, security boundaries, or local requirements.

Keep evidence beside the decision record so a later reviewer can distinguish observed behaviour from an assumption, estimate, supplier statement, school policy, local requirement, or qualified review.

Revisit the boundary when the school adds a campus, user group, device, integration, identity provider, report, data field, supplier, retention rule, or operating responsibility. A small change can alter access, recovery, support, or records.

Set the next review date and owner. A dependable implementation is maintained through clear scope, controlled change, usable security, tested recovery, support, campus governance, and visible evidence rather than a one-time launch.

Make the handoff readable to leaders, campus teams, office staff, teachers, students, families, IT, support, privacy, security, records, safeguarding, accessibility, finance, suppliers, and reviewers. State what passed, what remains manual, which records are authoritative, and who owns unresolved conflicts.

Keep approved requirements beside role rules, configuration, integrations, training, support routes, retention, incident handling, change history, backup and recovery evidence, renewal, data return, and exit requirements.