What to measure after launching school management, ERP, and SIS

Return to the launch question

The first measure should answer why the school launched the change. If the goal was a reliable student handoff, inspect identity matches, corrections, late updates, and downstream use. If the goal was clearer family visibility, inspect published information, support questions, and permitted access.

Choose a baseline and a review period before interpreting the result. A measure without a definition can create activity without learning.

Pair activity with quality

Logins, records entered, or messages sent may show activity but not useful completion. Pair them with correction loops, missing values, blocked steps, support questions, access exceptions, and the outcome the school intended to improve.

• Discovery: impressions, visits, or questions
• Engagement: completed workflow and return use
• Quality: duplicates, missing values, and corrections
• Control: permissions, publishing, exports, and incidents
• Value: defined school, family, or operational outcome

Review causes, not only scores

The U.S. Department of Education data-quality guidance points to business rules, validation, infrastructure, and professional learning as causes of data quality. A weak result may need training, a definition, a permission change, a product fix, or a narrower scope.

GOV.UK procurement guidance recommends attention to data protection, access control, security, subprocessors, breach notification, and data return or deletion. Keep those controls in the post-launch review.

Turn measures into action

Review at 30, 60, and 90 days. Name the action, owner, evidence expected, and date of the next review. Hold expansion when a critical identity, privacy, access, payment, assessment, or family-visibility problem remains unresolved.

Make the next step specific

Use this guidance to improve one bounded part of what to measure after launching 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.