The whole school, module by module
Eight modules, one database. A pupil is entered once, at admission, and then goes through marks, attendance, finance and the report without being retyped.
From the family’s enquiry to an enrolled pupil, with no gap in the file.
- Admission request, traced exchanges, waiting list.
- Required documents: شهادة المغادرة, birth certificate, guardian’s ID. While a document is missing, enrolment cannot be completed.
- A priced quote built on the level’s fee scale, deposit recorded as family credit and applied automatically at enrolment.
The whole school’s timetable is generated in one go, and refuses the impossible.
- Generation for one class, one level or the whole school, from the official weekly hours.
- A teacher, a class and a room cannot be in two places at once: the clash is refused as you type, not reported afterwards.
- Closed slots, dated absences, service ceilings: whatever cannot be placed is listed with its reason, never forced.
One place computes an average, and a published report never changes.
- Entry by subject, absence codes, coefficients and rounding set by the school.
- Two report models: the national framework and the school’s own, in French and in Arabic.
- Twelve checks before publication; a published report is frozen and reads as it was handed over.
The register, absence notes, incidents, sanctions from the school rules.
- Register by half-day or by lesson, absence notes, counts by term.
- Only registers validated by the discipline office count towards the report.
- Incidents and sanctions: the family only sees what it was notified of.
Payment schedules, receipts with continuous numbering, prepared reminders.
- Fees by level, automatic schedules, after-school services billed to whoever signed up (canteen, transport, study).
- Payments to the centime, receipts numbered in a continuous series: a number is never reused and never deleted.
- One unified reminder queue, message prepared, sending decided by a person.
Sessions, papers, rooms, invigilation shared out without clashes.
- Pupils allocated to rooms according to their real capacity.
- A subject teacher does not invigilate their own group: that is refused as you type.
- A teacher absent or unavailable on the exam date is not proposed as an invigilator.
A parent sees what concerns them, and nothing else.
- Reports, notified absences, payment dates, activities and parental permissions.
- A parent only reaches their own children’s documents: verified, refused otherwise.
- Pupil accounts in lower and upper secondary.
The dashboard, the staff, the school’s own rules.
- Terms, coefficients, grades, subjects, rooms, fee scale: the rules are configured, not hard-coded.
- Staff accounts created by the school, initial password shown once only, an account is deactivated rather than deleted.
- Action log: who entered what, and when.
Each role, its own screen
Permissions are not a convenience setting: they decide what a person can read and write. They are checked on the server, not merely hidden on screen.
What is not delivered today, and therefore not sold
- The Massar-format export: the Massar code is kept in the pupil’s file, but the export needs a real school file to be built without inventing anything.
- Automatic SMS and WhatsApp messages: messages are prepared by the software, sending remains a human action.