---
title: Release Notes Template (Plus an AI Prompt to Write Them)
url: "https://goremy.ai/blog/articles/release-notes-template-an-ai-prompt-that-writes-them-from-your"
author: Luis Chavez-Mattos
editor: Luis Chavez-Mattos
editor_title: Director, Product
published: "2026-11-16T10:20:12.866Z"
updated: "2026-11-16T10:20:12.866Z"
topic: Product Requirements and Design
description: Copy a release notes template for customers and internal teams, see a filled-in example, and paste an AI prompt that turns your changelog into release notes.
---

# Release Notes Template (Plus an AI Prompt to Write Them)

> Copy a release notes template for customers and internal teams, see a filled-in example, and paste an AI prompt that turns your changelog into release notes.

Edited by Luis Chavez-Mattos, Director, Product · Published 2026-11-16

## What is a release notes template?

A release notes template is a fixed outline for telling people what changed in a software release: what is new, what is improved, what is fixed, what is going away, and whether anyone needs to do anything. The same headings every time mean writers stop reinventing the format each sprint, and readers learn where to look. The template below is ready to copy. After it you get a filled-in example and an AI prompt that turns a raw changelog into a finished draft.

## TL;DR

- **Use one template with fixed sections** (summary, new, improved, fixed, deprecated, known issues, action required) so every release reads the same way.
- **Release notes are not a changelog.** A changelog lists every change for builders. Release notes pick the changes that matter and explain them for a specific reader.
- **Write about what the reader can now do**, not about what the team built or which ticket closed.
- **AI is good at the first draft**: grouping, rewording and cutting jargon. It is not good at knowing what actually shipped, who is affected, or what you are allowed to say.
- **Always give the AI rules and a "do not invent" instruction**, and have someone who was in the sprint check every line before it publishes.
- **Keep a short version and a long version** so customers, support and internal teams each get what they need from the same source.

## What goes in release notes?

Every release note, whatever the product, answers five questions:

1. What is this release, and when does it apply to me?
2. What can I do now that I could not before?
3. What got better or stopped being broken?
4. What is going away or changing in a way that could surprise me?
5. Do I need to do anything?

The template maps one section to each question. Skip a section when it is empty. Do not write "Nothing this release" under every heading, because it adds noise.

## What does the release notes template look like?

Paste this into your docs tool, wiki, or help center. Text in brackets is what you replace. Section titles are shown in bold here; format them as headings in your own tool.

```
# [Product name] [version number or release name]
Release date: [Month Day, Year]
Audience: [All customers / Admins only / Internal / API users]
Availability: [Available to everyone now / Rolling out over [timeframe] / Enterprise plan only / Behind a feature flag]

**Summary**
[One to two sentences. The single most important thing in this release, in plain words.]

**Highlights**
- [Biggest change 1, written as what the reader can now do]
- [Biggest change 2]
- [Biggest change 3, if there is one]

**New**
### [Feature name]
[What it is in one sentence. Who it is for. How to find it.]
[Optional: link to the help article or a short video.]

### [Feature name]
[Same pattern.]

**Improved**
- [Area]: [What is better, and what the reader will notice.]
- [Area]: [Same pattern.]

**Fixed**
- [What was going wrong, from the reader's point of view, and that it now works.]
- [Same pattern.]

**Changed or deprecated**
- [What is changing, the date it takes effect, and what to use instead.]

**Action required**
[Only if someone must do something. Who, what, and by when. Put this near the top if it is urgent.]

**Known issues**
- [Problem still present, who it affects, workaround if there is one.]

**Questions or feedback**
[Where to go: support link, channel, or contact.]
```

### The internal addendum

Support, sales and customer success often need more than customers do. Add this block for internal readers only:

```
**Internal notes (not for customers)**
- Tickets / PRs: [IDs and links]
- Teams to brief: [Support, Sales, CS, Legal, Docs]
- Feature flags and rollout plan: [Flag name, percent rolled out, owner]
- Customer-facing talking points: [Two or three sentences]
- Likely questions and answers: [Q: ... A: ...]
- Rollback plan: [Owner and trigger]
```

## What's the difference between a changelog and release notes?

A changelog is a complete, chronological record of changes, usually written by or for the people building the product. It includes small fixes, refactors, dependency bumps and internal tickets. Release notes are a selected, rewritten subset aimed at the people using the product.

| | Changelog | Release notes |
|---|---|---|
| Reader | Engineers, QA, release managers | Customers, admins, support, sales |
| Coverage | Everything | What matters to the reader |
| Language | Technical, often terse | Plain, benefit-focused |
| Source of truth? | Yes | No, it is derived from the changelog |
| Example line | "Fix null check in invoice export (#4821)" | "Exporting an invoice with no tax ID no longer fails." |

That derivation step is the part that eats time every sprint, and it is the part AI handles well.

## How do you fill in the template? A worked example

Here is a fictional product, Tallyboard (an invoicing tool), and a raw changelog pulled from a sprint. This is the kind of input most teams actually have: inconsistent, full of ticket numbers, written for engineers.

**Raw changelog:**

```
- TB-2210 Add bulk invoice export to CSV (admin only), behind flag bulk_export, 100% rolled out
- TB-2231 Fix null check in invoice export when tax_id empty
- TB-2244 Refactor PDF renderer to new lib
- TB-2250 Reminders: allow custom send time per customer
- TB-2255 Bump dependency versions
- TB-2262 Fix duplicate email on payment confirmation for card payments
- TB-2270 Deprecate v1 /invoices endpoint, removal planned for March 31
- TB-2275 Dashboard load time improved for accounts with 10k+ invoices
- TB-2281 Known: dark mode logo is wrong color on login page
```

**Step 1: Decide the audience.** This one is for customers, including admins and API users.

**Step 2: Sort each line.** Keep what changes the reader's experience. Drop what does not.

| Ticket | Decision | Why |
|---|---|---|
| TB-2210 | Keep: New | Admins can do something new |
| TB-2231 | Keep: Fixed | Export used to fail |
| TB-2244 | Merge into Improved, or drop | Reader only cares if PDFs look or load different. Ask the engineer. |
| TB-2250 | Keep: New | Reader can control timing |
| TB-2255 | Drop | No reader impact |
| TB-2262 | Keep: Fixed | Customers noticed duplicate emails |
| TB-2270 | Keep: Deprecated, Action required | API users must migrate |
| TB-2275 | Keep: Improved | Large accounts will notice |
| TB-2281 | Keep: Known issues | Visible, cosmetic |

**Step 3: Rewrite each kept line as what the reader can do or what now works.**

**Finished notes:**

```
# Tallyboard 4.12
Release date: March 3
Audience: All customers
Availability: Available to everyone now

**Summary**
Admins can now export invoices in bulk, and you can choose what time payment reminders go out for each customer. This release also ends duplicate payment confirmation emails.

**Highlights**
- Export many invoices to CSV in one step
- Set a custom reminder send time per customer
- Faster dashboard for accounts with large invoice histories

**New**
### Bulk invoice export
Admins can select multiple invoices and export them to a single CSV file. Find it under Invoices > Export.

### Reminder send time per customer
Payment reminders no longer have to go out at the same time for everyone. Open a customer's profile and choose when their reminders are sent.

**Improved**
- Dashboard: Loads faster for accounts with more than 10,000 invoices.

**Fixed**
- Exporting an invoice for a customer with no tax ID no longer fails.
- Customers paying by card no longer receive two payment confirmation emails.

**Changed or deprecated**
- The v1 /invoices API endpoint is deprecated and will be removed on March 31. Use the v2 endpoint instead.

**Action required**
API users: move any integrations that call the v1 /invoices endpoint to v2 before March 31.

**Known issues**
- The logo on the login page shows the wrong color in dark mode. Functionality is not affected.

**Questions or feedback**
Contact support at [link] or post in the community forum.
```

Notice what happened. Ticket numbers are gone. "Refactor PDF renderer" and "Bump dependency versions" did not appear. The deprecation, which is the only item that requires effort from the reader, appears in two places: once as a change and once as an action. In a real release you might move "Action required" above "Highlights" if the deadline is close.

## What AI prompt turns a changelog into release notes?

Paste this into ChatGPT, Claude, Gemini or your company's approved AI tool. Replace the bracketed parts, and paste your changelog and template at the bottom.

```
You are a technical writer preparing release notes for [Product name], version [number], released [date].

AUDIENCE: [Customers / Admins / API users / Internal support team]. They are [non-technical / mixed / technical].

TASK: Turn the raw changelog below into release notes using the template I provide. Follow the template's headings and order exactly. Omit any section that has no content.

RULES:
1. Use only information in the changelog. Do not invent features, benefits, numbers, dates, plan names, or availability. If something is unclear, do not guess.
2. Write each item from the reader's point of view: what they can now do, or what now works. Do not describe how engineers built it.
3. Remove ticket IDs, internal code names, flag names, and library or dependency details from customer-facing text.
4. Drop items with no reader impact (refactors, dependency bumps, internal tooling), but list them at the end under "Omitted items" with a one-line reason each, so I can overrule you.
5. Put anything that requires reader action (deprecations, migrations, setting changes) in "Action required" with the deadline, and also mention it in "Changed or deprecated".
6. Keep the tone plain and neutral. Avoid hype words like "exciting", "powerful", "game-changing". Avoid quantified claims ("50% faster") unless the number is in the changelog.
7. Write the Summary last. It should be one or two sentences covering the most important change.
8. Keep sentences short. Use present tense for new behavior ("Admins can now...") and past tense for fixes only when needed for clarity.

AFTER THE NOTES, add three lists:
- "Questions for the team": every place where the changelog was ambiguous or where you need to know who is affected, how it is rolled out, or what the user-visible effect is.
- "Omitted items": as described above.
- "Claims to verify": every sentence in your draft that states availability, plan restrictions, dates, or performance.

TEMPLATE:
[paste the template]

CHANGELOG:
[paste the raw changelog]
```

Want the internal version too? Add one more line to the prompt: "Then produce a second version for the internal support team using the Internal addendum section, including likely customer questions and short answers, based only on the changelog."

## What should you check in the AI's draft?

The draft will read well. That is the danger: fluent text hides errors. Go through this list before anything publishes.

- **Every claim against the source.** Match each line in the draft to a changelog entry. If a sentence has no source, delete it.
- **Availability.** Does the draft say "available to everyone" when the feature is behind a flag, rolling out gradually, or limited to one plan? AI often defaults to "everyone."
- **Dates.** Release date, deprecation date, removal date. Confirm each with the owner.
- **Who is affected.** "Admins can now..." might be true only for some roles. Check permissions.
- **Where to find it.** Menu paths and button names are easy for AI to guess wrong. Click through the product.
- **Numbers.** If the draft says "faster" with a number you did not supply, cut it. If you supplied one, check it carries the same units and conditions.
- **Omitted items.** Read the AI's list of dropped items. Occasionally a "refactor" quietly changes behavior users will notice.
- **Tone.** Cut anything that sounds like marketing. Release notes earn trust by being accurate and calm.

## Where should you not trust AI with release notes?

Treat these as human-only decisions:

- **Security fixes.** How much to disclose, and when, is a judgment call involving security and legal teams. Do not let a model decide the wording of a vulnerability fix.
- **Commitments.** "We will add X next quarter" in release notes can become a promise. AI will happily write one if the changelog hints at it.
- **Compliance and contractual language.** Anything touching data handling, retention, or regulated features needs review by the right owner.
- **What is actually live.** The model only sees the text you gave it. It cannot check production.
- **Customer-specific impact.** If a change breaks a particular customer's workflow, a person who knows that customer should say so directly.
- **Confidential material.** Check your company's policy before pasting unreleased roadmap or customer data into an AI tool. Use an approved tool, and strip names and internal links you do not need.

## How do you adapt the template for different audiences?

Same source, different cuts. Keep one changelog and produce each version from it.

| Audience | Keep | Change |
|---|---|---|
| Customers | New, Improved, Fixed, Action required | Plain language, no IDs, link to help articles |
| Admins | Add permission changes, settings, rollout dates | More detail on what to configure |
| API and developer users | Add endpoints, parameters, breaking changes, version numbers, code examples | Technical wording is fine; be exact |
| Internal (support, sales, CS) | Add the Internal addendum | Include flags, talking points, and likely questions |
| Executives | Summary and Highlights only | Two or three lines on business impact, no feature detail |

For frequent releases (weekly or continuous), switch to a lighter pattern: a date, a one-line summary, and bullets under New, Improved and Fixed. Save the full template for larger releases, major versions, or anything with a deprecation.

## How long should release notes be?

As short as they can be while answering the five questions at the start. A practical rule: if a reader needs more than two minutes to understand what changed for them, move detail into a linked help article and keep the note to a sentence or two. A single bug fix gets one line. A significant new feature gets a short paragraph and a link.

Habits that keep notes useful:

- Lead each bullet with the thing the reader recognizes (the feature or screen name), not with a verb like "Updated" or "Improved".
- Use the same names the product's interface uses. If the button says "Export," do not write "Download."
- Put the date on every release so readers can tell what is current.
- Link to the previous notes and to a full archive.
- Never delete old notes. People search them to find out when something changed.

## Can you build your own release notes tool?

If your team keeps assembling release notes from a spreadsheet, a ticket export and a shared doc, you could describe a small app that does it instead. For example: a form where engineers log each change with an audience tag and a "customer-visible" checkbox, a review queue for the PM, and a public release notes page that publishes when approved. With [Remy](https://goremy.ai), you describe that in plain English and it builds the full-stack app, with a database, sign-in and hosting included, and a typical initial build takes about an hour. Remy apps can also send email from your own domain, so subscribers could get each release by email. You own the code, so it is not another subscription you rent.

## Frequently Asked Questions

### What is the best format for release notes?

Group changes under consistent headings such as New, Improved, Fixed, and Changed or deprecated, and open with a one or two sentence summary. Put anything requiring action near the top. Use short bullets for small changes and a short paragraph for major features.

### Should release notes include bug fixes?

Yes, when the bug was visible to users. Describe the fix from the user's side, such as "Exporting an invoice with no tax ID no longer fails," rather than the technical cause. Leave out internal fixes that nobody outside the team would notice.

### Can AI write release notes on its own?

AI can produce a solid first draft from a changelog, especially for grouping, rewording and trimming jargon. It cannot verify what shipped, who is affected, or what you are permitted to say. Give it clear rules, tell it not to invent details, and have someone who was in the sprint review every line.

### Who should own release notes: product, engineering or a tech writer?

It varies by company, but one named owner per release works best. Product managers or technical writers usually draft, engineers confirm accuracy, and support reviews for customer impact. Whoever owns them, agree on the template so the output stays consistent.

### How often should you publish release notes?

Publish with each release that changes what users see. Teams shipping continuously often batch small changes into a weekly or biweekly post and reserve a dedicated note for major features, deprecations, or anything that needs user action.
