What a school management system should do: a checklist for schools

Quick answer: what should a school management system do?

At its core, a school management system should do five things well: keep one trustworthy record of every student and staff member, track fees and payments, process scores into report cards, record attendance, and let parents see the information that concerns them. Everything else, such as timetables, messaging and tests, is built on top of those foundations.

The test is simple. If your bursar, class teachers, proprietor and parents each get the information they need without someone retyping it or searching a cupboard, the system is doing its job. If it only adds another place to enter the same data, it is not.

The sections below walk through each area, what to look for, and the questions that separate a dependable system from a flashy demo.

Student and staff records: the foundation

Every other feature reads from the student record, so weak records spoil everything downstream. A good system should hold:

• Student profile: names, admission number, date of birth, class, arm or section, house, photo, and any medical or special-needs notes the school chooses to keep.
• Guardian details: more than one contact per child, with a clear marker for who pays fees, who collects the child and who gets results.
• Siblings linked together, so a parent with three children sees one account, not three.
• Staff profiles: roles, subjects taught, classes handled, and contact details.
• History: promotions, transfers, withdrawals and graduations kept rather than deleted, so you can answer questions years later.

Check how records get in. You should be able to import an existing class list from a spreadsheet rather than typing hundreds of students by hand, and the system should warn you about duplicates. Check too that corrections are easy and leave a trail, because records will need correcting every term.

Fees and payments

Fees are where schools feel the pain first, so this area deserves your closest attention. The system should let you set a fee structure per class and term, with items such as tuition, uniform, books, transport and levies. It should handle instalments, discounts, scholarships and carry-over balances from earlier terms.

Each payment should produce a numbered receipt, whether it came by cash, bank transfer or an online gateway such as Paystack or Flutterwave. Parents should be able to see a statement, and the bursar should be able to see at a glance who owes what, by class, without counting by hand.

Ask specifically: can we record part payments? Can we reverse a wrong entry without deleting it? Can the proprietor see collections without asking the bursar to compile a report? Our guide on digital fee management goes deeper on setting this up.

Results, grading and report cards

This is where schools differ most, which is why you must test it with your own material. Your school may use continuous assessment plus exam, a particular grade scale, positions in class, subject remarks, affective and psychomotor domains, or a format required by your owner or association.

A good results module should:

• Let each subject teacher enter scores for their own subjects only, and lock them after a deadline.
• Calculate totals, averages, grades and positions automatically using your grading scale.
• Handle subject groupings, optional subjects and different arms of the same class.
• Produce report cards that match your existing layout, with your logo, principal and teacher comments, and next-term dates.
• Support cumulative results across terms for the annual report.
• Allow the head to review and approve before anything is released.

Never accept a screenshot of a sample report card. Give the vendor last term's real scores for one class and ask them to reproduce your report cards.

Attendance, timetable and academics

Attendance should take a teacher under a minute per class: tick absentees, save, done. Look for daily and per-subject options, reasons for absence, and simple reports showing who is frequently absent or late. If you want parents notified of an absence, check how that message is sent and what it costs.

For academics, the system should know your classes, subjects and teachers, and ideally build a timetable that flags clashes, such as one teacher in two rooms. Smaller schools often do not need an automatic timetable generator, but they do need a clear record of who teaches what.

Extras such as lesson notes, assignments, a library record or a transport list are useful but secondary. Do not let a long list of extras distract you from getting the first five areas right.

Parent access and communication

Parents mostly want three things: results, fee balances and notices. A parent portal answers these without a trip to the office. What matters is how easy it is on an ordinary phone with limited data, because most parents will never open it on a laptop.

For communication, look for notices to the whole school, to one class or to one parent, with a record of what was sent. Find out whether messages go by email, SMS or in-app notification, and who pays for SMS credits. A system that lets you keep WhatsApp for conversation but moves official information, such as results and fee statements, into one controlled place usually works best. Our guide on parent portals covers rollout in detail.

Roles, security and data protection

A school holds children's names, photographs, addresses and sometimes medical details, plus family finances. That is sensitive, and Nigeria's data protection law expects organisations to handle personal data responsibly. Whatever the law requires in your case, these basics are non-negotiable:

• Separate logins for the proprietor, head, bursar, teachers, office staff and parents, each seeing only what their job needs. A teacher should not see fee balances; a parent should see only their own children.
• An audit trail showing who changed a score, a fee or a record, and when.
• Strong passwords, and a way to disable an account immediately when a staff member leaves.
• Automatic backups stored away from the school, with the vendor able to tell you how often and how to restore.
• Clarity about where data is hosted and who at the vendor can see it.

Also ask what happens during a power cut or when the connection drops mid-entry. Teachers entering scores should not lose work.

Questions to ask any vendor before you choose

1. Can you reproduce our report card and grading scale using our real data?
2. Does it work well on a basic phone and on a slow connection, and what works offline?
3. Who owns our data, and can we export everything, including past results, in a usable format?
4. How are backups done, how often, and have you ever restored one for a customer?
5. What training do you provide for teachers, the bursar and parents, and what support is available when something breaks on a results deadline?
6. Can the system serve more than one campus or school under the same owner?
7. How do you handle updates, and will our setup be affected?
8. What exactly is included in the quote, and what costs extra, such as SMS, extra students, extra modules or customisation? Ask for it in writing.
9. What happens if we want to leave?
10. Can we speak to a school that has used it for at least a full year?

Vendors who answer these plainly are usually worth talking to. Vague or defensive answers about data ownership and backups are a warning.

How to roll it out without disrupting the term

1. Pick a start date away from exams. The beginning of a term works best. Never switch in the middle of results season.
2. Clean your data first. Prepare class lists, guardian contacts and current fee balances in a spreadsheet. Fixing errors before import saves weeks.
3. Start with two or three modules. Records and fees, then results the following term, then parent access.
4. Train by role. Short sessions for the bursar, the exams officer and teachers, using their own classes as examples.
5. Run old and new side by side for a limited time. One term is usually enough. Compare totals so you trust the new numbers.
6. Name one internal owner. Someone on staff should be the go-to person, so the system does not depend on the proprietor.
7. Review after the first term. Ask what slowed people down and fix it before adding more.

Common mistakes schools make

• Choosing on price or on a polished demo without testing real report cards.
• Buying every module at once and training nobody properly.
• Letting one person hold the only admin login.
• Not asking about data export, then discovering years later that leaving is painful.
• Skipping the clean-up of old data and carrying errors into the new system.
• Forgetting parents: a portal nobody was shown how to use gets ignored.

If your school runs on spreadsheets today, that is a fine place to start from. The goal is not to be fashionable but to give staff time back and give parents clear, consistent information.

Frequently asked questions

Written by the ICT AccessPoint team

We repair laptops and build websites and business systems. Have a question this guide did not answer? Message us.

This guide is general advice. Every device and business is different, so if you are unsure, ask a technician before you act.