Every school in Kenya that starts looking for a management system runs into the same wall. Ten vendors, ten feature lists, and every one of them says it does everything. The lists are not much help, because they are all written to look complete rather than to help you choose.
This guide is the other way round. It is about how to judge a system against the way your school actually runs — and what separates a system that survives its first term from one the staff quietly stop using by mid-March.
What a school management system actually has to do
Strip away the marketing and a school management system — sometimes called a school ERP — holds one shared record of your school and keeps four groups of people working from it: the office, the teachers, the parents and the directors.
When it works, the bursar is not retyping an M-Pesa statement, the class teacher is not chasing marks on WhatsApp, the parent is not phoning to ask for a balance, and the director is not waiting until closing day to find out how the term went. Everything below is really a test of whether those four things hold.
Start with your list, not their feature list
Before you sit through a single demo, write down the five things that go wrong most often in your school. Not the aspirational list — the actual one. For most schools it looks something like:
- Fee balances that parents dispute because the receipt never reached them.
- Report cards that take a week of evenings to assemble.
- Payments landing on the wrong learner's account.
- No idea where the term's spending stands until it is over.
- The same information typed into three different books.
That list is your specification. A system that fixes four of those five is a better buy than one with two hundred features that fixes two. Take the list into every demo and ask the vendor to show you each item.
The eight criteria that decide it in a Kenyan school
1. CBE assessment and report cards
Kenya now runs Competency-Based Education on the 2-6-3-3-3 structure: two years of pre-primary, six of primary, three of Junior School (Grade 7–9), three of Senior School (Grade 10–12), then tertiary. Classroom assessment uses competency rubrics — Exceeding Expectation, Meeting Expectation, Approaching Expectation and Below Expectation — not just a mark out of 100.
A lot of systems were built for 8-4-4 and have had CBE bolted on top, which shows the moment you try to produce a real report card. Ask to see one generated for the grade you actually teach. Ask whether it can run 8-4-4 or IGCSE alongside CBE, because most schools will need both for a few more years yet. Our guide to CBE assessment and report cards goes through this in detail.
2. Fee collection and M-Pesa reconciliation
Almost every vendor will tell you they integrate with M-Pesa. Far fewer will show you what happens after the money arrives. Collecting is the easy half; the hard half is getting each payment onto the right learner's account the same day, without the bursar reading a statement line by line.
The question to ask is about the exceptions, not the happy path. What happens when a parent pays using a sibling's admission number, or leaves the account reference blank, or pays a round figure that matches nothing? A system that surfaces those on the same day is worth considerably more than one that produces a tidy report only when everything went right. See how to collect school fees via M-Pesa Paybill.
3. Parent communication
Parents are the group most likely to judge your school by your systems, because it is the only part of them they see. Look for three channels doing three different jobs: SMS for the short, urgent and universal; WhatsApp for the conversational and the detailed; and a portal for everything a parent should be able to check without asking anyone.
Two details matter more than they sound. First, whether messages go out from the school's own identity or a shared shortcode. Second, whether you can see delivery status — because a fee reminder that silently failed is worse than one you never sent. Our guide on parent communication across SMS, WhatsApp and the portal covers how to divide the work.
4. Receipting and compliance
Receipting used to be a finance-office habit. It is now also a compliance question, and the schools that struggle at audit are almost always the ones whose receipts live in more than one place. Whatever system you pick should make the receipt the automatic by-product of the payment, not a separate act of typing. Read more in eTIMS and KRA compliance for Kenyan schools.
5. Budgeting and votehead visibility
This is the criterion most schools skip in the demo and regret in the third term. Ask to see a votehead report generated mid-term, showing what was budgeted, what has been received and what has been spent. If the answer involves exporting to Excel and building it yourself, you have found the limit of the system — and you will be living inside that limit every term. See school budgeting and votehead management.
6. Staff, payroll and HR
Payroll is where a general-purpose system usually gives itself away. Kenyan school payroll has to cope with statutory deductions, allowances, loans and staff who join or leave mid-term. If payroll is a separate product with a separate price, find that out now rather than after you have signed.
7. The rest of the school
Transport, library, inventory, the clinic, visitors at the gate. None of these will win the decision, but together they decide whether you end up with one system or five. If your school runs buses, look closely at how routes, stops and transport billing are handled — it is a common weak point, and we go into it in school transport and bus tracking.
8. Support, training and the first week of term
This is the criterion that most reliably predicts whether the system will still be in use a year from now, and the one least likely to appear on a feature list. Ask who trains each role, how long it takes, what it costs, and — the real question — who picks up the phone at 7am on the first day of term when nobody can log in.
A scorecard you can use
Take this into each demo and score honestly out of five. Weight the rows that match your own list of five problems, and let the total do the arguing for you.
| Criterion | What good looks like | Score /5 |
|---|---|---|
| CBE assessment | Rubric-based reports for your grades; runs alongside 8-4-4 or IGCSE | |
| Report cards | Generated in your format, in bulk, without manual assembly | |
| Fee collection | Paybill, bank and cash visible in one place | |
| Reconciliation | Same-day posting by admission number; mismatches surfaced, not buried | |
| Receipting | Automatic on payment; one searchable record | |
| Parent communication | SMS, WhatsApp and portal, with delivery status you can see | |
| Budgeting | Votehead budget vs actual, available mid-term | |
| Payroll and HR | Included, statutory-ready, handles mid-term joiners and leavers | |
| Operations | Transport, library and stores in the same system | |
| Migration | Clear plan for learners, balances and staff; vendor states who cleans the data | |
| Training | Role by role, scheduled, priced up front | |
| Support | Reachable during the hours a school actually needs help | |
| Three-year cost | Licence, setup, training, messaging and growth, written down |
What it really costs
Most quotes are per learner, per term or per year. That number is comparable between vendors. The rest usually is not, so ask for it in writing:
- Setup and data migration. Who cleans and loads your existing records, and is it included?
- Training. Per role, and whether refresher sessions cost extra when staff change.
- Messaging. SMS bundles and WhatsApp charges are metered. Estimate your real termly volume — fee reminders alone add up quickly.
- Support. What is included, and what is chargeable.
- Growth. What the price does when you add a stream or a hundred learners.
Put three years of all of that side by side. The ranking often changes once you do.
Questions to ask in a demo
A demo is a performance unless you interrupt it. These questions tend to end the performance quickly, in a useful way:
- Generate a report card in our format, for our grade, right now.
- Receipt an M-Pesa payment and show me where it lands on the learner's account.
- A parent has paid using the wrong admission number. Show me what happens.
- Show me a votehead report for a term that is half finished.
- Send a fee reminder and show me the delivery status.
- Who will train my bursar, and when?
- What happens on the first morning of term when a teacher cannot log in?
- Which schools like mine can I call and ask?
That last one carries more weight than anything on a feature list. Ask for a school of similar size and curriculum, and actually make the call.
Five mistakes schools make
- Choosing on price alone. The cheapest licence with paid training, metered messaging and thin support is frequently the most expensive option over three years.
- Buying without the bursar and a class teacher in the room. They are the daily users. If they were not in the demo, the system does not get used the way you imagined.
- Migrating dirty data. Duplicated learners and stale balances follow you into the new system and get blamed on it. Clean before you move.
- Starting mid-term. Switch between terms, with balances brought forward properly.
- Treating training as a one-off. Staff change. Budget for refresher sessions from the start.
Where Mzizi fits
We build one of the systems you will be comparing, so read this section with that in mind — and score us on the same card as everyone else.
Mzizi is used by more than 300 schools across Kenya and Uganda. It runs CBE alongside 8-4-4 and IGCSE, collects fees through M-Pesa, bank and cash in one view, sends parent messages by SMS, email and WhatsApp on the school's own number, and includes payroll, transport, library and stores rather than selling them separately. If you want to see it against your own list, the demo is the place to bring it.
If you are still narrowing down what you need, the pages on CBC/CBE school management, M-Pesa fee collection and school ERP for Kenya go deeper on each area.