The challenge
A private school group operating several campuses was running coursework, grading, and parent communication through a mix of messaging groups, printed handouts, and a separate spreadsheet per teacher. Assignments were distributed in whichever channel a teacher preferred, submissions came back as photos and attachments in chat threads, and end-of-term grades were assembled by hand from spreadsheets that only their author fully understood.
The group had no shared academic record. A student who moved between campuses effectively started over, a parent asking about progress got an answer only as current as the last teacher who checked their own file, and administrators had no way to see how a class or a subject was tracking without asking each teacher individually. Every term rollover meant recreating class lists and grade sheets from scratch.
They also needed the platform to work in Arabic and English, on the phones parents actually use, and on the mixed connectivity a campus network provides — not just on a laptop in a staff room.
Our approach
We built a learning management platform structured around the academic calendar rather than around individual documents: terms, courses, sections, and enrollments are first-class records, so class lists and gradebooks are generated from enrollment data instead of being retyped each term. Assignments, submissions, and feedback all live against the course they belong to, which means a student's academic history follows them across campuses instead of ending at a teacher's spreadsheet.
The gradebook is derived, not typed. Teachers record marks against individual assessments with their defined weights, and term grades are computed from those records — so a corrected mark propagates automatically and the calculation behind any grade can be inspected rather than trusted. Roles are separated deliberately: teachers see their own sections, parents see only their own children, administrators see the whole group, and access is enforced on the server rather than by hiding menu items in the interface.
Bilingual Arabic and English support and full right-to-left layout were built in from the first screen, not retrofitted. File uploads go to cloud object storage rather than through the application server, so submitting a large assignment on a slow campus connection doesn't tie up the platform for everyone else.
Outcome
The group now has one academic record per student that persists across terms and campuses, instead of a set of teacher-owned spreadsheets. Parents check progress themselves rather than waiting for a scheduled update, and term rollover is a structural operation on enrollment data rather than a manual rebuild of every class list.