The rule for leave records: application, approval, departure, return — all four events recorded with dates and approver. Verbal permission, a tick on the register cover, or keeping it in memory all end in the same place: the student did not return, nobody remembers who approved, and the guardian’s question has no answer.
What to verify: application-approval and return verification
A leave record must carry these fields:
| Field | Example | Why it exists |
|---|---|---|
| Student + department | DEMO-031, Hifz | whose record it enters |
| Reason | home, medical, family | seeing patterns later |
| Direction / companion | to home, with guardian | safety accountability |
| Departure date-time | 12 Nov, afternoon | reconciliation with attendance |
| Approver | room ustadh → muhtamim | fixed duty |
| Return date-time | 15 Nov, morning | proof the leave closed |
| Return verifier | who saw the student back | accountability |
The most common error sits in the return field: leave is granted, return is never recorded — then the student counts as “absent” on the roll and an unexplained SMS goes to the guardian.
A usable sample: the permission review checklist
Before closing any leave event, ask four questions:
- Does the approver have the authority to grant this leave (by role)?
- Is guardian consent recorded (a call note or written)?
- Did the departure affect the attendance list?
- Is the return recorded — when, and by whom?
At month-end this checklist reveals: which students take frequent leave, and which leaves are “without a return record”.
Leave records: workflow steps and limitations
- Fix leave types first: daily / overnight / extended / medical — do not merge all into one filter.
- Split approval levels: a day-leave by the room ustadh, an overnight leave by the muhtamim — everyone granting everything blurs accountability.
- The return should remove the student from the absent list — not by hand.
- Limitation: emergencies record late — in that case add an “emergency note”; do not delete anything.
Leave records: questions to ask before your demo
- Are leave and attendance connected in one system — does an approved leave reconcile that day’s roll automatically?
- Is a leave without a return record flagged as “open”?
- Can the guardian see the leave status in the app?
To connect leave with attendance see the attendance documentation and the attendance module; guardian contact via the communication module; the boarding context in madrasa operations.
Leave records FAQ
Why keep leave and absence separate?
Absence raises questions; an approved leave does not. Merged, even frequent approved leave looks like a “problem” — a false pattern.
Do we need leave types on the admission form?
Small madrasas do not — a return record is enough. Large boarding institutions benefit from type-based filters.
Should the guardian’s written application be kept?
For electronic leave the system record is enough; if a paper application exists, ask in the demo for an option to attach its scan/photo to the record.