Choosing a School Management System: A Practical Checklist

Choosing a school management system is one of the highest-leverage decisions a school leader makes. Get it right and admissions, fees, attendance, exams and communication hum along in the background. Get it wrong and you inherit a second bureaucracy.

Start with the whole workflow

Map how information actually flows through your school, from an enquiry, to enrolment, to daily attendance, to assessment, to a report card and an invoice. A good system supports that entire journey without forcing you to switch tools or re-enter data. The moments where staff currently copy information from one place to another are exactly the moments the new system must eliminate; walk the front-desk staff through the map, because they know where the friction lives better than anyone.

The checklist

• Student information, admissions, records, and easy day-to-day updates.
• Finance, fees, invoicing, payments and clear statements for parents.
• Attendance & timetabling, quick to mark, easy to analyse.
• Examinations, mark entry, grading and report cards.
• HR & payroll, staff records and pay runs in the same place.
• Communication, messaging and announcements that reach parents reliably.
• Teaching tools, does it help teachers plan and assess, or only administer?

That last line is the one schools most often miss. A system that only administers gives the bursary office a smooth ride and the staffroom nothing. Teachers are the users who touch the system dozens of times a day; if planning and assessment are not first-class features, adoption quietly fails.

Understanding the true cost

Sticker price is rarely the whole price. When comparing systems, line up the total cost of ownership for one year: the subscription for your actual student count, per-module or per-feature add-ons, SMS or email credits, payment-processing percentages on fee collection, setup and data-migration fees, and training charges. A cheaper platform that charges separately for attendance, messaging and reports frequently ends up more expensive than a transparent flat subscription. Ask every vendor the same question, “what will this school pay in year one, and in year three?”, and put the answers side by side.

Migration: getting your data in safely

The most underestimated part of any switch is the move itself. Before committing, ask exactly how existing data arrives: student records, guardians and contacts, fee balances, staff records, historical results. A vendor who answers with a clear import process, spreadsheets in, validated data out, a trial import before the live one, has done this before. A vendor who shrugs will hand your team the spreadsheet work. Insist on a trial import with a small sample, check it yourself, and only then schedule the cutover, ideally at a term boundary when records are naturally at rest.

Rollout: a 30–60–90 day adoption plan

Systems fail in rollout more often than in features. A realistic sequence: in the first thirty days, enrol staff, load students and run the daily essentials, attendance and records. By day sixty, add the financial loop (invoicing, payments, receipts) and start sending announcements through the platform. By day ninety, examinations, report cards and the teacher-facing tools. Announce each step, train just before each step, and resist switching everything on at once, momentum beats memorisation.

Red flags to walk away from

• No data export. If you cannot leave with your data, you do not own your data.
• “Custom development” quoted for basic features, you are funding someone’s learning curve.
• No offline or low-connectivity story in a region where connectivity is intermittent.
• Per-device pricing that punishes growth, classes and staff only increase.
• A demo that avoids your workflow and shows only the vendor’s favourite screens.

Don’t forget the non-features

Security & data ownership

Ask directly: is data encrypted, who can access it, and does the school own it? You should be able to export everything and control access per device. A system holding children’s records carries a duty of care beyond convenience, device-level access control and audit trails are not luxuries.

Devices & connectivity

Staff and parents use phones as much as computers. The system should work well on web, mobile and desktop, and keep itself up to date automatically.

Support & onboarding

The best software fails without good onboarding. Ask what training and ongoing support are included.

One platform beats five

Every extra system is another login, another data silo and another integration to maintain. Schools increasingly consolidate onto one platform that covers teaching and administration. LexsEdu’s School ERP brings all of the above together, with AI teaching tools like the AI Lesson Planner built in and per-device security by default. Before you sign anything with any vendor, run their product against the checklist above; a system that earns its place on your workflow map, at a transparent three-year cost, is a system that will still be serving the school in a decade.

Involve the staffroom early

The system will be chosen in the head’s office but lived with in the staffroom, and the fastest way to poison a rollout is to spring it on teachers after the contract is signed. Put two or three teachers on the evaluation panel, including the colleague most sceptical about technology, because their objections are the ones every teacher will raise in week two. Let them test the tasks they do daily: mark a register, enter marks, print a report, message a parent. Their verdict on daily friction is worth more than any feature list, and adoption doubles when staff can say they helped choose. The bursary and one front-desk administrator deserve seats too, admissions and fees are where the data lives.

Seven security questions worth asking any vendor

1. Where is our data physically stored, and who can see it at the provider?
2. Is traffic encrypted in transit and is data encrypted at rest?
3. How are staff accounts authenticated, passwords only, or device binding and session control?
4. Can access be revoked instantly when a staff member leaves?
5. Is there an audit trail of who changed a record, a fee or a mark, and when?
6. How quickly is data restored after an incident, and is there an offline backup?
7. What is the documented process if we terminate the contract, format, timescale and cost of our export?

Hesitant answers to any of these are a louder alarm than a missing feature. Children’s records deserve a vendor who has thought about this list before you ask it.