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:
- Risk — at-risk work, and low-confidence P0s.
- Blockers — blocked items and the reasons behind them.
- Ownership — items with no owner team.
- Planning — missing time horizon, missing target period, and overdue target periods on unfinished work.
- Decisions — items flagged as needing a decision.
- Dependencies — dependency problems.
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
- Open the Check tab and read the score.
- Start with critical issues — they cost the most points and usually matter most.
- Use the category chips to work one kind of issue at a time.
- Click an issue's action button to fix it on the item, then return.
- Watch the score update 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.
Related guide pages
Availability
Free. Available on every plan.