What small schools should know about school management, ERP, and SIS

Capacity is part of the requirement

A small school may not have a dedicated data team, project manager, or IT specialist. That does not make good software impossible, but it changes the rollout requirement. The school needs a phase it can test, explain, support, and review with the people it has.

Ask who owns the student record, permissions, family questions, fee corrections, training, support, and go-live decision. If one person owns everything, define a backup before adding complexity.

Choose one workflow first

Select a workflow that causes repeated work or visible confusion. Map it from trigger to outcome, including the exception that consumes the most time. Keep unrelated features in a later phase until the school can operate the first change reliably.

• Admissions to enrollment
• Student records to class roster
• Fees to payment and receipt
• Attendance or assessment to family visibility

Keep data and support explicit

Define the source of truth for students, guardians, classes, dates, fees, and staff. Profile a sample for duplicates, missing values, stale contacts, and unclear ownership. The U.S. Department of Education data governance checklist treats quality, access, security, lifecycle, and disposal as connected responsibilities.

Request task-based training, documentation for common exceptions, a support route, escalation expectations, and a plan for term-start pressure. Ask what the vendor needs from the school and what happens when no specialist is available.

Protect a small-school rollout

GOV.UK procurement guidance recommends data protection by design and default, minimum necessary data, access control, security measures, and clear end-of-contract responsibilities. Do not use a shared spreadsheet as an easy answer if it broadens access or creates another copy of sensitive data.

A rollout is ready when owners can perform the workflow, correct an exception, explain it to a family or colleague, and identify the condition that would pause the next phase.

Make the next step specific

Use this guidance to improve one bounded part of what small schools should know about 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, next action, and condition that would make the team revisit the decision.

Check the result against an ordinary case and one meaningful exception. If either case depends on undocumented knowledge, add the missing definition, training note, permission rule, or support route before calling the change ready.