A residential madrasa record must always contain at least three things: which room a student is in, who is responsible for that room, and who authorised any trip outside the gate (leave). Vendors will capture the admission-form data themselves — it is these three boarding-specific verifications that most implementations miss.

What to verify: room responsibility and authorised guardian contact

Keep at least these fields for every residential student:

Field Why it exists Common mistake
Room number + roommates night roll-call and tracing issues assuming room = class
Responsible ustadh for the room first contact in an emergency responsibility never written down
Authorised guardians list who may legally take the student out treating a phone number as permission
Leave history return times and who approved leave on paper, attendance in software
Health/medication note duty staff awareness showing sensitive notes to everyone

The guardian-contact field is the most sensitive: a student leaves only with an authorised person. The rule of “which number is valid to call” must exist in writing.

A usable sample: the hostel onboarding checklist

Treat a new resident’s record as incomplete until these steps are done:

  1. Room allocation — room number and roommates recorded.
  2. Room ustadh assigned — who checks the night roll.
  3. Authorised guardian contact — name, relation, number.
  4. Special instructions — medication, diet, any restriction.
  5. Leave rules explained — who approves, how it is recorded.

Check the first night roll-call: if the new student appears on the room list, the pipeline works.

Hostel records: workflow steps and limitations

  1. The software must produce both room-wise and jamaat-wise lists — giving only one pushes the other back to paper.
  2. Leaving and returning are two separate events — record the time and approver of each.
  3. When a guardian’s number changes, keep the old number in history.
  4. Limitation: biometric or RFID door security is not part of ordinary software bundles; treat it as a separate project if needed.

Hostel records: questions to ask before your demo

  • Can we take a room-wise night roll-call, or is all attendance only by jamaat?
  • Can we create a separate leave-approver role?
  • Can we control that SMS never goes to a non-authorised number?

For the full boarding picture see madrasa operations and the boarding features; to connect leave records with attendance, read the attendance documentation.

Hostel records FAQ

Should day attendance and night roll-call be separate?

Yes — jamaat attendance measures teaching work; room roll-call measures responsibility. Test both in the demo.

Can a guardian request leave in the app themselves?

Depends on the system — but approval must live in the record, not in conversation. Run one full leave cycle (request → approval → return) in the demo.

What happens to records when a room changes?

History should persist — which room, which dates. A system that only shows “current room” cannot answer accountability questions.