Skip to content

Understand page coverage and milestones

Coverage reports answer which canonical Quran content has been completed—not just how much activity was recorded. They require approved page-position data and qualifying recitation outcomes.

Waqar student page-coverage report with full, partial, and remaining ranges

For an authorized student, the report can show:

  • current page position;
  • pages fully covered;
  • pages partially covered;
  • per-page completion percentages;
  • covered Quran ranges;
  • remaining ranges;
  • underlying workload used for the calculation.

A page can be partial because only part of its canonical Quran range qualifies. Touching a page once does not make it fully covered.

Milestones mark supported Quran boundaries such as pages, rub al-hizb, hizb, juz, ruku, or manzil when the approved dataset includes them. A milestone reflects canonical position and qualifying coverage; it is not created merely by typing a label.

  • Activity counts each qualifying recitation’s measured work. Repeated review can add activity again.
  • Unique coverage unions qualifying Quran ranges so the same covered content is not counted repeatedly.
  • Page touches count encounters with pages.
  • Distinct pages touched count each encountered page once.

State the selected measure whenever reporting a result.

Zero-rated Repeat attempts remain in history but do not count as completed coverage. Date, semester, student, halqa, and recitation-type filters can alter the result. Learning Plan assignments alone do not create actual coverage; saved qualifying recitations do.

School administrators open coverage from Reports or a student record. A sheikh opens it from an assigned student’s record and cannot discover or open an unassigned same-school student. A parent can see only a linked child’s parent-visible coverage or milestones. Report return links lead each role back to its allowed student or child workflow.