The rule for catching revision exceptions in Hifz: keep planned revisions and completed revisions in two separate records, then reconcile one against the other at week’s end. Manzil cycles slip in small daily pieces — nobody notices in one or two days, and three months later a whole Juz has eroded. You need a gap-finding system, not memory.

What to verify: assigned and completed revisions, kept apart

The two-column structure:

Column Meaning Written by When
Planned which Juz should be cycled today per the plan cycle planning week start
Completed was it actually cycled ustadh day end

Week-end gap = planned − completed. Classify three gap types separately:

  1. One-day gap — normal; no note needed if covered next day.
  2. Continuous gap (3+ days) — student-specific; re-plan the manzil cycle.
  3. Pattern gap — the same Juz missed by a whole jamaat — a routine problem; fix the schedule.

A usable sample: the revision gap table

The week-end table (per student):

Student (ID) Cycle Planned Juz Completed Gap days Class Action
H-014 1 Juz / 7 days Juz 15 6 1 one-day note
H-022 1 Juz / 7 days Juz 15 3 4 continuous cycle to 10 days + guardian note
jamaat total — Juz 21 0 — pattern fix the routine

Zero gaps is not the goal — gap visibility is. One-day gaps across twenty students are normal; the danger is continuous and pattern gaps staying invisible.

Manzil revision gaps: workflow steps and limitations

  1. Write the cycle plan at week start — otherwise “planned” has no meaning.
  2. Match action to gap class — a guardian call for a one-day gap is excessive.
  3. Month-end: is the continuous group shrinking — the measure of whether actions work.
  4. Limitation: the gap table does not treat holidays as equal — exclude holiday days from “planned”, or holidays will show as gaps.

Revision gaps: questions to ask before your demo

  • Can manzil keep “planned” and “completed” separately?
  • Is the gap calculated automatically, or extracted by hand?
  • Can holiday days be excluded from the cycle?

See the Hifz & Quran module and the Hifz tracking documentation for structural solutions; the glossary sharpens terminology.

Revision gaps FAQ

What cycle pace is right for manzil?

Based on your department’s current pace — typically 1 Juz per 7–10 days. Write it down; otherwise “planned” means nothing.

Is a gap always the student’s fault?

No — pattern gaps are usually schedule problems. Student faults stay with students; pattern faults with planning — do not merge them.

Can gaps for all Juz live in one view?

Yes — but keep a Juz-based filter; one Juz’s problem can hide another’s.