The rule for daily attendance review: look at department-level exceptions every day — absent, late, or unexcused — and record a decision for each exception the same day. Reading the full student list daily is nobody’s job; normal presence wastes time. Exceptions are the work.

What to verify: department-level daily exception handling

A review structure should look like this:

Time Who looks What they look at Decision
10:00 department ustadh absences in own class contact made, SMS sent?
Noon room ustadh absent in room but present in class reconcile location, fix the error
Afternoon muhtamim/nazir combined exception list whose action is pending — list

The most common exception: a student is in class but missing from the room roll-call (or the reverse). Reconciling the two lists must happen the same afternoon — by the next day the error has become history.

A usable sample: the daily review log

Keep the daily review in four columns (paper or software — either works):

  1. Date and department.
  2. Exception — student name + type (absent / late / half-day).
  3. Action — guardian informed / room checked / record only.
  4. Resolution status — resolved / pending / family contact needed.

At month-end this log answers: which student is frequently absent, which department enters late, whose corrections are incomplete.

Daily attendance review: workflow steps and limitations

  1. Fix the roll-call time — the first ten minutes of class.
  2. Close the correction window — yesterday’s attendance cannot be edited today; only a correction note is added.
  3. Every exception row carries a named responsible person.
  4. Limitation: attendance software records, it does not verify truth — the honesty of roll-calls remains human. Keep the daily reviewer.

Attendance review: questions to ask before your demo

  • At day’s end, can the combined exception list be seen on one page?
  • If an attendance entry is corrected, is there a history of who changed it and when?
  • Does the absence SMS go out immediately with the entry, or in a later batch?

Build the review structure with the attendance module and its step-by-step documentation; for the economics of guardian notifications, see the communication module.

Attendance review FAQ

Who reviews daily — the ustadh or the muhtamim?

Two levels: the ustadh reviews own-class exceptions; the muhtamim reviews the combined list. One level works for small institutions, not large ones.

Is a paper exception log acceptable?

It works — but month-end reporting requires writing everything a second time, and that second writing is where most errors are born.

Is SMS mandatory?

Not for every event — but a guardian should know about absences; unnotified absences grow.