The rule after software goes live: four numbers + one list — in five minutes weekly. Buying software is not management; the first three months decide whether the system runs forever or falls back to registers. Five minutes weekly is that decider.
The four weekly numbers
| Number | Where | Why it matters |
|---|---|---|
| Attendance entry coverage | all classes marked? | once entry discipline breaks, all reports become incomplete |
| Absence SMS delivered% | delivery report | guardian connection still running? |
| Dues list movement | fee module | are dues shrinking or growing |
| New entries (admissions/changes) | office | data staying current |
The list: what looks “good” but is not
- All attendance complete — but no absences at all? Impossible in reality; entries are not being made properly.
- No receipts all month? The collection pipeline is off.
- The same teacher repeatedly entering late — needs training.
Five minutes of these by the muhtamim/head weekly keeps the system running forever; three months of not looking guarantees the return to registers.
Weekly review: workflow steps and limitations
- The five minutes belong to one named person — everyone’s duty is nobody’s duty.
- Issues found get weekly actions too — “will look at month-end” delays bring the system back to registers.
- Limitation: entries get missed in the first month — that is habit-building time, not a system fault; keep patience.
Weekly review: questions to ask before your demo
- Does a weekly summary (attendance completeness, delivery%, dues) come on one page?
- Are entry-skipped classes listed?
See the weekly view in dashboard features; delivery status in the communication module, dues in fee management.
Weekly review FAQ
Whose weekly check is it — the muhtamim or the office?
The muhtamim/head looks; the office prepares the data — the five minutes exist for the decision.
Found an issue — tell the vendor or the staff?
Staff first (habit problems), vendor second (system problems) — the number separates the two kinds.
Is weekly verification really necessary?
Five minutes — and those five minutes build the difference between software success and failure; after three months it can drop to monthly.