Imagine you’re reviewing a roadmap you approved at the start of the quarter. Since then, the roadmap has evolved - dates shifted, scope changed, items were added and others dropped.
But there’s a problem: the plan you originally agreed to is no longer there. As work items changed and various fields got updated, you can clearly see where things stand now, but it's hard to see what you originally agreed to.
The ‘Planned vs Actual’ view mode brings that original commitment back into focus. It displays the plan as it was saved and highlights where changes were made, so you can see what stayed the same, what changed, what was added, and what left the plan.
Use Planned vs Actual when the question is about the commitment: what did we agree to, and what became of it?
Before you begin
The 'Planned vs Actual' view mode compares the plan as it was saved with what happened to it afterward.
Before using this mode, you will need a saved plan to use as the baseline for the comparison.
If you haven't created one yet, see Getting started with Actual vs Planned to create and save your first plan.
💡 Planned vs Actual is read-only: This mode is designed for reviewing the original plan compared to the current state, so you can’t make changes directly on the view.
How it works and what it shows you
With 'Planned vs Actual' view mode selected, the roadmap shows the plan as you saved it, while what happened since is laid over each item. The same three signals from the 'Actual vs. Planned' view mode surface what changed.
3 signals show you what became of the plan:
'Changed fields' badge - how many tracked fields changed.
'Changed values' highlighted on the item - which visible values changed from the plan.
Items entering or leaving the plan - which items were added, descoped, or deleted.
1. 'Changed fields' badge
The round yellow badge on the right side of an item counts how many tracked fields have changed since the plan was saved.
Select the badge to see the full list of changes for that item. The original planned value appears on the left, and the current value on the right.
Select any individual change to see the full history of that field since the plan was saved.
In the example below: the badge shows 2, meaning two tracked fields have changed, Title and Assignee. When we open the history for Title, we can see who changed the field and when, as well as the new updated title.
2. 'Changed values' highlighted on the item
For fields displayed on the roadmap item, changed values are highlighted directly on the item, so you can see what moved from the plan without opening the Changed fields badge.
Which changes appear directly on the roadmap item depends on your view configuration. The field must be both tracked in Actual vs planned and displayed on the roadmap item via the Column or Layout button (depending on the view type).
3. Items entering or leaving the plan
Changes aren't limited to individual fields. Entire items can also be added to or removed from the plan after it was saved.
Planned vs actual marks these items directly on the roadmap, so you can tell a change in scope apart from a change within an existing item.
Added - the item was not part of the saved plan and was added afterward.
Descoped - the item was part of the saved plan but is no longer included in it.
Deleted - the item was part of the saved plan but has since been deleted entirely.
What comes next
Getting started with Actual vs Planned - create your first plan and read what it tells you.
Plan view mode 'Actual vs planned' - the other live perspective. While Planned vs actual starts from the commitment, Actual vs planned starts from today's roadmap and marks where it has drifted.
Actual vs Planned - the full feature release notes, including the health and change badges and the field history line chart.
Need more guidance? 🙋 Our LIVE support team (at the bottom right corner of your screen) replies to ANY question!