Suku360: A School Operations and Intelligence Platform Built for African Classrooms

01 / Overview

02 / The challenge

Most school management systems stop at digitizing paper: a gradebook here, an attendance sheet there, leaving school leadership with data but no way to act on it, and leaving staff locked out the moment connectivity drops in a classroom. Suku360 needed strict per-school data isolation for a multi-tenant platform, role-based access precise enough that a teacher, a finance officer, and a parent each see only their own slice of a student's record, and a way to flag at-risk students without hiding the reasoning behind an opaque AI score.

03 / What we built

1. 01Multi-tenant architecture with database-level tenant isolation and role-based access enforced per domain, finance, observations, and audit data are restricted even from most staff roles
2. 02Deterministic, explainable learner-risk indicators (attendance and academic thresholds, not a black-box model) that auto-resolve once the underlying condition clears
3. 03An intervention-management workflow, open, in progress, completed, escalated, with an eligible-owner picker and full action history, closing the loop between a leadership 'Needs Attention' dashboard and actual staff follow-up
4. 04Student 360: one aggregated profile combining academics, attendance, indicators, interventions, observations, parent engagement, and finance, each section visible only to the staff roles that need it
5. 05Versioned, immutable report cards, each pinned to the exact result snapshot used to generate it and auto-superseding on correction, with server-rendered PDF generation and SHA-256 content-hash integrity verification
6. 06Server-authoritative finance: fee structures, bulk charge generation across a class's enrolments, and idempotent payment recording, allocation, and reversal, never trusting a client-submitted amount
7. 07Offline-capable PWA sync for attendance, score, and observation entry, a local mutation queue that flushes as one idempotent batch on reconnect, re-validated server-side through the exact same checks as the online path
8. 08Staff account lifecycle management: server-generated one-time temporary passwords, forced password change on first login, and suspend/reactivate/revoke controls that take effect immediately on an already-logged-in session

04 / Where it stands