Votelantern

Release notes template for software teams

Release notes tell the people who use your product what changed and why they should care. Written well, they cut support questions, remind customers you're still improving things, and close the loop with whoever asked for a feature in the first place.

Below is a free template with three sample releases. It's shown the way readers would see it: as a changelog page, newest release first.

The template, filled in

Example (fictional) Release notes for a software product
Tidepool is a fictional scheduling app for dance studios; the releases and dates below are made up.

3.4: Waitlists for full classes 2026-10-14

When a class is full, students can now join a waitlist and get a spot automatically if someone cancels.

New

  • Waitlists on any class, with a limit you choose.
  • Students on a waitlist get an email when a spot opens.

Improved

  • The class calendar loads faster on phones.

Fixed

  • Recurring classes no longer skip the week after a holiday.

3.3: Studio hours and closures 2026-09-23

New

  • Set regular studio hours and one-off closure days; bookings respect both.

Fixed

  • Instructors with two classes at the same time now see a clear warning.

3.2.1: Small fixes 2026-09-02

Fixed

  • Receipts show the studio's address again.
  • Searching students by last name works with accented letters.

Security

  • Sign-in links now expire sooner.

The sample releases belong to Tidepool, a fictional scheduling app for dance studios. Version numbers and dates are invented.

Open this in Votelantern

Open it in Votelantern and these entries become your changelog page. Delete the samples and write your own release in their place.

The parts of a release note

Each entry in the template uses up to five parts, and some leave the intro empty. Copy them in this order.

  1. Version (optional). Use it if your customers see version numbers. Web apps that deploy daily often skip it.
  2. Date. Always. Readers want to know how recent a change is.
  3. Title. Name the main change in plain words: "Waitlists for full classes", not "Release 3.4".
  4. One-sentence intro. Say who benefits and how. Skip it for small fix releases.
  5. Sections. Group the bullets under fixed headings so readers can jump to what they care about.

The headings the template uses are New, Improved and Fixed, with Security when it applies. For bigger changes you can also use Removed and Deprecated. Keep the set small and use the same words every time. A reader who learns that "Fixed" means bug fixes shouldn't have to guess what "Polish" or "Tweaks" mean next month.

How to write a good bullet

A release note bullet is one sentence about a result. Three tests help:

Leave out internal refactors, dependency bumps and anything a user can't see, unless it changes speed or reliability in a way they'll feel. If it does, say so in their terms: "The class calendar loads faster on phones."

Customer notes, internal notes and deployment notes

Searches for this topic mix three different documents. It helps to know which one you're writing.

If you keep notes in a GitHub release, a Confluence page or a Jira version list, the same structure works there, though Votelantern doesn't sync with Jira or GitHub, so you'd copy the customer-facing part across by hand.

A checklist before you publish

That last point is where release notes earn their keep. Someone who voted for waitlists months ago gets a clear signal, without having to ask, that the request was heard and acted on.

What Votelantern adds to a plain template

Votelantern is a feedback board for small software teams, with a roadmap and a changelog built from the same requests. When you publish a changelog entry and link it to requests on your board:

The Free plan includes the changelog, the roadmap, one public board and the widget, with a "Powered by Votelantern" badge. The paid plans are Team (price not set yet) and Business (price not set yet); prices may change before launch. Team adds a custom domain, identify-users tokens and Slack and Teams alerts.

If your notes describe items from your plan, a roadmap template shows where they came from. For roadmaps by product theme or quarter, see the product roadmap template.

FAQ

How long should release notes be? As short as the change allows. A small fix release can be one heading and two bullets. A big release still shouldn't need more than a short intro and a handful of bullets per section.

Should I write release notes for every deploy? No. Group small deploys into one entry every week or two. Readers follow a steady rhythm better than a stream of tiny posts.

What's the difference between release notes and a changelog? A changelog is the running list; each release note is one entry in it. The words are often used for the same page.

Do I need version numbers? Only if customers see or install versions. For a web app that updates itself, a date and a title are enough.

Who should write them? Whoever can explain the change to a customer. That's often the product manager or support lead, with an engineer checking the facts.

All templates and guides