Skip to content
SayScreen

Templates

Release notes template, with examples

Release notes tell the people who use your product what changed and what they can do now. Here's a template to copy, the same template filled in, a shorter one for a single feature, and how to write each line so people can act on it.

Updated

$1 for 7 days, then $49/month
On this page

What release notes are for

Release notes tell the people who use your product what changed in a release, what they can do now, and anything they need to do about it. Several groups read them, for different reasons:

  • Customers, looking for what's new and whether it affects them.
  • Admins, who need to turn something on, tell their team or prepare for a change.
  • Your support and sales teams, who will be asked about it first.
  • People deciding whether to try or update your product.

Write for customers first: if a customer understands a line, so will everyone else.

Release notes vs a changelog

The two terms are often used for the same thing, but they do different jobs.

Release notes and a changelog compared
Release notesChangelog
Covers
CoversOne releaseEvery release, newest first
Written for
Written forThe people who use the productAnyone who wants the full history, often developers
Says
SaysWhat's new, why it matters, what to doWhat changed, briefly
Detail
DetailThe changes that matter to users, with linksEvery change, sometimes down to each fix
Where it lives
Where it livesAn email, an in-app message, a postOne page that keeps growing

You can do both: write notes for each release, then collect them, dated, on a changelog page. The template below works for either: for a changelog entry, keep the date, the title and the New, Improved and Fixed lines, and add each release at the top of the page. For a live example of dated, customer-facing notes, see our own changelog: newest first, each release with a short title and one line per change.

The release notes template

Copy this, replace the brackets, and delete any part with nothing in it. New, Improved and Fixed are enough for most releases.

Release notes template
Title
[Product] [version or month]: [the biggest change, in a few words]
Date and version
[Month day, year], version [number]
Summary
You can now [the main thing], plus [number] smaller improvements and fixes.
New
[Feature]: you can now [do what], from [where it is]. [Link to the help article]
Improved
[What you improved] is now [faster, clearer, simpler], so you can [benefit].
Fixed
[The problem] no longer happens when you [action].
What to do next
[Anything people need to do: update, turn on a setting, tell their team.] Questions? [Where to ask].

Here's the same template filled in for an invoicing app:

Example: a monthly releaseTaskly is a made-up app
Title
Taskly, November 2026: scheduled invoice exports
Date and version
November 11, 2026, version 4.2
Summary
You can now send invoice exports on a schedule, plus two smaller improvements and a fix.
New
Scheduled exports: send last month's invoices as a CSV to your accountant on the first of every month. Set it up in Billing, under Export. See how scheduled exports work.
Improved
The invoice list opens faster on large accounts, and the date filter now remembers your last choice.
Fixed
Exported CSV files no longer split a customer's name into two columns when it contains a comma.
What to do next
Nothing changes until an admin turns scheduled exports on. Questions? Reply to this email.

Notice what the example leaves out: ticket numbers, the name of the team that built it, and how it works inside. Every line says what changed for the person reading it.

A short template for one feature

When you ship one feature on its own, a full set of notes is too much. Use this for an in-app message, a short email or a social post:

Feature announcement template
Headline
New in [product]: [feature]
What it does
You can now [do what], without [the old way].
Where to find it
Open [place] and click [button].
Who gets it
Live today for [everyone, or which plans].
Learn more
[Link to the help article or a short video]
Example: one featureTaskly is a made-up app
Headline
New in Taskly: scheduled exports
What it does
You can now send last month's invoices to your accountant automatically, without exporting them by hand.
Where to find it
Open Billing, click Export, then Schedule.
Who gets it
Live today for every plan.
Learn more
A one-minute video of scheduled exports, from setup to the first email

Keep the headline short enough for an email subject line, and make the link go to the place that explains the feature, not to your home page.

How to write each line

  • Lead with what the user can now do. “You can now schedule exports” tells people more than “We've added a scheduling engine”.
  • Skip the build-up. “We're excited to announce” adds nothing, so start with the change.
  • One sentence each. If a change needs a paragraph, it needs a help article, so link to it.
  • Use the names on the screen. Write Billing and Export exactly as the app does, so people can find them.
  • Say where it is. A feature nobody can find hasn't shipped for them.
  • Say who gets it, if it's only for some plans, roles or regions.
  • Be specific about fixes. “Exports no longer split names that contain a comma” tells people their problem is gone; “bug fixes” doesn't.

Put breaking changes first

If something was removed, renamed or works differently now, say so at the top, with what people need to do and by when. Don't leave it at the bottom of the list for them to discover.

Mistakes to avoid

  • “Bug fixes and performance improvements” as the only line
  • Ticket numbers, code names and team jargon
  • Leading with how you built it instead of what people can do
  • A breaking change hidden at the bottom of the list
  • No date or version, so nobody can tell which release they're reading
  • A feature that's live for some plans only, announced as if everyone has it
  • One long paragraph instead of a list

Add a short video to each release

Some changes are easier to show than to describe. Pick the one in each release that's easiest to see, and make a video of 30 to 60 seconds: where to find it, using it once, and the result. You don't need a video for every line.

Write the script first. The feature announcement template in the video script templates fits about 40 seconds, and the free script timer tells you how long your draft runs. Record it in the real product with sample data, add captions for people watching without sound, and put the video at the top of the notes. A launch that needs more than a minute is a feature demo: the product demo video guide covers those.

For a web app, you can describe the change instead of recording it. In SayScreen, you give it the page where the new feature starts and describe what's new. Its AI uses your live app in a real browser, reads each screen, decides where to click and writes the narration, and a natural AI voice speaks it. You get an edited MP4 and an .srt caption file, with captions on the video if you want them, to upload anywhere you'd use a video. A demo or staging account with sample data is the best place to record, and release notes videos has example prompts.

A narrated video for every release

Paste the page where the new feature starts and describe what's new. You get a narrated walkthrough recorded in your live app, ready to go with the notes.

$1 for your first 7 days, then $49 a month for 60 minutes of video, up to 8 minutes each. Cancel anytime.

Where to publish release notes

Put them where each group already looks:

  • In the app. A short message or a What's new panel reaches people while they're using the product, next to the feature itself. Use the short template.
  • By email. Send the full notes to active users when a release changes how they work, with the headline change in the subject line.
  • On a changelog page. One dated page with every release, newest first, that you can link to from the app, emails and help articles.
  • In your help center. Update the articles a release touches on the same day, and link them from the notes.

Tell your support and sales teams before customers hear about it, so they can answer the first questions.

Questions

Skip the recording. Describe the video instead.

Point SayScreen at your app, say what to teach, and get a narrated, edited video back.

$1 for 7 days, then $49/month · Cancel anytime