Choosing software is the easy part. Getting a whole school to use it is where projects succeed or quietly fail.
This plan assumes a school moving from paper and Excel to a school management system. Adjust the timings to your school.
Before you start: decide three things
- Who owns the project? One named person with time to do it.
- What must work first? Usually learners, fees and report cards. Leave transport, library and extras for later.
- When is go-live? Pick the start of a term. Never switch in the middle of exams or report card week.
Week 1: Prepare
Clean your data
The system will only be as good as what you put in.
- Learner list: one row per learner, correct spelling, admission number, class, guardian name and phone.
- Remove duplicates and learners who have left.
- Fee balances: list what each learner owes as at a chosen date.
- Fee structure: write every fee item per class and term.
- Staff list: names, roles, contacts.
An hour of cleaning now saves a week of corrections later.
Choose your pilot group
Pick a few people who will use it first: the bursar, one or two teachers, and the secretary. They become your champions.
Week 2: Set up
- Create the school account and enter school details, terms and the academic year.
- Set up classes and subjects.
- Import learners from your spreadsheet. Check a sample against the source.
- Add guardians and their contacts.
- Create fee structures per class.
- Enter opening balances carefully, using the cut-off date.
- Add staff accounts with the right roles. Give people only the access they need. Our features checklist explains roles.
Week 3: Test with real work
Have the pilot group do real tasks:
- The bursar records a week of payments and prints receipts.
- Teachers mark registers.
- Teachers enter marks for one class and generate a report card.
- Someone checks that every figure matches the old records.
Write down every confusion, and fix settings or training accordingly. This is also where you decide how M-Pesa payments will be matched, for example by asking parents to use the admission number as the account reference.
Week 4: Train and go live
Train in small, practical sessions
- Thirty minutes per role, using real examples
- Teachers: registers and marks
- Bursar: payments, receipts, arrears
- Secretary: learner records
- Headteacher: dashboards and reports
Provide a one-page cheat sheet per role.
Run in parallel briefly
For a short period, keep the old method alongside the new one to confirm balances match. Then stop. Running two systems forever is the most common way for a new one to fail.
Tell the parents
Send a short message explaining what is changing and what they will see, such as new receipts or access to a parent portal. Give them a contact for questions.
After go-live
- Check in weekly for the first term. Ask what is slow, confusing or missing.
- Review the numbers monthly: fee collection, attendance rate, outstanding balances.
- Add modules gradually. Timetables, transport and messaging once the core is stable.
- Keep a short list of "how we do it" so new staff follow the same routine.
- Back up and export reports at term end for your own records.
Common mistakes
| Mistake | Better approach |
|---|---|
| Importing messy data | Clean first, import second |
| Everyone trained at once in a large room | Short, role-based sessions |
| No named owner | Assign one person with authority |
| Switching mid-term | Start at the beginning of a term |
| Turning everything on at once | Core modules first |
| Keeping the old system "just in case" | Short parallel run, then retire it |
If something goes wrong
Mistakes in the first weeks are normal. Keep the original spreadsheets until you are sure the new system is right. A system with an audit trail lets you trace what changed and fix it.
How DiraSchool helps
DiraSchool lets you import learners from a spreadsheet, set fee structures per class, and add staff with role-based access. Our team in Nairobi helps schools get started. You can create a school account to begin setting up, or contact us with questions.
Not sure you are ready? Read Excel vs a school management system: when to switch.
Related: On a budget? Read about free school management systems in Kenya.
Frequently asked questions
How long does it take to implement a school management system?
A small school with clean records can be running the core modules in a few weeks. Larger schools or those with messy data should allow longer. Start at the beginning of a term rather than in the middle.
What is the biggest cause of failed implementations?
Poor data and lack of ownership. Messy spreadsheets and no clear person responsible are more common problems than the software itself.
Should we run the old system in parallel?
Briefly, yes. Run both for a short period while you check that balances and records match, then retire the old one so staff do not keep two systems.
Who should lead the project?
A senior person with authority, usually the deputy headteacher or school administrator, supported by the bursar. The headteacher should visibly back it.