Roadmap template: two layouts you can use today
A roadmap answers one question for the people around your product: what are you working on, and what comes after that? It doesn't need to be pretty. It needs to be honest, short and easy to keep current.
This page gives you two free roadmap templates, both filled in with a made-up example so you can see how good items read. Use them as a layout to copy, or open either one in Votelantern and it becomes a live roadmap page that your customers can visit.
Template 1: Now, Next, Later
Ledgerly is a fictional invoicing app for freelancers; every item below is made up for the example.
| Now In progress | Next Planned | Later Under review |
|---|---|---|
Recurring invoices
Send the same invoice every week or month without copying it by hand. invoicing Faster invoice editor
The editor loads in a moment on long invoices with many line items. performance | Client portal
Clients see all their invoices and receipts on one page. clients Late payment reminders
A polite reminder goes out when an invoice passes its due date. reminders Multiple currencies on one account
Bill some clients in one currency and others in another. invoicing | Time tracking
Log hours against a client and turn them into invoice lines. time Expense receipts
Attach receipts to expenses and pass them on to clients. expenses Team accounts
A small studio can share one account with separate logins. teams |
The preview shows a roadmap for Ledgerly, a fictional invoicing app. Three columns, no dates.
This layout suits a small team that ships often and doesn't want to make date promises. Each column means something simple:
- Now: work that has started.
- Next: work you've decided to do once the current work is done.
- Later: ideas you're weighing. Nothing here is a commitment.
The strength of this layout is that it rarely goes stale. When something ships, it leaves Now and the next item moves up. You never have to explain a missed date, because there isn't one.
Template 2: Quarterly roadmap
Parcelwren is a fictional shipping-label app for small online sellers; every item and quarter below is made up for the example.
| Q1 2027 | Q2 2027 | Q3 2027 | Q4 2027 |
|---|---|---|---|
Batch label printing
Print labels for a whole day's orders in one go instead of one at a time. labels Saved package sizes
Pick a box you use often from a list rather than typing its size each time. labels | Return labels
Send a buyer a prepaid return label from the order page. returns Address check before printing
Warn the seller when an address looks incomplete, before a label is bought. addresses | Tracking page for buyers
A simple page where buyers see where their parcel is, with the seller's logo. tracking Customs forms for international parcels
Fill in customs details once per product and reuse them on every label abroad. international | Packing slips
Print a packing slip that lists the items in each parcel next to its label. labels Shared account for a small warehouse team
Two or three packers can print labels from one account with their own logins. teams |
The preview shows four quarters of work for Parcelwren, a fictional shipping-label app for small online sellers.
Pick this layout when the people reading your roadmap plan by the calendar: a sales team, investors, or customers who budget once a year. Quarters are loose enough to absorb surprises and firm enough to plan around.
A tip we suggest for quarterly roadmaps: keep the current quarter specific and let each later quarter get vaguer. The fourth column should hold two or three outcomes, not a task list. If you fill it with detail, readers will treat every card as a promise.
How to fill in a roadmap in about an hour
You can get from a blank template to something worth sharing in a single sitting.
- List what's in flight. Write down everything the team is actively building. If the list is long, you're probably doing too much at once; that's worth knowing too.
- List what you've agreed to do next. Only items with a real decision behind them go here.
- Gather the maybes. Pull ideas from support tickets, sales calls and feature requests. Keep the ones you'd genuinely consider.
- Rewrite every item as an outcome. "Recurring invoices" beats "billing service refactor". Customers read roadmaps to learn what they'll be able to do.
- Cut. A roadmap with a dozen cards gets read. One with a hundred gets skimmed and ignored.
- Decide who sees it. A public roadmap builds trust with customers. An internal one can hold cost, staffing and other detail that shouldn't be shared.
Writing items people understand
Each card needs a title and one sentence. The title names the change in the reader's words. The sentence says what gets easier for them.
Good card: "Late payment reminders. A polite reminder goes out when an invoice passes its due date."
Weak card: "Notification engine v2." Nobody outside the team knows what that means, and nobody can vote on it.
Avoid exact dates on public cards unless you're certain. A missed date costs more goodwill than a vague one earns. Tags help readers scan for the area they care about, such as "invoicing" or "returns", so add one or two per card.
Slides, spreadsheets or a live page?
If you came looking for a roadmap template in PowerPoint, Excel or Canva, those tools are fine for a one-off presentation. A slide is a snapshot, though. It's out of date the week after the meeting, and customers can't see it or tell you what they think.
A live roadmap page solves a different problem. The Now, Next, Later layout stays current because it reads the statuses on your board, and anyone with the link sees the latest version. On the quarterly layout you place each card yourself, so it is as current as your last edit. If you need a slide for a board meeting, you can still copy the columns from the live page by hand.
What happens when you open a template in Votelantern
Votelantern is a feedback board with a public roadmap and a changelog attached. Opening a template gives you a roadmap page with the example cards in place. From there:
- Your customers post requests on your board, vote on them and comment.
- You set each request's status. On the Now, Next, Later roadmap, In progress shows under Now, Planned under Next and Under review under Later. You can rename the columns.
- When work ships, you publish a changelog entry linked to the requests it covers. Those requests move to Shipped, and voters who chose "Email me updates" get an email.
The Free plan covers one public board with its roadmap, changelog and widget, with no limit on end users, posts or votes, opt-in status emails to voters, one admin, and a "Powered by Votelantern" badge. Paid plans are Team (price not set yet) and Business (price not set yet), and prices may change before launch. Team adds a custom domain, identify-users tokens, Slack and Teams alerts and up to five boards; Business adds private boards and CSV export of posts and votes.
Building a roadmap for one type of work? See the product roadmap template, the project roadmap template, the technology roadmap template or four filled-in product roadmap examples. When something on your roadmap ships, the release notes template helps you announce it.
FAQ
Should a roadmap have dates? Only if your readers need them and you can keep them. Now, Next, Later avoids dates entirely. A quarterly roadmap gives rough timing without pinning a day to each card.
How often should I update the roadmap? Whenever an item starts or ships. If the roadmap is tied to request statuses on a board, that happens as part of the work rather than as a separate chore.
What's the difference between a roadmap and a backlog? A backlog is every idea, sorted for the team. A roadmap is the short list you're willing to show other people, worded for them.
Can I keep the template's column names? Yes, or rename them to fit your tone, such as Building, Up next and Exploring. The statuses behind the columns stay the same.