School setup and academic configuration
Frameworks, years, terms, grades, classes, subjects and readiness checks before a school goes live.
Platform overview
One connected record, four families of work.
BAINI is a single platform per school: academics, operations, engagement and the platform underneath share one record, so a register, an approval and a published report all point at the same learners.
How the pieces connect
Each module writes the records the next one relies on.
Admissions creates the learner. Setup places them in a class. Attendance and lessons record the day. Assessment produces evidence. Reporting combines it under the school's configuration — and the leadership dashboard shows what is complete and what is not.
Good morning, Asha
Mlima School · Term 3, 2026 · Monday 9 November
Registers submitted28 / 32
Formative approved46 / 52
Ready to publish9 / 10classes
Requires attention 3 items
4 East register not submittedAttendance · due 08:30Open
7 East Mathematics awaiting approvalFormative evidence · Head of DepartmentOpen
Grade 4: one class not readyReport cards · Term 3Open
Capabilities
Everything BAINI brings together.
Four families of work on one platform, and the intelligence layer that will build on them. Capabilities still in development are grouped under “On the roadmap” and described as what they will do.
BAINI is being introduced through a phased rollout. Features, integrations and availability are confirmed with each school before onboarding.
Academics
Setup, delivery, attendance, assessment and reporting under the school's own policies.
Timetables and curriculum delivery
Schemes of work, dated lessons and delivery tracking against the timetable.
Daily attendance and oversight
Class registers with submission tracking, so leaders see which registers are outstanding.
Formative evidence and approval
Teachers record evidence per learner; heads of department approve only the classes they supervise.
Assessment and school-owned grading
CBE performance levels, Cambridge stages, IGCSE A*–G and 9–1 — all from the school's own policies.
Report cards with versioned publication
Batch generation, readiness gates, publication to guardians, and correction by reissue — never by overwriting.
Report configuration provenance
Each report records which weighting applied — this class, this grade or the whole school — and says so on the card.
Leadership and academic dashboards
Curriculum-aware views of progress, coverage and readiness, computed from verified records.
Operations and administration
Admissions, people, fees and finance, and the modules a school chooses to run.
Admissions and enrolment
Applications, learner profiles, guardians, bulk import and class placement.
Staff, roles and scoped permissions
Invitations, multi-role staff, and leadership authority limited to assigned classes.
Fees and finance
Fee setup, invoicing, payment allocation and statements, switched on for the schools that use it.
Library
Catalogue, circulation and charges.
Transport
Routes, stops and learner assignment.
Email notifications
Account activation, password recovery and school notices from the school's own sender name.
On the roadmap
SMS notifications
Text-message delivery of school notices will be added with a production messaging provider.
Payment and service integrations
BAINI is being designed to connect with the services Kenyan schools rely on, such as mobile-money fee collection, with each connection confirmed per school.
Engagement and mobile
Guardians see published results; teachers work where the class is.
Guardian access to published reports
Guardians see only the current published version, and only for their own learners.
Parent Android access
Phone-based registration, confirmation by the school and a device-bound PIN.
Teacher Android app
Registers — including secure offline registers — and lesson delivery, on Android.
On the roadmap
iPhone and iPad apps
BAINI will come to iPhone and iPad after the Android rollout.
App-store listings
Public listings on Google Play and the App Store will follow the direct rollout to schools.
Platform and security
Isolation, scoped access, audit, and the console BAINI operators use.
Separate database per school
Each school's operational data lives in its own database, and requests are bound to the school's own address.
Audit trails
Sensitive changes — configuration, approvals, report revisions — are recorded for review.
Platform operations console
Provisioning, lifecycle and support access for BAINI's own operators.
The intelligence layer
In development, on top of the same verified evidence. These capabilities are not part of today's product.
In development
AI-written insights
Plain-language readings of school data will be grounded in authorised records, with their sources shown.
Early-warning signals
BAINI is being designed to flag learners or classes that may need attention before results are final.
Questions in plain language
Leaders will be able to ask about attendance or progress and see the evidence behind each answer.
See BAINI with your school's own structure in mind.
Tell us about your school and we will walk you through the workflows that matter to you — and how a phased rollout would work for your school.