What an IT lead should document about implementation, security, and multi-campus operations

Document the architecture

An IT lead should document identity, student, staff, household, academic, attendance, finance, HR, communication, reporting, calendar, permission, integration, backup, archive, support, incident, and exit records.

For each boundary state source, destination, identifier, fields, purpose, owner, access, sync, validation, error route, audit, retention, rollback, recovery, and deletion.

Document access and change

Map role access for leaders, campuses, office, teachers, students, families, IT, support, suppliers, privacy, security, records, safeguarding, accessibility, finance, and communications.

Record configuration version, change reason, approver, affected campuses, dependency, test, limitation, rollback, support, and review date. Temporary access and emergency records need expiry.

Document failure paths

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

Define detection, alert, safe temporary action, communication, reconciliation, incident route, recovery, retention, owner, and acceptance test.

Review documents in operation

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

Decide expand, repair, narrow, consolidate, or hold. Documentation is a control only when people can find, understand, and use it under pressure.

Make the next implementation step testable

Use this guidance to improve one bounded part of what an IT lead should document about school software implementation. Name the owner, implementation record, evidence, correction route, support path, and review date so staff can apply it consistently.

Check ordinary work and one meaningful exception. If either depends on undocumented knowledge, add the missing definition, validation rule, permission, approval, accessible instruction, security control, or escalation route.

Record what changed, what remains manual, and who reviews the result before the next implementation, campus, security, support, or reporting cycle.

Keep the decision beside its evidence so the next implementation colleague can understand the rule without relying on informal memory.

Use the review to decide whether the change should be expanded, repaired, narrowed, consolidated, or held.

Recheck the boundary when a user, campus, device, integration, calendar, report, supplier, or local requirement changes.