Every module, grouped the way the app groups them

• Enrol a student and attach a guardian in one form. A guardian whose phone number is already on file is reused, so a second child does not create a second parent.
• Attaching a guardian creates their portal account: a memorable password, sign-in by phone number, and a forced change on first use.
• Teachers and support staff share one employee record with separate permissions and separate pages.

• Class levels carry their sub-system, their cycle, whether marks are out of 20 or out of 100, and which report card layout they print.
• Subjects carry a coefficient, a group and a head of subject. Six sequences across three terms.
• Timetable, homework, examinations and per-class exam papers.
• Attendance is recorded per day and shown per student, per class and on the report card.

• Subject averages per sequence first, then across sequences, so two papers in one sequence cannot make that sequence count twice.
• Moyenne générale weighted by coefficient, and a rang where ties share a position rather than being broken on a name.
• A missing mark is not a zero. The student is averaged over the subjects they sat and the row prints blank.
• Class average, minimum and maximum, per-subject statistics and subject rank, and an appréciation from your school's own grade bands.
• An issued report card is a snapshot. Correcting a mark afterwards changes nothing until somebody re-issues, which bumps the version and the date.
• Four layouts, built to what a Cameroon bulletin carries: the bilingual state header, coefficients, sequence columns, class statistics, rang, appréciation and signature blocks. Prints on A4 from the browser.

• Fees: invoices and payments, with the invoice total kept correct by database triggers rather than recomputed per page.
• Library: books and loans. Hostel: rooms and allocations. Transport: routes and subscriptions.

• Payroll runs and payslips with CNPS deductions.
• Income, expenses, and a read-only transaction view across both.

• Raising an invoice puts a message in the guardian's portal inbox, every time.
• A WhatsApp copy is queued alongside it. With no provider connected, the message is composed and addressed and a person presses send from the outbox page. Connect the Meta Cloud API and the same queue sends itself.
• An undelivered message is a row with a status, so nothing disappears between the outbox and the family.

• Import students, guardians, teachers, staff, subjects, class levels and classes from Excel. Download the template, upload, preview what will change, then commit. Column headings are recognised in English and French.
• Roles and permissions as a grid: twenty-six modules by five actions, per role, per school. Editing it is audited.
• The query layer applies row-level scoping, so a page cannot widen it. A parent asking for fees gets their own children's rows; a student gets their own.
• Every create, update and delete is written to the audit log with the user, the table, the record and the changed values.
• CSV export on every list page, with no export fee and no notice period.

The full GCE walkthrough