The business problem
Fee balances scattered across books and Excel, parents queueing at the bursar's office, report cards that take the whole closing week, and class lists rebuilt every term.
Our solution
One learner record from admission to completion, with fees, statements and parent messages built on it, and assessment entered once to produce report cards.
Key capabilities
- Learner register: admissions, transfers, promotions, ID cards and spreadsheet import and export
- Guardian and staff records
- CBE assessment: school-based assessment, summative scores, performance levels and report cards (the scoring rules are still being finalised)
- Assessment analytics by learning area and class, and senior-school pathway guidance
- Attendance registers and attendance analytics, and behaviour records
- Finance: fee structures, invoices, payments and receipts, arrears, bursaries, capitation and expenditure
- Communication: SMS to parents, announcements, circulars and a parent portal
- Compliance: KEMIS and KNEC returns with readiness checks
- Timetable, staff HR and payroll, library, clinic and other facilities
- Data protection: retention rules, requests and learner data export
Screenshots
Implementation scope
Our own product, built and running in our development environment with a complete demo school — fictional learners, guardians, staff and fees. It is not yet running at a school.
M-Pesa fee payments run in simulation mode until a school's Daraja credentials are added, and the CBE scoring rules use placeholder settings that will be replaced with the final rules before release.
