Skip to main content

Release notes article guidelines

Writing guidelines for your release note articles.

Written by Asa MacLean

Release notes are our opportunity to generate excitement and sell the benefits of our new features and improvements. The article serves as a high-level overview and links off to more in-depth how-to help articles to talk about the specifics.

Before you start

To write great release notes, you need to have the right preparation. Ensure you can check off everything on this list.

I know what the key benefits are.

I know what I want to generate excitement about.

I know the how-to help articles I need to link off to.


Article structure

Title

Use straightforward titles that include the version number. If you don’t use version numbers, or if you’re making a content release, you can use the month and year instead.

✅ Do

❌ Don't

25.8 release notes

25.8 release notes including updates to the reporting functionality

Working at height – August 2025

Working at height safety

Description

One sentence that highlights the one or two key features you’re wanting to talk about.

✅ Do

❌ Don't

Introducing enhanced reporting, user journeys and more.

Enhanced reporting, user journeys, key metrics inputs, new screens, extra login abilities, new surveys, bug fixes, printing options.

Article body

Introduction

Welcome the readers to the release notes and add any extra information on the focus of the release.

✅ Do

❌ Don't

We’re pleased to announce the 28.0.136 release, focusing on improvements to reporting and bug fixes.

28.0.136 release.

Welcome to the August 2025 release, bringing you several quality improvements to your user management.

  • Enhanced reporting

  • User journeys

  • Key metrics inputs

  • New screens

  • Extra login abilities

  • New surveys

  • Bug fixes

  • Printing options

Sections overview

Your article body should include at least two sections: What's new and How to access this update. You can also include Additional information if you feel you need to.

These headings will use the Heading 1 (H1) option, with Heading 2 (H2) for sub-sections. Headings 3 and 4 can be used if you need to drill into each section further.

What's new (H1)

Add this section to talk about the new features and improvements you’re releasing. Add each feature as a sub-heading and give a brief overview before linking off to any specific how-to help content.

🔎 Example

How to access this update (H1)

This section needs to be added to explain to the reader how they get the update. If required, include any information on where to download or request it.

✅ Do

❌ Don't

This version updates automatically on Friday 19 August 2025.

This updates automatically.

This version releases on Friday 19 August 2025. To request an update file...

Contact support.

This version releases on Friday 19 August 2025. Follow our help article on downloading...

Download the file.


RACI

Tasks

P&E

Digital CS

DCL

DSL

DSE

Identify need for a release note article

R

I

I

I

C

Create first draft of article

R

I

I

I

C/R

Review content for quality, tone, and structure

A

I

A/R

I

C

Review technical accuracy

R

C

I

I

C/I

Approve final article for publication

A

I

R

I

C

Maintain article

R

I

A

I

A

Did this answer your question?