Configure tracks and workload

A track describes one kind of Quran work inside a Learning Plan. Each selected track advances independently and retains its own workload and tolerance.

Choose only tracks the learner will actually use:

• New memorization
• Recent review
• Distant review
• Tilawa

A plan cannot contain the same track type twice. The recitation type recorded in a session must match the planned track before Waqar can apply its outcome.

Waqar can offer:

• Lines using the selected Quran dataset’s verified line workload;
• Ayahs;
• structural Pages, Ruku, Quarter hizb, Hizb, Juz, or Manzil when the dataset advertises the required structural positions.

Page availability is a capability shown by Waqar, not something staff should assume. If page positions are unavailable, use a supported unit rather than estimating page boundaries manually.

The Target workload is the desired amount per generated assignment. Tolerance ± defines the permitted variation around it. Waqar considers eligible ayah endpoints and can prefer a meaningful structural boundary inside that tolerance.

For example, a target of 10 ayahs with a tolerance of 2 permits a result from 8 through 12 ayahs. The selected result can differ to finish a preferred boundary. Always review the explanation shown with generated work.

1. In Create Learning Plan, add each required track.
2. Select its recitation type and offered workload unit.
3. Enter a positive target and a non-negative tolerance.
4. Repeat for other distinct tracks.
5. Create the plan and open Effective configuration.
6. Verify the effective target, unit, tolerance, source, and boundary order for every track.

An administrator can set school and halqa defaults. On a plan, permitted staff can expand a track override and set target, tolerance, deviation preference, minimum workload, small-remainder handling, and ordered boundary preferences. More specific values override less specific ones.

Use a minimum workload to avoid impractically small assignments. Use small-remainder handling to avoid leaving a tiny final fragment when an eligible endpoint can absorb it. Boundary priority influences selection only inside valid Quran ranges and permitted tolerance.

Review the result in page and partition planning and planning reports.