Check — roadmap health
The Check tab grades your roadmap and lists exactly what is wrong with it, before a stakeholder does it for you.
What it does
Check produces a health score from 0 to 100 — green at 80 and above, amber from 50, red below. The score drops for critical issues and for warnings.
Below the score, Check lists issues in categories you can filter:
At-risk work, low-confidence P0s, and items marked high risk.
Blocked items and the reasons behind them.
Items with no owner team.
Missing time horizon, missing target period, and overdue target periods on unfinished work.
Items flagged as needing a decision.
Dependency problems.
Items at the tech-readiness gate that are missing what a delivery team would need — description, owner, outcome, scope, measure or target.
An item sitting somewhere its level cannot legally sit. See Initiatives, epics, and features.
Every actionable issue has a button that jumps straight to the item that caused it, so fixing the roadmap is a loop, not a scavenger hunt.
When to use it
- Before any roadmap review — run Check and clear what you can.
- After a big round of edits, to catch what you left half-done.
- When a roadmap "feels off" but you cannot say why.
When not to use it
- While the roadmap is still a rough draft. A half-built roadmap always scores low; that is not useful information yet.
- As a target in itself. A perfect score on a roadmap nobody believes is worth nothing. Check supports judgement; it does not replace it.
3-minute flow
Read the score
Open the Check tab.
Start with critical issues
They cost the most points and usually matter most.
Work one category at a time
Use the category chips.
Fix it on the item
Click an issue's action button, then return.
Watch the score move
It updates as you go.
Best use cases
- A pre-review quality pass.
- Catching missing owners and overdue target periods.
- Surfacing low-confidence P0s so the review can discuss them on purpose.
Common mistakes
- Chasing the number instead of fixing the substance.
- Ignoring warnings because they are not critical — several warnings usually point at a real gap.
Cleaning up orphan dependencies
If you delete a roadmap item that other items depended on, the Check tab flags the dependency as broken. The issue card shows the dependency's reference, the source item's RF-ID, and the direction of the broken link. Click Remove orphan dependency to clean it up — the validation issue clears immediately and the cleanup persists after reload.
Related guide pages
Availability
Free. Available on every plan.