Tracking progress
Two views of the same data, for two different questions.
Table view
Every plan with its owner, target date, status and completion percentage. This is the working view — sort by target date to find what is late, or by completion to find what has stalled.
Timeline view
The same plans as bars on a calendar, with controls, tasks and sub-tasks nested underneath. Use this for the question “will we make the date?” rather than “what is the status?”
The legend explains the bar colours; select it if a state is unclear.
How completion rolls up
Completion is calculated bottom-up:
- A sub-task is done or not done.
- A task is the proportion of its sub-tasks complete.
- A control is the proportion of its tasks complete.
- The plan is the proportion of its controls complete.
Because progress rolls up from real work — and, when Jira sync is enabled, from real Jira issues — the number is not somebody’s estimate. It is the state of the work.
What progress does to the risk
Completing a planned control changes its implementation status, which moves it from planned to existing. That changes the residual score, not just the target. This is the whole loop closing: work gets done, and the risk actually goes down.
Overdue plans
A plan past its target date is flagged on the risk and counted in the register’s quick stats. If the risk is above appetite and its plan is overdue, that combination is the first thing a risk committee should be shown.