Automatic Objective Mastery

1. What does this feature do? (High-Level Overview)

This process automatically checks whether plan objectives should be marked as mastered based on weekly report results. When the required pattern is met, it advances the objective status and moves the plan forward without manual review.

2. Who is this for? (Roles & Permissions)

• System: Runs the evaluation in the background.
• Technical operations: Can trigger the process indirectly by generating or updating weekly reports.
• Administration: Benefits from the automatic progression of objectives inside the plan.

This flow is internal to the backend and does not depend on a frontend screen.

3. Business Rules & Enforcements

• Rule 1: The process evaluates only STO objectives that are already in progress.
• Rule 2: An STO must have all required mastery fields filled in: weeks_to_complete, comparison_operator, and target.
• Rule 3: The system checks the most recent weekly reports up to the evaluation date.
• Rule 4: The weekly reports for an objective must cover the required number of consecutive weeks.
• Rule 5: If the plan uses a weekly timeframe, the raw weekly value is compared directly to the target.
• Rule 6: If the plan uses an hourly timeframe, the system adjusts the weekly value before comparing it to the target.
• Rule 7: If the objective meets the rule for the required number of consecutive weeks, it is marked as mastered.
• Rule 8: When an STO is mastered, the next STO in sequence is moved to in progress and starts the day after the mastered objective ends.
• Rule 9: When all STOs are mastered, the plan’s LTO is moved to in progress.
• Rule 10: The process does not reverse or downgrade objective status once mastery has been applied.

4. UI Placement

No UI screen applies to this process because it runs in the backend.

5. How-To Guide (Step-by-Step)

Scenario A: Weekly mastery check after report generation

1. Weekly reports are generated for a plan.
2. The system evaluates the STO objectives tied to that plan.
3. It checks whether the reports satisfy the objective rules for the required number of consecutive weeks.
4. If the rule is met, the STO is marked as mastered.
5. The next STO, if available, is moved to in progress.

Scenario B: Objective progression after manual weekly report updates

1. A weekly report is created, updated, or imported manually.
2. The backend runs the same objective evaluation.
3. The system re-checks the affected plan using the latest available weekly report date.
4. If the objective now meets the rule, it is mastered.
5. The plan progress is updated automatically.

Scenario C: What happens when all STOs are mastered

1. The system evaluates the STOs for a plan.
2. If all STOs are already mastered, it checks the plan’s LTO.
3. The LTO is moved to in progress.
4. The LTO starts the day after the latest STO end date.

6. What happens if…? (Edge Cases / FAQ)

• Q: What happens if an STO does not have the required mastery fields?
  • A: It is ignored by the automatic evaluation.
• Q: What happens if the weekly reports are not consecutive?
  • A: The objective is not mastered until the required consecutive weeks are present.
• Q: What happens if the plan uses hourly tracking?
  • A: The system adjusts the weekly value before comparing it to the target.
• Q: What happens if the next STO is already in progress or mastered?
  • A: The system leaves it unchanged.
• Q: What happens if the LTO is already in progress or mastered?
  • A: The system leaves it unchanged.

---

APPENDIX

Evaluation Rules

• Only STO objectives in progress are evaluated.
• Mastery requires the configured number of consecutive weekly reports.
• The evaluation can use the weekly report date passed by the caller as the upper bound.
• The objective starts being considered from its own initial date when one is set.