Student Information System

One student record the whole school can trust

Profiles, guardians, sections, documents and academic history in a single record — so the registrar, the class teacher and the head are reading the same thing.

What usually goes wrong

  • A student's details live in the admissions sheet, the class list, the bus list and the nurse's folder.
  • When a guardian's phone number changes, four places need updating and two get missed.
  • Prior-school history arrives as a PDF and then effectively disappears.

What this module does

One record, many views

Registrar, class teacher, nurse and transport coordinator each see the same student through their own lens, with access scoped to role.

Guardians and custody

Multiple guardians per student with contact priority and collection authorisation recorded — not a single 'parent phone' field.

Sections and movement

Year group, section and stream changes are tracked over time, so a mid-year move does not rewrite history.

Documents with expiry

Visa, passport and medical documents carry expiry dates that surface before they lapse rather than after.

Why this fits UAE schools

A UAE student record has to survive visa renewals, a transient population and families moving between schools each summer. Documents, guardians and prior schooling are first-class fields rather than notes.

How it runs day to day

  1. 1

    The record opens

    A student record is created once, at admission, and everything afterwards attaches to it. Nothing about the child should ever need creating a second time.

  2. 2

    Family and household are linked

    Guardians, siblings, contact preferences and who may collect the child are held as relationships rather than as repeated text fields on separate records.

  3. 3

    Documents and expiry dates are tracked

    Passport, visa and identity documents are held with their dates, and approaching expiries surface before they lapse rather than after.

  4. 4

    The record accumulates

    Attendance, assessment, medical notes, inclusion plans and behaviour entries all reference the same student, which is what makes a complete history possible at all.

  5. 5

    Documents are generated from it

    Certificates, letters and extracts are produced from the record itself, so what leaves the school matches what the school holds.

  6. 6

    The student leaves with their history intact

    On departure the full record is exportable, and what stays behind remains available for the records requests that arrive years later.

The cases that usually break things

Any system handles the straightforward path. These are the situations that decide whether it survives a real school year.

The same child exists twice under different spellings

Duplicates are surfaced for a human to judge rather than merged automatically or left to quietly break every report that counts students.

A student leaves and comes back two years later

They return to their existing record with the earlier history attached, instead of becoming a new student with no past.

Parents separate and contact rules change

Guardian relationships, contact permissions and collection rights are held per guardian, so the change is recorded once and applies everywhere.

A student moves up a year group

Historic attainment and attendance stay attached to the student rather than to the class, which is what makes multi-year trends possible.

Someone asks for a record from six years ago

Historic data migrated in and stayed. A record that begins on the migration date cannot answer this question at all.

A sensitive note must not be broadly visible

Medical, safeguarding and inclusion entries sit in restricted categories rather than being visible to every account with a login.

Frequently asked questions

Can we import our existing student data?

Yes. Import is by year group so it can be staged, and the first pass is validated against a report before anything is committed.

Who can see a student's full record?

Access is role-scoped. A class teacher sees their own students; medical and pastoral detail is restricted to the staff whose role requires it.

What happens when a student leaves?

The record is retained per your retention policy with a leaving reason and date, so transfer certificates and historical reporting still work.

Can we add fields specific to our school?

Yes. Schools track things that no standard schema anticipates, so custom fields can be added to the student record without a development request.

How are photographs handled?

Student photographs attach to the record and flow through to class lists and registers, so staff are not maintaining a separate photo folder that goes stale each year.

Can we bulk-update at the start of a year?

Yes. Year-group promotion, class allocation and status changes run as bulk operations rather than student by student, which matters when the roll runs to thousands.

Who decides what each staff role can see?

The school does. Roles are configured to your actual staff structure, and sensitive categories are restricted separately rather than bundled into a general staff permission.