🚧 Checkpoints – Sub-Tasks for Long Tasks

👤 Who Can Access

🚧 Checkpoints are automatically generated by HOLIZE for long-running tasks inside a 📋 Project Plan.
Only Project Managers and L1/L2 Managers can view and manage the follow-up workflow triggered from these checkpoints.

Checkpoints are mini-milestones created within a task from the 📋 Project Plan to ensure steady progress.
For example, a 20-day task may have checkpoints every 5 days.
Each checkpoint has a planned start and end date. As per these planned dates, a ⛏️ Worklog is triggered to the Project Manager, who forwards it to the Team Lead, and then to the Team Member.
This ensures that progress inside long tasks is not silent — but tracked, confirmed, and escalated if needed.

Checkpoints are only generated for tasks where the duration is at least 5 days (configurable).
If a task is shorter than the configured default checkpoint span, checkpoints will not be created.

📋 Number of checkpoints is automatically calculated by HOLIZE based on the task's duration from the 📋 Project Plan
📅 Checkpoints are spaced evenly between the planned start and end dates of the task
🧠 Each checkpoint is tracked for on-time closure

📬 As per planned start date of every checkpoint, ⛏️ Worklogs are auto-triggered to the respective Project Managers
🔁 If a checkpoint is missed (i.e., not discussed or closed on time):
▫️⚠️ If still not addressed: HOLIZE auto-creates a ⚠️ Risk (if the parent task is upcoming) or an 🔥 Issue (if the parent task is ongoing)
▫️🛡️ This protects the flow of the 📋 Project Plan from silent task delays