← All work
Sikolo
A connected management platform for schools
A connected management platform for schools
01 / 05
The problem
A school runs on attendance, money, learning and family communication. When those live in four different tools, staff repeat work and contact falls through the gaps.
What it does
- Leaders and administrators
- Manage pupils, staff, guardians, classes, timetables, attendance, fees, notices and guardian requests.
- Teachers
- Get a daily action centre: registers to take, marking due, parent requests waiting, and pupil-level progress.
- Parents
- Follow each child’s attendance, homework, reports, invoices and activities from one account.
- Pupils
- Get an age-appropriate view of the same records.
Decisions worth explaining
- Multi-tenant safety is structural, not a filter
- School scope is carried through authentication, authorisation, services and database queries. It is never left to the interface to hide the wrong class.
- Finance separates setup, billing, payment and audit
- Fee structures are distinct from invoices, payments can be allocated across several invoices, and sensitive changes write to an append-only trail.
- Shared rules prevent gentle drift
- Audience targeting, schedule aggregation, status meaning and assessment state are centralised, so five parts cannot quietly calculate five different answers to the same question.
Where it got to
The core administration experience and the first-year teacher workflow are implemented and verified: around 3,000 automated tests, 71 pages under accessibility and performance review, and an independent recovery copy still outstanding.
- No school is using this in production, so there are no adoption or outcome figures.
- A human screen-reader assessment is still outstanding; accessibility figures below are automated checks only.
- Final data-processing sign-off and an independent recovery copy remain before any production release.