Data-retention questions for implementation, security, and multi-campus operations

1. Define retention purpose

Data-retention questions should begin with purpose and record type: identity, student, staff, household, academic, attendance, finance, HR, communication, reporting, calendar, permission, audit, support, incident, backup, archive, and integration data.

For each record state purpose, owner, jurisdiction, access, retention trigger, review date, legal or policy basis, correction, archive, deletion, backup, export, supplier, and evidence.

2. Separate active, archive, and backup

Define when a record is active, archived, held for an incident or dispute, included in backup, restored, returned, or deleted. A backup copy may have different operational controls, but it cannot be ignored in a retention decision.

Restrict access and document expiry for temporary exports, migration files, test data, support attachments, local campus copies, and emergency records.

3. Connect retention to purpose and access

Review least privilege, authentication, role changes, vendor access, exports, reporting, integrations, recovery, incident response, correction, safeguarding, privacy, records, accessibility, and local requirements.

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. Ask suppliers precise questions

Request retention defaults, configurable periods, deletion evidence, backup treatment, archive behaviour, sub-processors, data location, legal hold support, data return, exit, audit, support access, and incident handling.

Label supplier capability, school responsibility, local requirement, qualified advice, professional judgement, evidence date, and limitation. Public guidance is contextual and does not replace local review.

5. Review retention in operation

At 30, 60, and 90 days review stale records, excessive access, exports, corrections, failed integrations, incidents, recovery, support, campus variation, manual work, and outcome.

Decide expand, repair, narrow, consolidate, or hold. Keep the retention schedule, owner, evidence, approval, and next review together.

Turn the guidance into an accountable implementation decision

Apply this guidance to one bounded part of data-retention questions 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.