TinyKPI

FREE EDITABLE TEMPLATE

Release notes template.

Copy the blank template or use the example below to write your next release notes.

Choose your format

Sample release notes Fictional release · Notes in the margin

How to write release notes

Version 2.4.0

Saved report views and clearer exports

Web app · All plans

Save a report’s filters once and return to the same view next time. This release also fixes date ranges in CSV exports.

New

Saved views

Open a report, choose your filters, then select Save view. Give it a name, such as “Weekly revenue,” and reopen it from the Views menu. Saved views are private to your account.

Improved

Export filenames include the date range

Downloaded reports now include their start and end dates in the filename, so you can tell last week’s export from this week’s without opening either file.

Fixed

  • CSV exports now include the final day of your selected date range. Previously, that day could be missing when your account used a timezone ahead of UTC.
  • Changing the date range no longer clears your selected customer filter.

Known issue

Shared links do not include saved views yet

Someone opening a shared report link will see the default view. To share a filtered result, export the report and send the file instead.

Need a hand? Open Help → Contact support from any report.

Ready to write yours? Get the blank template

WRITING GUIDE

How to write
release notes.

Someone opening your update usually wants to know what changed, whether it affects them, and what to do next. Start there.

01

List the changes people will notice.

Start with the work that actually shipped. Leave out a refactor or dependency update unless it changes something for the reader. For a new feature, name what they can do and where to find it. If access depends on a plan or a gradual rollout, say so.

A title like “Saved report views” gives the feature a name. The next sentence should tell someone how to use it.

02

Explain what was broken.

“Bug fixes and performance improvements” gives the reader nothing to check. Describe the situation that caused trouble and what happens now. Include a ticket link when your audience uses it, but make the sentence understandable on its own.

Too vagueFixed an export issue.

SpecificCSV exports now include the final day of your selected date range.

03

Put required actions near the top.

If an update changes an API, removes a feature, or needs new settings, say who is affected before listing the other changes. Give the exact action, any deadline, and a link to the instructions.

Keep known issues separate from fixes. Explain the symptom and any workaround. If you don’t have a confirmed resolution date, leave the date out.

04

Check it against the release.

Try the feature using the steps you wrote. Check that the version, date, availability, and links are right. Ask someone who didn’t build the change to read it. If they still need to ask where the feature is, add that detail.

Remove unused headings and leftover prompts. For a small fix, the version, date, and one sentence may be enough.

For more detail: a guide to customer-facing release notes .

YOUR COPY

Choose your format.

The same template and example, in the app you already use. Free, with no signup here.

Notion

Native template · Blank page + example

A small home page with two documents: a blank release note to duplicate and a finished example to follow.

Use in Notion
How to use this template
  1. Open the template and choose Duplicate to save it in your workspace.
  2. Open Blank release note and make a copy for your next release. Rename it with the version or release title.
  3. Fill in the prompts and remove unused sections. Keep the original blank page for next time.

Release Notes

Copy Blank release note for your next release.

The example shows how to describe a new feature, a fix, and a known issue. Delete any sections you don’t need.

📄 Blank release note

A short structure for features, improvements, fixes, and anything users need to do.

🗒️ 2.4.0 · Saved report views

A finished example with a change, a fix, and a workaround.

How to use the template
  1. Duplicate the template into your workspace.
  2. Copy Blank release note for your next release.
  3. Fill in the prompts and remove unused sections.

▸   How to write release notes

▸   Before you publish

▸   Writing a small bug-fix release?

Template home pageLayout preview · Scroll to read

Google Docs

ZIP · Two editable DOCX files

The blank template and finished example, ready to upload and edit together with your team.

Download for Docs
How to use this template
  1. Unzip the download and upload the two DOCX files to your Google Drive.
  2. Open them with Google Docs. To convert a file, choose File → Save as Google Docs.
  3. Make a copy of the blank template for each release. Replace the prompts, delete unused sections, and share the finished document.

Version 2.4.0 · 25 September 2026

Saved report views and clearer exports

Web app · All plans

Save a report’s filters once and return to the same view next time. This release also fixes date ranges in CSV exports.

New

Saved views. Open a report, choose your filters, then select Save view. Give it a name, such as “Weekly revenue,” and reopen it from the Views menu. Saved views are private to your account.

Improved

Export filenames include the date range. Downloaded reports now include their start and end dates in the filename, so you can tell last week’s export from this week’s without opening either file.

Fixed

CSV exports now include the final day of your selected date range. Previously, that day could be missing when your account used a timezone ahead of UTC.

Changing the date range no longer clears your selected customer filter.

Known issue

Shared links do not include saved views yet. Someone opening a shared report link will see the default view. To share a filtered result, export the report and send the file instead.

Need a hand? Open Help → Contact support from any report.

Completed exampleLayout preview · Scroll to read

Word / DOCX

DOCX · Editable document

A formatted release note with proper headings and lists. Edit it in your document editor and save a copy for each release.

Download template Download the example
How to use this template
  1. Download the blank template and open it in Word or a compatible editor.
  2. Replace the prompts with your release details. Remove headings that do not apply.
  3. Save the completed document under its version or release date. Download the example below if you want a reference.

Version 2.4.0 · 25 September 2026

Saved report views and clearer exports

Web app · All plans

Save a report’s filters once and return to the same view next time. This release also fixes date ranges in CSV exports.

New

Saved views. Open a report, choose your filters, then select Save view. Give it a name, such as “Weekly revenue,” and reopen it from the Views menu. Saved views are private to your account.

Improved

Export filenames include the date range. Downloaded reports now include their start and end dates in the filename, so you can tell last week’s export from this week’s without opening either file.

Fixed

CSV exports now include the final day of your selected date range. Previously, that day could be missing when your account used a timezone ahead of UTC.

Changing the date range no longer clears your selected customer filter.

Known issue

Shared links do not include saved views yet. Someone opening a shared report link will see the default view. To share a filtered result, export the report and send the file instead.

Need a hand? Open Help → Contact support from any report.

Completed exampleLayout preview · Scroll to read

Plain text

TXT · Copy, paste, or download

The same sections in a text file. Paste the template into an email, help article, or wherever you publish updates.

Download .txt Download the example
How to use this template
  1. Copy the blank template or download the TXT file.
  2. Paste it into your editor and replace the prompts with the changes in this release.
  3. Remove unused sections and any remaining placeholders before publishing.
release-notes-template.txt Plain text
[Product] release notes

Version: [Version]
Released: [Release date]
Applies to: [Platform, plan, or users affected]

[In one or two sentences, describe the main change and what it lets users do.]

Action required (if applicable)
- [Change that needs attention]: [Who is affected, what they need to do, and by when. Link to upgrade or migration instructions. Remove this section if no action is needed.]

New
- [Feature name]: [What users can now do. Say where to find it and whether access depends on a plan, platform, or rollout.]

Improved
- [Existing feature]: [What changed in the existing workflow and how it affects the person using it.]

Fixed
- [Describe the problem users saw, when it happened, and what works correctly now.]

Known issues (if applicable)
- [Issue users may encounter]: [Who is affected and any workaround. Include a tracking or support link if available. Remove this section if it does not apply.]

Questions or trouble with this release? [Support contact or help link]
Blank release noteLayout preview · Scroll to read
Just need to copy the blank template? 
[Product] release notes

Version: [Version]
Released: [Release date]
Applies to: [Platform, plan, or users affected]

[In one or two sentences, describe the main change and what it lets users do.]

Action required (if applicable)
- [Change that needs attention]: [Who is affected, what they need to do, and by when. Link to upgrade or migration instructions. Remove this section if no action is needed.]

New
- [Feature name]: [What users can now do. Say where to find it and whether access depends on a plan, platform, or rollout.]

Improved
- [Existing feature]: [What changed in the existing workflow and how it affects the person using it.]

Fixed
- [Describe the problem users saw, when it happened, and what works correctly now.]

Known issues (if applicable)
- [Issue users may encounter]: [Who is affected and any workaround. Include a tracking or support link if available. Remove this section if it does not apply.]

Questions or trouble with this release? [Support contact or help link]

QUESTIONS

Using the template.

What should release notes include?

Identify the release with a version or date, say who it applies to, and explain the changes users will notice. Include new features, improvements, fixes, and known issues where relevant. If an update requires action, explain who needs to act, what to do, and any deadline near the top. Remove sections that do not apply.

What’s the difference between release notes and a changelog?

A changelog records changes across releases. Release notes explain a particular release for its audience, often with extra context, instructions, and links. They can overlap: a small product might publish each release note as an entry in its changelog. Write for the people reading it, whether they are customers, administrators, or developers.

How do I use the Notion template?

Open the published template and choose Duplicate to save a copy in your workspace. It includes a home page, a blank release note, and the completed example. Duplicate the blank page for each release and replace the prompts. You need your own Notion account; no import or database setup is required.

Can I use the release notes template in Word or Google Docs?

Yes. The Word download is an editable DOCX, with a separate completed example. The Google Docs download contains those two documents in a ZIP. Unzip it, upload the documents to Drive, and open them with Google Docs. Use File → Save as Google Docs if you want to convert them to native documents.

Do I need every section for a bug-fix release?

No. A version, release date, and a few specific fixes may be enough. Keep upgrade instructions or known issues when they matter. Delete unused headings instead of filling them with “No changes.” The short example in the guide shows how little a patch release may need.

Can I use this for internal or technical release notes?

Yes. Add the details your readers need, such as affected versions, configuration changes, issue links, migration steps, or rollback instructions. The Action required section in the blank template gives you a place to start. Keep confidential implementation details out of a customer-facing copy.

Free Release Notes Template + Examples in 4 Formats