Product guides
A school leader’s field notes on school management, ERP, and SIS
Field notes for school leaders reviewing management software after launch: follow the work, question the measure, inspect the exception, and decide the next phase.
Begin with what changed for people
A post-launch review should start with the work people now perform. Follow a student record, payment, attendance entry, assessment, message, or approval from trigger to result. Ask what became clearer, what remained manual, and where staff or families still need help.
Do not let a dashboard replace conversations with the people who own the workflow. Numbers identify a signal; operators explain its cause.
Inspect the exception
For each workflow, examine one incomplete, duplicated, late, corrected, denied, or reversed case. Check who handled it, what was visible, whether the record remained traceable, and whether the result reached the next team or family safely.
- Source of truth and data quality
- Role and relationship permissions
- Approval and publishing boundary
- Support and reconciliation route
- Retention, export, and copy control
Keep claims proportional to evidence
The U.S. Department of Education data governance materials connect quality, access, security, lifecycle, sharing, disposal, and monitoring. GOV.UK guidance highlights responsibilities, access control, security, subprocessors, incidents, and contract-end data handling.
Use those frameworks to ask whether the change is operating safely. Do not describe a successful launch as a measured improvement unless the school has a baseline and a defined outcome.
Make the next decision
At 30, 60, and 90 days, choose reinforce, repair, narrow, expand, consolidate, or hold. Record the evidence, owner, next action, and review date. A leader’s job is not to defend the original decision; it is to keep the school’s next decision honest.
Make the next step specific
Use this guidance to improve one bounded part of a school leader’s field notes on 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.
