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

1. Ask what the demonstration proves

Demo questions should connect each screen or workflow to a defined school outcome, user, campus, record, security control, dependency, evidence, limitation, owner, and acceptance test.

Ask the vendor to show configuration, not only a polished default. Record whether the result is demonstrated, dependent, manual, roadmap, unsupported, or not evidenced.

2. Test ordinary and exceptional work

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

Observe identity, relationships, permissions, workflow, integration, audit, notifications, support, recovery, retention, local campus variation, and manual effort. Capture expected and observed result.

3. Ask about operating responsibility

Ask who owns data quality, migration, configuration, content, approvals, access, integrations, security, privacy, records, safeguarding, accessibility, support, incidents, backup, recovery, local changes, and exit.

Ask what the school must provide: staff time, data cleaning, policy, local review, translation, accessibility, training, support cover, devices, identity, calendars, and family or staff communication.

4. Ask about evidence and limits

Request source, date, scope, jurisdiction, configuration version, dependency, limitation, audit evidence, support target, incident commitment, recovery objective, retention, data return, and deletion.

NIST and CISA resources offer useful questions, not a vendor certification. Obtain qualified local security, privacy, records, safeguarding, accessibility, and legal review where required.

5. Close with a decision record

Keep scores, evidence, open questions, risks, conflicts, assumptions, acceptance tests, fallback, owner, approval, and review date. Ask an independent reviewer to challenge the strongest claim.

At 30, 60, and 90 days compare the chosen option with adoption, data quality, access exceptions, failed integrations, incidents, recovery, support, campus variation, manual work, and outcome.

Turn the guidance into an accountable implementation decision

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