How to Create a Project Roadmap in Confluence: A Filled CRM Example
9 min read · 2026-11-21
How to create a project roadmap in Confluence comes down to five moves in the editor: create a reusable page template, insert the Roadmap Planner macro, fill it with lanes, bars and markers, add the Jira timeline for delivery detail, then export the page to PDF for leadership. This guide builds one real roadmap from start to finish, a five-month CRM rollout, so you can copy each step for your own project.
It assumes your project goal, scope and phases are already agreed. The guide stays inside Confluence: which elements to click, what to type in each bar and how to hand a readable version to people who never open your wiki.
The roadmap at a glance
Goal: Publish an approved project roadmap page in Confluence, with a PDF version for leadership, that the team updates every two weeks. Duration: About 2 weeks to the first approved version, then a review every 2 weeks
Prepare the inputs (Day 1)
Gather what the page needs before you open the editor.
- One sentence for the goal, with a date and a measurable outcome.
- The list of workstreams and their leads.
- Phases with start and end weeks, already agreed with the team.
- Fixed dates: steering committees, contract deadlines, go-live window.
Milestone: Phases, owners and fixed dates confirmed in writing.
Create the page template (Day 2)
Build the structure once so every project roadmap in the space looks the same.
- Ask a space admin to create a template in Space settings.
- Add the sections listed further down, with placeholder text.
- Create the project page from that template.
Milestone: An empty roadmap page with all sections in place.
Build the timeline (Days 3-4)
Turn the agreed phases into a visual roadmap.
- Insert the Roadmap Planner macro and choose weeks or months.
- Create one lane per workstream and one bar per phase.
- Add markers for fixed dates and link each bar to its detail page.
Milestone: A complete timeline visible to the project team.
Connect Jira and fill the context (Days 5-6)
Give readers the detail behind each bar.
- Insert the Jira timeline below the Roadmap Planner, or link the relevant epics.
- Fill milestones, dependencies, risks and the change log.
- Write the executive summary last, at the top of the page.
Milestone: A draft page that answers the sponsor's questions without a meeting.
Review and export (Week 2)
Get sign-off and hand over a version anyone can read.
- Walk workstream leads through the page and fix conflicting dates.
- Export the page to PDF with the version date in the file name.
- Record the sponsor's approval in the change log.
Milestone: Sponsor approval logged on the page, with the date.
Keep it current (Every 2 weeks)
Make the page the single source of truth for dates.
- Update bars and markers after each review meeting.
- Log every moved date with its reason and approver.
- Export a new dated PDF when a milestone moves.
Milestone: First scheduled review held and logged.
Step 1: Agree on the inputs before you open Confluence
Keep this short. The editor is not the place to debate scope. For the CRM example, the inputs fit in five lines: the goal ("All sales reps work in the new CRM by the end of month 5, with the old system in read-only"), five workstreams, their leads, the phase ranges and two fixed dates (contract end of the old CRM, sales kickoff). If you still need to define phases with the team, settle that first, then come back to this guide.
Step 2: Create a Confluence project roadmap template
A template saves you from rebuilding the page for every project, and it makes roadmaps comparable across a portfolio. According to Atlassian's Confluence Cloud documentation, only space admins can create templates: open Space settings from the ••• menu next to the space name, go to Look and feel, then Templates, and select Create new template. Templates support placeholder text, variables and labels.
Use the sections below, in this order. The executive summary sits above the timeline on purpose. When the page becomes a PDF, the first thing a director reads is the status and the decision you need.
- Goal. One sentence: what will be delivered, by when, and why.
- Executive summary. Five lines at most: status, next milestone, top risk, decision needed.
- Timeline. The Roadmap Planner macro.
- Delivery detail. The Jira timeline or links to epics.
- Milestones. Date, owner and how you will know it is done.
- Workstreams and owners. One line per lane.
- Dependencies. Written out in plain sentences.
- Risks and fallback plans. Each risk with its owner and response.
- Out of scope. Ideas raised but not committed.
- Change log. Date, what moved, why, who approved.
Step 3: Insert and fill the Roadmap Planner macro
Atlassian's support page for the Roadmap Planner describes how it works in Confluence Cloud. Type / while editing, search for Roadmap Planner and select it. The roadmap is made of lanes (teams, products or streams), bars (phases of work), markers (important dates and milestones) and a timeline you can set in weeks or months. You can add a description to each bar and link a bar to a page.
Two practical points from the same documentation. The macro is configured only through its visual interface, not through wiki markup or the storage format. And it is not yet available in live docs: if you started in a live doc, convert it to a page first.
For a project under six months, weeks are easier to read. Here is the CRM rollout as you would enter it. Lanes: Requirements, Configuration, Data, Training, Go-live. Markers: steering committee at weeks 4, 10 and 18, sales kickoff, old CRM contract end. The bars and their descriptions are listed below.
Write the owner and the "done when" test in every bar description. A bar without an owner is a bar nobody updates. Then link each bar to its detail page, so readers can drill down without leaving the roadmap.
Notice that Configuration and Data migration overlap in weeks 9 and 10. That is deliberate in this plan, and it is exactly the kind of thing to explain in the Dependencies section: "Data migration starts once the core objects are configured in week 8; Training cannot start before the test migration passes."
- Discovery and requirements, weeks 1 to 4. Description: "Owner: business analyst. Done when sales leadership signs the requirements."
- Configuration, weeks 5 to 10. Description: "Owner: CRM admin. Done when the test environment is ready."
- Data migration, weeks 9 to 14. Description: "Owner: data lead. Done when a test migration passes with no blocking errors."
- Training, weeks 15 to 18. Description: "Owner: enablement lead. Starts after data migration. Done when every sales rep has completed training."
- Go-live and support, weeks 19 to 22. Description: "Owner: project manager. Done when the old CRM is switched to read-only."
Step 4: Add Jira epics under the roadmap
Leadership reads phases. The delivery team works in epics. Show both on one page, in that order.
Atlassian documents two ways to add a Jira timeline to a Confluence Cloud page: paste the timeline URL into the page while editing, and Confluence turns it into the Jira Timeline macro, or type /timeline in the editor. The embedded timeline updates in real time.
For the CRM project, create one epic per phase in Jira and keep the same names as your bars. Then link each Roadmap Planner bar to the matching epic or to a detail page listing its epics. Readers move from "Data migration, weeks 9 to 14" to the actual work in one click, and the names never drift apart.
Keep tickets out of the Roadmap Planner. Once individual tasks land on the visual roadmap, the phases disappear and the sponsor stops reading.
Step 5: Fill the context sections with the CRM example
The timeline answers "when". The rest of the page answers what a sponsor asks next. For the CRM rollout:
- Goal: All sales reps work in the new CRM by the end of month 5, with the old system in read-only.
- Executive summary: On track. Next milestone: test environment ready, week 10. Top risk: data quality. Decision needed: approve archiving inactive accounts.
- Top risk: Data quality in the old system delays migration. Fallback: migrate active accounts first and archive the rest. Owner: data lead.
- Out of scope: Marketing automation and customer support modules, planned for a later phase.
- Change log, first entry: Version 1, approved by the sales director.
Step 6: Present the Confluence roadmap to leadership as a PDF
Many readers will never log into Confluence. Directors read on a phone between meetings, and clients usually have no access to your workspace.
Atlassian's documentation says any user who can view a page can export it to PDF: open the page, select •••, then Export and Export to PDF. Before you send it, open the file and check that the timeline is readable. If bars are hard to read at page size, the milestone list and executive summary still carry the message, which is another reason to keep them as text.
Prepare three versions from the same page, and put the version date in the page title of every export, so nobody presents an outdated plan.
- The live page for the project team, with links to bars, epics and detail pages.
- The dated PDF for leadership and steering committees, for example "CRM rollout roadmap, version 3, week 10".
- A one-slide summary with the phases, the next two milestones and the top risk, for meetings where you have five minutes.
Common mistakes to avoid
- Building the timeline in a live doc, then losing time when the macro does not appear; start from a page.
- Using different names for bars and Jira epics, so nobody can match them.
- Writing owners in a separate table nobody reads; put them in each bar description.
- Keeping dependencies only in people's heads; write them in plain sentences under the timeline.
- Moving bars silently; log every change with its reason and approver.
- Sending leadership a link to a page they cannot open; send the dated PDF.
Frequently asked questions
Can I create a roadmap in a Confluence live doc?
Not with the Roadmap Planner for now. Atlassian's documentation says the macro is not yet available in live docs and that you need to convert the live doc to a page first.
How do I show Jira epics on a Confluence project roadmap?
Paste the Jira timeline URL into the page while editing, or type /timeline, and Confluence adds the Jira Timeline macro. Keep the Roadmap Planner above it for the phase view, and link each bar to its epic.
Can I reuse the same roadmap page for every project?
Yes, by turning it into a space template. A space admin creates it from Space settings, Look and feel, Templates, then Create new template. Each new project page then starts with the same sections.
How do I share a Confluence roadmap with people who have no access?
Export the page to PDF from the ••• menu. Atlassian says single-page PDF export is available to anyone who can view the page. Put the executive summary at the top and the version date in the title.