The rule for preserving former student records: when a student leaves, do not delete them — change their status (enrolled → passed → left/graduated). The current-student list stays small, but the institution’s history — who passed which jamaat in which year, when their Ijazah was granted — is an asset like fifty years of paper files.

What to verify: current enrolment vs prior history, kept separate

The record lifecycle should look like this:

Status Meaning What must be known in this state
Enrolled current student jamaat, room, guardian, fee balance
Passed/not passed year ended, jamaat changes which jamaat, what result
Left permanent departure date, last jamaat, reason
Graduated/completed course finished Ijazah/certificate, year

The core test: when an old student returns (asking for a certificate copy, a marriage-nikah verification), can you show the entire history from the left status? A system that deletes on departure is not a record — it is a temporary list.

A usable sample: the record lifecycle table

Each student file carries these events in time order:

  1. Admission — date, jamaat, guardian.
  2. Department change (Hifz → Kitab) — date, reason, approval.
  3. Annual result — jamaat + result per session.
  4. Significant leave/discipline events — with dates (otherwise later questions have no answers).
  5. Completion/departure — date, status, certificate number.

After configuring the lifecycle, test it: admit one fictional student, run the full cycle, then confirm every event is visible in one profile.

Alumni records: workflow steps and limitations

  1. Digitise at least the last 5 years of old registers — certificate-verification demand comes from exactly there.
  2. One person = one permanent ID — do not create a new ID for a new jamaat.
  3. Keep departure reasons categorised (completed / transferred / removed / family decision) — the statistics become useful later.
  4. Limitation: very old years may have different name spellings — proving “same person” during certificate verification remains the institution’s duty.

Alumni records: questions to ask before your demo

  • Can departed students be filtered separately (by year, by jamaat)?
  • Is re-printing a certificate/Ijazah possible from the departed status?
  • If an old record is edited, is there a history?

Configure the record cycle with student management features, Ijazah certificates in the Hifz module, and certificate printing in the certificates features.

Alumni records FAQ

How long should records be kept?

At least the course cycle plus the real life of certificate verification (often 10–20 years). Storage cost is negligible — there is usually no reason to delete.

Two students with the same name?

The permanent ID separates them — adding a guardian’s name to create a “new person” is not the rule.

A departed student returns — re-admission?

A new “enrolled” status on the same ID — the earlier cycle stays in history. Creating a new ID splits the file in two.