School Management System in Kenya: Features Schools Actually Use

A school management system in Kenya earns its keep in three places: fees, exams and parents. Get fee collection through M-Pesa, report forms and parent communication right, and the system pays for itself within a term or two. Most of the other modules on a vendor's brochure are useful, but they are not why bursars and principals stop using Excel.

This guide ranks the features by how much they matter to schools of different sizes, so a 200-pupil academy in Nyeri and a 1,500-student boarding school in Kisii can each see what to insist on and what can wait.

What a school system replaces

Before comparing features, list what the system is meant to retire. In most schools we see, it is some mix of:

• A fees spreadsheet maintained by the bursar, updated from M-Pesa statements and bank slips.
• Receipt books written by hand at the office window.
• Mark sheets in Excel, one per teacher, combined by the deputy or a willing ICT teacher before reports can be printed.
• A class register on paper, rarely summarised.
• A timetable on the staffroom wall.
• Parent WhatsApp groups for announcements, and phone calls for fee balances.

Every item on that list involves typing the same student's details again. The real job of a school management system is to hold each learner once, and let fees, marks, attendance and messages all hang off that single record.

Priority by school size

Schools often buy more than they will use. This table is a realistic view of what matters first.

If your budget only stretches to a few modules, start at the top of the table and work down. A system with excellent fees and report forms and no library module is more valuable than the reverse.

Admissions and student records

The student record is the foundation. Get it right and everything else is easier.

• Admission numbers issued consistently, because parents will use them as the M-Pesa account number.
• Parent and guardian contacts, with more than one phone number per student and a clear "who pays" field.
• Class, stream and year, with promotion at the end of the year done in bulk, not student by student.
• Siblings linked, so a parent with three children sees one account and gets one SMS.
• Transfers and leavers handled without deleting history, so a former student's records remain available for certificates and references.
• Medical notes and special needs, visible only to staff who need them.

Learner data is personal data under the Data Protection Act 2019, and data about children deserves extra care. Ask where the system stores it, who can see it, and whether access is restricted by role. The ODPC publishes guidance for organisations handling personal data.

Fees, M-Pesa and statements

This is the module that changes a bursar's life, and the one to test hardest in any demo.

What good fee management looks like

1. Fee structures per class and term, with optional items (transport, lunch, trips) added to specific students.
2. Automatic invoicing at the start of each term, carrying forward any balance or overpayment.
3. M-Pesa Paybill payments matched to the student by admission number, with the balance updated and a receipt issued as soon as the money lands.
4. Bank deposits and cash recorded with the same receipt numbering.
5. Bursaries and discounts recorded as such, not as fake payments.
6. Statements per student, and arrears lists per class, printable or sent by SMS.

Ask what happens when a parent types the wrong admission number, or pays for two children in one transaction. A good system puts those payments in a list for the bursar to allocate, rather than dropping them or guessing.

Some schools are moving to instalment plans or monthly payments rather than full-term fees. If that is you, our guide to recurring M-Pesa payments explains the options and what is realistic.

Exams and report forms

Report forms are the second reason schools buy software. The end-of-term rush of combining mark sheets is painful, error-prone and late every time.

• Mark entry by teachers, each seeing only their subjects and classes.
• Automatic grading against your grading scale, with means and positions where you use them.
• Report forms in your format, with the school crest, class teacher's and principal's remarks, and next term's opening date and fee balance.
• Exam analysis by subject, stream and teacher, so you can see which classes need attention.
• Competency-based assessment for CBC grades: rubrics and performance levels as well as marks.

With the curriculum transition still working its way through the grades, do not accept a vague "yes, we support CBC". Give the vendor a real grade and assessment structure and ask them to produce a sample report form from it during the demo.

Parent communication

Parents want three things: to know what they owe, how their child is doing, and what is happening at school. A system that answers those without a phone call to the office saves hours each week.

SMS

SMS is still the most reliable channel, because it reaches every parent, including those on basic phones in areas with weak data coverage. Use it for:

• Payment confirmations with the new balance.
• Fee reminders before opening day, sent only to parents with a balance.
• Results notifications with a summary.
• Urgent notices: closures, schedule changes, emergencies.

Parent portal

A portal lets parents check balances, statements, report forms and attendance whenever they like. It matters more in larger schools and with parents who work away from home. Check that parents see only their own children and that it works on a cheap smartphone over a slow connection.

What about WhatsApp?

Class WhatsApp groups are not going away, and they are fine for informal updates. They are a poor place for fee balances or results, which are private. Keep personal information in SMS and the portal.

Comparing prices fairly

School systems are sold on very different pricing models, which makes quotes hard to compare. Put every option on the same footing: total cost over three years at your expected enrolment.

Take a hypothetical mixed day school in Nakuru with 450 learners, growing to about 550. It receives three quotes (figures invented for illustration):

• Vendor A: KES 100 per learner per term. Year one is 450 × 100 × 3 = KES 135,000; by year three, at 550 learners, it is KES 165,000. Three-year total: roughly KES 450,000. SMS charged extra.
• Vendor B: a flat KES 120,000 per year regardless of numbers, SMS bundled up to a limit. Three-year total: KES 360,000, plus any SMS over the bundle.
• Vendor C: a one-off KES 250,000 setup and licence, then KES 40,000 a year for support. Three-year total: KES 370,000, and the cost barely moves as the school grows.

None of these is automatically best. Vendor A is cheapest if enrolment falls; Vendor C wins if the school keeps growing. What matters is that you do the sum, read the SMS terms carefully, and ask what each vendor charges for data migration, training and extra modules. Also ask what happens to your data if you stop paying: a school should never lose access to its own learners' records over a disputed invoice.

What software will not fix

A system makes a well-run office faster. It does not fix unclear policies. Before go-live, settle the questions staff will otherwise argue about at the counter: how bursaries are approved, whether a learner with a balance gets a report form, who can waive a penalty, and which teacher owns each mark sheet. Write the answers down and configure the system to match them. Software that enforces a rule nobody agreed on just moves the argument from the staffroom to the support line.

Rollout and staff training

Schools have a natural rhythm, so plan around it:

1. Choose the system during a term, while you can still observe how staff work.
2. Load data in the holidays: students, classes, parents and opening fee balances per student.
3. Check every opening balance against the bursar's records before invoicing the new term.
4. Train the bursar first, then class teachers on attendance and marks, then subject teachers.
5. Tell parents by SMS how to pay into the Paybill using the admission number, before opening day.
6. Run the first exam cycle with support on hand, since report-form week will be the real test.

Expect the first term to be bumpy and the second to be easy. Schools that try to switch everything mid-term usually regret it.

Questions to ask vendors

1. Show us a parent paying by M-Pesa and the student's balance updating. What happens if the account number is wrong?
2. Can you produce a report form in our format, for our grades, during this meeting?
3. How do parents, teachers and students log in, and what does each see?
4. Is SMS included, or billed separately per message? Can we use our own sender name?
5. Where is our data stored and backed up? Can we export everything, students, fees and marks, at any time?
6. How is the price calculated: per student, per term, or flat? What does it cost in three years if enrolment grows?
7. Who trains our staff, and who answers the phone on opening day when something goes wrong?
8. Which schools of our size use it, and may we call one of their bursars?

Your website and your management system should work together. Our checklist of school website must-haves covers the public side, and the wider guide to buying business software explains the buy-versus-build decision if you are weighing a custom system.

Our own School Manager is built around the fees, exams and parents core described above: fee structures per class, M-Pesa Paybill payments reconciled to each student, marks with means, ranks and printable report cards, attendance, timetables, SMS and separate portals for administrators, teachers, parents and students. There is a live demo on the product page, and you can see what else we do for schools on our schools page.