Planned vs. Unplanned Work
Planned versus unplanned work shows whether completed work followed the plan or came from unplanned intake.
What it measures
The dashboard chart is called Planned vs Unplanned Work. Completed tasks linked to initiatives count as planned. Completed work that is not linked to an initiative counts as unplanned.
This is about initiative-linked completed work. It does not read Jira, Linear, GitHub, or GitLab issue status as the plan by itself.
The chart appears in Insights when initiative allocation data exists for the selected workspace or team.
Planned vs Unplanned Work
Distribution of planned and unplanned completed work
How to read it
A high planned share usually means completed work is attached to initiatives before it ships. A high unplanned share does not mean the team is doing the wrong work. It means more work is coming through interrupts, bugs, support, operations, or undocumented decisions.
It helps decide whether unplanned work should become a tracked initiative, move through Triage, or change the roadmap conversation.
How to improve the data
Link completed work to its initiative, and keep statuses and owners current. Route reactive work through the backlog or triage instead of hiding it inside feature initiatives.