Roadmap overview
The Roadmap turns your CAMP assessment into a sequenced plan you can defend to leadership and execute against.
Last updated June 30, 2026
Your assessment tells you where you stand. The Roadmap tells you what to do next, in what order, and what it should produce. It connects the gaps Forest finds to dated, owned work you can defend in a board meeting.
The Roadmap has two tabs. Trajectory is the picture of where your security posture is going. Recommendations is the ranked, gap-driven worklist that gets you there — it used to be its own page and now lives here as a tab.
The Trajectory tab offers two views over the same timeline:
Org trajectory plots your Forest score and each domain as lines over time — where you were, where you are now, and where you're headed once the planned work lands. Click any line to read that domain's were/now/headed and the capabilities driving it; toggle "Hover values" to read every line at a point in time.
Gantt timeline lays the milestones on a time axis, each bar colored by the outcome it belongs to with a dot for its status. Group it by Timeline, priority, or goal.
The Roadmap is built on capabilities. Every CAMP capability carries a current maturity, a target, and a criticality. Forest computes priority as (target maturity minus current maturity) multiplied by criticality, so the work that closes the most important gaps rises to the top. You are not guessing what matters. The math makes the case.
From there, the Roadmap organizes effort in views that stay in sync:
Goals and milestones define the outcomes you commit to and the checkpoints along the way.
Domain goals and capability goals set targets at the level you actually plan and report.
Timeline and projections show how those targets move your scores over time.
Projections come from the Forest Intelligence Service, which is deterministic. The same targets and dates always produce the same projected scores, and every projected number traces back to the inputs behind it.
Work is then placed into planning horizons and execution lanes so a quarter of activity reads as a plan, not a backlog. Start with goals, then let the horizons and lanes give the plan shape and ownership.