Student information.

Most schools keep a child in a dozen places at once — an admissions folder, a class register, a fees ledger, a sick-bay note, a WhatsApp group of parents. When a question comes (Which class? Whose phone do we call? Are they allergic to anything? What do they still owe?) the answer means hunting across all of them.

The Student Information System collapses that into one record. The roster at /dashboard/students lists every student; each one opens to a profile that gathers their whole school life in one place. Money is shown in the school's own currency, every screen reads cleanly in English, French, or Arabic and on a phone, and the headline numbers at the top — total, active, new this term — update the moment a record changes.

The roster at /dashboard/students is where every student lives. Search by name; filter by status, gender, or campus; sort any column. A gold bulk-action bar appears when you select rows, so you can change status or move many students to the trash at once. Anyone with the export permission can pull the whole list to CSV with one click, and a toggle reveals the trash for anything recently deleted.

New students arrive two ways: added one at a time through the create form, or — most often — converted automatically from an accepted admission application, which carries the original file across as intake context. Every student carries a unique matricule (their student-id, unique within the school), a class and section, a programme, and a campus.

Open any student and you land in their mini-world — an identity header with photo, status pip, class and campus, followed by a vital-signs strip (attendance rate, academic average, behaviour score, outstanding fees) and then a set of rooms. Only one room is open at a time, so the page is never an overwhelming wall; you click the room you need. The profile lives at /dashboard/students/[id].

From the right-rail actions you can edit the record, print a committee-ready packet, message the whole family (the send is logged to the notes thread), add a discipline record, upload a document, and run the lifecycle actions — withdraw, readmit, or mark a transfer-in — without leaving the page.

A child is rarely an island. The guardians directory at /dashboard/parents holds every parent and guardian, each linked to one or more children with a stated relationship (mother, father, uncle, sponsor) and flags for who is the primary contact, who is an emergency contact, and who can collect the child. The roster shows at a glance who is linked and who is not, so a guardian record with no children attached never slips through unnoticed. (A separate, lighter list of non-portal contacts can also be attached straight to a student, so even a relative who never logs in is still recorded.)

The link is what makes the family real to the rest of YESS. A linked guardian receives the child's fee receipts and overdue reminders, sees their grades and attendance in the parent portal, and — when they have more than one child at the school — switches between them in a single login. Siblings are derived from shared guardians, which also carries sibling discounts in finance and feeds the sibling lookup in admissions.

A student's status moves through a clear lifecycle of five states — active, withdrawn, transferred, graduated, and suspended. Withdraw a student and a time-in-status chip starts counting so the re-engagement window is visible, with a recorded reason (relocation, financial, behavioural, health, family, and the rest) and a last-attended date; readmitting preserves the matricule and the whole history. Students who arrived from another school can be marked transfer-in with their previous school recorded, and an intake-source badge tells any operator at a glance how the child entered — walk-in, online self-service, batch import, or direct admission — with a deep-link back to the original admission file.

The most sensitive facts are the most protected. Safeguarding flags — trauma, SEN/IEP, an active behaviour-intervention plan, a mental-health alert — surface as discreet pills on the profile so a counsellor sees the lens before they judge any single event. The accommodations card (SEN / IEP / 504 / EHCP and the specific adjustments under them) and the school's infirmary records carry their own row-level security in the database; the medical summary and the safeguarding flags on the record are gated by permission so only the right staff ever see them.

The record is the centre, but a few focused surfaces orbit it. The at-risk queue at /dashboard/students/at-risk gathers the students whose attendance, grades, behaviour, or lateness signal that someone should reach out — each flagged student decomposed into those four factors, with acknowledge and dismiss actions for the counsellor working the inbox.

Academic standing lives at /dashboard/students/standing, a per-term decision list driven by GPA. And a student's own academic surfaces — their /dashboard/students/[id]/subjects choices, their /dashboard/students/[id]/conduct timeline, their /dashboard/students/[id]/transcripts, and a /dashboard/students/[id]/degree-audit — each open from the profile, so the record is the hub and never a dead end.

The student record is the spine almost every other module reads from. Some links flow in automatically; some are configured.