Product guides
Where spreadsheets break down in school management, ERP, and SIS
Field notes for school leaders who need to judge whether a management software project is improving the work people actually do.
Watch the handoffs, not only the screens
A school leader can learn more from a five-minute handoff than from an hour of feature demonstrations. Follow an application into enrollment, a student into a class, a fee into a receipt, or an assessment into a published report. Ask where the next person gets the information and what happens when it is incomplete.
The aim is not to inspect every task personally. It is to identify where the school depends on re-entry, a private spreadsheet, one experienced administrator, or an approval that nobody can explain.
Ask operators what they protect
Staff often have a practical reason for keeping a workaround. It may preserve a report, protect a sensitive field, cover an exception, or give a family a reliable answer when the official workflow is slow. Ask what the workaround protects before removing it.
- Which value must never be overwritten?
- Which correction needs a second person to approve it?
- Which report or family action depends on the process?
- Which exception occurs during the busiest period?
- Who can operate the workflow when the usual owner is absent?
Make leadership questions testable
Replace “Will this improve efficiency?” with a test: fewer duplicate entries, fewer correction loops, faster reconciliation, clearer publishing, or fewer unresolved support questions. Choose the measure with the owner before launch and record a baseline.
Do not turn a measure into a promised result. A platform may make a workflow possible, but the school’s definitions, training, permissions, adoption, and support model affect what happens in practice.
Keep the decision honest
The U.S. Department of Education’s data governance resources emphasize roles, data quality, access, security, lifecycle, sharing, and monitoring. GOV.UK procurement guidance similarly recommends early attention to responsibilities, access control, security, subprocessors, breach notification, and data return or deletion. Use these as question frameworks, then obtain advice for the school’s jurisdiction.
A good leadership review ends with one of three decisions: proceed with a bounded test, hold while evidence is gathered, or change the scope. “Proceed” should not mean that every uncertainty has disappeared; it should mean that the remaining risk has an owner and an acceptable next step.
