← All posts

Release notes template for SaaS teams

A free release notes template for SaaS products, with a filled-in example. Copy it into Google Docs, Word, Notion, Confluence or Markdown.

Ryan StevensRyan Stevens November 17, 2026 · 9 min readLaunches
Release notes template for SaaS teams

On this page

This release notes template has nine parts: a title line, a one-sentence summary, then Action needed, Changed, New, Fixed, Known issues, Retiring and Where to get help. Copy it from this page, delete the sections a release doesn't need and write each entry for the customer. Keep the order the same in every release.

A release notes template is a reusable outline for the note you publish with each software release, so every note has the same sections in the same order.

On 17 November 2026, we read three pages from the first page of Google's results for "release notes template": TechWhirl's Release Notes Template, ClickUp's Release Notes Template for Confluence and FeatureBot's list of release notes examples and templates. TechWhirl offers a Microsoft Word file to download and says it's "designed around four separate sections." ClickUp's template is a doc inside ClickUp that outlines new features, improvements, bug fixes and known issues, and the page says you can export it or copy and paste it elsewhere. FeatureBot reviews seven tools and template sources, with LaunchNotes first and Aha! last. The three sat at positions five to seven on 14 November 2026, below a Facebook post, a Pinterest pin, a Craft doc and a YouTube video. None of the three pages shows the template text itself, and ClickUp's list of sections has no place for what the customer has to do. The template below has both.

The release notes template

Copy from the title line down to "Where to get help." Text in square brackets is yours to replace.

Release notes template

[Product name] release notes: [date] [version number, if you use one]

[One sentence on what this release is about and who it affects.]

Action needed

  • [What the customer has to do, who it applies to and the date it's due.] [Link to the steps]

Changed

  • [What works differently or has moved and where it is now.] [Who it affects, if it's not everyone]

New

  • [Feature name.] [What the customer can do now and where to find it.] [Who gets it, if it's not everyone] [Link to the tutorial or help article]

Fixed

  • [What the customer saw before and what happens now.]

Known issues

  • [What isn't working yet, the workaround and when you expect a fix.]

Retiring

  • [What's going away, the date and what to use instead.]

Where to get help

  • [Links to the help center, the tutorials for this release and support.]

What is the release notes format?

The release notes format in this template is a title line, a one-sentence summary and short entries grouped under fixed labels. The labels run in a fixed order. Anything a customer has to do comes first, then what works differently, what's new and what's fixed, then what still isn't working and what's going away.

SectionWhat goes in itKeep it when
Title lineThe product name, the date and the version number if you use oneAlways
SummaryOne sentence on what the release is about and who it affectsAlways
Action neededWhat a customer must do, who it applies to and the deadlineA change needs the customer to do something
ChangedFeatures that work differently or have moved on screen, including small improvementsA customer would notice the difference
NewFeatures a customer can use nowYou shipped one
FixedBugs, described as what the customer saw before and what happens nowYou fixed one a customer could have hit
Known issuesWhat still isn't working, with a workaround if there is oneYou know of one
RetiringFeatures that are gone or going away, with the date and the replacementSomething is being removed
Where to get helpLinks to the help center, the tutorials and supportAlways, except in a fix-only note

If your team follows Keep a Changelog (read on 17 November 2026), some of the labels will look familiar. It groups changes into six types: Added, Changed, Deprecated, Removed, Fixed and Security. In this template, Added becomes New, and Deprecated and Removed share Retiring. A security fix goes under Fixed. If the customer has to do something about it, it goes under Action needed too. So does anything that retires before your next release.

Sample release notes: the template filled in

Here's the template filled in for one release of an imaginary appointment booking product. Nothing is retiring in that release, so the Retiring section is gone.

Booking release notes: 6 April 2027 (version 4.12)

This release adds waitlists, moves reminder settings into each service and asks admins who send text reminders from their own phone number to verify it again by 30 April.

Action needed

  • Verify your phone number again by 30 April if you send text reminders from your own number. This applies to account admins. Open Settings, choose Messaging and select Verify number. [link to the steps]

Changed

  • Reminder settings have moved. They're now inside each service, under Services, instead of in Settings. Your existing reminders carry over. [link to the help article]

New

  • Waitlists. When a time slot is full, clients can join a waitlist and get the slot if someone cancels. Turn it on for each service under Services. [link to the tutorial]

Fixed

  • The staff calendar cut off appointments longer than four hours. It now shows them in full.
  • The weekly summary email sometimes arrived twice. It's now sent once.

Known issues

  • Waitlists don't work for group classes yet. We expect to add them in the next release.

Where to get help

  • The help center has an article for each change above. To reach support, use the chat in the app. [link to the help center]

Every link in the note needs a page behind it on launch day. In this note, that's three new or updated pages: the steps for verifying a phone number, a tutorial on waitlists and an updated help article on reminders, because the old one still points to Settings.

At SWFTMENT, the release notes are one of two things we ask for ten days before launch. The other is test access to the product.

How do you adapt the template for a major release, a minor release or a fix?

Keep the same order every time and change how much you write. A major release uses every section that applies. A minor release mostly needs Changed and Fixed. A fix can be three or four lines.

ReleaseSections to keepHow much to write
Major: a new feature or a change every customer will noticeEvery section that applies. The summary names the main feature.Two or three sentences per New entry, each with a link to a tutorial or help article
Minor: small improvements and fixesTitle line, summary, Changed, Fixed and Where to get help, plus Action needed and Known issues if there are anyOne line per entry
Fix onlyTitle line, summary, FixedThree or four lines in all

Appcues' guide to release notes (read on 17 November 2026), which has its own template in three sizes, puts the rule this way: "The format and depth of your release notes should match the scope of the change."

Here's the fix-only version for the same imaginary product.

Booking release notes: 13 April 2027 (version 4.12.1)

This release fixes one problem with the staff calendar.

Fixed

  • Appointments changed on a phone didn't always update in the staff calendar. They now update within a minute.

How do you use the template in Google Docs, Word, Notion, Confluence or Markdown?

The template is plain text, so it pastes into the editors below. Set it up once as a template in the tool your team already writes in, so each release starts from a clean copy. We read each help page below on 17 November 2026.

ToolHow to set it up
Google DocsPaste the template into a new document and make each label a heading. To paste the Markdown version with its headings in place, check Enable Markdown under Tools, then Preferences, then right-click and choose Paste from Markdown (Google Docs Editors Help).
Microsoft WordPaste the template into a blank document, then save it as a Word template from the File menu (Microsoft Support).
NotionKeep release notes in a database with one page per release and save the outline as a database template. A template is only available in the database where you created it (Notion Help).
ConfluenceA space administrator can create a template under Space settings. Put the bracketed prompts in as placeholder text, which shows while someone is editing and not on the published page (Atlassian Support).
MarkdownUse the version below in your repository or docs site.

The release notes template in Markdown:

Release notes template in Markdown
# [Product name] release notes: [date] [version number, if you use one]

[One sentence on what this release is about and who it affects.]

## Action needed

- [What the customer has to do, who it applies to and the date it's due.] [Steps](link)

## Changed

- [What works differently or has moved and where it is now.] [Who it affects, if it's not everyone]

## New

- [Feature name.] [What the customer can do now and where to find it.] [Who gets it, if it's not everyone] [Tutorial](link)

## Fixed

- [What the customer saw before and what happens now.]

## Known issues

- [What isn't working yet, the workaround and when you expect a fix.]

## Retiring

- [What's going away, the date and what to use instead.]

## Where to get help

- [Help center](link), [tutorials](link), [support](link)

If your code is on GitHub, the Generate release notes button gives you a list of merged pull requests, a list of contributors and a link to a full changelog (GitHub Docs). Treat that as the list of changes to start from. You still have to write the note for customers from it.

What should you cut from release notes?

Cut anything a customer can't use. Take these six things out before you publish:

  • Ticket numbers, branch names and internal code names.
  • Changes no customer can see, such as a refactor or an internal tool.
  • How a bug was fixed. Say what the customer saw and what happens now.
  • Empty sections. If nothing is retiring, delete the label.
  • Step-by-step instructions longer than three steps. Link to the help article or tutorial.
  • The list of who built what. It belongs in the changelog or the team channel.

Then have someone who didn't write the note check each entry against the build that will ship.

Questions people ask about release notes templates

Can I get this release notes template as a Word document?

You can make one by pasting. Copy the template into a blank Word document and save it as a Word template from the File menu, so it opens as a clean copy for each release. There's no file to download from this page.

Can I use this template for sprint, deployment or internal release notes?

You can use this template for sprint, deployment or internal release notes, with two changes. Internal readers such as support and sales need things customers don't: the rollout date, who gets the change first and who to ask when a customer reports a problem. Add those under the summary. A sprint or deployment note for the team can also list work no customer will see, which the customer version leaves out.

What is the difference between a release notes template and a changelog template?

A changelog template lists every notable change in a version under types such as Added, Changed and Fixed. This release notes template is written for customers. It leaves out changes no customer can see and has a section for anything the customer has to do.

Who should fill in the release notes template?

We recommend that one named person fills it in and owns it. Engineering supplies the list of changes, and the owner sorts them, writes each entry and has someone else check the note against the product. That owner can be a product manager, a marketer or a founder.

Ryan Stevens
Ryan Stevens Founder of SWFTMENT. We make the launch video, tutorials and help docs for each release, and keep them current.
About SWFTMENT →

Rather have it done for you?

Book a free 20-minute release review. We look at your next release and what your customers need to learn it. No pitch.

Book a release review