How to prepare evidence for school management, ERP, and SIS

Evidence answers a specific question

Evidence is useful only when it answers a decision question. “Does the workflow work?” is too broad. Ask whether a teacher can record the right class and period, whether finance can reconcile a reversal, whether a family sees only an approved result, or whether an administrator can correct a duplicate safely.

Write the question, affected role, record, expected behavior, test data, acceptance rule, owner, and review date before collecting screenshots or vendor claims.

Use several evidence types

A single demonstration rarely proves an operating model. Combine evidence that shows behavior, responsibility, and sustainability.

• Workflow demonstration with normal and exception cases
• Controlled migration sample and reconciliation
• Role and permission matrix
• Data-flow, retention, supplier, and incident documentation
• Training, support, monitoring, and commercial assumptions

Keep claims bounded

Separate what the product does from what the school must configure, decide, train, support, or measure. GOV.UK procurement guidance recommends data protection by design and default, minimum necessary data, access control, security, subprocessors, breach notification, and data return or deletion.

The U.S. Department of Education data-quality guidance emphasizes business rules, validation, infrastructure, and professional learning. A strong evidence pack includes those operating controls instead of relying on feature volume.

Record what remains unknown

An unknown is not a failure, but it must have an owner and next step. Mark it as a hold condition when it affects identity, privacy, access, payment, assessment, family visibility, recovery, or another high-consequence workflow.

Make the next step specific

Use this guidance to improve one bounded part of how to prepare evidence for school management software. Name the person who owns the decision, the record or workflow affected, the evidence needed, and the date for review. Keep the test small enough for operators to complete and specific enough for a later audit. Record the result and the next action.