Release document template for SaaS release notes
Give customers a clear account of what changed, who can use it, and what they need to do next. Copy this release document template into your team's publishing process.
This page covers software release notes. If you need a press release for media coverage, use a press release format with a news angle and media contact instead.
Copy the template
Release: [name or version]
Released: [date]
Availability: [plans, regions, rollout stage]
Summary:
[What changed and which customer problem it addresses.]
New features:
- [Feature]: [customer benefit and how to access it]
Improvements:
- [Existing behavior]: [what is different]
Fixes:
- [Affected behavior]: [what now works as expected]
Required actions:
- [Action, affected users, deadline, and support reference]
- [Or explicitly state that no action is required]
Known issues:
- [Issue, affected users, workaround, and tracking reference]
Deprecations or breaking changes:
- [Change, migration steps, timeline, and owner]
Documentation and support:
[Relevant links]
Delete empty sections. Preserve required actions and availability when they change whether someone can use the release.
A worked example
The following release is fictional.
Release: Reporting export update
Availability: Pilot workspaces only
Summary: Workspace members with export permission can download the reporting period they are viewing as a CSV.
New feature: Select a reporting period and choose Export CSV. Existing record permissions apply to the exported data.
Known issue: Empty reporting periods do not generate a file; the interface explains that no records match.
Required action: No action is required for existing reports. Administrators should confirm which workspace roles have export permission before inviting pilot users to test.
Notice the boundaries. The note does not imply that every customer has access or that scheduled exports are available.
Choose the right format
Single feature: Lead with the customer outcome, explain access, and include one useful example.
Weekly release: Group changes into features, improvements, fixes, and known issues. Keep each entry independently understandable.
Technical change: Put migration requirements and breaking changes near the top. Include the affected versions and links to implementation guidance.
Internal release: Add owners, rollout status, verification results, and the support handoff. Keep operational details separate from the customer message.
Draft with AI from shipped changes
Write customer-facing release notes from the supplied approved changes.
Use the release template above.
Preserve availability, limitations, and required actions.
Translate internal ticket language into customer outcomes.
Do not describe proposed features as shipped.
Do not invent metrics, dates, documentation links, or performance claims.
Flag missing facts for the release owner to confirm.
Use the release notes writer for a reusable starting point. Review the draft against the release record before publishing.
Verify the note before it goes live
Check that the described behavior is available to the stated audience. Confirm migration instructions with engineering, support guidance with the relevant owner, and any measurable claims against their source.
A release note can be brief. Missing a required customer action is more consequential than leaving out a minor improvement.
Frequently asked questions
What is a good format for release notes?
Start with the release and availability, then explain customer-visible changes, required actions, known issues, and supporting documentation. Choose sections that match the release.
How do I write release notes?
Review approved shipped changes, identify their customer impact, write plain-language entries, and verify availability and limitations before publishing.
Can AI create a release template?
Yes. AI can draft the structure and rewrite supplied changes. You must confirm that the content accurately describes the released product.
Is a release document the same as a release plan?
No. A release plan coordinates scope, owners, readiness, and rollout before release. Release notes explain the changes to their audience. Use the agile release plan template for planning.
References: The Good Docs Project's release notes guidance, Documentero's template, and Frill's release formats.