A public product roadmap is a page where your users see what you plan to build, what is in progress and what has shipped. In Planner.day it has four lanes, Under review, Planned, In progress and Shipped, with anonymous voting, and each card changes lane by itself when the task behind it changes status.
The usual public roadmap is a second product. You collect requests in one tool, decide in another, then maintain a third artefact that tells customers what is coming. It is accurate the week you build it and wrong a month later, because keeping three things in sync is somebody’s job and it is nobody’s priority.
Planner.day publishes the data you already have.
The same records, made public
A feature request arrives through the feedback widget and sits in your triage queue. When you want the world to see it, you publish it. The public board reads the same submission records your team is working from, so there is no synchronisation step and nothing to forget.
You decide what is published. Nothing becomes public automatically.
Voting
Anyone can vote, without creating an account. That is deliberate: a login wall in front of a vote button collects opinions only from people motivated enough to sign up, which is a biased sample of the people who use your product.
Votes give you a ranked signal about demand, attached to the same record that will eventually become a task.
Two places it appears
Inside the widget, so a user who opens the report button sees what is already planned and can add a vote instead of filing the same request again.
And on a standalone page you can link from your site, your changelog or a sales conversation.
What does a public roadmap tool do?
A public roadmap tool publishes the requests you have accepted, shows how far along each one is, and lets users vote so you can see demand. In Planner.day it is part of the same product as your tasks and your feedback widget: a request moves from Under review to Shipped as the work does, and every linked reporter is emailed when it ships.
What happens when it ships
When the task behind a published request is marked done, every linked reporter is emailed automatically, including everyone whose duplicate was merged in. The roadmap is not a promise board that goes stale. It is the front end of a loop that finishes.