Mistakes to avoid when planning school management, ERP, and SIS

Mistake one: starting with the product category

“We need a school ERP” does not tell a project team what to configure, migrate, test, or measure. Start with the workflow and decision. Define which teams must work together, which record connects them, and what a successful first phase looks like.

Mistake two: treating data migration as a file upload

Migration is a set of decisions about identity, definitions, history, quality, retention, and ownership. Profile the source data, identify duplicates and missing values, and ask who validates each imported sample. A clean import file can still contain the wrong business meaning.

• Name the source of truth for every important entity.
• Document transformations and intentional omissions.
• Use fictional or controlled sample data for early rehearsals.
• Reconcile outputs such as rosters, balances, reports, and family views.

Mistake three: leaving permissions until the end

Permissions shape the workflow. A teacher, finance user, academic head, administrator, and family may need different access to the same student identity. Test view, edit, approve, publish, export, and role-change scenarios before the project calls itself ready.

GOV.UK guidance on procuring educational technology recommends considering staff access control, security measures, subprocessors, data return or deletion, and breach notification before signing. These questions belong in planning and vendor evaluation, not only in a late technical review.

Mistake four: planning against an abstract timeline

A generic implementation duration is not an academic plan. Check admissions deadlines, examinations, holidays, staff availability, fee cycles, and family communication windows. Build a hold rule for critical failures and an escalation path for issues that cannot be resolved before launch.

A safer planning sequence

Define the workflow, name owners, profile data, write acceptance tests, design permissions, rehearse with sample records, train by task, communicate the change, and review the first phase. Each step should produce evidence for the next. When evidence is missing, narrow the scope rather than hiding the uncertainty.

Use a short decision log throughout the project. Record the question, options considered, evidence available, owner, decision, and review date. This protects the team from reopening settled questions while still making it possible to change course when new evidence appears.