Release notes

Turn product updates and fixes on your engineering changelog into user-facing release notes.

When you’re building and growing a product, release notes are a great tool to engage your user base and showcase the momentum of your team. But from tracking down which updates have shipped when, figuring out which ones should be included, to making sure you don’t miss any key details, writing good release notes can feel like a scavenger hunt.

This release notes template helps you get an accurate, always up-to-date picture of what your team has shipped so you can write better, user-friendly updates.

Here’s how:

  • Collect all product updates including new features, bug fixes, performance improvements, and more.
  • Find documentation about each change including how it works and how it looks like.
  • Browse a central directory of all your product releases.

What are release notes?

Release notes, aka product changelogs, are pieces of content you publish regularly to share product updates with your user base. They inform your users (and your team) of what has changed in your product including new features, performance improvements, or fixed bugs. Product updates covered in release notes usually include a brief description of the feature, how to use it, product screenshots or videos, and relevant links for more details.

Who is this release notes template for?

This release notes template is designed for product managers, product marketers, developers, or QA analysts who are compiling, writing, and distributing release notes, internally or externally.

What’s the best way to write and distribute release notes?

  1. Automatically collect recent releases and product launches

With a smart list, pull all tasks tagged as “New release” in one place, and set additional filters to focus only on tasks completed within a specific date range. You could also section your list by custom attributes such as update type, product area, or customer impact.

  1. Get context and translate technical updates to user-friendly content

With in-task chat, you’ll find documentation on the entire process, from idea to release. All of the details are preserved within tasks, including conversations the team had, Figma design file previews, and code updates from GitHub or GitLab. Read through the chat history, reply to specific messages, and tag teammates for clarification.

  1. Draft your release notes

Once you’ve identified the product updates you’ll include in your release notes, you can attach a Notion page, upload a file, or include a link to your draft so you can review and proof the content with the team before you set it live.

  1. Publish and distribute your release notes

Whether you publish weekly, monthly, or quarterly release notes, you can set a recurring task with the different steps for distribution clearly laid out as subtasks: from publishing your release notes on your website or blog, sending out a product announcement email or app notification, to posting about your release on social media.

What should be included in release notes?

Release notes should cover any changes or updates to the product that impact users including new features, resolved bugs, security updates, API changes, performance enhancements, and deprecated features. You can also mention upcoming features on your roadmap to drive awareness and excitement for their release.

Release note content should be high-level, brief, and easy-to-understand. State the release number and the date of the release at the top.

For each update that you cover in the release note include a:

  1. Title: a header that refers to the new feature, improved functionality, resolved bug, etc.
  2. Description: a short explanation about what’s new, improved, or fixed, and guidance for the user on how it works.
  3. Supporting visual: any screenshots, GIFs, or videos that show the product update in action.
  4. Relevant link: additional documentation such as help center articles or website landing pages where users can find more information.