Integration questions for implementation, security, and multi-campus operations

1. Map every integration boundary

Integration questions should cover identity, student, staff, household, academic, attendance, finance, HR, communication, reporting, calendar, permission, audit, backup, archive, support, and exit systems.

For each boundary request source, destination, identifier, fields, purpose, owner, permission, frequency, effective time, validation, error route, correction, audit, retention, rollback, recovery, and deletion.

2. Ask about data meaning

Ask which system is authoritative, how relationships and role changes are matched, how duplicates are handled, how late or conflicting data is reconciled, and who approves corrections.

Do not assume a technically valid identifier proves an authorised relationship or that synchronising every field is necessary. Minimise data by purpose and role.

3. Test failure and recovery

Require validation, deduplication, ordering, retry, partial success, schema change, alerting, support, rollback, reconciliation, backup, restore, retention, and manual fallback behaviour.

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. Review security and responsibility

Ask about authentication, least privilege, role review, logging, secure configuration, vendor access, exports, backups, recovery objectives, incident notification, offboarding, retention, data return, and exit.

Name who owns integration configuration, relationship quality, content, approval, permissions, support, privacy, security, records, safeguarding, accessibility, finance, and local campus variation.

5. Approve with evidence

Keep architecture, data mapping, test results, configuration version, source, date, scope, limitation, owner, dependency, acceptance test, fallback, rollback, approval, and review date.

At 30, 60, and 90 days review duplicate or missing data, access exceptions, failed integrations, incidents, recovery, support, manual reconciliation, campus variation, and outcome before expanding.

Turn the guidance into an accountable implementation decision

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