Votelantern

Project roadmap template: month by month, with milestones

A project has a start, an end and a result. A project roadmap shows the path between them at a level anyone involved can follow: the stages, the milestones that mark each one done, and roughly when each lands. It's the page you send when someone asks "where are we?" so you don't have to write the answer again.

The template below covers six months of a fictional project and marks its milestones with a tag. It's free to copy, and you can open it in Votelantern as a roadmap page that people outside your team can check whenever they like.

The template

Example (fictional) Project roadmap by month
The project is moving Saltmarsh, a fictional booking app for surf schools, to a new payment provider; every month, milestone and task below is made up for the example.
January 2027February 2027March 2027April 2027May 2027June 2027
Milestone Pick the new provider
Compare two providers on fees, payout timing and refunds, and sign with one.
decision
Map today's payment flows
List every place the app takes, refunds or holds money today.
discovery
Build the new checkout behind a switch
The new checkout works in testing while customers still use the old one.
build
Refunds and deposits on the new provider
Lesson deposits and refunds work the same way they do today.
build
Milestone Pilot with three surf schools
A few friendly schools take real bookings on the new checkout and report problems.
pilot
Milestone Move every school over
Switch the rest of the schools in small groups, with a way back for each group.
rollout
Milestone Turn off the old provider
Close the old account once the last payouts and refunds have cleared.
cleanup
Write up what we learned
A short note on what went well and what to do differently next time.
review

The example follows a made-up project: moving Saltmarsh, a fictional booking app for surf schools, to a new payment provider. Six monthly columns, eight cards, four of them tagged as milestones.

Open this in Votelantern

How a project roadmap differs from a product roadmap

The two get confused, and the difference changes how you write one.

Project roadmap Product roadmap
Ends? Yes, when the result is delivered No, the product keeps going
Columns Months or weeks Now, Next, Later, or quarters
Cards Stages and milestones Customer problems to solve
Readers Sponsors, stakeholders, affected customers Customers, sales, the whole company

If your work has no end date, you probably want the product roadmap template instead.

The parts of a project roadmap

A goal in one sentence. Put it at the top of the page. For the example: move every surf school to the new payment provider without a missed payout. Every card should serve that sentence.

Time columns. Months suit a project of three to nine months. For a shorter project, rename the columns to weeks. For a longer one, consider quarters and keep months only for the next stretch.

Milestones. A milestone is a point where something is finished and checkable: a contract signed, a pilot running, the old system switched off. The template marks them with a "milestone" tag so readers can pick them out. A useful test is whether someone outside the team could confirm it happened.

Work cards. The steps between milestones. Keep each to a title and one sentence. A project roadmap isn't a task list; the task list lives in whatever tool your team uses day to day.

A way back. Risky steps deserve a card that says how you'd undo them. In the example, schools move over in small groups "with a way back for each group". Stakeholders sleep better when they can see it.

Building one in five steps

  1. Write the goal. If you can't fit it in a sentence, the project may really be two projects.
  2. Name the milestones first. Work backward from the end: what has to be true just before you finish? And just before that?
  3. Place milestones on months. Leave slack. A milestone at the very end of a month will slip into the next one.
  4. Fill in the work between them. One or two cards per month is plenty for a roadmap readers will actually look at.
  5. Add a review card at the end. A short write-up of what went well is cheap, and the next project benefits.

Keeping it current

A project roadmap goes stale faster than a product one, because a project has a fixed shape and every slip shows. Three habits help:

Excel, PowerPoint or a live roadmap?

Searches for a project roadmap template in Excel or PowerPoint make sense: spreadsheets handle dates well, and slides are what steering meetings run on. The trouble starts after the meeting. The file gets emailed around, someone edits an old copy, and nobody's sure which version is right.

A live roadmap page has one version, at one link. Use a spreadsheet for the detailed plan if you like, and keep the roadmap page as the summary everyone else reads.

Using the template in Votelantern

Votelantern is built for feedback boards and public roadmaps, and a project roadmap fits well when the project affects customers who want updates, such as a migration, a redesign or a beta. Open the template, change the months and cards, and share the link.

On the Free plan you get one public board with its roadmap and changelog, and a "Powered by Votelantern" badge. The paid plans, whose prices may change before launch, are Team (price not set yet) and Business (price not set yet). Team adds a custom domain, so the roadmap can live at an address such as roadmap.yourcompany.com.

For other layouts, see the general roadmap template. If the project is mainly engineering work, the technology roadmap template splits it into lanes. To announce milestones well, borrow the structure in the release notes template.

FAQ

How detailed should a project roadmap be? Detailed enough that a sponsor can see progress, not so detailed that it duplicates your task tracker. One or two cards per month is a good starting point.

What's the difference between a milestone and a deliverable? A deliverable is a thing you hand over. A milestone is a moment you can check. Many milestones are "a deliverable is accepted", but not all; "pilot running with three schools" is a milestone with no single deliverable.

Can I show owners on each card? The template doesn't have an owner field. You can put a name or team in a tag if your readers need it, though on a public roadmap we suggest teams rather than people.

Should a project roadmap be public? Only when people outside the company are affected and want updates. For internal projects, keep it private.

All templates and guides